After installing X.25 for OpenVMS it must be configured specifically for your system. X.25 for OpenVMS provides a configuration program that enables you to define configuration parameter values specific to your system. The program generates a script containing the Network Control Language (NCL) commands necessary to set up your X.25 configuration. When invoked, the X.25 startup procedure (X25$STARTUP.COM) executes the NCL script.

An NCL script is a series of NCL commands, each of which relates to a specific aspect of configuration. To make each script more readable, the NCL commands are interspersed with comments that indicate what actions the subsequent NCL commands perform. Two example NCL scripts are shown in Appendix C, Example Configurations.

To allow flexibility, configurations need to be modified on either a temporary or permanent basis.

X.25 for OpenVMS provides a number of methods to modify an existing configuration. These methods are detailed in Chapter 10, Modifying the Configuration.

A comprehensive Help facility is available in both BASIC and ADVANCED mode and can be used if further information is required while running the configuration program. Full details of the help facility available in each mode are given in Chapter 2, Using the Configuration Program.

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

This chapter explains how to invoke the VSI X.25 for OpenVMS configuration program and provides details on the facilities and keys that are available to help you to complete the configuration.

In both cases, you are then prompted whether to load the WANDD management software and the auto–configurable synchronous devices.

If you select to load the auto–configurable synchronous devices, you are further prompted whether to configure the built–in serial port as a synchronous device.

An example showing these prompts and example responses is given below.

$ @sys$startup:x25$configure
  Configuring WANDD... [’?’ for HELP]
%WANDD$CONFIGURE-I-WANDDNOTCONFIG, WANDD has not been configured.
Configure WANDD? [YES] Return
Load WANDD? [YES] Return
  All installed synchronous devices will be automatically
  configured. However, the built--in serial port will only
  be configured at your request.
Configure built-in serial port as synchronous? [YES] Return
! SYS$STARTUP:WANDD$CONFIG.DAT
! Created by SYSTEM on 10-FEB-1994 14:28:09.02
!
load_wandd     YES
load_zrdriver  YES
!
! End of SYS$STARTUP:WANDD$CONFIG.DAT
Are you satisfied with your answers? [YES] Return
%NET-I-LOADED, executive image X25$KERNEL_RTL.EXE loaded
%NET-I-LOADED, executive image X25$MEL.EXE loaded
%NET-I-LOADED, executive image X25$L2.EXE loaded
%NET-I-LOADED, executive image X25$L1.EXE loaded
%SYSMAN-I-OUTPUT, command execution on node SPTENZ
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-PREFIX, searching for ICBM with prefix X25$
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0
%RUN-S-PROC_ID, identification of created process is 00000092
  Available Synchronous Communication Ports:
    1. ZRA0 - SSCC-0-0
 Press RETURN to continue...

Once WANDD$CONFIGURE has been run, the initial screen of the X.25 configuration program is displayed.

The configuration program consists of a number of sections, each corresponding to a logical group of information.

Most sections are optional, that is you do not have to enter information unless you want to. Such sections begin with a question in the form: Do you want to set up X?

If you respond “Yes” to the prompt, the rest of that section is presented to allow you to complete it. If you respond “No” to the prompt, the next new section is presented. You can decide at a later stage to complete any section that you bypass (refer to Section 2.3.5, “Accessing the Options Menu”).

Each section commences with a screen of introductory information and is followed by one or more screens on which you can enter data. Each data entry screen contains one or more fields in which you can enter data. Some fields are mandatory, others are optional.

$ SET TERMINAL/DEVICE=terminal-type

Continue to a new section
Add a Remote DTE Class
Modify a Remote DTE Class
Delete a Remote DTE Class
Go to Sections Menu

You can get help at any time during the program by pressing the Help key. The level of help you receive depends on where the cursor is positioned when you press the Help key. Subsections Section 2.4.1, “Obtaining Help on a Specific Field or Menu Choice”, Section 2.4.2, “Obtaining General Help”, and Section 2.4.3, “Obtaining Help on the Program” detail each level of help.

The final section in the configuration program, NCL Script, allows you to initiate the generation of the relevant NCL script for the configuration file from the information held in the configuration database.

Do you want to modify your answers?

To create the NCL script, enter NO in response to the prompt.

If you want to return to any of the completed sections and modify the existing data before creating the NCL script, enter YES in response to the prompt. The Sections Menu is redisplayed.

To quit from the configuration program without generating an NCL script, refer to Section 2.6, “Quitting from the Configuration Program”.

During the creation of the NCL script a number of messages are displayed on the screen and a number of system files are created:

SYS$SYSTEM:X25$SECURITY_IDENTIFIERS.COM

SYS$SYSTEM:MODPARAMS.DAT

SYS$STARTUP:X25$SESSION_STARTUP.COM

SYS$STARTUP:X25$APPL_STARTUP.COM

SYS$STARTUP:X25$MAIL_SETUP.COM

Finally, the Main Menu is redisplayed to allow you to exit the configuration program.

If, for some reason, the program cannot create the NCL script, an error message is displayed at the foot of the screen. This may occur if, for example, a file cannot be created due to incorrect permissions. You must correct the problem before making a further attempt to create the NCL script.

Once the configuration program has created the configuration file containing the NCL scripts, the Main Menu is redisplayed.

To leave the configuration program, select the option “Exit this program”.

The BASIC mode of the configuration program allows you to configure a working X.25 system without needing to have any knowledge of the X.25 management entities and the relationship between such entities.

To use the BASIC mode, you only need to have a knowledge of the network components of your system and a basic knowledge of X.25. If you are new to X.25 and you have not already done so, you are encouraged to read the VSI DECnet-Plus for OpenVMS Introduction and User's Guide before using the configuration program.

You do not need to complete each of the available sections; you only need to complete the sections relevant to the configuration that you want to set up. For example, you might only want to configure the X.25 Connection as an X.25 Client and configure security. Note that only one of the subsections in the first section can be completed.

The data required to complete a configuration depends on the sections to be completed. Details explaining the purpose of each section are given in Section 3.3, “Configuration Sections” and full details about the data required to complete each section are given in Chapter 4, Required Configuration Data.

X.25 Connection

PVCs

This section allows you to define one or more Permanent Virtual Circuits (PVCs). Your PSDN subscription will determine whether you are permitted to set up any PVCs. For each PVC you name you must specify a channel number.

This section is not presented if you configure your system as an X.25 Client.

Incoming Call Security

If restricted incoming access is selected, you must enter remote DTE addresses for each remote DTE that needs to make an incoming call. The remote DTE addresses must be categorized and entered in one of two Access Level categories: Remote Charge or All.

X.29 Support

This section allows you to configure X.29 support on your system so that remote users can access the local system via an X.25 network and local users can access a remote system via an X.25 network. If required, you can specify a Network User Identity (NUI) to identify the party that is to pay for each outgoing call.

X.25 Mail

This section allows you to include X.25 Mail support on your system so that users can send mail to, and receive mail from, other systems that implement the Mail-11 protocol over X.25.

This chapter details the information you will need to provide while running the configuration program in BASIC mode.

Tables 4.1 to 4.6 list all the information you willrequire during the configuration. You should write down the configuration parameter values specific to your system in Appendix A, Values Specific to Your Configuration (which provides a series of blank forms) and refer to that Appendix when you run the configuration program.

Figure 5.1, “Introduction” illustrates the Introduction Section.

The Introduction Section provides you with options to create a new X.25 for OpenVMS configuration, modify an existing configuration, or exit from the program. These options are detailed more fully in subsections 5.1.1, 5.1.2, and 5.1.3 respectively.

This section allows you to enter details about an X.25 network to which your system is attached. You must provide information associated with the DTE connected to the named network. It is assumed that the system is to be attached to a public or private network and will have a DTE connected to the specified network.

Figure 5.2, “X.25 over Wide Area Network Section” illustrates the X.25 over Wide Area Network Section.

Profile Name

An X.25 profile is a set of parameters that indicate to X.25 for OpenVMS the correct operating procedures for a particular network. The profile name defines a specific profile. The valid profiles are given in the help text for this prompt. Typically, the profile name corresponds to the name of the PSDN.

X.25 Address

The X.25 address is the X.25 DTE address assigned by the PTT when the network connection to a Packet Switched Data Network (PSDN)is purchased. An X.25 address is a series of numeric digits similar to a telephone number.

Synchronous Line

The synchronous line indicates which of the available synchronous communications devices supported by this host can be used by the specified DTE for its connection to a PSDN. Select one of the available lines.

Incoming Logical Channel Range

{[start-of-range .. end-of-range]}

Outgoing Logical Channel Range

The outgoing logical channel number range specifies what channel numbers can be used by X.25 for OpenVMS when an outgoing call request is made. This information is supplied by the PTT authority when the DTE subscription is made.

Enter the channel range in the same format as the incoming channel range. For example, to enter the range 1 to 4095, enter {[1..4095]}. See Note under Incoming Logical Channel Range.

This section allows you to enter details about each of the LAN–based X.25 remote hosts you want to access from this system. For each LAN remote host you name, you must provide information on the DTE that is connected to the LAN.

Figure 5.3, “X.25 over Local Area Network Section” illustrates the X.25 over Local Area Network Section.

LAN Device Name

The LAN device name indicates which of the available LAN connections the LAN–based DTEs are to use as the connection to the LAN–based X.25 network. You are only permitted to specify one LAN device.

X.25 DTE Address

The X.25 DTE address is the X.25 address that is used by other nodes in this X.25 network to identify this DTE. A DTE address is a series of numeric digits similar to a telephone number. It must be unique within each X.25 network.

LAN Remote Host Name

The LAN remote host name is simply a name that is used to distinguish between the different remote hosts. This name must be unique. For example, REMOTE-LAN-1.

To specify more than one LAN remote host, complete this section for the first remote host and then select to define another.

Remote MAC Address

The remote Media Access Control (MAC) address identifies the remote node accessed by this DTE. This address is fixed. A MAC address consists of a series of up to twelve hexadecimal digits, optionally separated by hyphens. For example: 1b-34-5f-78-e4-ab.

Note that each DTE may access only one other X.25 node on the LAN.

Incoming Logical Channel Range

{[start-of-range .. end-of-range]}

Outgoing Logical Channel Range

The outgoing logical channel number range specifies what channel numbers can be used by X.25 for OpenVMS when an outgoing callrequest is made.

Enter the channel range in the same format as the incoming logical channel range. For example, to enter the range 1 to 4095, enter {[1..4095]}. See Note under Incoming Logical Channel Range.

This section allows you to enter details about an X.25 network to which your system is attached via one or more X.25 Connector systems through which your system gains access to the PSDN. You must provide the node names of the X.25 Connector systems that provide the connection to the required PSDN.

Figure 5.4, “X.25 Client” illustrates the X.25 Client Section.

Network Name

Connector Node Names

This section is not presented if the X.25 Client Section is completed.

This section allows you to enter details about each of the Permanent Virtual Circuits (PVCs) to be used by your system. Your PSDN subscription will determine whether you are permitted to set up any PVCs.

PVC Name

The PVC name is simply a name that is used to distinguish between the different PVCs. This name must be unique. For example, PVC-1.

Channel Number

The channel number must be specified as an integer and must lie outside the outgoing and incoming logical channel ranges specified in the X.25 over Wide Area Network Section or X.25 over Local Area Network Section.

This section allows you to enter details about the type of incoming call security to be applied to your X.25 system.

Figure 5.6, “Incoming Call Security” illustrates the Incoming Call Security Section.

If the “Restrict Incoming Access” option is selected, you must define the access level to be granted to each remote DTE that needs to make an X.25 call to the local system.

Separate screens are presented for each access level. On the relevant screen, enter the Remote Address Prefix (RAP) of each remote DTE to be granted the specified access level.

Wildcards can also be used to specify an address. Entering only the wildcard, *, implies that the local system can receive calls from any DTE address.

Note that any calls from DTE addresses with RAPs that are not specified will be cleared.

Support for X.29 allows users to access the local system remotely via an X.25 network and to access remote systems via the X.25 network from the local system.

Figure 5.7, “X.29 Support Section” illustrates the X.29 Support Section.

X.29 Network User Identity

The X.29 Network User Identity (NUI) identifies the party that is to pay for each outgoing call, and the DTE class to be used for the outgoing X.29 calls. Enter the NUI in the form %x nnnnn or 'nnnnn'H where nnnnn can consist of up to 107 octets.

X.25 Mail allows users to send mail to, and receive mail from, other systems that implement the Mail–11 protocol over X.25.

If you answer “Yes” when prompted whether to configure X.25 Mail, the configurator will create an account called X25$MAIL in which X.25 Mail will run when X.25 Mail calls are received by the system being configured.

Figure 5.8, “NCL Script” illustrates the NCL Script Section.

When you reach this section, you have entered sufficient information to create a working X.25 configuration. If you want to verify some of the information you have entered, or add or delete some information, enter “Yes” in response to the question “Do you want to modify your answers?”. The Sections Menu will be displayed, from which you can choose the section you want to review.

When you are sure that the information you have entered is correct and complete, display the Sections Menu and select the option “Create the NCL Script”.

If the program creates the configuration file, a message is displayed which indicates the filename assigned to the file.

If, for some reason, the program cannot create the NCL script, error messages are displayed at the foot of the screen. If this occurs, you must correct the problem before making a further attempt to create the NCL script.

Next, if you have configured an X.25 Client system, you are presented with a screen that details the minimum number of session connections required for your X.25 for OpenVMS configuration. The number of connections is calculated on the basis of 128 connections per X.25 Connector node specified.

The configuration program now displays the number of Session Connections that can be established based on the configuration you have defined. You must ensure that the NSP attributes Maximum Transport Connections and Maximum Remote NSAPs are large enough to support this number of session connections. The default values of these attributes are 200 and 201 respectively.

The ADVANCED mode of the configuration program allows you to fully configure an VSI X.25 for OpenVMS system or to reconfigure an existing system.

To use the ADVANCED mode, you should have a good understanding of the X.25 management entities, the relationship between those entities, and a good understanding of X.25.

When you invoke the utility in ADVANCED mode, you can decide whether to create a new configuration or modify an existing configuration.

This mode of the configuration program can also be used to modify a configuration that was defined using the BASIC mode of the utility. When the utility is run, any existing configuration data is retrieved from the configuration database so that it can be viewed and, if required, modified.

The configuration program consists of a number of sections, each section corresponding to a logical group of information.

Details explaining the purpose of each section are given in Section 6.3, “Configuration Sections” and full details about the data required to complete each section are given in Chapter 7, Required Configuration Data.

Remote DTE Classes

This section allows you to specify the DTE classes on the X.25 Connector systems that your X.25 Client system will use to access one or more PSDNs.

You must configure at least one Connector node to complete this section.

Lines and DTEs

This section allows you to enter details relevant to Lines and DTEs.

You must configure at least one synchronous line to complete this section. Choose a line on your system to configure for X.25 communications.

LLC2 DTEs

This section allows you to enter details relevant to LLC2 DTEs. This allows your system to communicate using X.25 over a local area network (LAN).

You must configure at least one LAN device to complete this section.

XOT DTEs

This section allows you to enter details relevant to XOT DTEs. This allows your system to communicate using X.25 over a TCP/IP connection.

You must configure at least one TCP/IP connection to complete this section.

Session Connections

This section allows you to specify the maximum number of session control connections (virtual circuits) supported by the X.25 for OpenVMS interface. This section is presented only if the Remote DTE Classes Section has been completed.

PVCs

This section allows you to define one or more Permanent Virtual Circuits (PVCs). Your PSDN subscription will determine whether you are permitted to set up any PVCs. This section is presented only if the Lines and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section has been completed.

Groups

This section allows you to enter details of Closed User Groups (CUG) and Bilateral Closed User Groups (BCUG) on your system. Thissection is presented only if the Lines and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section has been completed.

If your DTE belongs to a CUG, it can communicate freely with remote DTEs that are members of the same CUG. Your DTE's communication with other DTEs (outside the CUG) may be restricted, depending on your PSDN subscription options.

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

X.29 Support

This section allows you to add support for X.29 communications. X.29 support is required if you want users of character–mode terminals to be able to log in from this system to remote X.25 systems, or from remote X.25 systems to this system, using X.29 protocols.

X.25 Mail

This section allows you to add support for X.25 Mail. X.25 Mail is required if your X.25 for OpenVMS system is to send mail to,or receive mail from, other X.25 nodes.

Applications

This section allows you to specify X.25 and X.29 applications on your system that are used to accept incoming calls.

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

For each application you must define at least one filter, the name of the command file that starts the application, and a username.

Relay–Clients

This section allows you to specify X.25 Relay–Clients on your X.25 Relay system. This manual uses the term Relay–Clients to refer to the X.25 management entity on the X.25 Relay system that holds the information about the actual X.25 Relay Client system. These allow your system to relay incoming calls to other X.25 nodes in your local network.

For each X.25 Relay–Client, you must specify a DTE class and at least one filter. The filter is used to match incoming calls to the Relay–Client, and the DTE class and template (if present) are used by the Relay–Client when making the outgoing call used to relay the call.

Filters

This section allows you to specify the filters to be used to determine the action taken when an incoming call is received.

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.

One filter, called OSI Transport, is automatically created on your system. In addition, if you choose X.29 support,an additional filter, called X29, is created. If you choose X.25 Mail support, a third filter, called X25_MAIL is also created.

Templates

This section allows you to define the templates to be used when an outgoing call is made.

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

Two templates, called Default and OSI Transport, are automatically created on your system. Appendix D, Characteristic Values of the Default and OSI Transport Templates lists the characteristic values of these templates. In addition, if you choose X.29 support, two additional templates, called X29Login and X29Server, are created. If you want additional templates, then you must complete this section.

Reachable Addresses

This section allows you to define the addresses of remote DTEs that are permitted to communicate with the X.25 system.

If you have local applications that use NSAP addresses to communicate with remote DTEs, then you must complete this section to provide a mapping between NSAP addresses and DTE addresses. Reachable addresses are used to convert NSAP addresses into DTE addresses.

Server–Clients

This section allows you to specify X.25 Server–Clients on your system. This manual uses the term Server–Clients to refer to the X.25 management entity on the X.25 Connector system that holds the information about the actual X.25 Client system. These allow your Connector system to service requests from X.25 Client systems in your DECnet network.

For each X.25 Server–Client, you must specify at least one service node and at least one filter. The filter is used to match incoming calls to the Server–Client, and the service node is used by the server to identify the node to contact when making the connection to the X.25 Client system.

X.25 Security

NCL Scripts

This section allows you to initiate the generation of NCL scripts based on the configuration data that you have entered.

This initiation should be performed only when you are satisfied that all the data you have entered is complete and correct.

This chapter details the information you will need to provide while running the configuration program in ADVANCED mode.

Tables 7.1 to 7.18 list all the information you will require during the configuration. You should write down the configuration parameter values specific to your system in Appendix A, Values Specific to Your Configuration (which provides a series of blank forms) and refer to that appendix when you run the configuration program. Note that the tables are presented in the order that the Sections are displayed if an X.25 system is configured for Client, WAN,and LAN usage.

Figure 8.1, “Introduction” illustrates the Introduction Section.

The Introduction Section provides you with options to create a new X.25 for OpenVMS configuration, modify an existing configuration, or exit from the program. These options are detailed more fully in subsections 8.1.1, 8.1.2, and 8.1.3 respectively.

Figure 8.2, “Remote DTE Classes” illustrates the Remote DTE Classes Section.

This section allows you to define remote DTE classes, in which you specify the X.25 Connector systems that your Client system will use in making a call.

Remote DTE Class Name

The name you specify for a remote DTE class on an X.25 Client system must match the name of a local DTE class on the X.25 Connector system you specify in the Connector Node Names list.

Outgoing Session Template

Specify the name of an OSI TRANSPORT TEMPLATE entity on the X.25 Client system that the Client should use when establishing the DECnet–Plus connection to the X.25 Connector system. If the template doesn't exist, you must create the template using the DECnet–Plus configuration program.

Connector Node Names

You must specify the name of at least one X.25 Connector node hosting the local DTE class referenced by this remote DTE class.

Figure 8.3, “Lines and DTEs” illustrates the Lines and DTEs Section.

This section allows you to configure synchronous lines and associated DTEs. You must set up at least onesynchronous line and associated DTE, unless you intend to set up LLC2 or XOT DTEs on your system.

Synchronous Line

This screen displays the available synchronous lines. Only lines configured when the synchronous devices were installed are presented. Select a line for the specified DTE. You will have the opportunity to set up further lines later.

Line Speed

The available line speeds are displayed. Select a speed for the line.

Link Name, DTE Name, X.25 Address, and Inbound DTE Class

You will be required to provide a unique link name, DTE name, and X.25 DTE address to identify the DTE to be associated with the line you select.

Additionally, before completing this section the configuration program will prompt you to enter the Inbound DTE Class with which the DTE is associated. All calls received on the DTE will be associated with the indicated DTE class.

Profile Name

You must provide the name of the profile to be used by the DTE you specified. Information on frame and packet control parameters will be derived from the profile you specify.

If you want to set up a point–to–point link then the ISO8208 profile should be specified.

Logical Channel Ranges

Logical channel numbers are required to identify logical links between your system and the PSDN for both incoming and outgoing calls. See Section 5.2, “X.25 over Wide Area Network” for more detailed information about the required syntax.

If you intend to configure any PVCs, select Logical Channel Ranges for the SVCs that leave enough channels free for the required PVCs.

Extended Packet Sequence Numbering

If the profile you have selected supports extended packet sequence numbering, you will be prompted whether you want to use this facility.

Packet Level Negotiation

If the profile you have selected supports packet level negotiation, you will be prompted whether to use this facility. If you select to use the facility, you will be prompted to specify the minimum, maximum, and default packet size to be used, and to specify the level 3 minimum, maximum, and default window size. If you select not to use the facility, you will be prompted to enter the packet size and level 3 window size to be used.

Extended Frame Sequence Numbering

If the profile you have selected supports extended frame sequence numbering, you will be prompted whether you want to use this facility.

Link Interface Type

If the DTE is connected to a PSDN, you should select DTE for the interface type.

If the DTE is to use a point–to–point protocol (that is, ISO8208), you must set the interface type correctly for both DTEs. Two DTEs using a point–to–point protocol can communicate only if one is set to DCE, and the other is set to DTE.

Segment Size

The call will be charged based on the number of segments sent. Thus, this value must be provided if you want to generate accounting records. Note that the value must match the value set in the network.

Figure 8.4, “LLC2 DTEs” illustrates the LLC2 DTEs Section.

This section allows you to configure LLC2 DTEs.

LAN Device Name

The LAN devices available on your system are displayed. Choose one to associate with your LLC2 SAP DTE. You will have the opportunity to set up further LLC2 DTEs later, using either a different LAN device (if you have more than one) or the same one.

LLC2 DTE Name, LLC2 DTE Address, Local LSAP Address, and Inbound DTE Class

You must provide a unique name and address to identify the LLC2 DTE to be associated with the link you select. In addition, you must specify the Link Service Access Point (LSAP) for the specified LLC2 DTE.

Additionally, before completing this section the configuration program will prompt you to enter the Inbound DTE Class with which the DTE is associated. All calls received on the DTE will be associated with the indicated DTE class.

Level 3 Profile

You must provide the name of the profile to be used by the LLC2 DTE you specified. For most LANs, the profile used is ISO8881. Information on frame and packet control parameters will be derived from the profile you specify.

Logical Channel Ranges

Logical channel numbers are required to identify logical links between the LLC2 DTEs for both incoming and outgoing calls. See Section 5.2, “X.25 over Wide Area Network” for more detailed information about the required syntax.

If you intend to configure any PVCs, select Logical Channel Ranges for the SVCs that leave enough channels free for the required PVCs.

Remote System Parameters

You must provide the unique Media Access Control (MAC) address of the remote system and the Link Service Access Point (LSAP) for the remote LLC2 DTE.

Link Interface Type

For two systems to communicate using the LLC2 protocol, one must be configured as a DCE and one as a DTE. You must determine the interface type being used by the remote system and the select the appropriate type for the local system. If the interface typebeing used by the remote system is unknown, set the interface type to Negotiated.

Extended Packet Sequence Numbering

If the profile you have selected supports extended packet sequence numbering, you will be prompted whether you want to use this facility.

Packet Level Negotiation

If the profile you have selected supports packet level negotiation, you will be prompted whether to use this facility. If you select to use the facility, you will be prompted to specify the minimum, maximum, and default packet size to be used, and to specify the level 3 minimum, maximum, and default window size. If you select not to use the facility, you will be prompted to enter the packet size and level 3 window size to be used.

Figure 8.5, “XOT DTEs” illustrates the XOT DTEs Section.

This section allows you to configure XOT DTEs.

Local TCP/IP Address

XOT DTE Name, XOT DTE Address, Local RFC1613 Port Number, and Inbound DTE Class

You must provide a unique name and address to identify the XOT DTE to be associated with the link you select. In addition, you must specify the local RFC1613 port number for the specified XOT DTE SAP. VSI recommends that you use the value 1998 as specified in RFC 1613.

Additionally, before completing this section the configuration program will prompt you to enter the Inbound DTE Class with which the DTE is associated. All calls received on the DTE will be associated with the indicated DTE class.

Level 3 Profile

You must provide the name of the profile to be used by the XOT DTE you specified. You must specify ISO8881. Information on frame and packet control parameters will be derived from the profile you specify.

Logical Channel Ranges

Logical channel numbers are required to identify logical links between the XOT DTEs for both incoming and outgoing calls. See Section 5.2, “X.25 over Wide Area Network” for more detailed information about the required syntax.

If you intend to configure any PVCs, select Logical Channel Ranges for the SVCs that leave enough channels free for the required PVCs.

Remote System Parameters

You must provide the unique IP address of the remote system and the RFC 1613 TCP port number of the remote system for the XOT DTE SAP link.

Packet Level Negotiation

If the profile you have selected supports packet level negotiation, you will be prompted whether to use this facility. If you select to use the facility, you will be prompted to specify the minimum, maximum, and default packet size to be used, and to specify the level 3 minimum, maximum, and default window size. If you select not to use the facility, you will be prompted to enter the packet size and level 3 window size to be used.

This section is available only if the Remote DTE Classes Section has been completed.

This section allows you to specify the maximum number of session control connections (virtual circuits) supported by the X.25 for OpenVMS interface. A value must be entered for this parameter. The default value is 10.

    ADD_CHANNELCNT
    ADD_NPAGEDYN
    ADD_NPAGEVIR

    @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK

This section is available only if the Lines and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section has been completed.

Figure 8.6, “PVCs” illustrates the PVCs Section.

This section allows you to set up permanent virtual circuits between the host system and specified DTEs.

DTE Name

Each of the DTEs created in the Lines and DTEs Section, LLC2 DTEs Section, and XOT DTEs Section are listed. Select one from the list.

PVC Name

Enter the name of the PVC.

For each PVC you name, you must define values for the channel number, packet size, and window size.

Channel Number

The channel number entered must not be within the range of incoming and outgoing logical channel numbers specified in the Lines and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section. The logical channel number range currently defined for PVCs is displayed beneath the DTE name at the top of the screen.

The channel number should be unique amongst PVCs associated with the specified DTE.

Packet Size and Window Size

The default values for the packet size and window size are taken from the profile specified in the Line and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section. The default values can be overridden if required.

XOT PVCs

For PVC circuits to interoperate correctly over a XOT DTE, it is necessary to specify additional information in the NCL configuration for the PVC. EachXOT PVC must have a REMOTE PVC NAME specified via NCL, via the command:

SET X25 PROTOCOL DTE dte-name PVC pvc-name REMOTE PVC N

The name should match the name configured on the remote system. The X.25 Configurator does not support this attribute when creating a PVC, so the appropriate NCL command should be placed in the file SYS$STARTUP:X25$EXTRA_SET.NCL.

This section is available only if the Lines and DTEs Section, LLC2 DTEs Section, or XOT DTEs Section has been completed.

Figure 8.7, “Groups” illustrates the Groups Section.

This section allows you to assign any of the DTEs you have created to Closed User Groups (CUGs), Bilateral Closed User Groups(BCUGs), or Closed User Groups with Outgoing Access (CUGOAs).

All the DTEs you have created are listed.

To place a DTE in a group, enter the PSDN–assigned CUG, BCUG, or CUGOA number beside that DTE. The same number can be assigned to more than one DTE.

To remove a DTE from a CUG or BCUG, delete the CUG or BCUG number associated with that DTE.

Figure 8.8, “X.29 Support” illustrates the X.29 Support Section.

This section allows you to provide support for X.29 communications.

You are prompted to provide the network user identity (NUI) to identify the party that is to pay for each outgoing call, and the DTE class to be used for the outgoing X.29 calls.

Note that if you answer “No” to configuring X.29 Support, no further questions will be displayed. Instead, the X.29 Support Options Menu is displayed from which you can move on to the next section.

This section allows you to provide support for X.25 Mail.

X.25 for OpenVMS uses an OpenVMS account (X25$MAIL) in which X.25 Mail runs when an incoming X.25 Mail call is received by your system. If the required account does not exist, it will be created before you exit the configuration program.

Note that if you answer “No” to configuring X.25 Mail, no account is created. Instead, the X.25 Mail Options Menu is displayed from which you can move on to the next Section.

Figure 8.9, “Applications” illustrates the Applications Section.

This section allows you to specify any applications running on your system.

Application Name, Application Type, Command File, and Username

The name you give an application is used to generate a rights identifier in the file SYS$STARTUP:X25$SECURITY_IDENTIFIERS.COM. For example, if you enter the application name TEST$1, and subsequently specify (in the Incoming Security: Applications Section) that one or more remote DTEs should be given an access level of REMOTE CHARGE, the rights identifier created will be APPL_TEST$1_REMOTE. Similarly, if you specify that one or more remote DTEs should be given an access level of ALL, the rights identifier created will be APPL_TEST$1_ALL.

Finally, you must provide the name of the command file that starts the application and a user name.

Application Templates

Application Filters

You must create at least one unique filter for each application. The Filter Name and Priority fields are mandatory; the other fields are optional. Note that you can set attributes to “unspecified” by leaving the appropriate field blank.

If you want to add a further filter to this application, answer “Yes” to the prompt “Do you want to associate another filter with the same application?”.

Figure 8.10, “X.25 Relay–Clients” illustrates the X.25 Relay–Clients Section.

The X.25 Relay–Clients Section allows you to set up call relaying from one DTE to another.

Client Name

You must specify a unique name for each Relay–Client. The name you give a Relay–Client is used to generate a rights identifier in the file SYS$STARTUP:X25$SECURITY_IDENTIFIERS.COM. For example, if you enter the Relay–Client name TEST$1, and subsequently specify (in the Incoming Security: Relay–Clients Section) that one or more remote DTEs should be given an access level of REMOTE CHARGE, the rights identifier created will be RELAY_TEST$1_REMOTE. Similarly, if you specify that one or more remote DTEs should be given an access level of ALL, the rights identifier created will be RELAY_TEST$1_ALL.

DTE Class

You must specify the DTE class that the Relay–Client should use to make the outgoing call as part of the relay function.

In order for a call to be forwarded on a Relay connection, the DTE that received the inbound call must be configured to be in DCE mode.

Template

You must specify one template for each X.25 Relay–Client. If you specify a template other than the Default template,the specified template will be created and its attributes amended if required. The Relay–Client uses the template when making the outgoing call as part of the relay function.

X.25 Relay–Clients may share templates, that is, you can specify the same template for more than one X.25 Relay–Client.

Filters

You must specify at least one unique filter for each X.25 Relay–Client. The Filter Name and Priority fields are mandatory; all other fields are optional. Incoming calls are handled by an X.25 Relay–Client only if they match one of that client's filters.

When creating an X.25 Relay–Client you can create a number of filters. To add, modify, or delete filters associated with an existing X.25 Relay–Client, select the “Modify” option on the X.25 Relay–Client Options Menu.

Figure 8.11, “Filters” illustrates the Filters Section.

This section allows you to create additional filters to screen incoming calls. The Filter Name and Priority fields are mandatory.

Note that you can set attributes to “unspecified” by leaving the appropriate field blank.

Filter Names

The name you give a filter is used to generate a rights identifier in the file SYS$STARTUP:X25$SECURITY_IDENTIFIERS.COM. For example, if you enter the filter name TEST$1, and subsequently specify (in the Incoming Security: Filters Section) that one or more remote DTEs should be given an access level of REMOTE CHARGE, the rights identifier created will be FILTER_TEST$1_REMOTE. Similarly, if you specify that one or more remote DTEs should be given an access level of ALL, the rights identifier created will be FILTER_TEST$1_ALL.

Figure 8.12, “Templates” illustrates the Templates Section.

The Default and OSI Transport templates are set up automatically. The characteristic values of these templates are given in Appendix D, Characteristic Values of the Default and OSI Transport Templates.

This section allows you to create additional templates with which to make outgoing calls.

Note that you can set attributes to “unspecified” by leaving the appropriate field blank.

The Template Name field is the only mandatory field.

Figure 8.13, “Reachable Addresses” illustrates the Reachable Addresses Section.

This section allows you to convert NSAP addresses to DTE addresses.

Choose either “X.121” or “Manual” for the mechanism by which the destination DTE address is supplied.

Figure 8.14, “X.25 Server–Clients” illustrates the X.25 Server–Clients Section.

The X.25 Server–Clients Section allows you to set up a number of X.25 Server–Clients that represent the server's Client systems.

You must specify at least one service node and at least one filter for each X.25 Server–Client. Incoming calls are handled by an X.25 Server–Client only if they match one of that Server–Client's filters. The X.25 Server–Client then uses the service node information to contact the Client system.

Service Node

You must specify at least one service node for each X.25 Server–Client.

When creating an X.25 Server–Client you can include a number of service nodes. To add, modify, or delete service nodes associated with an existing X.25 Server–Client, select the “Modify” option on the X.25 Server–Client Options Menu.

Filters

You must specify at least one unique filter for each X.25 Server–Client. The Filter Name and Priority fields are mandatory; all other fields are optional.

When creating an X.25 Server–Client, you can create a number of filters. To add, modify, or delete filters associated with an existing X.25 Server–Client, select the “Modify” option on the X.25 Server–Client Options Menu.

Figure 8.15, “Incoming Security: Applications ” illustrates the Incoming Security: Applications Section.

This section allows you to specify the type of incoming access for each application you specified. You must complete this section if you want Applications to receive incoming calls.

Figure 8.16, “Incoming Security: Filters ” illustrates the Incoming Security: Filters Section.

This section allows you to specify the type of incoming access for the Filters specified. You must complete this section if you want Filters to be able to receive incoming calls.

Figure 8.17, “Incoming Security: Relay Clients” illustrates the Incoming Security Section for X.25 Relay–Clients. This section allows you to specify remote DTEs and the related type of incoming access to the specified X.25 Relay–Client.

Figure 8.18, “Outgoing Security: Local Processes” illustrates the Outgoing Security: Local Processes Section.

You must complete this section if you want processes on this system to be able to make outgoing calls. Processes include X.25 applications.

For X.25 applications, enter the name of the group to which the process belongs when prompted for the Rights Identifier.

$ set def sys$system
$ run authorize
UAF> show /identifier *

If the rights identifier you enter does not exist, it will be defined before you exit the configuration program provided that you select to run the command procedure SYS$SYSTEM:X25$SECURITY_IDENTIFIERS.COM.

Figure 8.19, “NCL Script” illustrates the NCL Script Section.

When you reach this section, you have entered sufficient information to create a working X.25 configuration. If you want to verify some of the information you have entered, or add or delete some information, then answer No to the question “Do you want to create an NCL script now?” You will then go back to the Sections Menu, from which you can choose the section you want to review.

When you are sure that the information you have entered is correct and complete, display the Sections Menu and select the option Create the NCL Script.

If the program creates the configuration file, a message is displayed which indicates the filename assigned to the file.

If, for some reason, the program cannot create the NCL script, error messages are displayed at the foot of the screen. If this occurs, you must correct the problem before making a further attempt to create the NCL script.

If you have configured the Remote DTE Classes Section, the configuration program now displays the number of Session Connections that can be established based on the configuration you have defined. You must ensure that the NSP attributes Maximum Transport Connections and Maximum Remote NSAPs are large enough to support this number of session connections. The default values of these attributes are 200 and 201 respectively.

You can run the CTP either in loop back mode (from your system through the PSDN and back to your system), or to a remote system through the PSDN.

This section describes the privileges and system quotas required, and the actions that must be taken, before you can run the CTP.

Privileges Required

System Quotas Required

Rights Identifiers Required

When CTP is initialized, users are given the rights identifier PSI$X25_USER. This privilege should be sufficient. If this provides insufficient privileges to run CTP, assign the BYPASS privilege.

X.25 for OpenVMS Software

Partner System

Partner systems may be either the local system running the CTP or an accessible X.25 for OpenVMS system correctly configured to allow access from the local system and running CTP in Receive–Only mode.

You must know the X.25 address of the partner system.

You can run the CTP can either interactively or as a network object (that is, a predefined X25 ACCESS APPLICATION entity).

$ run sys$test:x25$ctp

$ @sys$test:x25$ctp_add_netobj

$ @sys$test:x25$ctp_rem_netobj

Full details about each of these modes are given in Sections 9.4.1, 9.4.2, and 9.4.3 respectively.

Figure 9.1, “Configuration Test Procedure Flowchart” provides a flowchart of the testing procedure for testing of SVCs and PVCs. For details of the steps required to test SVCs and PVCs, refer to Sections 9.5.1 through Section 9.5.3, “Testing Remote SVCs”. A summary of the tests performed on each SVC or PVC are provided in Section 9.5.4, “Test Summary”.

Note that at the end of testing you are prompted whether to repeat any of the tests. If during the initial testing you chose to set up PVC receivers, those receivers are used for any repeat testing.

                       LOCAL DTE SVC TESTING
DTE            Usable  Test  DTE Class      Dest Addr  Result
---            ------  ---   ---------      ---------  ------
LLC2-LCL-REM1  Yes     Yes   LLC2-LCL-REM1  12345
LLC2-LCL-REM2  Yes     Yes   LLC2-LCL-REM2  6789
LLC2-LCL-REM3  Yes     Yes   LLC2-LCL-REM3  9876

                    LOCAL DTE SVC TESTING
   DTE            Usable  Test  DTE Class         Dest Addr        Result
   ---            ------  ---   ---------         ---------        ------
   LLC2-LCL-REM1  Yes     Yes   REMCLASS-0        12345            Success
   LLC2-LCL-REM2  Yes     Yes   REMCLASS-1        12345            Success
   LLC2-LCL-REM3  Yes     Yes   REMCLASS-2        9876             Fail

         LOCAL DTE SVC TEST FAILURE
         DTE Class        Failure Analysis
         ---------        ----------------
         REMCLASS-0       Test:   SVC outgoing call test
                          Reason: Unsolic MSG$_DISCON mbx msg received
                                  cause code = 00, diag code = 00
                          Cause:  Call cleared unexpectedly
                          Action:

                       PVC RECEIVER SET UP
                 PVC              Test   DTE Class        Result
                 ---              ----   ---------        ------
                 CLASSA-RCV       Yes    CLASSA
                 AUSNAC-RCV       Yes    AUSNAC

          PVC RECEIVER SET UP
                 PVC           Test   DTE Class        Result
                 ---           ----   ---------        ------
                 CLASSA-RCV    Yes    CLASSA           Fail
                 AUSNAC-RCV    Yes    AUSNAC           Success

          PVC RECEIVER FAILURE
      PVC                   Failure Analysis
      ---                   ----------------
      CLASSA-RCV            Reason: Failed to set up receiver
                                    status = SS$_IVDEVNAM
                                    2nd status = PSI$C_ERR_NOSUCHPVC
                            Cause:  Specified PVC is not known
      Action:    The entity you specified does not exist.
                 Ensure that the name was entered correctly in
                 the test data. To determine which entities are
                 configured, use the ncl command:
                   ncl> show x25 proto dte <dte-name> pvc * name
                 at the remote node

                             REMOTE DTE SVC TESTING
                DTE Class         Test   Dest Addr        Result
                ---------         ----   ---------        ------
                REMCLASS-0        Yes    12345
                REMCLASS-1        Yes    9876

                         REMOTE DTE SVC TESTING
                DTE Class         Test   Dest Addr        Result
                ---------         ----   ---------        ------
                REMCLASS-0        Yes    12345            Fail
                REMCLASS-1        Yes    9876             Success

       REMOTE DTE SVC TEST FAILURE
         DTE Class        Failure Analysis
         ---------        ----------------
         REMCLASS-0       Test:   SVC outgoing call test
                          Reason: Unsolic MSG$_DISCON mbx msg received
                                  cause code = 00, diag code = 00
                          Cause:  Call cleared unexpectedly
                          Action:

These events and how to proceed if one occurs are described in Sections 9.6.1 and 9.6.2 respectively.

x25$pr file not found

no connection to X25$PR –
timed out trying to connect to x25$pr –

version mismatch between X25$PR interface and X25$PR –
x25$ctp and x25$pr images not compatible –

x25$pr has no room for new connections

invalid X.25 Client installation

X.25 Client not running

invalid receiving mode

$ show logical PSI$PR_NETOBJ_MODE

exceeded <quota type> quota

Four user NCL script files are created the first time the configuration program is run. These script files can be used to contain user–supplied NCL commands. The script files are called when the startup script is invoked and any commands defined in them are used to augment the NCL commands in the master NCL script file generated as a result of running the configuration program.

SYS$STARTUP:X25$EXTRA_CREATE.NCL

SYS$STARTUP:X25$EXTRA_ENABLE.NCL

SYS$STARTUP:X25$EXTRA_SECURITY.NCL

SYS$STARTUP:X25$EXTRA_SET.NCL

A standard text editor can be used to add NCL commands to these script files. Each command should be placed on a separate line. Only valid NCL commands should be added to the script files.

ncl> do script-filename

To modify an existing configuration dynamically, use NCL commands to alter the configuration parameters initially set up when the configuration file is run. Full details on how to use NCL are given in the VSI DECnet–Plus for OpenVMS—Network Control Language Reference manual.

If you want to discard your existing configuration or make extensive modifications to your configuration, it may be more efficient to create an entirely new configuration. This can be achieved by invoking the configuration program and selecting the Create option from the Main Menu.

The existing configuration is superseded when the new configuration file is generated.

Whenever a configuration file is generated by the configuration program, the previous script (if any) is saved. Provided that you have not manually deleted a saved version, a specific version can, if required, be recalled and used in place of the current version.

$ rename x25$config.ncl_sav;3 x25$config.ncl