Bull DPS 7000 Configuration Manual

Transcription

1 Communications Bull DPS 7000 Configuration Manual CNS7-A2 NGL - Reference Manual GCOS 7 Software Subject : This manual describes how to configure and generate the Communications Network Software (CNS). It provides an alphabetic reference to the Node Generation Language for CNS. Special instructions : Software supported : CNS 7 A2 Date : July 992 Bull Electronics Angers S.A. Bull HN Information Systems Inc. CEDOC Publication Order Entry Atelier de reprographie FAX: (508) , Avenue Patton MA02/423S ANGERS Cedex 0 Technology Park FRANCE Billerica, MA 082 U.S.A. 39 A2 32DN Rev0

2 Copyright Bull S.A., 992 Bull acknowledges the rights of proprietors of trademarks mentioned herein. Suggestions and criticisms concerning the form, content, and presentation of this manual are invited. A form is provided at the end of this manual for this purpose. Bull disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Bull liable to anyone for any indirect, special, or consequential damages. The information and specifications in this document are subject to change without notice. Consult your Bull Marketing Representative for product or service availability. 39 A2 32DN Rev0

3 Preface PURPOSE This manual describes how to configure and generate the Communications Network Software (CNS 7), independently of an associated Bull DPS 7000 host. For information on configuring OSF/SNA functions, refer to the OSF/SNA Reference Manual. In normal operation, generation uses the CNS 7 automatic generation facility, FPG7. But, this manual also provides an in depth description of the startup and generation procedures for more complex systems than can be generated by the automatic generation facility. INTENDED READERSHIP This manual is for Data Processing Managers, System Engineers, Network Designers and Network Administrators with experience in configuring and managing systems operating in the Bull Distributed Systems Architecture (DSA) environment. It is assumed that any reader is familiar with DSA "objects" used for configuration and the systems operation in a DSA network. The following manual directory contains a list of publications that may also be helpful in understanding the functions of configuration and generation described in this manual. 39 A2 32DN Rev0 iii

4 CNS7-A2 NGL - Reference Manual STRUCTURE Section A general introduction to DSA and CNS 7. Section 2 Section 3 Section 4 Section 5 Section 6 Section 7 Appendix A Appendix B Describes the conceptual aspects of the Distributed Systems Architecture and introduces DSA "Objects". Describes the configuration file and the methods of declaring the basic directives required to configure CNS. A configuration example is shown. Describes the configuration of administrative functions. Briefly describes the Node Generation Language (NGL), and gives full details of configuration and generation directives AC to MD. Gives full details of configuration and generation directives ML to WM inclusive. Describes the startup and generation procedures. Describes the Dynamic Network Extension facility. The SYSGEN IMA File. MANUAL DIRECTORY The Bull publications listed below constitute the reference manual set for CNS 7. Ordering Information Bull customers may order any Bull publication from the address given on the title page of this manual. Bull software reference manuals are periodically updated to support improvements to the software. Before ordering any manual listed below, it is recommended that the customer refer to one of the Bull Documentation Directories to obtain information concerning the specific edition of the manual supporting the installation's current software. iv 39 A2 32DN Rev0

5 Preface You should see your Bull representative for information concerning the availability of applications software and supporting documentation, as these provide specialized services. CNS 7 A2 Documentation Directory A4 30DN CNS 7 A2 NGL Reference Manual A2 32DN CNS 7 A2 Terminal Management A2 33DN CNS 7 A2 NOI Operator Guide A2 34DN CNS 7 A2 In- & On- Line Tests A2 35DN FPG7 Simple Generation Guide A2 46DM The following publications provide additional information: OSI/DSA Network Administration Guide...39 A OSI/DSA Concepts...39 A OSI/DSA Network Operator's Handbook...39 A OSI/DSA Log File Messages...39 A OSI/DSA Network Systems Messages & Return Codes A2 26DM OSF/SNA NGL Reference Manual A2 99DM GCOS 7 Network Overview and Generation A2 30UC GCOS 7 Network Operations A2 3UC Getting started with your Telecommunications A2 70UC 39 A2 32DN Rev0 v

6 CNS7-A2 NGL - Reference Manual vi 39 A2 32DN Rev0

7 Table of Contents. Overview INTRODUCTION ARCHITECTURE The Primary Network The Secondary Network Distributed Systems Administration and Control (DSAC) Architecture GENERAL OBJECTS MAPPING DIAGRAMS Generation Files - Basic Requirements and Methodology INTRODUCTION GENERATION METHODOLOGY CNS 7 GENERATION FILE STRUCTURE A2 32DN Rev0 vii

8 CNS7-A2 NGL - Reference Manual 3.5 NODE GENERATION LANGUAGE Symbols Used Parameter Values Multiline Directives Multi-Directive Line Mapping Comment Lines DECLARING THE OBJECTS Automatic creation of Objects Declare the Local System Define the Controllers Declare the Lines for the Primary Network and Associated Functions Declare the Configuration to Access Host System, and Associated Functions Declare the Other DSA Remote Systems and the Way to Access Them Declare the ISO/DSA Workstations Non-DSA Remote Systems Using the local System as a switch Declare the Other Remote ISO Systems Declare the Statistics Blocks Declare the Terminal Model Types To Be Used Declare the Secondary Network Declare Terminal Clusters Declare the Administrative Functions Declare the Possible Connections To Remote Applications Declare the Physical Subscription DYNAMIC NETWORK EXTENSION Dynamic Network Extension in DSA/SID environment Dynamic Network Extension in full ISO environment EXAMPLE OF GENERATION Configuration of Administration Functions INTRODUCTION NAD NODE ADMINISTRATOR Mapping Connection NOI NETWORK OPERATOR INTERFACE Mapping NOI Connection Terminal Manager Connection viii 39 A2 32DN Rev0

9 Table of Contents 4.4 ASF ADMINISTRATIVE STORAGE FACILITY Mapping ASF Connection Back-up ASF IN/ON-LINE TESTS Configuration and Generation Directives (AC to MD) ADMINISTRATIVE CORRESPONDENT (AC) ADMINISTRATIVE FUNCTION (AF) ADMINISTRATIVE GROUP (AG) APPLICATION (AP) CABLE (CB) CONNECTION DESCRIPTOR (CD) CLUSTER (CL) CNS CORRESPONDENT (CO) CONTROLLER (CT) DEVICE MACRO (DEVICE) DIR DEVICE POOL (DP) DEVICE OBJECT (DV) A2 32DN Rev0 ix

10 CNS7-A2 NGL - Reference Manual 5.5 END EXECUTIVE (EX) FILTER (FL) LANGUAGE (LANG) LOGICAL DEVICE (LD) LINK FILE (LKFL) LOGICAL LINE (LL) LOGIN DESCRIPTOR (LN) MAILBOX (MB) MODEL (MD) Configuration and Generation Directives (ML to WM) MULTILINK (ML) NETWORK ENTITY (NE) NETWORK ROUTE (NR) NETWORK SUBSCRIPTION (NS) NETWORK SERVICE ACCESS POINT (NSAP) NETWORK USER (NU) OPERATOR OP) PATCH x 39 A2 32DN Rev0

11 Table of Contents 6.9 PATCH PHYSICAL LINE (PL) PAD PROFILE (PROFIL) PHYSICAL SUBSCRIPTION (PS) REMOTE NETWORK SERVICE ACCESS POINT (RNSAP) STATISTIC BLOCK (SB) SESSION CONTROL (SC) CHARACTER SEQUENCE (SEQ) SUBSCRIPTION GROUP (SG) TERMINAL STATION (SN) SESSION ROUTE (SR) TABLE FILE (TBFL) TEMPORARY FILE (TMP) TERMINAL CODE CONVERSION TABLE (TRS) TRANSPORT STATION (TS) TERMINAL UNIT (TU) MAILBOX EXTENSION (TX) USER DESCRIPTOR (UD) USER A2 32DN Rev0 xi

12 CNS7-A2 NGL - Reference Manual 6.28 TRANSPORT USER (UT) WELCOME MESSAGE (WM) System Generation and Startup GENERAL PREPARING THE NECESSARY FILES Writing the Generation File Writing or Modifying Other Files PERFORMING GENERATION Performing Generation Via The SYSG Mailbox Entering the command directly Using a scenario file Performing Generation Via The NOI Performing Generation From The DPS 7000 Console LOADING THE SYSTEM Application of Patches THE GO FUNCTION Description Syntax Description of Parameters xii 39 A2 32DN Rev0

13 Table of Contents 7.6 THE CONFIGURATION COMMANDS USED BY THE GENERATOR Generation Load Application of New Patches Generation File Copy Execution of a Scenario Parameter Description SUMMARY A2 32DN Rev0 xiii

14 CNS7-A2 NGL - Reference Manual Appendices A. Dynamic Network Extension... A- A. DYNAMIC NETWORK EXTENSION... A- A.. Introduction... A- A..2 Calling systems and called systems... A- A..3 Uses and Misuses... A-4 A..4 Implementing the DNE facility... A-4 A..4. ISO DNE connected directly to an X.25 PDN... A-5 A..4.2 ISO DNE connected directly to an E-LAN... A-5 A..4.3 DSA DNE connected via a remote DSA TS (Transport Station)... A-6 A..4.4 DNE Connected via a remote ISO/DSA TS (Transport Station)... A-7 A..5 Calling DNE systems... A-8 A..5. The EX directive... A-8 A..5.2 The GO command... A-8 A..5.3 The EQU file... A-9 A..5.4 Syntax for SC EQU... A-9 A..6 Examples of Declarations... A-0 A..6. DNE on an E-LAN... A-0 A..6.2 DNE on a PDN subscription... A- A..7 Declaring SC EQU in the CONFIG file... A-2 A.2 DYNAMIC NETWORK EXTENSION FOR ISO NETWORKS... A-4 B. The SYSGEN IMA... B- Index... i- xiv 39 A2 32DN Rev0

15 Table of Contents Illustrations Figures - The Elements That Communicate Via CNS The Functions of CNS Application Access () Application Access (2) Local Host Connections Remote Systems on an HDLC (LAPB) Line Remote Systems on an X25 Network Remote Systems on HDLC NRM Links Remote Systems on a LAN Switch Functions Synchronous Devices on Line Synchronous Devices on an X25 Network Asynchronous Devices on a Line Asynchronous Devices on a PAD PAD Devices on an E-LAN Secondary Network Local Configuration Terminal Connection Procedures ASPI Devices on a PAD Administration The Local System Terminal Connections () Terminal Connections (2) Connections Between Administrative Functions Example of Primary Network Connection To Remote Bull DPS 7000 With Bull Datanet NAD Administrative Object Relationships NOI Administrative Object Relationships The welcome handler The polling phase Device Pool Configuration Filter Logic Acknowledgment Mechanism Timer Mechanism Calculating Timer T VIP and 3270 timers Polling groups Polling versus selecting BCC calculation for 2780 terminals Lost frame detection PROFIL Mapping Use of the SEQ directives A- Dynamic Network Extension... A-3 A-2 DNE on a LAN... A-0 A-3 DNE on a PDN... A- A-4 Declaring ISO/DSA workstations... A-3 39 A2 32DN Rev0 xv

16 CNS7-A2 NGL - Reference Manual Tables 2- CNS Objects End of Page Parameter Validity Relationship between LCON/LCOFF, S64/S96 and LOWCAS/UPCAS parameters: Summary of LL Parameters (/2) Summary of LL Parameters (2/2) Standard VIP Models (/4) Standard VIP Models (2/4) Standard VIP Models (3/4) Standard VIP Models (4/4) Standard Models (/3) Standard Models (2/3) Standard Models (3/3) Standard Models Asynchronous Standard Models (/4) Asynchronous Standard Models (2/4) Asynchronous Standard Models (3/4) Asynchronous Standard Models (4/4) Value n and v0 for filling algorithms Filling algorithms Default Packet/Window Sizes (/2) Default Packet/Window Sizes (2/2) PAD profile parameters (/6) PAD profile parameters (2/6) PAD profile parameters (3/6) PAD profile parameters (4/6) PAD profile parameters (5/6) PAD profile parameters (6/6) Default Site Address values Summary of GCOS7 Files xvi 39 A2 32DN Rev0

17 . Overview. INTRODUCTION This manual provides an overview of CNS 7 and presents the procedures and directives required for the startup and generation, covering: architecture, configuration, node generation language, startup and generation. 39 A2 32DN Rev0 -

18 CNS7-A2 NGL - Reference Manual.2 ARCHITECTURE CNS 7 provides communications over many types of link, for example, dedicated lines, switched telephone networks or X.25 public networks. It allows Bull DPS 7000 systems to access applications in other host processors and allows terminals to access applications running on the Bull DPS 7000 system running CNS 7. HOST SYSTEM SUPPORT VIA INTERNAL SYSTEM LINK ADMINISTRATION FACILITIES CNS REMOTE SYSTEMS (PRIMARY NETWORK SUPPORT) TERMINALS (SECONDARY NETWORK SUPPORT) Figure -. The Elements That Communicate Via CNS A2 32DN Rev0

19 Overview The functions of CNS 7 are as follows: as a front-end processor, CNS 7 provides the interface between a Bull DPS 7000 host and a primary and/or secondary network, as a switch, CNS 7 routes messages in the primary network. FRONT-END PROCESSOR SWITCH Figure -2. The Functions of CNS 7.2. The Primary Network A primary network is a group of one or more systems interconnected by an ISO/DSA network. This part of the network supports data transfers between remote systems. CNS 7 also supports local area networks based on ISO protocols..2.2 The Secondary Network A secondary network is a group of terminals connected to a system and supported by the Terminal Manager. Information is exchanged across a secondary network by physical links and between processes located in the same system. Terminals may access the primary network via the Terminal Manager. 39 A2 32DN Rev0-3

20 CNS7-A2 NGL - Reference Manual.2.3 Distributed Systems Administration and Control (DSAC) Distributed Systems Administration and Control is the name for components, languages, data formats and protocols that provide control and administration for the network, systems in the network and for distributed applications. The administrative functions are distributed among the network components and cover: loading network systems, dumping systems locally from the host or remotely via an HDLC line or Bull Establishment Network cable, monitoring the network, matching system parameters to network characteristics, logging information for statistical, accounting and maintenance purposes, in-line tests, software generation. Note: The TELELOAD function is supported by any system running under DNS (Bull Datanet, Bull CpNet) but not CNS 7. The Network Control and Administrative facilities for CNS 7 are provided by: NGL Node Generation Language (see sections 5 and 6 of this manual). NCL Network Control Language (see Bull Publication, CNS 7 NOI Operator Guide). NOI Network Operator Interface (see section 4 of this manual). NAD Node Administrator (see section 4 of this manual). ASF Administrative Storage Facility (see section 4 of this manual) A2 32DN Rev0

21 2. Architecture 2. GENERAL A network is a set of components connected by communication links. The components can be hardware or software. Computer processors, communications processors and telephone lines are examples of hardware components. Routing and operating systems are examples of software components. A system requires data about the hardware and software components with which it communicates. This data is subject to a set of protocols defined by DSA. To describe the network, a hardware or software component (described as objects) are mapped to another component. Mapping can be: on a one to one basis, one object is related to one other object, on a one to many basis, several objects are related to one object. 2.2 OBJECTS This section lists the objects that may be used in CNS 7, and shows how they relate one to another. There are two types of objects in CNS 7: Static objects that must be declared during system generation using directives (see list of directives in chapter 3 and description in chapter 5). Dynamic objects that are created by CNS 7 when necessary. These objects are known as connection objects and must NOT be declared at system generation. The following tables show the full set of types of objects existing for each family (or class) of object. 39 A2 32DN Rev0 2-

22 CNS7-A2 NGL - Reference Manual Table 2-. CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Administrative Correspondent AC ASF NAD NCC NOI Administ.Storage Facility Node Administrator Network Control Center Network Operator Interface Adm inistrative Image Administrative Function AF NAD NOI SYSG Node Administrator Network Operator Interface System Generator Adm inistrative Proper Administrative Group AG ASF NAD NCC NOI OP Administ. Storage Facility Node Administrator Network Control Center Network Operator Interface Operator Adm inistrative Image Address List Element AL LOC Local address (automatically generated) Addressing Application AP TMG SECU Welcome Application D-Spy Application Proper Proper Application Element Connection AX TMG SECU Terminal Management 'Ease of use' Security Connection Object Cable CB LAN Local area network Routing Channel Connection CC ATS Allows mapping between an ATS session and a Transport session Connection Object Connection Descriptor CD TMG Terminal Management Descriptor Cluster CL TGX VIP X X25 (foreign) VIP X Adm inistrative Proper Correspondent CO ATS AX25 TMG X29 OSI Correspondent X25 Correspondent Terminal Management X29 Application Image Image Addressing Image A2 32DN Rev0

23 Architecture Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Controller CT DCA DCBE DCE MLNA RLNA Communications Communications Communications Communications E-LAN or ISL Proper " " " " Device Pool DP TMG Terminal Management Addressing Device DV ASPI ASY BSC PAD TGX VIP VPAD ASPI Printer Asynchronous NJE Terminal Packet Assembly-Disass. TGX VIP PVC PAD Terminal Addressing " " " " " " " Device Connection DX ASY PAD TGX VIP Mapped onto a DV of the same type Connection object " " " " Executive EX Unsolicited message only Filter FL IN OUT Input Output Administrative Proper Administrative Function Connection FX Mapped onto AF object Unsolicited message only Internet Activity IK IPFL IPHD IPSW Internet full ISO on LAN Internet full ISO on HDLC Internet full ISO on X25 Connection Object Encription KR GUS General Utility Service Descriptor Logical Connection LC DSA ISO LOC M apped onto SC/SR same type Connection object " 39 A2 32DN Rev0 2-3

24 CNS7-A2 NGL - Reference Manual Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Logical Device LD TMG Terminal Management Addressing Proper Link Connection LK ASY ASYV BDL MTPT SLV VIP Mapped onto an LL or DV of same type object Connection object " " " " " " Logical Line LL ASPI ASPV ASY ASYV BSC BDL MTPT SLP SLV VIP ASPI Printer ASPI on VC Asynchronous Videotex NJE Terminal HDLC Multipoint HDLC Proper Multilink Procedure Multipoint HDLC Image VIP BSC 2780 BSC 3270 Addressing " " " " " " " " " " " Login Descriptor LN TMG Terminal Management Descriptor Logical Device LX TMG Mapped onto an LD of the same type Connection object Mailbox MB ATS AX25 STAT TMG USER Applicative Transport Service Applicative X25 Service Station Terminal Management User Addressing Proper " " " Model MD ASPI ASY TGX VIP BSC ASPI Printer Asynchronous TGX VIP BSC 2780 BSC 3270 BSC Multileaving Descriptor " " " " " A2 32DN Rev0

25 Architecture Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Multilink Connection MK MLP Multilink Connection Connection Object Multilink ML MLP Multilink Procedure Addressing Network Connection NC ASPI DSA DIW S TGX Mapped between TS LOC type and other TS (or CL) whose type it takes Connection object " " Network Entity NE CLNS CONS Connectionless Connection Oriented (RB object attribute) Routing " Internet N etw ork Activity NK IP Internet protocol Connection Object Network Route NR AX25 HDLC IPFL IPHD IPSW LAN LPAD PAD PER SLAN SW SX25 AX25 Interface HDLC Internet ISO Full on LAN Internet ISO on H D LC Internet ISO on X25 Local Area Network PAD over E-LAN PAD Permanent X.25 PAD for LAN (gateway) Switched X.25 Private Switch Routing " " " " " " " " " " " Network Subscription NS HDLC RMT X25 HDLC Remote X.25 Proper Image Proper Network Service Access Point NSAP LOC Local System (AL object attribute) Proper Network User NU LOC X25 Local X.25 network Proper Im age Operator OP OP Operator Adm inistrative Proper 39 A2 32DN Rev0 2-5

26 CNS7-A2 NGL - Reference Manual Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Physical Connection PC ASY HDLC SYN CSMA Mapped onto the PL of the same type Connection object " " Physical Line PL ASY CSMA CSM CSM2 HDLC SYN X2 Asynchronous LAN proper LAN image LAN for Internet proper HDLC Synchronous X.2 Addressing " " " " " " X25 Profile PROFIL PAD PAD Descriptor Physical Subscription PS X2 Subscription Administrative Routing Information Base Entry RB CLNS CONS Connectionless Connection Oriented (automatically generated) Routing " Remote Network Service Access Point RNSAP CLNS CONS Connectionless Connection Oriented (RB object attribute) Routing " Statistic Block SB SBCT SBLC SBLH SBLS SBN SBN2 SBPH SBPS SBSR SBV All Controllers All Session Controls All Logical lines except 3270 VIP 3270, VIP logical lines DSA transport stations All other transport stations All physical lines except SYN SYN physical lines All session routes All Network Subscriptions Administrative Proper Session Control SC EQU LOC RMT Generalized equipment Local Remote Image Proper Image A2 32DN Rev0

27 Architecture Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY Sequence SEQ IN OUT SESS Input Output Session Descriptor Subscription Group SG X2 X.2 Subscription Group Administrative Terminal Station SN TMG Terminal Management Addressing Proper Session Route SR BAN DSA ISO "Generalized" DSA ISO Routing " " Start Up SU Unsolicited Message only Station Connection SX TMG Mapped onto SN of the same type Connection object System SY Transport Connection TC TC mapped onto TS, of the same type (DSA, DIWS, TGX, X25). Connection object Transliteration TRS Descriptor Transport Station TS CLNS CONS DIWS DSA IPNL LOC SX25 ISO with Internet ISO on X25 DSA/ISO Workstation DSA Null Internet Local Private Switch Image Image Image Image Image Proper Image Terminal Unit TU ASY PAD TGX VIP VPAD Asynchronous PAD TGX VIP VPAD Addressing Proper Mailbox Extension TX TMG Terminal Management Addressing 39 A2 32DN Rev0 2-7

28 CNS7-A2 NGL - Reference Manual Table 2-. (Cont'd) CNS Objects FAMILY/CLASS OBJECT MNEMONICS OBJECT TYPE NAME OBJECT TYPE DESCRIPTION COMPONENT CATEGORY User Descriptor UD TMG Terminal Management Descriptor User USER Descriptor Transport User UT ATS HOST ISO on DPS7 ISO on rem ote hostim age Im age Virtual Circuit Connection VC SW PER Switched VC Permanent VC Connection object Welcome Message W M TMG W elcome Message Image A2 32DN Rev0

29 Architecture 2.3 MAPPING DIAGRAMS The rest of this section shows the relationship between objects and how one is "mapped" to another. The following symbols are used: A B n This represents the principle that when an object A is declared, one of its param eters w ill be the map to B. A is therefore m apped onto B, and B is mapped from A. Here a list of Bs may be declared in one A. An image object is always shown in lower case. 39 A2 32DN Rev0 2-9

30 CNS7-A2 NGL - Reference Manual DJE (GCOS 7) accessing NJE (IBM* ) (BSC multi-leaving) MB STAT SN TMG LD TMG DV BSC LL BSC PL SYN n CT n MD (BSCDJE) BSC * IBM is a trademark of the International Business Machines corporation. Figure 2-. Application Access () A2 32DN Rev0

31 Architecture X.29 Access (via an X.25 network) (outgoing call) AX25 Access (via an X.25 netw ork) MB TMG n TX TMG n NR AX25 outgoing call incoming call NU X25 MB AX25 CO AX25 NR AX25 (incoming call) NU X25 SN TMG LD TMG DP TMG DV type n n CD TMG CO X29 CO X29 backup NR SX25 NS X25 PL type n LL BDL NR SX25 NS X25 LL type PL type n to terminal CT CT type to network to network Figure 2-2. Application Access (2) 39 A2 32DN Rev0 2-

32 CNS7-A2 NGL - Reference Manual DSA host OSI host NSAP GCOS 7 n LOC n n n SC LOC SC RMT n SR ISO TS DIWS NR LAN PL CSM n CB LAN PL CSMA CT RLNA UT HOST n SR ISO TS DIWS NR LAN PL CSM n CB LAN PL CSMA CT RLNA UT ATS CO ATS MB ATS SC RMT n SR ISO TS DIWS NR LAN PL CSM n CB LAN PL CSMA n CT RLNA DPS 7 with DSA session DPS 7 with OSI native session DPS 7 with OSI session relayed by ATS Figure 2-3. Local Host Connections A2 32DN Rev0

33 Architecture SC LOC TS LOC DSA System SC RMT SC LOC SC RMT n n SR SR DSA ISO n n TS DSA TS LOC TS DIWS n NR HDLC LL BDL PS RMT SG (I) X2 SG (O) X2 n n n n PS X2 PL PL X2 HDLC n n X.2 switched circuit CT Dedicated line ISO/DSA System n NS HDLC TS CLNS (no mapping) RNSAP CLNS n NE CLNS n NR IPHD OSI System (IP full) TS LOC NSAP LOC Figure 2-4. Remote Systems on an HDLC (LAPB) Line 39 A2 32DN Rev0 2-3

34 CNS7-A2 NGL - Reference Manual SC LOC TS LOC DSA System NS RMT PS RMT SG (I) X2 SG (O) X2 n n n n PS X2 PL X2 n SC RMT n SR DSA n TS DSA X.2 switched circuit SC LOC SC RMT n SR ISO n TS LOC TS DIWS CT Dedicated line PL HDLC n ISO/DSA System (cons) TS CONS (no mapping) TS LOC RNSAP NSAP CONS LOC n NE CONS n n n n n n NR NR NR SW NR SW PER (-CONS) IPSW n n n n NS X25 LL BDL ML MLP n LL SLP M ultilink Full OSI System (IP full) TS CLNS (no mapping) n n n NE CLNS Figure 2-5. Remote Systems on an X25 Network A2 32DN Rev0

35 Architecture SC LOC SC RMT n SR DSA n TS LOC NR HDLC n TS DSA n NR PER n n NR SW n n NS HDLC NS X25 NS RMT Master station LL SLV n LL MTPT LL MTPT Slave station PL HDLC n CT Figure 2-6. Remote Systems on HDLC NRM Links 39 A2 32DN Rev0 2-5

36 CNS7-A2 NGL - Reference Manual DSA System ISO/DSA System -NAT DSA SC LOC TS LOC SC RMT n SR ISO TS DIWS n SC RMT -NAT ISO SC LOC [-ISOPLG] TS LOC (IP Full) TS IPNL Full O SI System TS LOC (IP full) TS CLNS (no mapping) NSAP LOC RNSAP CLNS n n NE CLNS n NR LAN NR IPFL PL CSM n CB LAN PL CSMA n CT RLNA PL CSM2 Figure 2-7. Remote Systems on a LAN A2 32DN Rev0

37 Architecture DSA addressing DSA systems on X.25 X.2 addressing OSI addressing ISO/DSA systems NSAP LOC TS LOC CONS on X.25 IP full on X.25 IP full on HDLC IP full on LAN TS SX25 NU LOC [{-STID/-ISO}] NU X25 RNSAP CONS n n NE CONS n RNSAP CLNS n n NE CLNS n RNSAP CLNS n n NE CLNS n RNSAP CLNS n n NE CLNS n n NS RMT n NR SX25 ML MLP n NR SX25 n NS X25 NR SW (-CONS) n n LL SLP LL BDL PL HDLC n CT NR NR IPSW IPHD n NS HDLC NR IPFL PL CSM2 CB LAN PL CSMA n CT RNLA Figure 2-8. Switch Functions 39 A2 32DN Rev0 2-7

38 CNS7-A2 NGL - Reference Manual Mailboxes DV DV DV VIP n n n n n n MD MD MD MD VIP BSC TRS (IN) TRS (OUT) TRS (IN) TRS (OUT) TRS (IN) TRS (OUT) TRS (IN) TRS (OUT) DV BSC n CL VIP n TU VIP n Cluster controllers CL 3270 n LL LL LL LL VIP BSC PL SYN n CT Figure 2-9. Synchronous Devices on Line A2 32DN Rev0

39 Architecture Mailboxes TRS (IN) MD VIP TRS (OUT) DV VIP n n TU VIP n TRS (IN) MD TGX TRS (OUT) DV TGX n n TU TGX n Specific transport CL layer CL X25 TGX n n NR NR SW/PER SW/PER n n n n NS NS NS RMT X25 RMT ML MLP LL n BDL LL SLP PL HDLC n CT Figure 2-0. Synchronous Devices on an X25 Network 39 A2 32DN Rev0 2-9

40 CNS7-A2 NGL - Reference Manual Mailboxes n DV ASY n DV ASPI n MD ASY SEQ IN SEQ OUT TRS TRS (IN) (OUT) SEQ SESS TU* ASY * TU - may be used only for VIP 780 with attached printer LL ASY LL ASPI PL ASY n CT MD ASPI Figure 2-. Asynchronous Devices on a Line A2 32DN Rev0

41 Architecture PAD model can be selected with call number () NU X25 MB STAT PAD model can be selected with MB name MB TMG MB TMG MB STAT n n (3) TX TMG TX TMG n n SN Notes : SN TMG () TU used only for VIP780, TMG n with attached printer n LD (2) Mapping TU-PAD and DV-PAD LD TMG to NR-PAD is n to if NS-RMT TMG is not declared (3) Mapping TX to MB is to if PAD DP model is selected with MB name. DP TMG In this case NS-RMT must not be TMG n declared (see note (2)). n n n DV n DV DV n PAD DV PAD n n n n VPAD USER n (2) TU TU TU () PAD PROFIL PAD VPAD n (2) NR NR NR AX25 MD PAD PER ASY n n (no mapping) NS NS NS X25 RMT X25 SEQ SEQ SEQ IN OUT SESS LL ML LL BDL MLP BDL/HDLC TRS TRS PROFIL n (IN) (OUT) PL LL PL HDLC SLP HDLC n n CT CT MD ASPI DV ASPI LL ASPT Figure 2-2. Asynchronous Devices on a PAD 39 A2 32DN Rev0 2-2

42 CNS7-A2 NGL - Reference Manual NU LOC DV PAD n ** MD PROFIL TU* ASY PAD ** SEQ IN SEQ OUT PROFIL NR LPAD TRS (IN) TRS (OUT) SEQ SESS NS RMT SC RMT n SR ISO n TS DIWS *TU - may be used only for : VIP780 ** "n" if no NS-RMT Mailbox n with attached printer DV USER NR LAN PL CSM n CB LAN PL CSMA n Gateway System Towards T.M. system NU X25 NR SLAN n n n ML MLP n LL SLP CT RNLA NU LOC Towards PAD device NU X25 n NR SX25 NS X25 LL BDL PL HDLC n CT Figure 2-3. PAD Devices on an E-LAN A2 32DN Rev0

43 Architecture Without MB extension With MB extension The DEVICE macro The Operator's Console MB STAT SN TMG n LD TMG n DP TMG n DV type n MB TMG n TX TMG n DEVICE type MB STAT SN TMG LD TMG DV type MB STAT SN TMG LD TMG DV LOC MD (DKULOC) ASY to terminal to terminal Figure 2-4. Secondary Network Local Configuration 39 A2 32DN Rev0 2-23

44 CNS7-A2 NGL - Reference Manual Welcome Message GENERAL MAPPING MB STAT SN TMG n LD TMG n DV type MB TMG n TX TMG n CO TMG CO TMG CD TMG UD TMG LN TMG n KR GUS MB SN TMG LD TMG DV type WM TMG DEFAULT MAPPING default CD default LN LOGIN AND CONNECTION VARIATIONS LOGIN command LOGIN command CONNECT command CONNECT command LN TMG UD TMG CD TMG CO TMG CD TMG LN TMG CO TMG CD TMG CO TMG CD TMG Figure 2-5. Terminal Connection Procedures A2 32DN Rev0

45 Architecture ASPI PAD Mailbox Mailbox n NS RMT DV ASPI LL ASPI NR PAD n Via a switched virtual circuit n MD ASPI NS X25 LL BDL PL HDLC n CT NMLC n n DV ASPI LL ASPV NR PER n Via a permanent virtual circuit NS RMT Figure 2-6. ASPI Devices on a PAD 39 A2 32DN Rev0 2-25

46 CNS7-A2 NGL - Reference Manual NODE ADMINISTRATOR n AG NOI n AC NOI n FL IN/OUT AF NAD n AG NCC n AC NCC n FL IN/OUT n AG ASF n AC ASF n FL OUT NETWORK OPERATOR INTERFACE n AG NAD n AC NAD ON LINE SYSTEM GENERATOR AF NOI n FL OUT n AG OP n OP OP n FL IN/OUT n FL IN/OUT ADMINISTRATIVE STORAGE FACILITY AF ASF LG LG n FL OUT IN/ON LINE TESTS TL TL MB USER AF SYSG Figure 2-7. Administration A2 32DN Rev0

47 3. Generation Files - Basic Requirements and Methodology 3. INTRODUCTION This section gives general guidelines about what to do before a system builder generates the system software and network configuration. The preliminary actions are described in stages aimed at helping the system builder to: organise the network, create the generation files, describe the hardware configuration and the user-available functions using NGL directives in the generation files. Finally, to show the method, an example of a network configuration and corresponding generation is provided. 39 A2 32DN Rev0 3-

48 CNS7-A2 NGL - Reference Manual 3.2 GENERATION The generation is done using 2 to 3 generation files. These files will contain generation directives that describe the networking environment (the systems and their interconnections) and the permitted resources. The directives represent static logical and physical DSA objects and their mappings (the relationships between objects). There are two kinds of generation files:. The main system generation file used to build the basic configuration. 2. Two optional files used to declare the correspondents of type EQU and ISO primary network. These files are processed at starting time. They are referred in the GO card in -EQ <file_name> and -RIB <file_name> parameters. Notes:. The session Control object of type EQU can be declared in the main system generation file. 2. The ISO primary network must be declared in the RIB file A2 32DN Rev0

49 Generation Files - Basic Requirements and Methodology 3.3 METHODOLOGY To simplify the generation, the following steps should be carried out:. Define at which level a remote system will interface with your system. 2. For the connection and use of terminals with CNS 7, see the CNS 7 Terminal Management Reference manual. 3. Document all details about your system's physical configuration. For example, the physical links, line speeds and terminal characteristics. 4. Draw the network (or possible variants) illustrating the network systems, the various intersystem links and the terminals connected. This is useful when a mixture of communication line types is used (e.g., X.25 public data network connections, private X.25 network connections, local area network connections, etc.). 5. Define your system's visibility of the network in terms of computers, terminals and applications and their interconnections. Administrative facilities must also be considered. 6. Create the generation file on the Bull DPS 7000 host. This is done using the FPG7 generation facility (see FPG7 User's Guide). For information on the directory name and the files used for generation from the Bull DPS 7000, see "Generation File Structure" later in this Section. For further details see the GCOS 7 Network Operations manual. 7. To modify or add to the file which FPG7 has created, you can use either: - FSE (Full Screen Editor), or - EDIT. to declare directives, as described in this manual. The use of either depends on the software in use. For example, modifications may be required for: - non-standard device models, - administrative filters (FL), - backup possibilities, - use of some non-default values, - non-standard LANG or other files. 39 A2 32DN Rev0 3-3

50 CNS7-A2 NGL - Reference Manual 3.4 CNS 7 GENERATION FILE STRUCTURE The generation file must have the following structure: CNS 7 <sysgen_identif> -EOS <unbundling string> (note that the <unbundling string> is supplied with the software). The CNS 7 directive is mandatory. It must be the first directive declared in the generation file. FILE DECLARATIONS must be included if the files required have names that are different from the default. Default names are: DIR BLIB LKFL SLIBCHXMOD TBFL BLIBYTABLE PATCH SLIBPATCH PATCH2 SLIBPATCH2 TMP TEMP LANG <language name> -MESFIL <messages file name> -KEYFIL <keywords file name>. Object declaration. For further details on how to arrange the objects for the network organization, see Declaring the Objects, below. END <options>. The END directive is mandatory. It is the last directive of any generation file and is used to define where the generation is to be saved. For information on where to find the file in which the absolute memory image will be stored, refer to the GCOS 7 Network Operations manual A2 32DN Rev0

51 Generation Files - Basic Requirements and Methodology 3.5 NODE GENERATION LANGUAGE The Node Generation Language (NGL) of CNS 7 has a set of directives. Each directive is used to define one object and to assign explicit or default values to their attributes. The general syntax of a directive is: <directive-name> <object-name> <object-type> <list-of-attributes> Directive names are identical with the family names of the objects that they configure. Each directive starts with two mandatory positional parameters (i.e., name and type of object). These are followed by other attribute values, introduced by keywords. The keywords can be entered in any order. The attribute list depends on the object type. As well as the directives which define each object, there is also a set of directives that define the configuration. General configuration directives (see figure 3-) and object generation directives (see figure 3-2) are summarized and shown in detail on the following pages. Configuration examples are also shown. Two objects of the same family must have different names. Also, CB, LL and PL objects must not have the same names Symbols Used The following symbols are used in the commands: UPPER CASE CHARACTERS lower case characters Brackets [ ] Braces {} Reserved word or symbol Symbolic name or value Optional parameter One of the enclosed entries must be selected. Brackets and braces [{}] One of the enclosed entries (separated by ) may be selected, but all are optional. The default parameter is underlined. Parentheses Underlining Vertical bar (min,max) default. Show minimum, maximum and default values. If no values are specified, values between 0 and are assumed. Shows the default parameter Separates a list of parameters for choice 39 A2 32DN Rev0 3-5

52 CNS7-A2 NGL - Reference Manual Parameter Values For the commands, the parameter values are as follows: v Decimal or hexadecimal values will be accepted. Hexadecimal is represented by X'v' (e.g., X'2F'). If there is no specific indication, a value can be between 0 and or X'FFFF'. addr The physical address. It may be entered either as a decimal or a hexadecimal value. If hexadecimal, the format X'addr' is used. Leading zeroes are accepted. id-code A hardware identifier that is entered as a string of 4 characters. name A user-defined alphanumeric string (including _ and $) of to 4 characters. If less than 4 characters are entered, trailing blanks are added by the system. This string may be from to 8 characters for the following: - Connection Descriptor (CD). - Correspondent (CO). - Logon Descriptor (LN). - Mailbox (MB). - Model (MD). - User Descriptor (UD). string v : v2 A user-defined alphanumeric string (including _ and $). If less than the maximum number of characters are entered, trailing blanks are added by the system. A network address entered as decimal or hexadecimal values Multiline Directives Directives can be continued across multiple lines or records. To show continuation, enter the ampersand (&) as the last character of the line. The end of the directive is indicated by no ampersand Multi-Directive Line It is possible to have more than one directive per line, provided each directive is separated by a semi-colon (;) A2 32DN Rev0

53 Generation Files - Basic Requirements and Methodology Mapping Mapping is a relation that exists between two objects. In some directives the name of an object to which another object is mapped is introduced by a keyword. When this keyword and the associated object names are optional, the described object will be generated with the status ENBL if no mapping is given. MAP shows the first mapping (or first mapped object). MAP2 refers to the second mapping (or second mapped object) Comment Lines Comments may be introduced into a generation file by initiating a record with the characters '&*' (ampersand asterisk) or '&b' (ampersand space). A record initiated with '&' and not followed by '*' or 'b' (space) will result in a syntax error message. Object Generation Directives Directive CNS7 DIR LKFL TBFL PATCH PATCH2 TMP LANG LINK END Fonction Provides a description of the system. Defines directories used during system generation. Defines the name of a separate file containing LINK directives. Defines the table file. Describes the first patch file. Describes the second patch file. Defines directories of temporary files used during system generation. Defines the language used. Defines the list o modules and the conditions under which they are to be incorporated during system generation. Ends the configuration file. 39 A2 32DN Rev0 3-7

54 CNS7-A2 NGL - Reference Manual (Cont'd) Object Generation Directives Directive AC AF AG AP CB CD CL CO CT DEVICE DP DV EX FL LD LL LN MB MD ML NE NR NS NSAP NU OP Fonction Defines an Administrative Correspondent. Defines an Administrative Function. Defines an Administrative Group. Defines an Application. Defines a Cable. Defines a Connection Descriptor. Defines a Cluster. Defines a Correspondent. Defines a Controller. Macro instruction for terminal definition. Defines a Device Pool. Defines a Device. Defines the parameters of the executive. Defines a Filter. Defines a Logical Device. Defines a Logical Line. Defines a Login Descriptor. Defines a Mailbox. Defines a Model. Defines a Multilink Object. Defines a Network Entity*. Defines a Network Route. Defines a Network Subscription. Defines a Local Network Service Access Point. Defines a Network User. Defines an Operator A2 32DN Rev0

55 Generation Files - Basic Requirements and Methodology (Cont'd) Object Generation Directives Directive PL PROFIL PS RNSAP SB SC SEQ SG SN SR TRS TS TU TX UD USER UT WM Fonction Physical Line. Defines a PAD profile. Defines a Physical Subscription. Defines a Remote Network Service Access Point*. Defines a Statistic Block. Defines a Session Control. Defines special Terminal Manager actions associated with characters processed from/to an asynchronous terminal. Defines a Subscription Group. Defines a Terminal Station. Defines a Session Route. Defines Transcoding tables for a device model. Defines a Transport Station. Defines a Terminal Unit. Defines a Mailbox Extension. Defines a User Descriptor. Defines data of the call packet (PAD). Defines a Transport User. Defines a Welcome Message. * NE and RNSAP must be declared in the RIB file. 39 A2 32DN Rev0 3-9

56 CNS7-A2 NGL - Reference Manual 3.6 DECLARING THE OBJECTS A CNS 7 directive must be declared in the generation file. Subsequently other directives must also be declared describing the following: the particular hardware configuration, the different network elements, the functions that will be available. To build a coherent image of the network it is recommended that you declare the directives in the order described below Automatic creation of Objects Some objects are automatically created by CNS 7 as if the user has entered the following directives in the generation file: CO $ECHO CD $ECHO SC NOL LOC -ADDR 0:0 MB $NASF ADM MB $NOI ADM MB $NOIAEP ADM MB $LOGFILE ADM TS EXET LOC -ADDR 0:0 SB SBCC SBCC -SAMIN 80 SB SBSR SBSR SB SBLS SBLS SB SBLH SBLH SB SBN SBN SB SBN2 SBN2 SB SBV SBV SB SBLC SBLC SB SBCT SBCT SB SBPS SBPS SB SBPH SBPH SC EQU EQU SB SBEX SBEX WM LOC TMC AL ALDF LOC MB $NSE USER -CNx VSEQY -N0_SES MB $NSF USER -CNx VSEQX -N0_SES MB $ECHO USER -CNx VSEQO RNSAPB RBCN CONS RNSAPB RBCL CLNS NU CON X25 Note: The user must NOT enter these directives in his system generation file A2 32DN Rev0

57 Generation Files - Basic Requirements and Methodology Declare the Local System a. To declare the local DSA system: Session Control: SC name LOC -ADDR v:v2 The name and the values of v:v2 must be unique throughout the network. b. If the primary DSA network function is to be in the system, you must describe the local transport station as follows: TS name LOC -ADDR v:v2 -NET string The values of v:v2 and string must be unique throughout the network. c. If the non-dsa X.25 network function is to be available in the system, you must describe the local network user as follows: NU name LOC -CALL string NU name LOC -CALL string -ISO The name given to the digit string must be unique throughout the private network. The -ISO parameter is used to distinguish between DIWS and ISO. d. If the local system is used in full ISO network, you must describe the local address by: NSAP <NSAP_address> LOC... Also you must use the two directives TS -CLNS and TS -CONS to store the specific transport parameters Define the Controllers For example: CT name RLNA -PHAD addr CT name DCBE -PHAD addr CT name DCA -PHAD addr CT name DCE -PHAD addr 39 A2 32DN Rev0 3-

58 CNS7-A2 NGL - Reference Manual Declare the Lines for the Primary Network and Associated Functions a. Example for a leased line used as a point-to-point link: NS name HDLC -LL name LL name BDL -PL name PL name HDLC -PHAD addr -CT name b. Example for a leased line used as an X.25 link: NS name X25 -NBVC v -LL name [-NTW string] LL name BDL -PL name PL name HDLC -PHAD addr -CT name c. Example for a leased line used as a multi-point link, the local system being the master station (-PRIM): LL name MTPT -LAPN -PL name -PRIM PL name HDLC -PHAD addr -CT name d. Example for a leased line used upon a multi-point link, the local system being the secondary station (-SECD): LL name MTPT -LAPN -PL name -SECD v PL name HDLC -PHAD addr -CT name e. Example for a local area network: CB name LAN -PL name PL name CSMA -CT name Note: CB, LL and PL names must not be identical. It is recommended to use the ETHERNET address configured in the PROM of the first LNA controller, instead of the -ETHAD parameter Declare the Configuration to Access Host System, and Associated Functions For example: SC name RMT -ADDR v:v2 -SR name SR name ISO -TS name TS name DIWS -NR name NR name LAN -PL name PL name CSM -ETHAD v -CB name PL name2 CSM2 -CB name CB name LAN -PL name3 PL name3 CSMA -CT name CT name RLNA -PHAD addr A2 32DN Rev0

59 Generation Files - Basic Requirements and Methodology Declare the Other DSA Remote Systems and the Way to Access Them The name and values of v:v2 in SC and the values of v:v2 in TS must be unique for the network and correspond respectively to the name, v:v2 of the SC LOC and TS LOC in the remote system: a. X.25 point-to-point SC name RMT -ADDR v:v2 -SR name SR name DSA -TS name TS name DSA -ADDR v:v2 -NR name Also for a switched virtual circuit (SVC) on a public data network you must declare: NR name SW -NS name -RMT name NS name RMT -CALL String Or, for an X.25 permanent virtual circuit (PVC): NR name PER - LCN v -NS name b. HDLC multipoint SC name RMT -ADDR v:v2 -SR name SR name DSA -TS name TS name DSA -ADDR v:v2 -NR name NR name HDLC -NS name NS name HDLC -LL name LL name SLV -SECD v -LL name where name is the name of LL MTPT with parameter -PRIM of the primary station. c. X.25 multipoint SC name RMT -ADDR v:v2 -SR name SR name DSA -TS name TS name DSA -ADDR v:v2 -NR name NR name SW -NS name NS name X25 -DCE -NTW DSA -NBVC v -LL name LL name SLV -SECD v -LL name d. X.25 switch If CNS 7 also has the X.25 switch function to route X.25 calls between DSA systems, the access to it should be described as follows: TS name SX25 -ADDR v:v2 -NR name NR name SX25 -NS name The value of v:v2 is the same as in the target system's TS DSA directive. 39 A2 32DN Rev0 3-3

60 CNS7-A2 NGL - Reference Manual Declare the ISO/DSA Workstations First configure the remote ISO systems. a. Connection via X.25 SC name RMT -NAT ISO -SR name SR name ISO -TS name TS name DIWS -NR name NR name SW -NS name -RMT name2 NS name2 RMT -CALL String If over a Public Data Network, name defines the local PDN network subscription, and name2 the NS of the remote ISO station. This may also be done for private X.25. b. Connection via E-LAN SC name RMT -NAT ISO -SR name SR name ISO -TS name TS name DIWS -NR name NR name LAN -PL name PL name CSM -ETHAD v -CB name In both cases, the local system must have the -ISOPLG parameter declared in the SC LOC directive Non-DSA Remote Systems Using the local System as a switch If non-dsa remote systems (ISO) are using the local system as an X.25 switch, the following should be used: NU name X25 -CALL String -NR name NR name X25 -NS name NR name SLAN -SC name (on X.25) (on LAN) String is the complete X.25 address (complementary address included, if any) for the remote system. Zeroes are significant in the X.25 address A2 32DN Rev0

61 Generation Files - Basic Requirements and Methodology Declare the Other Remote ISO Systems The name and value of the NSAP of remote systems and the way to access them through the NE must be declared for both types of network services, CLNS and CONS. The directives used are RNSAP and NE which must be in the RIB file referred in the GO card. Example: RNSAP name CLNS -NEES name -NEIS name2 NE name CLNS -NR name NE name2 CLNS -NR name -NET string NR name2 IPSW -NS name2 NR name3 IPFL -PL name PL name CSM2 -CB ETH RNSAP name3 CONS -NEMAIN name4 -NEBACK name5 NE name4 CONS -NR name NE name5 CONS -NR name NR name SW -NS name Example of GO card used at load time: GO... -RIB <CONF subfile_name> Declare the Statistics Blocks See Sections 4 and 6 of this manual, as this is a part of the administration Declare the Terminal Model Types To Be Used This is done using the MD directive. This introduces the parameters of a device model, for example: MD DKU700 ASY All models (standard and non-standard) must be declared. For further details see the description of the MD directive in Section A2 32DN Rev0 3-5