OpenVMS requirements

Supported platforms

Synergy/DE 10.3.3 is supported on the following HP and VSI OpenVMS platforms.


System code



HP Alpha






where version is the OpenVMS version and #### indicates the version of the patch. You should install the most recent version of the patch available for your version of OpenVMS.

For example, for OpenVMS 8.4, the patches might be VMS84_ACRTL‑V0600, VMS84_RMS‑V0400, and VMS84_UPDATE‑V0300.

HP I64


8.3 or highera

Download and install the most recent version of the C++ runtime patch VMSversion_ICXXL‑V####, where version is the OpenVMS version and #### indicates the version of the patch, for example, VMS83I_ICXXL‑V0500. You will not be able to install Synergy/DE without first installing this patch!

VSI Alpha 200 8.4-2L1 or higher N/A

VSI Integrity


8.4‑1H1 or highera


a. Version 8.4 (HP) or 8.4‑2L (VSI) or higher is required for SSL1 compatibility. See OpenSSL requirements for more information. Because Connectivity Series supports only SSL1, version 8.4 (HP) or 8.4‑2L (VSI) or higher is required for encryption support with Connectivity Series.


The OpenVMS patches listed in the table above are available for download from the Hewlett‑Packard website. To find the most recent version of a patch, do a partial search on the patch name (e.g., search on VMS84_ACRTL).

TCP/IP (Alpha)

TCP/IP version 5.0a ECO2 or higher is required on OpenVMS Alpha. We recommend using the most recent version of TCP/IP available for your version of OpenVMS.

To check the TCP/IP version on your machine, execute this command:

$ tcpip show version

Sample output:

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 5 
on a AlphaServer DS10 617 MHz running OpenVMS V7.3-2 

If you’re having problems resolving an IP address in a subnet, install the most recent ECO (patch) for your version of TCP/IP. These patches are available on the Hewlett‑Packard website. For example, for TCP/IP version 5.4, the most recent is ECO 7, which is named DEC‑AXPVMS‑TCPIP‑V0504‑15ECO7‑1.

Environment setup

In a default installation, you must ensure that the system start‑up command procedure invokes SYS$MANAGER:SYNERGY_STARTUP.COM to set up the environment each time the system starts up.

In an alternate installation, you must run the command file DBLDIR:ACTIVATE_SDE.COM manually every time you log on to set up the environment.


The OpenVMS License Management Facility is used to license Synergy/DE on OpenVMS instead of Synergy/DE License Manager. The runtime supports cluster‑wide licensing. Synergy/DE 10 license PAKs must be installed and loaded before installing Synergy/DE. To obtain Synergy/DE PAKs, complete and return the Synergy/DE Product License Agreement. For more information about PAKs, see the OpenVMS License Management Utility Manual or your system administrator.


The Synergy/DE compiler is designed to take advantage of memory to increase performance. If your development machine has less than 64 MB of memory, we recommend that instead of dbl, you use the compiler distributed as dbl8. (See The dbl8 compiler for details on using dbl8.)

For maximum performance and to avoid “exceeded quota” errors, you must ensure that the account quotas for developers using the new compiler are set correctly. We recommend the following account quotas in the Authorize utility:

Authorize parameter





2,000 or higher


500 or higher


200,000 or higher


64,000 to 120,000


32,000 up to the value of WSEXTENT

a. To use the Synergy Prototype utility (dblproto) on large files (especially if they contain many import statements and .INCLUDE directives), you may need to increase the BYTLM value.

b. When setting FILLM, verify that the CHANNELCNT SYSGEN parameter is higher than the FILLM value.