qn-920-1 qnet configuration guide...desired qnet configuration record. 2. make sure the local client...

QN-920-1 QNET Configuration Guide

TDMS-Plus Master Station Software

December 2018

TDMS-Plus Master Station QN-920-1

Software QNET Configuration Guide

Copyright © 2016 QEI

Copyright © 2016 by QEI

QN-920-1 QNET Configuration Guide

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

reserves the right to make changes to any products herein described to improve reliability,

function or design. QEI does not assume liability arising from 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 constitute proprietary information of QEI and shall not be

reproduced, copied or disclosed to others, or used as the basis for manufacture without

written consent of QEI.

45 Fadem Road

Springfield, NJ 07081

Phone: (973) 379-7400

Fax: (973) 379-2138

Web Site: www.qeiinc.com

http://www.qeiinc.com/



Copyright © 2016 QEI Revisions i

Revisions

Revision Description Date

A Release to Production January 1997

B Revised per Marked Print September 2000

C Formatting Update August 2001

D Title Change to TDMS-Plus December 2004

E Updated for AQR 7.0.0 Release October 2006

F Latest Corrections June 2007

G Configuration Update December 2010

H Added section 7.4 March 2012

I Formatting Update August 2013

J Formatting Update April 2016

K Updated QEI Address December 2018



Copyright © 2016 QEI Contents i

Contents

1 INTRODUCTION ........................................................................1 1.1 Configuration Outline ........................................................... 1 1.2 Server Configuration Overview ............................................ 2 1.3 Client Configuration Overview ............................................. 3

2 OSI TRANSPORT TEMPLATES ...............................................5 2.1 NET$CONFIGURE .............................................................. 5 2.2 Verifying the NCL script ....................................................... 8 2.3 Verifying the Transport Templates ....................................... 9

3 OSIT$NAMES Table ................................................................11 3.1 Defining NSAPs ................................................................. 11 3.2 Showing Defined NSAP Logicals ....................................... 12

4 Configuring the SUIC.DIB File ...............................................13 4.1 Local Network Address ...................................................... 13 4.2 Local DIB Entries ............................................................... 13 4.3 Remote DIB Entries ........................................................... 15

5 Session Manager ....................................................................18 5.1 Installing the ICCP Pull Down Menu .................................. 18 5.2 Installing QNETConfig ....................................................... 19 5.3 Installing QNETMsg ........................................................... 20 5.4 Installing NewMessage ...................................................... 21

6 QNETConfig ............................................................................22 6.1 Main Window ..................................................................... 22 6.2 Client Window.................................................................... 22 6.3 Server Window .................................................................. 23

7 Master Station Configuration Changes ................................26 7.1 CONFIG.A and CONFIG.B files ......................................... 26

7.1.2 Adding the ICCP Scan Task ............................... 26 7.1.3 Adding ICCP Communication Lines .................... 26

7.2 OPTTSK.COM Modifications ............................................. 27 7.3 OPTRUN.COM Modifications ............................................ 28 7.4 Database Display Screen Modifications (for Q-Windows) .. 28

8 OpenVMS Resources .............................................................30 8.1 MODPARAMS.DAT Modifications...................................... 30 8.2 Transport connection ......................................................... 30 8.3 OpenVMS System Account Modifications .......................... 30

9 Appendix Notes ......................................................................31 9.1 PWIP driver configuration .................................................. 31 9.2 OSAK Configuration .......................................................... 33

9.2.1 Verify Installation of the OSAK Software ............. 33 9.2.2 Installing OSAK from HP OpenVMS CD ............. 33

9.3 OSI Timer Modifications .................................................... 34 9.4 SCADA Database Expansion............................................. 34



Copyright © 2016 QEI Configuration Outline 1

1 INTRODUCTION

This manual outlines a step-by-step approach to configuring a system for ICCP. The

implementation and database entry requirements for ICCP are described in the TDMS-PLUS

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, TDMS-Plus SCADA and ICCP

images have already been installed on the system.

Agree upon the Bilateral Table with the remote system administrator.

That is, decide which variables will be accessed, Domain names, the

NSAP(s)/IP(s) of each system, local and remote object names

Install and configure DECnet/OSI as per the DECnet/OSI Installation

Guide.

Install and configure TCP/IP, PWIP driver to support MMS-EASE over

RFC1006. See Appendix notes.

Install and configure for auto-start the OSAK network server. See

Appendix notes.

Disable the OSI Time Server. See Chapter 9 Appendix notes.

Configure OSI Transport Templates. See Chapter 2 OSI Transport

Templates.

Reboot the system if not done in the previous step.

Define NSAP logicals in OSIT$NAMES table (only if establishing an

ICCP-OSI connection…). See Chapter 3 OSIT$NAMES Table.

Edit SUIC.DIB to define Local Network Address, Local DIB Entries and

Remote DIB Entries. See Chapter 4 SUIC.DIB.

Add QNETConfig, QNETMsg and NewMessage to the Session Manager.

See Chapter 5 Session Manager.

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.

Edit CONFIG.A and CONFIG.B to define communication line devices and

scan tasks. See Chapter 7 Master Station Configuration Changes.

Edit OPTTSK.COM and OPTRUN.COM to define and run each ICCP

Server defined. See Chapter 7 Master Station Configuration Changes.

Adjust OpenVMS parameters and resources if the current configuration

of the OpenVMS is not adequate. See Chapter 8 on OpenVMS

Resources.

This concludes the steps for ICCP system configuration. The database for ICCP may now be

entered as described in the TDMS-PLUS ICCP FUNCTIONAL SPECIFICATION.



2 Server Configuration Overview Copyright © 2016 QEI

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

Remote Names Window (necessary for non-QEIICCP servers)

QNETConfig Client Window

1.2 Server Configuration Overview

The following diagram shows the relationship of configuration items for the ICCP server:

Server Configuration Checklist:

1. Make sure the QLINK record for the server contains the correct entry for the

Client Name field corresponding to the desired QNET configuration record.

2. Make sure the local server names are correct in the QNET configuration record

(Server Data tab) and match the desired AR names in the Local DIB Section of

the SUIC.DIB (Section 2).

3. Make sure the remote client names are correct in the QNET configuration record

(Client Data tab) and match the desired AR names in the Remote DIB Section of




Copyright © 2016 QEI Client Configuration Overview 3

4. Verify the Transport, Protocol, and Session Selectors for the local server entry

match the selectors that will be sent by the remote client and verify that the

Selectors are unique.

5. Verify the AE_qual setting for the local server AR entry to match the remote

client.

6. For multiple servers on a single system, verify the AR names and Selector values

are unique.

7. Verify that the AR names in the Remote DIB section match the requesting client

values (Selectors, AP_Title, AE_Qual, and NSAP).

8. Please note that the AR names in the SUIC.DIB are case-sensitive.

9. Make sure the data objects defined in HSLIST have the proper scope (VMD or

Domain) to match the remote client.

1.3 Client Configuration Overview

The following diagram shows the relationship of configuration items for the ICCP client:

Client Configuration Checklist:

1. Make sure the QLnn logical for the client (derived from CONFIG.x) equates to the

desired QNET configuration record.

2. Make sure the local client names are correct in the QNET configuration record

(Client Data tab) and match the desired AR names in the Local DIB Section of the

SUIC.DIB (Section 2).

3. Make sure the remote server names are correct in the QNET configuration record

(Client Data tab) and match the desired AR names in the Remote DIB Section of




4 Client Configuration Overview Copyright © 2016 QEI

4. Verify the Transport, Protocol, and Session Selectors for the local client match

the selectors that will be sent to the remote server and verify that the Selectors

are unique.

5. Verify the AE_qual setting for the local client AR entry to match the remote

server.

6. For multiple clients on a single system, verify the AR names and Selector values

are unique.

7. Verify the AR names in the Remote DIB section match the receiving server

values (Selectors, AP_Title, AE_Qual, and NSAP).

8. Please note that the AR names in the SUIC.DIB are case-sensitive.

9. Verify the data objects defined in Remote Names have the proper scope (VMD or

Domain) to match the remote server.



Copyright © 2016 QEI NET$CONFIGURE 5

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 8.2-1 of OSI. If the version of OSI

that you installed was not 8.2-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

Copyright 2003 Hewlett-Packard Development Company, L.P.

DECnet-Plus for OpenVMS ADVANCED network configuration procedure

This procedure will help you create or modify the management scripts

needed to operate DECnet on this machine. You may receive help about

most questions by answering with a question mark '?'.

You have chosen the ADVANCED configuration option. This option enables

you to do some specific tailoring of your system's network configuration

by answering some specific questions. If you do not want to do specific

tailoring of your system's network configuration but instead want to

quickly configure your system using most of the default answers, you

should invoke NET$CONFIGURE.COM with the BASIC configuration option, i.e.:

@SYS$MANAGER:NET$CONFIGURE BASIC

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

Configuration last run by SCADA on 9-OCT-2006 10:39:40.25

The following NCL script files have been modified since being created by this procedure:

SYS$SPECIFIC:[SYSMGR]NET$OSI_TRANSPORT_STARTUP.NCL;

This procedure may create a new version of these scripts or modify

information contained within them. In all cases, any previously

created NCL scripts are renamed to "file.NCL-OLD", so that you

may review any of the previous changes.



6 NET$CONFIGURE Copyright © 2016 QEI

Configuration Options for Node CSALPHA

[0] Exit this procedure

[1] Perform an entire configuration

[2] Change naming information

[3] Configure Devices on this machine

[4] Configure Transports

[5] Configure Timezone Differential Factor

[6] Configure Event Dispatcher

[7] Configure Application database

[8] Configure MOP Client database

[9] Configure Cluster Alias

[10] Replace MOP Client configuration

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

* Configure the NSP Transport? [YES] : <RETURN>

Answer YES to the next question if you wish to

change the current NSP transport configuration:

Maximum number of logical links 200

Maximum Transmit and Receive Window: 20

Maximum Receive Buffers: 4000

Flow Control Policy: Segment Flow Control

* Do you want to replace the existing NSP transport script? [NO] : YES

* Maximum number of logical links ? [200] : <RETURN>

* Maximum Transmit and Receive Window ? [20] : <RETURN>

* Maximum Receive Buffers ? [4000] : <RETURN>

* NSP flow control policy (SEGMENT, NO)? [SEGMENT] : <RETURN>

* Configure the OSI Transport or run over TCP/IP? [YES] : <RETURN>

Answer YES to the next question if you wish to

change the current OSI transport configuration:

Maximum number of logical links: 200



OSI applications over TCP/IP: Enabled

DECnet applications over TCP/IP: Enabled

* Do you want to replace the existing OSI transport script? [NO] : YES

* Maximum number of logical links ? [200] : <RETURN>

* Maximum Transmit and Receive Window ? [20] : <RETURN>

* Maximum Receive Buffers ? [4000] : <RETURN>

* Run OSI Applications over TCP/IP ? [YES] : <RETURN>

* Run DECnet over TCP/IP ? [YES] : <RETURN>

%NET$CONFIGURE-W-NODOMAIN, DECnet over IP requires DOMAIN in the directory

services list



Copyright © 2016 QEI NET$CONFIGURE 7

* Is this system operating in a multi-protocol network? [YES] : <RETURN>

* Username for OSI loopback test application to use? [SYSTEST] : <RETURN>

%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates

* Do you want to create additional OSI templates? [NO] : YES

* Type of network service (CLNS/CONS/RFC1006)? [CLNS] : <RETURN>

* Name of the OSI template? [OSIT$CLNS_Default0] : OSIT$OSIMMS

* Will this template be used for inbound packets? [YES] : <RETURN>

* Transport Classes to support? [4] : <RETURN>

* Allow use of expedited data? [YES] : <RETURN>

* Allow use of Checksums? [YES] : <RETURN>

* Use Full CLNP or Null Internet? [Full CLNP] : <RETURN>

* Do you want to create additional OSI templates? [NO] : YES

* Type of network service (CLNS/CONS/RFC1006)? [CLNS] : RFC1006

* Name of the OSI template? [OSIT$RFC1006_Default0] : OSIT$RFC1006

* Will this template be used for inbound packets? [YES] : <RETURN>

* Transport Classes to support? [0,2] : <RETURN>

* Allow use of expedited data? [YES] : <RETURN>

* Allow use of Checksums? [NO] : YES

* Local RFC1006 port number? [102] : <RETURN>

* RFC1006 listener port number? [102] : 102, 399

* Do you want to create additional OSI templates? [NO] : <RETURN>

Summary of Configuration

Node Information:

Directory Services Chosen: LOCAL

Primary Directory Service: LOCAL

Local Full name: LOCAL:.CSALPHA

Node Synonym: CSALPHA

Phase IV Address: 50.100

Phase IV Prefix: 49::

Session Control Address Update Interval: 10

Routing Node Type: ENDNODE

Autoconfiguration of Network Addresses: Enabled

Routing ESHello Timer: 600

Routing ES Cache Size: 512

Device Information:

Device: EIA0 (EI/82558):

Data Link name: CSMACD-0

Routing Circuit Name: CSMACD-0

Device: EIB0 (EI/82558):

Data Link name: CSMACD-1

Routing Circuit Name: CSMACD-1

Transport Information:

NSP Transport: Configured




Flow Control Policy: Segment Flow Control



8 Verifying the NCL script Copyright © 2016 QEI

OSI Transport: Configured




OSI applications over TCP/IP: Enabled

DECnet applications over TCP/IP: Enabled

Congestion Avoidance Disabled

Event Dispatcher Configuration:

Sinks: local_sink

Outbound Streams: local_stream

Phase IV Relay: Enabled

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

%NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by

NET$CONFIGURE

sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.

Your default namespace nickname is LOCAL.

Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00.

%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

Configuration Options for Node CSALPHA

[0] Exit this procedure

[1] Perform an entire configuration

[2] Change naming information

[3] Configure Devices on this machine

[4] Configure Transports

[5] Configure Timezone Differential Factor

[6] Configure Event Dispatcher

[7] Configure Application database

[8] Configure MOP Client database

[9] Configure Cluster Alias

[10] Replace MOP Client configuration

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

2.2 Verifying the 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. Also the maximum TPDU message size should be set to FLASE. The following

lines should be added to the bottom of NET$OSI_TRANSPORT_STARTUP.NCL file.

SET NODE 0 OSI TRANSPORT TEMPLATE DEFAULT SEND PREFERRED MAX TPDU SIZE FALSE

SET NODE 0 OSI TRANSPORT TEMPLATE osit$osimms SEND PREFERRED MAX TPDU SIZE FALSE

SET NODE 0 OSI TRANSPORT TEMPLATE osit$osimms KEEPALIVE TIME 15

SET NODE 0 OSI TRANSPORT TEMPLATE osit$rfc1006 SEND PREFERRED MAX TPDU SIZE FALSE

SET NODE 0 OSI TRANSPORT TEMPLATE osit$rfc1006 KEEPALIVE TIME 15



Copyright © 2016 QEI Verifying the Transport Templates 9

The system must now be REBOOTED before continuing.

2.3 Verifying the Transport Templates The OSIMMS transport template that was configured above can be verified for correctness

(after rebooting) by typing the following commands:

$ MCR NCL SHOW OSI TRANSPORT TEMPLATE OSIT$OSIMMS ALL

Node 0 OSI Transport Template osit$osimms

at 2006-10-16-11:44:39.013-05:00Iinf

Identifiers

Name = osit$osimms

Characteristics

Keepalive Time = 15

Retransmit Threshold = 8

Initial Retransmit Time = 5

CR Timeout = 30

ER Timeout = 30

Network Service = CLNS

Security = <Default value>

Classes = {4}

Checksums = False

Maximum NSDU Size = 2048

Expedited Data = True

CONS Template = "OSI Transport"

Use CLNS Error Reports = True

Acknowledgement Delay Time = 1

Local NSAP = <Default value>

CLNS Inactive Area Address = { }

Inbound = False

Loopback = False

Send Implementation Id = True

Extended Format = True

Network Priority = 0

Send Preferred max TPDU size = False

Send Request Acknowledgement = True

RFC1006 Port Number = 102

$MCR NCL SHOW OSI TRANSPORT TEMPLATE OSIT$RFC1006 ALL

Node 0 OSI Transport Template osit$rfc1006

at 2006-10-16-11:47:11.704-05:00Iinf

Identifiers

Name = osit$rfc1006

Characteristics

Keepalive Time = 15

Retransmit Threshold = 8

Initial Retransmit Time = 5

CR Timeout = 30

ER Timeout = 30



10 Verifying the Transport Templates Copyright © 2016 QEI

Network Service = RFC1006

Security = <Default value>

Classes = {0 , 2}

Checksums = True

Maximum NSDU Size = 2048

Expedited Data = True

CONS Template = "OSI Transport"

Use CLNS Error Reports = True

Acknowledgement Delay Time = 1

Local NSAP = <Default value>

CLNS Inactive Area Address = { }

Inbound = True

Loopback = False

Send Implementation Id = True

Extended Format = True

Network Priority = 0

Send Preferred max TPDU size = False

Send Request Acknowledgement = True

RFC1006 Port Number = 102

If some of the configurations on your system are not correct then you need to edit the

NET$OSI_TRANSPORT_STARTUP.NCL file and correct the entries. The OSIT$OSIMMS

and OSIT$RFC1006 transport templates sections should be as follows:

CREATE NODE 0 OSI TRANSPORT TEMPLATE osit$osimms

SET NODE 0 OSI TRANSPORT TEMPLATE osit$osimms NETWORK SERVICE CLNS, -

CLASSES {4}, -

EXPEDITED DATA TRUE, -

CHECKSUMS FALSE, -

INBOUND FALSE, -

LOOPBACK FALSE

SET OSI TRANSPORT RFC1006 LISTENER PORTS = { 102, 399 }

CREATE NODE 0 OSI TRANSPORT TEMPLATE osit$rfc1006

SET NODE 0 OSI TRANSPORT TEMPLATE osit$rfc1006 NETWORK SERVICE RFC1006, -

CLASSES {0,2}, -

EXPEDITED DATA TRUE, -

CHECKSUMS TRUE, -

INBOUND TRUE, -

RFC1006 PORT NUMBER 102, -

LOOPBACK FALSE

ADD NODE 0 OSI TRANSPORT RFC1006 LISTENER PORT {102,399}

If you made any changes to the file then reboot the system.



Copyright © 2016 QEI Defining NSAPs 11

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. NOTE: You do not need to configure this file if you are using a

TCP/IP-RFC1006 connection. 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)

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.

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_OSInetwork , 49::00-01:AA-00-04-00-AA-04:21 (LOCAL:.KAYAK) ]

) ,

(

[ DNA_CMIP-MICE ] ,



12 Showing Defined NSAP Logicals Copyright © 2016 QEI


[ DNA_IP , 0.0.0.0 ]

) ,

(

[ DNA_CMIP-MICE ] ,


[ 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



Copyright © 2016 QEI Local Network Address 13

4 Configuring the SUIC.DIB File 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 of the SUIC.DIB file 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:

*********************************

* SECTION 1

*

$

$ Local Network Address

/KAYAK$NSAP/

Alternately for the RFC1006 connection the following, example entry, must be made.

*********************************

* SECTION 1

*

$

$ Local Network Address

/RFC1006/192.168.6.80/

Where 192.168.6.80 is the local TCP/IP address.

4.2 Local DIB Entries

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/1/

where:

AR_Name. This required field is the Application Reference Name and is an ASCII

string of up to 32 characters (case-sensitive). 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 Applications 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).



14 Local DIB Entries Copyright © 2016 QEI

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 and is a long integer value. Suggest leaving this field blank.

AE_qual. This optional field is used to qualify the Application Entity and is a long

integer value. Suggest using the two digit innovation instance of the AP_Title.

AE_invoke_id. This optional field is used to identify an innovation instance of the

Application Entity and is a long integer value. Suggest leaving this field blank.

p_sel. This required field represents the Presentation Selector used to select the

appropriate application layer services and is an octet string. 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 and is an octet string. For suggested use,

see p_sel.

t_sel. This required field represents the Transport Selector used to select the

appropriate session layer services and is an octet string. For suggested use, see

p_sel.

“1”. This required field represents the use of RFC1006 in the AR_Name. This

parameter should be omitted when using the OSAK OSI convention.



Copyright © 2016 QEI Remote DIB Entries 15

A Local DIB Entry example follows:

*********************************

* SECTION 2

*********************************

$ Local DIB Entries

/EMC_CLIENT/1 3 9999 10//10//0001/0001/0001/

/EMC_SERVER/1 3 9999 11//11//0002/0002/0002/

Alternately for the RFC1006 connection the following, example entry, must be made

*********************************

* SECTION 2

*********************************

$ Local DIB Entries

/EMC_CLIENT/1 3 9999 10//10//0001/0001/0001/1/

/EMC_SERVER/1 3 9999 11//11//0002/0002/0002/1/

A simplified version is sometimes acceptable in some systems as shown below

*********************************

* SECTION 2

*********************************

$ Local DIB Entries

/EMC_CLIENT/1 3 9999 10////0001/0001/0001/1/

/EMC_SERVER/1 3 9999 11////0002/0002/0002/1/

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:

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

/AR_Name/AP_Title/AP_invoke_id/AE_qual/AE_invoke_id/p_sel/s_sel/t_sel/RFC1006/IP

Address

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.

AP_Title. This is an optional field, however, it is almost always used. It is an Object

Identifier representing the Applications 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



16 Remote DIB Entries Copyright © 2016 QEI

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. This optional field is used to identify an innovation 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.

NSAP. This is an ASCII string that must be defined in the OSIT$NAMES logical name

table.

RFC1006. This is a keyword and must appear as the literal “RFC1006”.

IPAddress. This is the Internet Protocol dotted decimal address of the remote

application.

A Remote DIB Entry example follows:

*********************************

* SECTION 3

*

*********************************

$ 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/



Copyright © 2016 QEI Remote DIB Entries 17

RFC1006 Configuration. When using RFC1006 connections the Remote DIB Entry

example is as follows:

*********************************

* SECTION 3

*

*********************************

$ Remote DIB Entries

/VMPA_Client/ 1 3 9999 37////01/01/01/RFC1006/192.168.120.91/

/VMPA_Server/ 1 3 8888 37////02/02/02/RFC1006/192.168.120.91/

Where 192.168.120.91 is the remote node’s TCP/IP address. Also note the

acceptable simplified version again as denoted by “////”



18 Installing the ICCP Pull Down Menu Copyright © 2016 QEI

5 Session Manager

5.1 Installing the ICCP Pull Down Menu

To make the ICCP Pull Down menu accessible the Session Manager, select the Options item

from the Session Manager window. From the Options menu select Menu. Add a new Menu

Names entry with the name as “ICCP” at the bottom of the Menu Names Listing as shown

below:



Copyright © 2016 QEI Installing QNETConfig 19

5.2 Installing QNETConfig

To make QNETConfig accessible from the ICCP 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 by pressing the enter key on the end of the

“DCL Command” entry box as shown below.



20 Installing QNETMsg Copyright © 2016 QEI

5.3 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:[HHSCAN.INSTALL]QNETMSG.





Copyright © 2016 QEI Installing NewMessage 21

5.4 Installing NewMessage

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.



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.



22 Main Window Copyright © 2016 QEI

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 or a local server.

6.1 Main Window

The main editor window defines the name and description of the remote system. Each local

ICCP client scan task has a QLnn logical (where nn is the communication line number). The

equivalence string is the name of QNETconfig record. See chapter 7 Config.A.

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 (Section 2) in the

SYS$STARTUP:SUIC.DIB file. 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 (Section 3) in the

SYS$STARTUP:SUIC.DIB file.

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.



Copyright © 2016 QEI Server Window 23

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.

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 (Section 2) in the

SYS$STARTUP:SUIC.DIB file. Note that this name is not the name of the ICCP Server

process. That name is ICCPSVnn where nn is the corresponding QLINK display record

number.



24 Server Window Copyright © 2016 QEI

Remote Client Object Names. The Remote Client Object Name is the name of the remote

ICCP client network object allowed to connect. This same name must appear in a Remote

DIB Entry (Section 3) in the SYS$STARTUP:SUIC.DIB file.

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 and is case-sensitive.

Site ID. The Site ID is the name of the data area at the local server that contains variables

accessible by the remote client in VMD scope. The Site ID will be prefixed to all object

names. The name cannot contain any spaces and is case-sensitive.

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.



26 CONFIG.A and CONFIG.B files Copyright © 2016 QEI

7 Master Station Configuration Changes

7.1 CONFIG.A and CONFIG.B files

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

system. The following two sections will instruct you to make changes needed for the ICCP

scan task to run. Please note that one additional communication line is required fro each

ICCP connection to another ICCP site.

7.1.2 Adding the ICCP Scan Task

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/I64.IMAGE

$ !

7.1.3 Adding ICCP Communication Lines

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 QNET configuration record. The remote system names must be defined

in QNETConfig. See Chapter 6 QNETConfig. The communications line speed is not required,

and is entered as a NULL string as shown below:

$ !

$ ! Communication Lines

$ !

$ COMLIN33 :== “SIEMNS”

$ COMLIN_SPEED33 :==

$ !

$ !



Copyright © 2016 QEI OPTTSK.COM Modifications 27

7.2 OPTTSK.COM Modifications

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

SCADA system.

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

file:

$ @MG:[HHSCAN.INSTALL]HHSCAN

This logical definition should always be executed before the following ICCP definition.

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

$ @MG:[UCA.INSTALL]ICCPSV

As an example the entry to the OPTTSK.COM file would look as follows:

$!

$! ====> Install Host to Host Communications

$!

$ @MG:[HHSCAN.INSTALL]HHSTSK

$ @MG:[UCA.INSTALL]UCATSK

$!



28 OPTRUN.COM Modifications Copyright © 2016 QEI

7.3 OPTRUN.COM Modifications

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

As an example the entry to the OPTRUN.COM file would look as follows:

$!

$! ====> Run Host to Host Communications

$!

$ @MG:[HHSCAN.INSTALL]HHSRUN

$ @MG:[UCA.INSTALL]ICCPSVRUN 00

$!

7.4 Database Display Screen Modifications (for Q-Windows)

Display the USERED display. Look through the many record pages and locate the three ICCP

displays (HSLIST, QLINK, and TXPARS) as shown below. If necessary, change the

displayed data in your record to match the record display shown below. If the three ICCP

displays are not shown, in your USERED displays, then add them to your USERED display.



30 MODPARAMS.DAT Modifications Copyright © 2016 QEI

8 OpenVMS Resources

8.1 MODPARAMS.DAT Modifications

The following changes may be needed for OpenVMS to support the MMS-EASE connections.

Edit the MODPARAMS.DAT file that resides in the sys$sysdevice:[sys0.sysexe] directory, By

typing the following command:

$EDIT SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT

The MIN_CHANNELCNT parameter may have to be increased to a value of 3000. If the

system is already configured for a value greater than 3000 then leave the greater value, in the

configuration. Also the MIN_PQL_MBYTLM parameter may have to be increased to the value

of 1510000. Again if the system is already configured for a value greater than 1510000 then

leave the greater value.

8.2 Transport connection

Depending on the system configuration and on the total number of connections the following

adjustment to the transport connections may be needed. To increase the connections insert

the following line in the SYS$STARTUP:NET$OSI_TRANSPORT_STARTUP.NCL file.

SET OSI TRANSPORT MAXIMUM CONNECTIONS 1000 TRANSPORT

8.3 OpenVMS System Account Modifications

Run the AUTHORIZE utility to increase the OpenVMS resources required to use additional

MMS-EASE channels, if they are needed. An example is given below:

$SET DEF SYS$SYSTEM

$RUN AUTHORIZE

UAF>MODIFY/ASTLM=1050 SYSTEM

UAF>MODIFY/FILLM=1050 SYSTEM

UAF>MODIFY/BIOLM=1000 SYSTEM

EXIT

$

The AUTOGEN utility must be run and the system rebooted after any change is made to the

files or the system parameters descried above. To run the utility type the following commands,

note that the system will reboot, automatically, after the execution of the commands.

$@SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK



Copyright © 2016 QEI PWIP driver configuration 31

9 Appendix Notes

9.1 PWIP driver configuration

In order to configure the PWIP driver you need to do the following:

CSALPH> set def sys$manager

CSALPH> @tcpip$config

HP TCP/IP Services for OpenVMS Configuration Menu

Configuration options:

1 - Core environment

2 - Client components

3 - Server components

4 - Optional components

5 - Shutdown HP TCP/IP Services for OpenVMS

6 - Startup HP TCP/IP Services for OpenVMS

7 - Run tests

A - Configure options 1 - 4

[E] - Exit configuration procedure

Enter configuration option: 4

HP TCP/IP Services for OpenVMS Optional Components Configuration Menu


1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS)

2 - Configure SRI QIO Interface (INET Driver)

3 - Set up Anonymous FTP Account and Directories

4 - Configure Kerberos Applications

5 - Configure failSAFE IP


[E] - Exit menu


TCP/IP Transport for DECnet and Pathworks Service Configuration

Service is not enabled.

Service is stopped.

TCP/IP Transport for DECnet and Pathworks Service configuration options:

1 - Enable service on this node



32 PWIP driver configuration Copyright © 2016 QEI

2 - Enable & Start service on this node

[E] - Exit PWIP_DRIVER configuration


%RUN-S-PROC_ID, identification of created process is 00002F22

%TCPIP-I-INFO, PWIP ACP process (pid=00002F22) created

%TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed

Press Return to continue ... <RETURN>

HP TCP/IP Services for OpenVMS Optional Components Configuration Menu


1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS)

2 - Configure SRI QIO Interface (INET Driver)

3 - Set up Anonymous FTP Account and Directories

4 - Configure Kerberos Applications

5 - Configure failSAFE IP


[E] - Exit menu

Enter configuration option: E

HP TCP/IP Services for OpenVMS Configuration Menu


1 - Core environment

2 - Client components

3 - Server components

4 - Optional components

5 - Shutdown HP TCP/IP Services for OpenVMS

6 - Startup HP TCP/IP Services for OpenVMS

7 - Run tests


[E] - Exit configuration procedure

Enter configuration option: E

$



Copyright © 2016 QEI OSAK Configuration 33

9.2 OSAK Configuration

9.2.1 Verify Installation of the OSAK Software

Check to see if OSAK is installed by typing the following command:

CSALPH> product show

_(PROD, HIST, OBJ, RECOV, UTIL): prod

_Product name (* to show list): *

----------------------------------- ----------- ------------

PRODUCT KIT TYPE STATE

----------------------------------- ----------- ------------

HP I64VMS AVAIL_MAN_BASE V8.2-1 Full LP Installed

HP I64VMS CDSA V2.1-355 Full LP Installed

HP I64VMS DECNET_PLUS V8.2-1 Full LP Installed

HP I64VMS DWMOTIF V1.5 Full LP Installed

HP I64VMS KERBEROS V2.1-75 Full LP Installed

HP I64VMS OPENVMS V8.2-1 Platform Installed

HP I64VMS OSAK V3.0-T Full LP Installed

HP I64VMS TCP/IP V5.5-11ECO1 Full LP Installed

HP I64VMS TDC_RT V2.1-78 Full LP Installed

HP I64VMS VMS V8.2-1 Oper System Installed

----------------------------------- ----------- ------------

10 items found

9.2.2 Installing OSAK from HP OpenVMS CD

If the product is not installed install it by using the OpenVMS bootable CD-disk with the following

label:

Version 8.2-1

Operating Environment Instructions

Follow the instructions on the CD-disk. After you installed the OSAK server and rebooted the

system you need to insert the following commands to the

SYS$MANAGER:SYSTARTUP_VMS.COM file at the end of the file a line or two before the

“EXIT” statement:

$ if f$search("sys$startup:osak$start.com") .nes. ""

$ then

$ @sys$startup:osak$start

$ endif

$!

$ EXIT

You also need to insert the following command to the SYS$MANAGER:SYSHUTDWN.COM, at

the start of the file:

$@sys$startup:osak$stop

mailto:$@sys$startup:osak$stop



34 OSI Timer Modifications Copyright © 2016 QEI

9.3 OSI Timer Modifications

To disable the OSI timer type the following command to the SYS$MANAGER:SYLOGICALS.COM

file:

$ DEFINE/SYSTEM NET$DISABLE_DTSS TRUE

An example is shown below:

$!

$! ******************************************************************

$!

$! Define any site-specific logical names below:

$!

$!

$! -----> For DTSS

$!

$ DEFINE /SYSTEM NET$DISABLE_DTSS TRUE

$!

$! -----> End of DTSS entry

$!

$!

$! ******************************************************************

$!

9.4 SCADA Database Expansion

A few files need to be expanded for ICCP to run properly. Use the following commands in a DEC

Term window to stop the SCADA software and expand the required files to their proper size.

CSALPH> @MG:[INSTALL]KILL

CSALPH> SET DEF ONLINE

CSALPH> FILCRT EXTEND/SIZE=100 156









You need to reboot the machine after all the above instructions are completed, unless you need to

make more changes as you follow the configuration Outline.

End of Configuration Procedure



Copyright © 2016 QEI SCADA Database Expansion 35

QEI provides a wide variety of Automation Products and services to the Electric Utility Industry. QEI customers are a mixture of major utilities, government and military agencies as well as global Electrical Transmission and Distribution OEM's.

45 Fadem Road

Springfield, NJ USA

T: +973-379-7400 F: +973-346-2138

W: www.qeiinc.com

http://www.qeiinc.com/

qn-920-1 qnet configuration guide...desired qnet configuration record. 2. make sure the local client...

Documents