OpenVMS system integration

You can adjust your OpenVMS system to obtain greater benefits from the use of the DS CLI application. The hints and tips that are provided in this section show how to obtain these benefits through the optimal integration of the DS CLI into your OpenVMS system.

The following list provides the areas that you might consider for optimizing the use of the DS CLI in your OpenVMS system:

• Command Console LUN (CCL)
• OpenVMS system messages
• Message help
• Java Run Time Environment (JRE)
• Quota recommendations

• Enhancing the command console LUN for DS CLI use
  The OpenVMS operating system considers a fibre-channel device with LUN ID 0 as Command Console LUN (CCL). These devices do not normally display when you issue the DS CLI lshostvol command. However, with adjustments, these devices can be displayed when you issue the lshostvol command. The following description provides the information that you need to make this enhancement work on your OpenVMS system.
• Enhancing the OpenVMS system messages
  When you use the DS CLI, the application provides messages regarding the application processes, status, and errors. You also receive the OpenVMS system messages but they are displayed in a different format. You can make this situation less confusing by making the following adjustments.
• Enabling OpenVMS to use the DS CLI help
  The DS CLI installation process offers the option to add modules to the system help library. If you enable OpenVMS with this option, you can use the DS CLI help.
• Java Runtime Environment considerations for DS CLI
  The DS CLI login procedure IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM defines JAVA$CLASSPATH in the OpenVMS process logical name table and it overrides any existing Java classpath definition. If you want to use other Java-based software in the same process, you must redefine JAVA$CLASSPATH so that it provides the classpath as a JAVA command parameter.
• Quota considerations for DS CLI
  The JRE was designed to perform optimally on UNIX systems, where each process is given large quotas by default. On OpenVMS, the default behavior gives each process lower quotas so that many processes can co-exist on a system.