QN-920-1

Q-NET

QUICS IV ICCP

CONFIGURATION GUIDE

January 1997

QEI, Inc
60 Fadem Road
Springfield, NJ
07081
Copyright c 1997 by QEI Inc.
Q-Net ICCP Configuration Guide
Software Version: QUICS IV QR6.0
All rights reserved.

NOTICE

The information in this document has been carefully checked and is believed to be
accurate. However, no responsibility is assumed or implied for inaccuracies.
Further more, QEI, Inc. reserves the right to make changes to any products herein
described to improve reliability, function or design. QEI, Inc. does not assume
liability arising our to the application or use of any product or circuit described
herein; neither does it convey any license under its patent rights nor the rights of
others.

This manual and all data contained constitutes proprietary information of QEI,
Inc. and shall not be reproduced, copied of disclosed to others, or used as the basis
for manufacture without written consent of QEI, Inc.

QEI, Inc
60 Fadem Road
Springfield, NJ
07081
 QN-920-1
REVISIONS
S)))))))))))))))))))))))))))))))))))))))))))))))))))))))))Q
Rev. Description Date
W44444444444444444444444444444444444444444444444444444444444444U
A Released to Production. 1/97
S))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))Q
B
S)))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))Q

ICCP CONFIGURATION
____________________________________________

November 28, 1996

This manual describes how to configure a system for ICCP.

The software described in this document is furnished under license and may only be used
or copied in accordance with terms of such license.

QEI, Inc
60 Fadem Road
Springfield, NJ
07081
 _______________________________
___
Content

Introduction 1
1.1 Configuration Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

OSI Transport Templates 3

2.1 NET$CONFIGURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Verifying NCL script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Verifying Transport Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

OSIT$NAMES Table 5

3.1 Defining NSAPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2 Showing Defined NSAP Logicals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SUIC.DIB 7

i
ICCP Configuration
ii

4.1 Local Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.2 Local DIB Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Remote DIB Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Session Manager 10

5.1 Installing QNetConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.2 Installing QNetMsg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3 Installing NewMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

QNetConfig 11

6.1 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6.2 Client Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.3 Server Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Config.A 15

7.1 Scan Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7.2 Communication Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Optional Software 16

8.1 OPTTSK.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.2 OPTRUN.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

ii
ICCP Configuration
ii
 1
_________________________________________________
Introduction

This manual outlines a step wise approach to configuring a system for ICCP. The implementation and database
entry requirements for ICCP are described in QUICS IV ICCP FUNCTIONAL SPECIFICATION ( Qnet
QN-920).

1.1 Configuration Outline

The following steps outline the requirements to configure a system for ICCP. Generally, the steps should be
followed in the order listed, however, some steps may be performed in various orders. This procedure assumes that
OpenVMS, QUICS IV SCADA and ICCP images have already been installed on the system.

1. Agree upon the Bilateral Table with the remote system administrator. That is, decide which variables will
be accessed, Domain names, the NSAP(s) of each system, local and remote object names, etc.

2. Install and configure DECnet/OSI as per the DECnet/OSI Installation Guide.

3. Disable the OSI Time Server.

4. Configure OSI Transport Templates. See Chapter 2 OSI Transport Templates.

5. Reboot the system if not done in the previous step.

6. Define NSAP logicals in OSIT$NAMES table. See Chapter 3 OSIT$NAMES Table.

7. Edit SUIC.DIB to define Local Network Address, Local DIB Entries and Remote DIB Entries. See
Chapter 4 SUIC.DIB.

8. Add QNetConfig, QNetMsg and NewMessage to the Session Manager. See Chapter 5 Session Manager.

1
ICCP Configuration
2

9. Using the QNetConfig windows define each remote system to be connected. This may include the Client
Window and or the Server Window. See Chapter 6 QNetConfig.

10. Edit CONFIG.A and CONFIG.B to define communication line devices and scan tasks. See Chapter 7
CONFIG.A.

11. Edit OPTTSK.COM and OPTRUN.COM to define and run each ICCP Server defined. See Chapter 8
Optional Software.

This concludes the steps for ICCP system configuration. The database for ICCP may now be entered as described
in the QUICS IV ICCP FUNCTIONAL SPECIFICATION.

To simplify database entry for the ICCP Server, the following editors are required:

! STNED
! QLINK
! HSLIST
! QNetConfig Server Window

To simplify database entry for the ICCP client, the following editors are required:

! STNED
! TXPARS
! RNAMES (if necessary)
! QNetConfig Client Window

2
2ICCP Configuration
 2
_________________________________________________

OSI Transport Templates

2.1 NET$CONFIGURE

The MMS layer of ICCP requires that two transport templates be configured for OSI. The
NET$CONFIGURE.COM command file with the ADVANCED option is used to configure a
template. Without duplicating all the information by this procedure, only the highlights will be
displayed. User input is indicated by bold text.

Note that the following transcript was produced with version 6.1 of OSI. If the version of OSI that you
installed was not 6.1 or different OSI options where selected during installation, your transcript may
appear different. In most cases you can simply select the default presented.

$ @SYS$STARTUP:NET$CONFIGURE ADVANCED.

…Welcome blurb…

* Do you wish to continue? [YES] : <RETURN>

…Checksum blurb…

Configuration Options:
[0] Exit this procedure
[1] Perform an entire configuration
[2] Change node name/name space name
[3] Configure Device on this machine
[4] Configure Transports
[5] Configure Time zone Differential Factor

3
ICCP Configuration
4

[6] Configure Event Dispatcher

[7] Configure Application database
[8] Configure MOP Client database
[9] Configure Cluster Alias

* Which configuration option to perform? [1] : 4

* Configure the NSP Transport? [YES] : <RETURN>
* Configure the OSI Transport? [YES] : <RETURN>
* Do you want to replace the existing NSP transport script? [NO] : YES
* Do you want to replace the existing OSI transport script? [NO] : YES
* Username for OSI loopback test application to use? [SYSTEST] : <RETURN>
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates
* Do you wish to create additional OSI templates? [NO] : YES
* Name of the template? [OSI$DEC_Default0] : OSIT$OSIMMS
(Select all the defaults for the OSIT$OSIMMS transport template)
* Do you wish to create additional OSI templates? [NO] : YES
* Name of the template? [OSI$DEC_Default1] : OSIT$SPARE
(Select all the defaults for the OSIT$SPARE transport template)
* Do you wish to create additional OSI templates? [NO] : <RETURN>

…Configuration summary blurb…

* Do you wish to generate NCL configuration scripts? [YES] : <RETURN>

…Modification information blurb…

…Configuration Options as above…

* Which configuration option to perform? [0] : <RETURN>

2.2 Verifying NCL script

The OSI transport startup script can be verified for correctness by typing or editing the following file:
SYS$STARTUP:NET$OSI_TRANSPORT_STARTUP.NCL

SISCO recommends that the Keep Alive timer should be set to a lower value than the default value
of 60. T he following lines should be added to the bottom of
NET$OSI_TRANSPORT_STARTUP.NCL file.

4
4ICCP Configuration
 Set Node 0 OSI Transport Template Default KeepAlive Time 15
Set Node 0 OSI Transport Template OSIT$OSIMMS KeepAlive Time 15

The system must now be REBOOTED before continuing.

2.3 Verifying Transport Templates

The OSIMMS transport template that was configured above can be verified for correctness (after
rebooting) by typing the following command:

$ MCR NCL SHOW OSI TRANSPORT TEMPLATE OSIT$OSIMMS ALL

5
ICCP Configuration
6

3
_________________________________________________

OSIT$NAMES Table

3.1 Defining NSAPs

The MMS and OSI layers of ICCP share a logical name table called OSIT$NAMES. Each logical
name in this table has an equivalence string which represents the NSAP of a local or remote node. The
NSAP logical is in turn, used as part of the complete client or server address specification in the
SUIC.DIB file (described in the next section).

The NSAP logical names are defined in SYS$STARTUP:OSIT$NAMES.COM. This file is

executed at system startup. The format of each entry in this file is as follows:

$ DEFINE/TABLE=OSIT$NAMES logical_name nsap

where
logical_name is the name of the logical
nsap is the actual NSAP (with all punctuation removed)

For example:

$ DEFINE/TABLE=OSIT$NAMES KAYAK$NSAP 490001AA000400AA0421

$ DEFINE/TABLE=OSIT$NAMES CNP$NSAP 49000202608C2DF6C401

The name you choose for logical_name is arbitrary. However, it is a good idea to follow some sort
of format. In the above example, the node or system name was incorporated into the logical name
along with the word NSAP to identify it as such.

The remote NSAP can be acquired from the system administrator of the remote system.

6
6ICCP Configuration
 The local NSAP can be determined by typing the following command. In the example output, the local
NSAP (complete with punctuation), is on the bolded line, where the address ends with "21”.

$ MCR NCL SHOW

Node 0
at 19996-11-19-22:24:42.870-05:00Iinf

Identifiers

Name = LOCAL:.KAYAK
Address =
{
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3 , number = 19 ] ,
[ DNA_OSItransportV1 , ‘DEC0’H ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-AA-04:21 (LOCAL:.KAYAK) ]
),
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV2 , number = 19 ] ,
[ DNA_OSItransportV1 , ‘DEC0’H ] ,
[ DNA_IP , 0.0.0.0 ]
),
(
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV3 , number = 19 ] ,
[ DNA_NSP ] ,
[ DNA_OSInetwork , 49::00-01:AA-00-04-00-AA-04:20 (LOCAL:.KAYAK) ]
)
}

3.2 Showing Defined NSAP Logicals

After the SYS$STARTUP:OSIT$NAMES.COM file has been executed (normally at system startup),
the following command can be used to show the currently defined NSAPs:

$ SHOW LOGICAL/TABLE=OSIT$NAMES

7
ICCP Configuration
8

8
8ICCP Configuration
 4
_________________________________________________

SUIC.DIB

The MMS layer of ICCP requires a definition of all nodes in a computer network to which a local
computer may wish to connect. All local and remote connections must be configured. This information
is configured in the file SUIC.DIB. A sample copy of SUIC.DIB may be found in
MG:[UCA.INSTALL] and must be copied to SYS$STARTUP.

Edit the file SYS$STARTUP:SUIC.DIB using a text editor. There are three sections to this file. The
Local Network Address, Local DIB Entries and Remote DIB Entries. Each section in turn is described
below:

4.1 Local Network Address

Section 1 contains the network address (NSAP) logical name of the local node. Only one NSAP may
be specified in this section. This logical name must also be defined in the OSIT$NAMES logical
name table. An example of this section follows:

$ Local Network Address

/KAYAK$NSAP/

4.2 Local DIB Entries

9
ICCP Configuration
10

Section 2 contains the local AR NAME information. There is one entry for each client process and
one entry for each server process that will be active on this computer. Each entry in the network must
be unique. The format of each entry is as follows:

/AR_Name/AP_Title/AP_invoke_id/AE_qual/AE_invoke_id/p_sel/s_sel/t_sel/
where:

AR_Name
This required field is the Application Reference Name. This is the network object name that the client or server declares
itself as. This same name is also entered as the Local Object Name in QNetConfig, which is described in sections
6.2 Client Window and 6.3 Server Window.

AP_Title

This is an optional field, however, it is almost always used. It is an Object Identifier representing the Application
Process Title given to this application. It is a series of up to 16 digits. Its typical use is as follows. The first value
is usually 1 (the valid range is 0 to 2). The second value is usually 1, 2 or 3 (the valid range is 0 to 39). The third
value is open for international assignment. For local addressing (always the case), use 9999. The rest of the values
are arbitrary, however, a standard format is recommended. Such as a two digit invocation instance identifier (similar
to a communication line number). An example of an AP_Title is /1 3 9999 37/ where 37 is the invocation instance
identifier.

AP_invoke_id

This optional field is used to identify an invocation instance of the Application Process. Suggest leaving this field
blank.

AE_qual

This optional field is used to qualify the Application Entity. Suggest using the two digit invocation instance of the
AP_Title.

AE_invoke_id

10
ICCP Configuration
10
 This optional field is used to identify an invocation instance of the Application Entity. Suggest leaving this field
blank.

p_sel

This required field represents the Presentation Selector used to select the appropriate application layer services.
There is no significant meaning attached to the selectors, they are arbitrarily assigned. Suggest the field should be
at least four digits long, using leading zeros. Suggest that p_sel, s_sel and t_sel be the same for an invocation
instance, the next invocation instance would be incremented by 1. For example, the first Local DIB Entry would
have a p_sel, s_sel and t_sel of /0001/0001/0001/ and the next entry would be /0002/0002/0002/. Also see the Local
DIB Entry example below.

s_sel

This required field represents the Session Selector used to select the appropriate presentation layer services. For
suggested use see p_sel.

t_sel

This required field represents the Transport Selector used to select the appropriate session layer services. For
suggested use see p_sel.

A Local DIB Entry example follows:

$ Local DIB Entries

/EMC_CLIENT/1 3 9999 10//10//0001/0001/0001/
/EMC_SERVER/1 3 9999 11//11//0002/0002/0002/

4.3 Remote DIB Entries

Section 3 contains the remote AR NAME information. There is one entry for each remote to be
recognized locally. Depending upon the implementation at the remote site, there may be one entry for
each client process and one entry for each server process or there may be one entry for both the client
and server or some variation. The format is as follows:

11
ICCP Configuration
12

/AR_Name/AP_Title/AP_invoke_id/AE_qual/AE_invoke_id/p_sel/s_sel/t_sel/NSAP/

All the fields have the same meaning and suggested use as the Local DIB Entries except for those fields described below.
Each Remote DIB Entry must match exactly at the remote site.

AR_Name

The AR_Name of the Remote DIB Entry is the network object name that the client or server declares itself as. This
same name is also entered as the Remote Object Name in QNetConfig, which is described in sections 6.2 Client
Window and 6.3 Server Window.

NSAP

This required field is the network address (NSAP) of the remote node. This is a logical name that must be defined
in the OSIT$NAMES logical name table.

A Remote DIB Entry example follows:

$ Remote DIB Entries

/CNP_Client/1 2 30 2/100/2/1/0032/0001/0001/CNP$NSAP/
/CNP_Server/1 2 30 3/100/3/1/0033/0001/0001/CNP$NSAP/

12
ICCP Configuration
12
 5
_________________________________________________

Session Manager

5.1 Installing QNetConfig

To make QNetConfig accessible from the Application menu of the Session Manager, select the
Options item from the Session Manager window. From the Options menu select Menu. Add a new
entry with the name as QNetConfig and the command as @MG:[UCA.INSTALL]QNETCONFIG.
Then add this new entry to the Application list.

5.2 Installing QNetMsg

To make QNetMsg accessible from the Application menu of the Session Manager, select the Options
item from the Session Manager window. From the Options menu select Menu. Add a new entry with
the name as QNetMsg and the command as @MG:[UCA.INSTALL]QNETMSG. Then add this new
entry to the Application list.

5.3 Installing NewMessage

13
ICCP Configuration
14

To be notified of new ICCP messages from other systems, select the Options item from the Session
Manager window. From the Options menu select Menu. Add a new entry with name as NewMessage
and the command as @MG:[UCA.INSTALL]NEW_MESSAGE. Then add this new entry to the
auto start list. NewMessage will start automatically the next time the Session Manager is restarted.

This same procedure should be done to all operator stations receiving ICCP messages.

14
ICCP Configuration
14
 6
_________________________________________________

QNetConfig

The QNet Configuration editor defines the connections to other systems. For each connection to a remote system there
may be a local client and or a local server.

6.1 Main Window

The main editor window defines the name and description of the remote system. See Figure 6.1-1.

Each local ICCP client scan task has a QLnn logical (where nn is the communication line number). The equivalence
string is the name of remote system it will attempt to connect to. See Chapter 7 Config.A.

Each local ICCP Server has a CLIENT NAME field on the QLINK editor. This is the name of the remote system it will
attempt to connect to.

15
ICCP Configuration
16

Figure 6.1-1 Qnet

Configuratio
n M a in
Window

6.2 Client
Window

Local Client
Object Names
The Local
Client Object
Name is the
name of the local ICCP client scan task network object. This same name must also appear in a
Local DIB Entry in the SYS$STARTUP:SUIC.DIB. Note that this name is not the name of the
ICCP client scan task process. That name is ICCPnn where nn is the communication line number.

Remote Server Object Names

The Remote Server Object Name is the name of the remote ICCP Server network object to be
connected to. This same name must appear in a Remote DIB Entry in the
SYS$STARTUP:SUIC.DIB.

Domain
The Domain is the name of the data area at the server that contains variables accessible by this
client. The name cannot contain any spaces.

Mailbox
The Mailbox name is not required in the Client window.

Local Client Operator Stations

The Local Client Operator Stations are names of nodes on the LAN accessible by the ICCP client
scan task. SYSTEM is a special operator station where messages are raised as alarms and printed
on the event logger. InfoRef is the Information Reference number assigned to that operator
station. The numbers are arbitrary but must be agreed upon by both the local and remote site
administrators.

16
ICCP Configuration
16
 Figure 6.2-1 Qnet Configuration Client Window

6.3 Server Window

Local Server Object Names

The Local Server Object Name is the name of the local ICCP Server network object. This same
name must appear in a Local DIB Entry in the SYS$STARTUP:SUIC.DIB. Note that this name

17
ICCP Configuration
18

is not the name of the ICCP Server process. That name is ICCPSVnn where nn is the
corresponding QLINK record number.

Remote Client Object Names

The Remote Client Object Name is the name the remote ICCP client network object to be
connected to. This same name must appear in a Remote DIB Entry in the
SYS$STARTUP:SUIC.DIB.

Domain
The Domain is the name of the data area at the local server that contains variables accessible by
the remote client. The name cannot
contain any spaces.

Mailbox
The Mailbox name is required in the
Server Window. The format of the
name is ICCPMXnn where nn is the
corresponding QLINK record
number.

Remote Client Operator Stations

The Remote Client Operator
Stations can be the names of nodes
or systems or applications that can
receive messages from the local
ICCP Server. InfoRef is the
Information Reference number
assigned to that operator station. The
numbers are arbitrary but must be
agreed upon by both the local and
remote site administrators.

18
ICCP Configuration
18
 Figure 6.3-1 Qnet Configuration Server Window

19
ICCP Configuration
20

7
_________________________________________________

Config.A

The MG:[CONFIG]CONFIG.A and CONFIG.B files contain definitions for the SCADA system.

7.1 Scan Tasks

The section Define Scan Tasks contains definitions for each protocol being used in the system. Each
entry has the following format:

SCAN_TASKnn == “/image_name/logical_name/image_directory”
Where:
nn is the scan task entry number
image_name is the name of the scan task image
logical_name is the name of the scan task logical
image_directory is the directory containing the scan task image

An example entry follows:

$!
$ ! à Define Scan Tasks
$!
$ SCAN_TASK01 == “/I_ICCP/I_ICCP/UCA.IMAGE”

7.2 Communication Lines

20
ICCP Configuration
20
 The section Communication Lines contains definitions for each communication line defined in the
system. Traditionally, each entry contains the name and speed of the device. The ICCP Client is a
network scan task. Therefore, instead of entering a communication line device, enter the name of the
remote system to be connected to. This same remote system name must be defined in QNetConfig. See
Chapter 6 QNetConfig. The speed is not required, enter as a NULL string. An example follows:

$!
$ ! à Communication Lines
$!
$ COMLIN33 == “SIEMNS”
$ COMLIN_SPEED33 == “”

21
ICCP Configuration
22

8
_________________________________________________

Optional Software

8.1 OPTTSK.COM

The file MG:[CONFIG]OPTTSK.COM is used to define and install optional applications in the
SCADA system.

To define the ICCP Server add the following line to the file:

$ @MG:[UCA.INSTALL]ICCPSV

To define the TXPARS, QLINK, HSLIST and RNAMES editors add the following line to the file:

$ @MG:[HHSCAN.INSTALL]HHSCAN

8.2 OPTRUN.COM

The file MG:[CONFIG]OPTRUN.COM is used to start optional applications in the SCADA system.

For each ICCP Server to be automatically started at system startup add the following line to the file:

$ @MG:[UCA.INSTALL]ICCPSVRUN nn
Where:
nn is the QLINK record number of the ICCP Server

22
ICCP Configuration
22