This guide is intended for OpenVMS system managers who need to configure and manage MultiNet.

To configure TCP/IP Services for DECnet Applications (formerly known as Phase/IP), refer to the TCP/IP Services for DECnet Applications Guide section of the MultiNet Message, Logicals, and DECnet Applications book in this MultiNet documentation set.

For information about basic TCP/IP concepts, see the Installation and Introduction section of this guide.

Obtaining Technical Support

Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained MultiNet from an authorized distributor or partner, you receive your technical support directly from them.

You can contact Technical Support by sending electronic mail or calling the Technical Support center.

Before Contacting Technical Support

Before you call or send e-mail please verify that your Maintenance Service Agreement is current, and have the following information available:

         Your name

         Your company name

         Your e-mail address

         Your telephone number

         Your Maintenance Agreement Number

         OpenVMS architecture and version

         MultiNet version

Have complete information about your configuration, error messages that appeared, and problem specifics.

Be prepared to let an engineer connect to your system either with TELNET or SSH. Be prepared to give the engineer access to a privileged account to diagnose your problem.

You can obtain information about your OpenVMS architecture, OpenVMS version, and MultiNet version with the MULTINET SHOW /LICENSE command. For example:


Process Software MultiNet V5.6, VAXstation 4000-90, OpenVMS VAX V7.1

In this example:

         The machine or system architecture is VAX.

         The OpenVMS version is V7.1.

         The MultiNet version is V5.6

Sending Electronic Mail

For most questions, electronic mail is the preferred communications method. Technical support via electronic mail is available to customers with a current support contract. Send electronic mail to

At the beginning of your mail message, include the information listed in the section Before Contacting Technical Support. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request.

Electronic mail is answered Monday through Friday from 9:00 a.m. to 5:00 p.m. United States Eastern Time.

Calling Technical Support

For regular support issues, call 800-394-8700 or 508-628-5074 for support Monday through Friday from 9:00 a.m. to 5:00 p.m. United States Eastern Time.

For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your account representative for further details.

Before calling, have available the information described in the section Before Contacting Technical Support. When you call, you will be connected to a Technical Support Specialist.

Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system.

If a Specialist is not immediately available, your call will be returned as soon as possible.


Obtaining Online Help

Extensive information about MultiNet is provided in the MultiNet help library. For more information, use the following command:


MultiNet Frequently Asked Questions List

You can obtain an updated list of frequently asked questions (FAQs) and answers about MultiNet products from the Process Software home page located at

Accessing the MultiNet Public Mailing List

Process Software maintains two public mailing lists for MultiNet customers.

The mailing list is a forum for discussion among MultiNet system managers and programmers. Questions and problems regarding MultiNet can be posted for a response by any of the subscribers. To subscribe to Info-MultiNet, send a mail message with the word SUBSCRIBE in the body to

The mailing list is a one-way communication (from Process Software to you) used for the posting of announcements relating to MultiNet (patch releases, product releases, etc.). To subscribe to MultiNet-Announce, send a mail message with the word SUBSCRIBE in the body to



Obtaining Software Patches Over the Internet

Process Software provides software patches in save set and ZIP format on its anonymous FTP server, For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches.

To retrieve a software patch, enter the following commands:


A message welcoming you to the Process Software FTP directory appears next followed by the FTP prompt. Enter the following at the prompts:

GET update_filename

         emailaddress is your e-mail address in the standard user@host format.

         nnn is the version of MultiNet you want to transfer.

         update_filename is the name of the file you want to transfer.

To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an intermediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system.

In addition, if you are fetching the software patch in save set format, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS system:

         If you use the GET command to download the file from the intermediate system, use the FTP RECORD-SIZE 2048 command before transferring the file.

         If you use the PUT command to upload the file to your OpenVMS system, log into the intermediate system and use the FTP quote site rms recsize 2048 command before transferring the file.

The following example shows how to use the UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory.

UNZIP filename.ZIP

Use VMSINSTALL to upgrade your MultiNet system with the software patch.


Typographical Conventions

Examples in this guide use the following conventions:




Any computer system on the network. The local host is your computer. A remote host is any other computer.

monospaced type

System output or user input. User input is in reversed bold type.

Example: Is this configuration correct? YES


Monospaced type also indicates user input where the case of the entry should be preserved.

italic type

Variable value in commands and examples. For example, username indicates that you must substitute your actual username. Italic text also identifies documentation references.


Directory name in an OpenVMS file specification. Include the brackets in the specification.


(Italicized text and square brackets) Enclosed information is optional. Do not include the brackets when entering the information.

Example: START/IP line address [info]

This command indicates that the info parameter is optional.

{value | value}

Denotes that you should use only one of the given values. Do not include the braces or vertical bars when entering the value.


Information that follows is particularly noteworthy.


Information that follows is critical in preventing a system interruption or security breach.


Press the specified key on your keyboard.


Press the control key and the other specified key simultaneously.


Press the Return or Enter key on your keyboard.