OpenVMS Installation Requirements

Operating System

OpenVMS For IA64 (Integrity) 8.4 or Higher

The Information Builders Technical Support web site maintains a current list of supported operating systems and levels.

Disk Space

Space for installation

Space after installation

8.4

1,100,000 blocks

IP Ports

Up to six consecutive IP ports (two in reserve for typical extra features).

The supplied IP port numbers must be above the IANA registered well-known reserve range (numbers under 1024) and not over the maximum legal number (65535). Additionally, do not use IP port numbers already being used by other applications or products. Netstat, or netstat like commands, should reveal what actual ports are in use.

Additional Java Listeners (post install option) require additional ports (beyond basic reserve).

Java

The Java Listener requires a 1.8 (or higher) JVM for full functionality.

A 64-bit version of java 1.8 is available for OpenVMS. However, this Java version is not compatible with the Server at this time, as it is a 32-bit build.

While Java 1.6 is available in 32-bit, the Java Listener will fail to start if 1.6 is used, and edaprint will display fail to load warning messages, and use of Java-based features in an application will fail. You can allow this to fail as an expected known behavior.

If an OpenVMS Java 32-bit JVM is released at some point in the future, it can be installed with applicable logicals set, and the Java Listener should then start on server startup with no need for a server software update.

If you want to bypass the Java Listener startup failure so it does not display in edaprint, edit the odin.cfg file and remove (or comment out) the JSS block.

See General Information for an OpenVMS Installation for listener configuration information.

Memory

Memory use depends on the following factors.

• Workspace Manager
• Listeners
• Concurrently running application agents

Actual memory usage varies depending on the features used by the application, and will increase or decrease as agents change between active and idle states.

The Workspace Manager makes use of a specific system resource known as shared memory. Each individually configured server, with or without adapters, uses one shared memory. The size of this memory varies based upon the sizes of the agents table and the queue.

Generally, shared memory use does not require special configuration. It is just a resource that system administrators like to know is being used so they can monitor it with the SHOW MEMORY/POOLED command (non-paged section).

Web Browser

Needed for using the Web Console.

Microsoft Internet Explorer® 11 or higher.

Microsoft Edge

Mozilla Firefox® 59 or higher.

Google Chrome® 65 or higher.