Kednos Corporation, makes no representations that the use of its
products in the manner described in this publication will not infringe
on existing or future patent rights, nor do the descriptions contained
in this publication imply the granting of licenses to make, use, or
sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this
publication is authorized only pursuant to a valid written license from
Kednos Corporation or an anthorized sublicensor.

No responsibility is assumed for the use or reliability of software on
equipment that is not listed as supported in the Product Description.

This document contains release information on Kednos Native IPF PL/I
Run-time Library for Translated Images Version 4.5-B. Release
information is necessary for gaining the best results from Kednos PL/I
Version 4.5-B on the HP OpenVMS for Integrity Servers operating system.
Kednos recommends that all users read this information.

Version 4.5-B is the first release of the Kednos Native IPF PL/I
Run-time Library for Translated Images. It provides on Itanium VMS
interface routines that are call-compatible to the Kednos PL/I Runtime
Library on Alpha VMS.

Versions V1.0 and V2.0 of AEST$MAIN.EXE from HP (product name HP
OpenVMS Migration Software for Alpha to Integrity Server) fail with an
error message when translating an Alpha image that contains PL/I code.
This can be avoided by patching AEST$MAIN.EXE using the command
procedure SYS$UPDATE:DPLI$PATCH_AEST.COM placed on your Itanium machine
by the installation of the PLI_RTL_AV kit.

If your operational plan calls for translating Alpha images on Alpha
and then moving the resulting Itanium images over from Alpha, you can
move SYS$UPDATE:DPLI$PATCH_AEST.COM to Alpha and run it there.

An MSAI release after V2.0 may eliminate this need to patch
AEST$MAIN.EXE in order to translate images containing PL/I code.

Up through Itanium VMS V8.3-1, programs that call FDLSHR and are
translated with AEST fail to find the image FDLSHR_AV. As it turns out
the native FDLSHR.EXE image on Itanium is adequate, so you can use a
site-specific systemwide logical name in the startup command procedure:

$ DEFINE/SYSTEM/EXECUTIVE_MODE FDLSHR_AV FDLSHR

It is possible that a release of Itanium VMS after V8.3-1 will include
this definition automatically, at which point a site definition in the
startup command procedure will be superfluous but harmless.

On Alpha and Itanium VMS emulates the VAX floating point types, but
those emulations are different and certain programs may get slightly
different floating point results on the two architectures. The
difference is discussed by HP in detail at:

If you have translated PLI programs that you install with privilege,
you will need to Install the RTL image:

$ INSTALL ADD SYS$SHARE:DPLI$RTLSHR_AV.EXE

Be sure to make that change to your site specific startup command
procedure, and also issue it interactively on all systems sharing a
common system disk (to ensure it is installed until the next reboot
invokes the site specific startup command procedure.

If you have particular performance needs, you may want additional
site-specific qualifiers on that INSTALL command.

If you encounter problems with the VMS Translated Image Environment
(TIE) you should report them to HP. However Kednos would appreciate
also hearing from you about any TIE issues that affect PL/I programs.