HP OpenVMS Systems Documentation

After you have made all your selections, the procedure displays a summary of your changes:

         Summary of Configuration

 Node Information:
        Directory Services Chosen:      DECDNS,LOCAL,DOMAIN
        Primary directory service:      DECDNS
        DECdns full name:       PHASEV:.ENG.SSG.TEST.ELMER
        Local Full name:        LOCAL:.ELMER
        Fully Qualified
        Host name:              ELMER.WABBIT.ACME.EDU
        Node Synonym:           ELMER
        Phase IV Address:       15.27
        Phase IV Prefix:        49::
        Autoconfiguration of Network Address: Enabled
        Session Control Address Update Interval:      10
        Routing ESHello Timer:  600

        Alias Name:     ACME:.WABBIT.HELP

 Device Information:

        Device: XQA0 (DELQA):

 Data Link name: CSMACD-0
                Routing Circuit Name:   CSMACD-0
                .           .
                .           .
                .           .

At the end of the summary, the procedure asks if you want to generate NCL configuration scripts (which now contain your updated information):

* Do you want to generate NCL configuration scripts?   [YES] :

If you answer YES, the configuration program uses the information you entered to create the alias NCL script. The configuration program then returns to the Configuration Options menu. To implement the alias NCL script, reboot the system or disable the entity and execute the script.

If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate any NCL scripts.

Part II describes the steps necessary to configure VAX P.S.I. and VAX P.S.I Access on a DECnet-Plus for OpenVMS VAX system.

This chapter describes how to configure the VAX P.S.I. and VAX P.S.I. Access software.

4.1 Steps in Configuring VAX P.S.I.

See Figure 4-1 and take the following steps to configure your VAX P.S.I. system:

1. Plan your configuration (see the DECnet-Plus Planning Guide and Section 4.2).
2. Make a note of the information you need during the configuration program, using Section 4.3.
3. Run the configuration program (see Section 4.4).
4. Run the net$configure procedure (in either BASIC or ADVANCED mode) to configure your network.
5. Carry out the postconfiguration tasks: starting VAX P.S.I. and testing your configuration (see Section 4.5).

This section introduces the aspects of your proposed configuration that you need to consider before you run the configuration program.

4.2.1 Configuring Access, Native, and Multihost Systems

There are three types of VAX P.S.I. systems:

• Access
• Native
• Multihost

Refer to the DECnet-Plus Planning Guide for an explanation of VAX P.S.I. systems.

The type(s) you can configure depends on the license(s) that you have installed. Table 4-1 summarizes the various possible configurations.

Figure 4-1 Installation and Configuration Flowchart

The VAX P.S.I. configuration program has many sections, but not all sections are relevant to all types of systems. Table 4-2 shows the sections that apply to each type of system.

The VAX P.S.I. configuration program automatically skips sections that do not apply to your type of system.

4.2.3 Sections in the VAX P.S.I. Configuration Program

This section explains the purpose of each section in the P.S.I. configuration program.

Lines and DTEs

Choose a line on your system to configure for X.25 communications. You must configure at least one synchronous line unless you intend to use LLC2 exclusively.

PVCs

Your DTE can communicate with a remote DTE using either an SVC (switched virtual circuit) or a PVC (permanent virtual circuit). A PVC is a permanent association between two specific DTEs.

Two DTEs connected by a PVC can communicate without the need for call clearing or call setup.

Complete this section if you have requested this facility from your PSDN.

Groups

If your DTE belongs to a closed user group (CUG), it can communicate freely with remote DTEs that are also members of that CUG. Its communications with other DTEs may be restricted, depending on your PSDN subscription options.

You must complete this section if you have requested this facility from your PSDN.

LLC2

LLC2 is a data link protocol used on LANs, over which the X.25 Packet-Level Protocol (PLP) is run.

You must set up an LLC2 DTE for each remote system to which you want to connect on the LAN. You can set up one or more LLC2 DTEs per LAN connection.

Remote DTE Classes

Use this section to specify the connector system(s) that your Access system uses.

X.29 and P.S.I. Mail

This section allows you to add support for X.29 communications and for P.S.I. Mail.

You need X.29 support if your VAX P.S.I. system is to communicate with character-mode terminals.

P.S.I. Mail is an extension of OpenVMS Mail that lets you send mail messages to and receive them from other VAX P.S.I. systems across a PSDN.

Gateway Clients

You must create gateway clients to allow your multihost system to pass incoming calls to the correct client system. A gateway client identifies a client system or group of client systems that use this multihost system to receive incoming calls.

In this section, you also set up filter(s) for gateway clients. You must set up at least one filter for each gateway client. See filters for more about filters.

Filters

Filters are sets of characteristics that can be matched to fields in an incoming call request packet. If the characteristics in an incoming call match the characteristics you set in a filter, then the call is passed to the gateway client or the application associated with that filter.

You must supply a filter name and a priority for each filter. You may leave all the other parameters unspecified.

The more parameters you specify in a filter, the more specific is that filter. For example, you could create a filter with most of its parameters unspecified and with a low priority to act as a "catchall" for unexpected calls.

Applications

You must specify any X.25 or X.29 applications on your system to allow incoming calls for those applications to succeed.

You must supply the name of the command file that starts the application. You may also supply a user name for the application.

Do not specify any applications that do not receive calls.

In this section, you also set up filter(s) for applications. You must set up at least one filter for each application. See filters for more about filters.

Declaring a Network Process

X.25 and X.29 programs on your system can issue $QIO(IO$_ACPCONTROL) calls to declare themselves as network processes. Each
$QIO(IO$_ACPCONTROL) specifies a filter used to determine which calls are able to access the program.

The filter specified by $QIO(IO$_ACPCONTROL) can be one of two types:

• Static
  In this case, $QIO(IO$_ACPCONTROL) names a filter that already exists on your system. Complete this section if you want to create static filters for use by $QIO(IO$_ACPCONTROL).
• Dynamic
  In this case, the filter characteristics are specified in the $QIO(IO$_ACPCONTROL) call. The filter created in this way by the $QIO(IO$_ACPCONTROL) call ceases to exist when the program exits. Complete this section if you want to name the dynamic filters created by $QIO(IO$_ACPCONTROL).

If your programs issue only $QIO(IO$_ACPCONTROL) calls that use unnamed dynamic filters, you do not need to complete this section.

Templates

Your system uses a template to make outgoing calls. A template sets various parameters for each call made using that template.

A template called "default" is created automatically on your system.

Security

Set up security to prevent unauthorized use of your VAX P.S.I. system. There are six security sections:

• X.25 Security
  This allows you to choose whether to set up X.25 security. If you do not set up X.25 security, any remote DTE can make a call to your system (provided it matches one of your filters), and any user on your system can make outgoing calls to any remote DTE. If you choose not to set up X.25 security, you do not see the following five security sections.
• Incoming Security for Applications
  You see this section only if you have an Access, Native, or Multihost system on which you have set up applications.
  Complete this section if you want your applications to be able to receive calls from remote systems.
• Outgoing Security for Local Processes
  Complete this section if you want users on your system to be able to make calls to remote systems.
• Incoming Security for Network Processes
  Complete this section if you have X.25 or X.29 programs that issue $QIO(IO$_ACPCONTROL) calls to declare themselves as network processes.
• Incoming Security for Gateway Clients
  You see this section only if you have a Multihost system on which you have set up gateway clients.
  Complete this section if you want your system to be able to pass incoming calls to client systems.
• Outgoing Security for Accessing Systems
  You see this section only if you have a Multihost system.
  Complete this section if you want your system to be able to make outgoing calls on behalf of client systems.

NCL Script

When you are satisfied that all the information you entered is complete and correct, the configuration program creates two NCL scripts using the information you provided.

When the NCL scripts have been created, you are asked if you want to run a command file called psi$security_identifiers.com.

This file is created by the configuration program to add certain rights identifiers to the system rights database on your system. The rights to be added depend on the security information you have supplied.

You can run the command file from within the configuration procedure, or you can exit from the configuration program and run the command file later. Note that you cannot start VAX P.S.I. until you have run this command file. This is true even if you have selected not to set up X.25 security for your system.

If you edit the command procedure before running it, you must make corresponding changes to the NCL scripts before attempting to start VAX P.S.I.

4.3 Recording the Information You Need for VAX P.S.I. Configuration

This section details the information you need to provide during the configuration program.

Tables 4-3 to 4-18 list all the information required during the configuration.

Table 4-3 lists the information you need to complete the lines and DTEs section of the configuration program.

Table 4-4 lists the information you need to complete the PVCs section of the configuration program.

Table 4-5 lists the information you need to complete the Groups section of the configuration program.

Table 4-6 lists the information you need to complete the LLC2 section of the configuration program.