HP OpenVMS Systems Documentation

The Modem Connect module provides management directives for creating and deleting the entity.

The modem connect entity has the following subordinate entities:

• data port --- Represents status information about each access point to the Physical layer currently provided by the Modem Connect module.
• line --- Defines attributes for the control and monitoring of a physical line.

The following sections show the association between Phase IV network management parameters and their equivalent DECnet Phase V attributes.

Each section contains a table listing the parameters that could be set by Phase IV network management. The columns in the table denote the following:

1. Phase IV Name --- The name of a Phase IV network management parameter.
2. DECnet Phase V entity --- The DECnet Phase V entity that contains the attribute that maps most closely to this parameter.
3. attribute --- The name of the attribute that maps most closely to the Phase IV network management parameter.
4. type --- The DECnet Phase V data type of this attribute. (Refer to the DECnet-Plus Network Control Language Reference for a description of common data types for NCL.)

The footnotes describe additional points to consider when converting from DECnet Phase IV to DECnet Phase V network management.

H.2.1 X25-ACCESS NETWORK Database

The X25-ACCESS NETWORK database points to the X.25 protocol networks on remote connector systems. It also contains session control access control information. Table H-1 shows the parameter mapping rules.

For example:

NCP> set x25-access network MYNET node GWYNOD

ncl> create x25 access dte class MYNET type remote
ncl> set x25 access dte class MYNET node LOCAL:.GWYNOD

The X25-PROTOCOL NETWORK database defines the base operating characteristics (including default values) for a collection of DTEs and their associated lines. The same profile can be used by more than one network name. Table H-2 shows the parameter mapping rules.

The X25-PROTOCOL DTE database contains the operating characteristics of each connection to the PSDN at X.25 level 3 (packet level). Default values are taken mostly from the profile; customers can modify these values so that their system configurations match their PSDN subscription options. Table H-3 shows the parameter mapping rules.

For example:

NCP> set x25-protocol network mynet profile iso8208
NCP> set x25-protocol dte 123456789 network mynet line dsv-0-0 state off
NCP> set x25-protocol dte 123456789 network mynet channels 1024-1
NCP> set dte 123456789 net mynet state on

ncl> create x25 access dte class mynet type local
ncl> set x25 access dte class mynet local dte {dte-0}
ncl> create x25 protocol dte dte-0 profile "ISO8208"
ncl> set x25 protocol dte dte-0 x25 address 123456789,inbound dte class mynet
ncl> set x25 protocol dte dte-0 link service provider LAPB link dsv-0
ncl> set x25 protocol dte dte-0 outgoing list {[1..1024]}
ncl> enable x25 protocol dte dte-0

The X25-PROTOCOL GROUP database associates individual local DTEs (qualified by their network) with an X.25 closed user group. The Phase IV database design is less flexible than the Phase V one (which allows complicated groups to be configured as one entity). Table H-4 shows the parameter mapping rules.

For example:

NCP> set x25-protocol group secret dte 123456789 network mynet type bilateral -
_ number 99

ncl> create x25 protocol group secret
ncl> set    x25 protocol group secret type bcug,members {(dte=dte-0,index=99)}

The X25-SERVER database serves as the incoming call handler and controls the total number of connections on the system. In DECnet Phase V, it is replaced by three distinct modules. Table H-5 shows the parameter mapping rules.

The local destinations in the X25-SERVER database are identified by the lack of a NODE qualifier.

Each destination points to an entry in the Phase IV OBJECT database, which identifies a command procedure to invoke. (VAX P.S.I. does not support executable images.)

In DECnet Phase V, objects are replaced by x25 access application entities. Each application specifies a set of filters to listen for incoming calls by using the filters attribute. The file attribute identifies a command procedure to invoke when a call is received. The type attribute for these applications should be set to X25.

Table H-6 shows the parameter mapping rules.

For example:

NCP> define object psi_mail number 0 file sys$system:psi$mail -
_ user username password secret

NCP> define module x25-server destination psi_mail object psi_mail -
_ call mask ffffffffffffffffffffffffffffffff -
_ call value ff00000056332e30204d41494c2d3131

ncl> create x25 access filter PSI_MAIL
ncl> set x25 access filter PSI_MAIL priority 3000 ,  -
_ncl> call data value %XFF00000056332E30204D41494C2D3131 ,  -
_ncl> call data mask %XFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

ncl> create x25 access application PSI_MAIL
ncl> set x25 access application PSI_MAIL type X25,  -
_ncl> file sys$system:psi$mail.com , user "mail$server", filters {PSI_MAIL}

H.2.7 X25-SERVER Remote Destination Database

Table H-7 shows the parameter mapping rules.