Digital PDFs

AA-JH72A-TV

April 1987

95 pages

Original

5.7MB

Document:	DECnet-DOS Supplemental Information
Order Number:	AA-JH72A-TV
Revision:	0
Pages:	95
Original Filename:	AA-JH72A-TV_DECnet-DOS_Supplemental_Information_Apr86.pdf

OCR Text

Networks- Communications

DECnet-—DOS
supplemental Information
AA-JH72A-TV

SOS0G20

DECnet—DOS
supplemental Information
Order No. AA-JH72A-TV

March

1987

This manual describes changes in updating DECnet-DOS and DECnet-

Rainbow V1.0 and V1.1 and DECnet-VAXmate V1.0 to DECnet-DOS,
DECnet-Rainbow, and DECnet-VAXmate V1.2. Changes for V1.2
include bug fixes, enhancements, and newly supported features.

Supersession/Update Information:

Operating System and Version:

This is anew manual.

MS-DOS V2.11
PC DOS V2.10
PC DOS V3.10
PC DOS V3.20

VAXmate MS-DOS V3.10
Software Version:

DECnet—DOS V1.2
DECnet—Rainbow V1.2
DECnet—-VAXmate V1.2

AA-JH72A-TV
First Printing, March 1987

The information in this document is subject to change without notice and should not be construed
as acommitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no
responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used or
copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied
by Digital or its affiliated companies.

The postage-prepaid Reader's Comments form on the last page of this document
user’s Critical evaluation to assist us in preparing future documentation.

requests tne

The following are trademarks of Digital Equipment Corporation:

ALL-IN-1

DIBOL

DECmate
DECnet
DECnet-DOS

MASSBUS
PDP
P/IOS

VAX
VAXcluster
VAXmate

Rainbow

DEC

Paegeo”

DECnet-Rainbow

Professional

DECUS
DECwriter

RSTS
RSX

DECnet-VAXmate

UNIBUS

VMS

Work Processor
WPS-PLUS

AT&T is a trademark of American Telephone & Telegraph Company.
IBM is a registered trademark of International Business Machines Corporation.

MS-DOS is a registered trademark of Microsoft Corporation.

PC/XT and Personal Computer AT are trademarks of International Business Machines
Corporation.
SideKick is a trademark of Borland International, Inc.

This manual was produced by Networks and Communications Publications.

Contents
Preface
DECnet-DOS Changes
1.1
1.2
1.3
1.3.1
1.3.2

1.4
1.4.1
1.4.2
1.4.2.1

OVELVIEW 266. ce
cen e enn eee eee enn n nn eee eens
Highlight of Changes from Previous Versions of DECnet-DOS .....
Changes to the DECnet—DOS Installation Procedure (DIP)..........
Newly Supported Features ........ 0.0...
eees
Enhancement. ....... 0...
een een e teen nee ennes

1-1
1-1
1-2
1-2
1-2

Changes to DECnet—DOS SETHOST ..............
00000 cc ccc eee eens
Bug Fixes 200.0.
n ene net bebe been ens
Newly Supported Features ............
0...
nee
Using 132—Column Suppott.......0..0.
000
ens

1-3
1-3
1-4
1-4

1.4.3

New Switches ......... 00.0 ccc cence
ence tenn nent ene

1-5

1.4.3.1
1.4.3.2
1.4.3.3)
1.4.3.4

/KEYBOARD .........0. 000 ccc
nnn tent enn tenn nes
/SERVICE. 2.0...
cnn n nee beeen tenn nen ees
/SETUP 2.00.06
nen enn n een een tenn es Leas
/SWITCH EDN... 6c
een tnt t nnn tnt aes

1-5
1-6
1-6
1-7

Changes to the DECnet—DOS Mail Utility .........................
Changes to the DECnet—DOS Network Device Utility (NDU) .....

1-11
1-11

Changes to DECnet—DOS Transparent File Access (TFA)..........
Bug Fix€S 2.0...
eee
e nent e ene n eee nnee

1-13
1-13

1.4.2.2

Using National and Multinational Character Sets....................

1.4.4

Enhancements..........0.

1.6.1

Bug Fixes 2.00...

1.8
1.9

Changes to DECnet-DOS DTR/DTS.............0
00. ccc cence
Changes to the DECnet-DOS Spawner.................
0000 e ee eee

1.5
1.6

1.7
1.7.1

00. cece
ent
ene e nen een eens
e nent nee n ene ees

1.9.1

Bug Fixes 0.0...

1.9.3
1.10
1.11

Enhancements... 1.0.0.0... ccc
ete
teee en neces
Changes to the DECnet—DOS File Access Listener (FAL) ..........
Changes to the DECnet-DOS Network File Transfer Utility
(NET) 202
e ene e tne e nent e beeen.
Enhancement..........
0... cece
nee e teen net eeee

1.9.2

1.11.1

Newly Supported Features 2.2.00...

eee ence

e nee

ccc cnn

e teens

e eens

1-5

1-8

1-11

1-14
1-14
1-14

1-14
1-17
1-17
1-17
1-17

Contents—1

1.12
1.12.1

Changes to the DECnet—DOS Programming Interface Library
(DNETLIB) .......0. 0.
e enn etn n nee eennes
Bug FixeS 2.0.0...
eee enn eee e ene e enn enas

1-18
1-18

1.12.3

Compiling DNETLIB Sources

1-18

1.12.2

1.12.4

Newly Supported Features ........0. 00...

nas

Changes to the DECnet—DOS Data Link Layer (DLL) ..............
Enhancements. ........ 0...
ccc cent
nett ttn n eens
MICOM Driver ...... 0.0.0
n nen
nnes
3COM Driver.......
0... cence
ene
eeenes
DEPCA Driver......
0.006
e enn
nnnes

1.14.1

Bug Fix€S 2.2... cen
ene n nee n enn nn eees

1.14.2
1.14.3
1.15

1-18
1-19

1-19
1-19
1-19
1-19
1-19

Changes to DECnet-DOS DECnet Network Process (DNP) .......

1-20

Newly Supported Features ............
0.00 ccc ccc
eee nes
Enhancements..........0..
000. c ccc ccc cence nee n enn eens

1-20
1-20

Changes to the DECnet—DOS Scheduler........................04.

1-20

DECnet-Rainbow Changes
2.1
2.2
2.3
2.3.1

OVELVIEW 206
ene nee te eee n eben beeen nnee
Highlight of Changes from Previous Versions of
DECnet—RainDow ..... 0...
cee nnn
n ene
e ees
Changes to the DECnet—Rainbow Installation Procedure (DIP).....
Enhancements..........
0.0
e nee e nnn eee e een ee

2.4
2.4.1
2.4.2
2.4.3
2.5

Changes to DECnet—Rainbow SETHOST ...............
0.00. e cece ees
|S] U CSAS 6b D. < oh
Newly Supported Features ......... 0.06.
n nee nes
Enhancements. ........ 0.0
n teen nee en neg
Changes to the DECnet-Rainbow Mail Utility.......................

2.6.1

Bug FIxeS 20.0000

2.6

2.7

Changes to the DECnet—Rainbow Network Device Utility
(NDU) 20.60.
n nent een n teen nnn ene eens

2-1
2-1
2-1
2-2

2-2
2-2
2-2
2-3
2-4
2-4

n ene e nent ene e nee es 2-4

Changes to DECnet—Rainbow Transparent File Access (TFA) ....... 2-6

2.7.1

Bug FIx€S 0.0.

2.8
2.9
2.9.1
2.9.2
2.9.3
2.10
2.11

Changes to DECnet-Rainbow DTR/DTS ............................ 2-7
Changes to the DECnet—Rainbow Spawner ................-..22005- 2-7
Bug FIxesS 00.
ene
en eee teen ee en eens 2-7
Newly Supported Features ............ 000s
2-8
Enhancements. ......... 00... cece
eee n eee nes 2-10
Changes to the DECnet—Rainbow File Access Listener (FAL)...... 2-10
Changes to the DECnet—Rainbow Network File Transfer Utility
(NET) 200
een eet nnn ete ene e eens 2-10
Enhancements. ..... 0.0... cnet
cee een eee
eees 2-10
Changes to the DECnet—Rainbow Programming Interface
Library (DNETLIB) ............0.0
0.0
nett
eees 2-11
Bug Fixes 2...
erent eet e eben een ene ened 2-11
Enhancements.........0..
00.
eee
enn eee tenn nnees 2-11
Compiling DNET Library Sources ..............
00... c cece eee eee 2-12

2.11.1
2.12
2.12.1
2.12.2
2.12.3

Contents—2

e dete bette ene ee eb ee teen e tenes

.............
0.0 c cece
e es

1.13
1.13.1
1.13.1.1
1.13.1.2
1.13.1.3

1.14

Enhancements........ We

en cen nen ened een eee e bn ents

2-6

2.12.4
2.13
2.13.1
2.13.2

Newly Supported Features ...............
0...
eee ee
Changes to DECnet—Rainbow DECnet Network Process (DNP)...
Bug Fixes 00... cee
cent nent eee n eas

Enhancements. ........00.00. 00 ccc cence ence ence e ence ees ..

2-12
2-12
2-12

2-13

DECnet-VAXmate Changes
3.1
3.2
3.3
3.3.1
3.3.2
3.4
3.4.)
3.4.2
3.4.3

3.4.3.1

3.4.3.2
3.4.3.3
3.4.4
3.5
3.6
3.6.1

3.7
3.7.1
3.8
3.9
3.9.1
3.10
3.11
3.11.1
3.12
3.12.1
3.12.2
3.12.3

3.12.4
3.13

OVELVIEW 261.
nee eee e enn n ene
e tenes 3-1
Highlight of Changes from Version 1.0 of DECnet-VAXmate....... 3-1
Changes to the DECnet—VA Xmate Installation Procedure (DIP) .... 3-2
Enhancements. ...... 0...
eee nett teen en nees 3-2
Using DIP ina VAXmate/VMS Services Environment ............... 3-3
Changes to DECnet-VAXmate SETHOST ......................2005. 3-3
Bug Fixes .... 0...
ccc
eee ene n nee
e eee ees 3-3
Newly Supported Features ...........
0... ccc cece ene tenes 3-4
New Switches ........ 0...
ccc
nnn e eee
nennas 3-5
ISERVICE.. 2...
n nent tenet e beens 3-5
/SETUP ......
een eee
e netted d eect tenet teen nee e es 3-5
ISWITCH F710. cnet
ene e teen nnn enens 3-6

Enhancemenmts........

0...

een n een tenn nee 3-6

Changes to the DECnet-VAXmate Mail Utility ...................... 3-9
Changes to the DECnet-VAXmate Network Device Utility
|
(NDU) 0.0006
e nee e teen n ete e eben e eens 3-9
Bug Fixes . 00...
n nee e cent eee eee nees 3-9
Changes to DECnet-VAXmate Transparent File Access (TFA) .... 3-11
Bug FIixeS 20...
cc
ene tebe teen nee ete nnnes 3-12
Changes to DECnet-VAXmate DTR/DTS ..................0.0000. 3-12
Changes to the DECnet-VAXmate Spawner....................005 3-12
Enhancement... ....... 0...
eee
e teenie neeees 3-15
Changes to the DECnet-VA Xmate File Access Listener (FAL) ..... 3-15
Changes to DECnet-VAXmate Network File Transfer (NFT)...... 3-15
Enhancements........
0.
een
eee een eee n nn neees 3-15
Changes to the DECnet-VAXmate Programming Interface
Library (DNETLIB) ...... 0...
ccc
cence een eee ees 3-16

Bug FIX€S 2.0 6.
nen ene n nee n een e een nes
Enhancements...................05. Lecce
cence teen eee cence

Compiling DNETLIB Sources ......... 0...
ees
Newly Supported Features .......... 0... ccs
Changes to the DECnet-VAXmate DECnet Newtork Process
(DNP). 00.60.
e ceed nen teen ene t eee nnnees

3-16
3-16
4-17
3-17
3-17

Keyboard Illustrations
Sample C Programs
B.1

Sample Client Program ..... 0.0...

eeee

B-1

Contents-—3

B.2

Sample Server Program ........
0... cect
cee nees
Sample Transparent Task-to-Task Program ....................055

Figures
The
The
The
The
The

Rainbow 100 System Keyboard .................
0... e eee ee
VAXmate (LK250) Keyboard ..............
0... cece eee
IBM PC and PC/XT Keyboard...........
0... cece eee
IBM PC AT Keyboard ...........
000.0
nes
IBM Enhanced Personal Computer Keyboard ................

Tables
Key Mappings (IBM PC/XT Keyboard to DEC VT102-Type
Keyboard) .... 0.
ccc enn nee
nn ne eee n ne neeeees
Keypad Mappings (IBM PC/XT Keypad Keys to DEC
VT102-Type Keypad Keys) .......... 0... cece
eee
Key Mappings (IBM PC AT Keyboard to DEC VT 102-Type
Keyboard)...
ccc cence nen etn een e eee enn nenees
Keypad Mappings (IBM PC AT Keypad Keys to DEC
VT102-Type Keypad Keys) ...........
0.0.
ccc cnn ees
Key Mappings (IBM Enhanced PC Keyboard to DEC
VT102-Type Keyboard) . . . . . .
0...
e eens
Keypad Mappings (IBM Enhanced PC Keypad Keys to DEC
VT102-Type Keypad Keys) ...........
0... cece
ees

Contents—4

Preface

This document includes updated information for version 1.2 of the DECnet—DOS,
DECnet—Rainbow, and DECnet-VAXmate software products. In the context of this
document, the terms DECnet-DOS, DECnet—Rainbow, and DECnet—VAXmate are
used to refer to the DECnet—DOS software, the DECnet—Rainbow software, and the
DECnet-—VA Xmate software.
This document describes changes that have been made since DECnet—DOS V1.1, DECnet-Rainbow V1.1, and DECnet-VAXmate V1.0 (there is no V1.1 for DECnet-—
VAXmate). The changes include bug fixes, enhancements, and newly-supported features.
You should use this information in conjunction with the material presented in the
DECnet-—DOS documentation set. Specifically, you should refer to the DECnet-DOS
Release Notes. You should also look at the README.TXT file which is included with
the other files for this kit.
Intended Audience

This document is intended for users of VAXmate workstations, Rainbow personal computer, and IBM PC, PC/XT, and Personal Computer AT personal computers. Some of
the information presented in this document is very technical. If you do not understand
the material, you should seek assistance from the person who is responsible for
configuring your network.

Preface—1

Structure of This Document
This document consists of 3 chapters and 2 appendixes:

Chapter 1

Describes changes to DECnet-DOS.

Chapter 2

Describes changes to DECnet—Rainbow.

Chapter 3

Describes changes to DECnet-VA Xmate.

AppendixA

Contains keyboard illustrations for VAXmate workstations and the
Rainbow, IBM PC/XT, and IBM PC AT personal computers. It also
includes an illustration of the IBM Enhanced PC keyboard.

AppendixB

Contains sample C programs. These programs are also available as files
on the diskettes that accompany this document.

Graphic Conventions Used in This Document
The following graphic conventions are used in this document:

Convention

Meaning

Monospaced
type

Monospaced type indicates examples of system output or user input.
System output is in black; user inputisinred.
_

italics

Lowercase italics in commands and examples indicate that either the
system supplies or you should supply a value.
Indicates that you should press the specified key.
indicates
that you should hold down the CONTROL key while you press the x
key, where x is a letter.
Note that unless otherwise specified, you should end every command line by pressing (RET).

Preface—2_

DECnet-DOS Changes

1.1

Overview

This chapter describes changes from DECnet-DOS Version 1.0 and Version 1.1 to
DECnet—DOS Version 1.2. (Note that although DECnet—DOS is a set of software products that includes DECnet-DOS, DECnet—Rainbow, and DECnet—VA Xmate, this chapter describes the changes that apply specifically to DECnet—DOS for the IBM PC, PC/
XT, and Personal Computer AT.)
The following list highlights the DECnet-DOS
down by components in later sections.

1.2

changes. The changes are then broken

Highlight of Changes from Previous Versions of DECnet-DOS
Bug fixes.

Support for the new Enhanced IBM PC/XT and PC AT. (The IBM PC/XT Model 286

is not supported.)

Support for PC DOS Version 3.20.
Performance improvements to Network File Transfer (NFT).
Functional improvements to the Job Spawner and the DECnet Test Receive utility
(DTR).
SETHOST support for DEC national character sets (7-bit) and DEC multinational
character sets (8-bit).
SETHOST local IBM-style print screen support (for IBM PCs).

1-1

SETHOST

132-column support (for IBM PCs).

Support for Digital’s new Ethernet communications board for personal computers,
the DEPCA. There is also support for the DEPCA Data Link layer (DLL).

Changes to the DECnet—-DOS Programming Interface Library sources (DNETLIB)
that provide enhanced performance for programming applications that use this
library.

The following sections describe changes that have been made to the individual components.

1.3

Changes to the DECnet-DOS Installation Procedure (DIP)

The DECnet-—DOS Installation Procedure (DIP) is an automated procedure that lets you
easily install DECnet—DOS by responding to a set of questions and making selections
from a series of menus. Refer to the DECnet—DOS Installation Guide for instructions
on how to use DIP, while noting the changes and enhancements that are described
here.

1.3.1

Newly Supported Features

Version 1.2 of DIP includes support for the following:
e

The PC DOS Version 3.20 operating system.

The new Enhanced IBM PC/XT and Personal Computer AT.

The DEPCA communications board and the DEPCA Data Link layer.

1.3.2

Enhancements

During installation, DIP now performs the following operations:
e

Checks for the proper version of the DIP.DAT/DIP.SAV database and displays an
error if it is an incompatible version.

Provides enhanced performance for copying files from the kit.

Checks
the
communication
type
of the
DECnet-DOS
parameter
file
- (DECPARM.DAT, if one exists). If the new configuration is for a different communication type, DIP deletes the existing DECPARM.DAT.
It creates a new
DECPARM.DAT when the network is reloaded and NCP is rerun.

Runs the new
reboot.

Adds the STACKS parameter to the system startup file, CONFIG.SYS (if you are
running DOS Version 3.20 and the parameter is not already there). Currently this
parameter is set to the default values defined by DOS. In subsequent releases the
default values may change.

1-2

configuration and verification utility automatically upon

system

DECnet-DOS Supplemental Information

Copies all character translation tables and keyboard screen template files automatically from the kit to the specified DECnet database path (if you select
SETHOST.EXE to be installed).
Copies the FIXNVD.EXE file automatically from the kit if you select the Network
Device utility (NDU) to be installed. (Refer to Section 1.6 for information about
using FIXNVD.EXE with NDU.)
Adds the command line switch /IRQ = 3 in the AUTOEXEC.BAT file when invoking
the DLL for either the 3COM driver or the MICOM driver. (Refer to Section 1.13 for
more information about this switch.)
Displays the current EXECUTOR node name and address if DECnet is already
installed and is running on your system. DIP gives you the option of changing the
node name and address at the same time it displays the information.
Creates and/or modifies the Spawner database file (DECSPAWN.DAT).
Creates backup copies of the CONFIG.SYS and AUTOEXEC.BAT
ing them. The backup files have the extension .BAK.

files before edit-

For example:
CONFIG.SYS will have a backup file named CONFIG.BAK
AUTOEXEC.BAT will have a backup file named AUTOEXEC.BAK
If you select the Job Spawner, FAL, or DTR during the installation procedure, DIP
will also create a backup copy of the DECSPAWN.DAT file.
For example:
DECSPAWN.DAT will have a backup file named DECSPAWN.BAK

1.4

Changes to DECnet-DOS SETHOST

1.4.1.

Bug Fixes

SETHOST has implemented bug fixes for the following problems:
The ‘“‘partial escape sequence seen’ error observed when running ALL-IN-1 Version 2.0 software with the WPS—PLUS editor over a CTERM link has been fixed.
Connections to reverse LAT service now work (Version 1.2 and later of the Terminal Server). (Reverse LAT service is a service offered by a terminal server for a host
connected to it by an asynchronous terminal line.) SETHOST connections to LAT
services behave as if you were connected to a terminal server. However, SETHOST
does not support direct connections to terminal servers.
In previous versions, using the HOLD SCREEN key while connected over a CTERM
link would cause the system to hang. This has been fixed so that HOLD SCREEN
now works properly with CTERM.

DECnet-DOS Changes

1-3

In previous versions, if you were logging a terminal session to the disk and the disk
became full, the system would hang. This has been fixed so that instead of hanging
the system when the disk fills up, SETHOST now closes the file and displays an
error message.

1.4.2

Newly Supported Features

Version 1.2 of SETHOST includes support for the following:
The IBM Enhanced PC keyboard for the IBM PC/XT and IBM Personal Computer
AT
|
Local IBM-style print screen (for IBM PCs)
132-column support (for IBM PCs with color adapters only)
The DEC LK250 keyboard
Four new switches (see Section 1.4.3)
DEC national character sets (7-bit) and DEC multinational character sets (8-bit).
Note that full use of 8-bit character sets is limited due to hardware and operating
system constraints.
1.4. 2.1
Using 132-Column Support — To use 132-column support on IBM PCs,
you must have a color adapter (monochrome adapters can only support the use of 80
columns). If you have a color monitor with color disabled, you need to enter the Setup
- menu and enable color. You must also set the terminal characteristics to 132-column
mode. You can set this mode either by selecting it from the Setup menu or by using a
SET TERMINAL command (such as the VMS command, SET TERM/WIDTH = 132).
Once this mode is set, you can switch easily back and forth between screens by using
the
key combination.

DECnet-DOS Supplemental Information

1.4.2.2

Using National and Multinational Character Sets

—

The

following

is a

detailed list of the character sets that are available with SETHOST:
DEC Multinational STD 1 Character Set
DEC Multinational STD 2 Character Set
United States/Canada Character Set
Dutch Character Set
Finnish Character Set
French Canadian Character Set
French Character Set
German Character Set
Italian Character Set

Norwegian/Danish Character Set
Spanish Character Set
Swedish Character Set
Swiss Character Set

United Kingdom Character Set
You can select or change character sets from the General setup menu, which is now
accessible with the new /SETUP switch. (Refer to the following section which
describes the four new switches for SETHOST.)

1.4.3

New Switches

Four new switches have been added to SETHOST. These switches allow you to:
e

tell SETHOST which keyboard layout to use.

§6display the LAT service name table (similar to the SHOW
terminal server).

change the setup for the terminal emulator without having to make a network connection first.
7

change the switch character that SETHOST uses for accessing the SETHOST menu.

SERVICE command ona

The switches are:
1.
2.
3.
4.

/KEYBOARD
/SERVICE
/SETUP
/SWITCH=n

1.4.3.1
/KEYBOARD — The /KEYBOARD
switch allows you to specify to
SETHOST the type of keyboard you are using. When you use this switch (or when you
first start SETHOST on an IBM PC), SETHOST displays the keyboard menu. You can
then specify the keyboard you want to use by making a selection from the menu.

DECnet-DOS Changes

1-5

The following is an example of the SETHOST keyboard menu:
Please
If you

use

indicate
the type of keyboard
wish
to change
keyboards
at a

SETHOST

/KEYBOARD

Enter
1)
2)
3)
4)
The

the

number

display

this

that

the

PC or PC/XT
PC AT
Enhanced
PC
Digital
VAXmate
current

Keyboard

Defaulting

default

number?
to

you
are using
later
date,

with

closest

your

system.

again.

match

your

keyboard:

(LK250)
its

keyboard

keyboard
number

number

In the previous example, the default keyboard selection was 3. If you do not select a
number from the menu, SETHOST tries to determine the type of keyboard you are
using and defaults to that number. SETHOST can also use information that was saved
from your previous keyboard selection. The information is stored in the NVTDEF.DAT
file in the DECnet database directory.
|
See on-line help (SETHOST /HELP) for further information.

1.4.3.2

/SERVICE

—

The /SERVICE switch displays the personal computer LAT

driver’s service name table. This table lists the services that are available for use by LAT.
The services listed are those that have been defined using NCP or those that are advertised on the local area network. If you are using LAT, you can only connect to a service
whose name appears in the service name table.
The default size of the service name table is 10. You can change the size of the table by
using the LAT switch, /D:n. (The DECnet Installation Procedure places the LAT command in the AUTOEXEC.BAT file without any switches. To add the /D switch and
change the value of 7, edit the AUTOEXEC.BAT file.) The value of 1 is added to the
default value of 10. For example, if you specify LAT /D:4, the list displayed by
SETHOST /SERVICE can include up to 14 service names.
Once you have seen the list of services that are available, you can connect to any of the
services by issuing the SETHOST service-name command. (You must be using LAT protocol for the connection.)

1.4.3.3

/SETUP

—

The /SETUP switch allows you to invoke the setup menus with-

out having to make a network connection. You can change settings in any of the setup
directories. Use the cursor arrow keys to move between boxes, then press
or
to make a selection in each box. When you have completed all of your selections, use
the Save Parameters option in the Action menu to save the new defaults.

1-6

DECnet-DOS Supplemental Information

1.4.3.4

use

/SWITCH=n

for

—

The /SWITCH=7n

switch lets you specify a character

accessing the SETHOST menu during an active session. By default, the
key combination displays this menu. In previous versions, the
key combination would display this menu. (The
combination was difficult
to use on European keyboards, so the default was changed to
(RET).) Both combinations will display the menu.

NOTE
This is a two-step sequence. In order for
erly, you must first press
two keys and press (RET).

to work prop-

and (4) simultaneously, then release the

With /SWITCH, you can replace the
default with a different character. The variable m can be an ASCII decimal code character from 1 to 28, where 1 is equivalent to
(CTRUA), 2 is equivalent to (CTRUB), 3 is equivalent to CTRUC), and so on up to 26. Character 27 is equivalent to the ESC character (not recommended, but it can be used) and 28
is equivalent to (CTRL).
For example:
SETHOST /SWITCH = 2 would change

to (CTRLUB XRET).

Using SETHOST /SWITCH with no argument resets the default to (CTRU4\RET).

DECnet-DOS Changes

1-7

1.4 .4

Enhancements

SETHOST Version 1.2 includes the following enhancements:
There is anew keyboard handler. It takes over the keyboard interrupt only for the
keys it needs. All other keys are handled or processed by the standard MS-DOS
Operating systems. This allows some software that was not compatible with DECnet—DOS Version 1.1 to run with DECnet—DOS Version 1.2 (for example, Borland
International’s SideKick).
New single screen keyboard templates are available on line as files in the DECnet
database directory (such as the \DECNET directory). The files are:

—

—
—
—
—
—

ATTPLUS.HLP (for the AT&T Personal Computer 6300 PLUS)
IBMAT.HLP (for the IBM Personal Computer AT)
IBMEPC.HLP (for the IBM Enhanced Personal Computer)
IBMXT.HLP (for the IBM PC/XT)
ZENAT.HLP (for the ZENITH AT compatible)
ZENXT.HLP (for the ZENITH XT compatible)

NOTE
Keyboard templates are provided for reference purposes only.
Their presence in the on-line help files does not imply support for
any PCs other than those listed in the Software Product Description (SPD).
The on-line help text also provides pointers to these files (when you use the /HELP
switch). Illustrations of the keyboard templates for the IBM PC/XT, PC AT and the
IBM Enhanced Personal Computer are included in Appendix A of this document.
Illustrations of the Rainbow and the VAXmate keyboards are also included in
Appendix A.
There is now a way to configure SETHOST for international keyboards. To do this,
follow these steps:
1.

Install the DOS KEYB program to select the keyboard you want. (The KEYB
program is a DOS program that replaces the resident keyboard program. For
example, if you wanted to use a French keyboard, you would install the
KEYBER program.)

Aw
k YN

Tell SETHOST which character set you wish to use (follow steps 3 through 6).
Type SETHOST/SETUP to get into the Setup menu.
Use the arrow keys and the

key to get to the General menu.

Select the character set you want to use.
Save this as the new default by using the Save Setup Parameters option on the
Action menu.
DECnet-DOS Supplemental Information

SETHOST provides translation only from the ROM character set toa DEC character
set and back again. On the IBM PC, this means that the IBM international key
sequences will work to generate an IBM character code. This code will then be
translated by SETHOST into a DEC character.
For example:

—

Two-key
press e.)

compose

sequences.

(To display é, you must first press “and then

to toggle back to a US English keyboard layout (press all 3 keys at
the same time).
to toggle back to the country keyboard layout.

—

(AlTinnn), where nnn is a 3-digit decimal number. This combination can be used
to generate any IBM ROM character.

SETHOST also has a DEC COMPOSE key. However, the operating system (DOS)
sees the keys first and may choose to preempt some of the keys for the IBM style of
international support. If this happens, there are two ways around it:
1.

Use the IBM method
or

Use
to switch temporarily back to a US English keyboard, then
use the COMPOSE Key.

DEC’s multinational STD 2 character set is for use in Norway and other countries
that use character set ROMs that are different from the US character set ROMs.

The character set files that SETHOST uses for translating are stored in the DECnet
database directory (for example, C:\DECNET \*.CHR). These are ASCII text files,
and they contain two 256-character tables. The first table is the DECIBM table. The
DEC character looks into this table to find the character it needs, then returns the
IBM ROM character (which is then displayed on the screen). The second table is the
IBMDEC table. The IBM ROM character looks into this table to find the character
that it needs, then returns the DEC character (which is then displayed on the
screen).
Since SETHOST uses the IBM ROM character set and not a graphic character set for
displaying characters, you are limited in the use of certain characters. When you
select a character from the character set file, SETHOST

tries to determine the clos-

est match to the character you want to display.
e

Inthe General setup menu, leaving or moving out of the character set menu causes
the character set file that you selected to be read to the disk. You can make your
selection while you are still in this menu, but it will not take effect until you move
out of the menu. Once you have left the menu, the file you selected will replace the
internal tables that SETHOST uses. If you hear a beep, then that file was not found.

DECnet-DOS Changes

1-9

SETHOST’s default table is for DEC multinational character sets with a US keyboard (this also works for 7-bit US keyboards). SETHOST will not beep if the
DECM1.CHR or US.CHR files cannot be found; it will just use the default tables.
Since the VT100 terminal does not have an escape sequence to tell the remote system that SETHOST can use 8-bit characters, you must tell the remote system and
the SETHOST terminal emulator to use 8-bit characters (if you select the DEC multinational character set). For example, on a remote VMS system, you would add
SET TERM/EIGHT to your LOGIN.COM file.
For the 7-bit national character sets, some keys will display different characters
depending on whether the keyboard is in typewriter mode or in data processing
mode. You can switch from one mode to the other using the General setup menu.
This allows you to get to characters that would normally be available only with
DEC multinational character sets.
The keys that are affected by this are @), CD, CD, @,

©,

C, C,

CD, GC, 0,7 and ©.

What these keys change to depends on the character set you select.
Two files, NVTDEF.DAT and NVTVID.DAT, are created when using SETHOST.
These files contain information about the version of SETHOST that you are using.
The NVTDEEF.DAT file is created when you use the /KEYBOARD switch to make a
keyboard selection, or when you use the /SAVE switch. The NVTVID.DAT file is
created when you save information using the Save Parameters option in the Setup
menu. In previous versions of SETHOST, the file names were SETHOST.DEF and
VT102.DAT. These older files are still intact if you want to use them, but you
should use the new files.
When you start SETHOST,
it checks for the proper version number in
NVTVID.DAT. If SETHOST determines that this file contains the wrong version, it
will beep and ignore the information in the file. You should use the Save Parameters option to replace the NVTVID.DAT file with an updated copy that contains the
correct information.
If you are using ALL-IN-1 or WPS-—PLUS software on a VT 100 terminal, DEC multinational characters are not displayed. In order to get WPS—PLUS software to use
the multinational character set (MCS) and to properly display the MCS characters in
the on-line help screens, you need to define the following symbols on your VMS
system:

DEFINE KOA$TERMINAL__xxxx ‘“‘OUTPUT__SETHOST”’
DEFINE KOA$TERMINAL.__MCS__SETHOST “Y”’
where xxxx is the terminal name (such as RTA1, VTA32, and so on).

1-10

DECnet-DOS Supplemental Information

1.5

Changes to the DECnet-DOS Mail Utility

Mail no longer uses the access control information that is saved by NCP.
Mail now adds the DECnet node address of the mail sender to the Subject field, just
before the ‘“‘Reply to’’ address. In Version 1.1, this address was not included. Now
when other users receive mail from your DECnet—DOS node, your node’s address
appears in this field. For example:
Subj:

Finance

Meeting

"From

55.125,

GRAVY:

:NELSON"

1.6

Changes to the DECnet-DOS Network Device Utility (NDU)

After you issue an NDU DELETE command, NDU now prompts you for confirmation in
the MS-DOS style:
Are

you

1.6.1

sure

(Y/N)?

Bug Fixes

In DECnet—DOS
problems:

Version 1.1, the virtual disk facility was shipped with the following

A bug caused all DECnet—DOS Version 1.1 32-megabyte disks created as the first
NDU function after a system boot (under MS-DOS or PC DOS Version 2 systems) to
have an error in their headers. This error does not affect the performance or integrity of the virtual disk facility.

32-megabyte disks created under MS-DOS or PC DOS Version 2 systems are not
usable from MS-DOS or PC DOS Version 3 systems. (The opposite of this is also
true: 32-megabyte disks created on MS—DOS or PC DOS Version 3 systems are not
~ usable from MS—DOS or PC DOS Version 2 systems.)

DECnet—DOS Version 1.2 solves both of these problems with the following:
e

§=6All virtual disks created by DECnet—DOS Version 1.0 software remain usable in all
configurations.

§6All 1.2-megabyte, 10-megabyte, and 20-megabyte virtual disks created by DECnet—
DOS Version 1.1 remain usable in all configurations.

All 32-megabyte virtual disks created by DECnet—DOS Version 1.1 under MS-DOS
or PC DOS Version 3 systems will remain usable on any Version 3 system. These
disks are not usable from MS—DOS or PC DOS Version 2 systems.

DECnet-DOS Changes

1-11

32-megabyte virtual disks created by DECnet—DOS Version 1.1 under MS—DOS or
PC DOS Version 2 systems are not usable with DECnet—DOS Version 1.2 until they
are repaired using the FIXNVD utility. The FIXNVD utility is automatically
installed by the DECnet—DOS Installation Procedure, DIP. The utility’s file name is
FIXNVD.EXE.

If you attempt to open a Version 1.1 virtual disk with Version 1.2, NDU generates
the following error message:
Cannot
OPEN
Run FIXNVD

this
disk
first.

created

with

older

release

DECnet.

To use the FIXNVD utility, first make a copy of your virtual disk file. For example:
$ COPY

V11IDISK1.FIL

V11DISKBU.DSK

Now you can run FIXNVD on the new file. This is the syntax for using FIXNVD:
FIXNVD node|/user/password/account] backup-disk-name
Example 1:
$ COPY

VDISK.DSK

DISK.007

(on VMS node VMSNOD)
C> FIXNVD

VMSNOD

DISK.007

(on your PC)
Example 2:
$ COPY

VDISK.DSK

DISK$07:

[SMITH.DISKS] PAYROLL . DAT

(on VMS node REMOTE)
C> FIXNVD

REMOTE/SMITH/HARP

DISK$07:

[SMITH.DISKS] PAYROLL . DAT

(on your PC)

1-12

DECnet-DOS Supplemental Information

FIXNVD will not write to a file unless it is a proper candidate for repair.
NOTE
FIXNVD will make the files and directories allocated in excess of
33,439,744 bytes inaccessible! In fixing the bug and making Version 2 and Version 3 disks compatible, FIXNVD must shrink the
maximum size of 32-megabyte disks. Any files or directories written when the disk volume was filled in excess of 33,439,744 bytes
will become inaccessible. Run CHKDSK to determine if this has

happened:

CHKDSK D:
If the disk volume is filled, reinstall DECnet—-DOS Version 1.1 (or
just NDU.EXE and NDDRV.SYS from DECnet—DOS Version 1.1)
and restore the backed-up virtual disk. Copy the files from the
backed-up disk to two new virtual disks, then reinstall DECnet—
DOS Version 1.2.

1.7

Changes to DECnet-DOS Transparent File Access (TFA)

Transparent file access functions let you open and close a remote file, create or delete a
remote file, read from or write records to a remote file, submit a batch job, or searcha

directory for a specific file or files. Since these functions are performed transparently,
you do not need to use the information in this section unless you are performing network programming tasks.
You can also use TFA to type and copy files to and from remote nodes. Use the following format:
|

TYPE \\f\node\ \ filespec
TYPE \\f\node\\remotefile > localfile
COPY localfile\ \f\node\ \remotefile
You should note that the COPY command only works if the remote file already exists
on the remote node. If the file does not exist on the remote node, the COPY operation
will fail.

1.7.1.

Bug Fixes

TFA has implemented bug fixes for the following problems:
e

§©In previous versions of TFA, a file OPEN operation which specified both read and
write access would only allow writing. Now it only allows reading. TFA cannot
both read and write a file during a single OPEN/CLOSE session.

The Transparent Network Test utility (TNT) previously reported a false error if it
was run right after TFA was installed. An actual error condition did not exist. This
has been fixed so that a false error is no longer reported.

DECnet-DOS Changes

1-13

Read access to a file larger than 64K bytes with null record attributes (such as a

large RUNOFF output file) would appear to succeed, but no data would be
returned. This has been fixed. Data is now returned, indicating whether or not the
Operation succeeded.

Issuing a file CLOSE with a handle of —1 indicates that the logical link in use for
directory functions be closed. TFA did not check to insure that it was open first.
This caused writing to random locations in memory. This has been fixed.

Ifa FIND FIRST FILE function was performed following a FIND FIRST FILE without an intervening CLOSE command (using a handle of -1), an error would occur.
The second FIND FIRST FILE function now closes the link automatically.

1.8

Changes to DECnet-DOS DTR/DTS

In DECnet—DOS Version 1.1, the DECnet Test Receive utility (DTR) would automatically log information to the file DT R.LOG in the DECnet database directory whenever
it was run by the Spawner. DTR no longer does this automatically. In DECnet—DOS
Version 1.2, if you want to log information to the DTR.LOG file you must specify the
/LOG switch. For example:

C:\DTR /LOG
1.9

Changes to the DECnet-DOS Spawner

1.9.1

Bug Fixes

There was a previous parsing restriction for DECSPAWN.DAT (the parameter file for
the Spawner utility) that would only allow a single space between the object name or
number and the parameter associated with it. This restriction has been removed. There
may be multiple spaces and/or tabs between the object name or number and the parameter.

1.9.2
e

Newly Supported Features

The Spawner can now support logging, using the /LOG switch. When you use this
switch, the Spawner creates a file called SPAWNER.LOG in the DECnet database
directory (for example, \DECNET\SPAWNER.LOG). All network accesses are
recorded into this file. The log information will include the name of the connecting
node, the object number, and the time of the request. The information in the log
file will not include any actions that occurred as the result of the request. (Those
actions or results would appear on the screen at the time of the request.)
Format for using the /LOG switch:
SPAWNER /LOG

1-14

DECnet-DOS Supplemental Information

The following is a sample SPAWNER.LOG file:
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986 at
15:41:52
Connect
request
from
node
BOCA
for
object
#17
on Wed
Sep
10
1986
15:42:02
Executing:
fal
-use
2...
on Wed Sep
10 1986 at
15:42:03
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986 at
15:42:08
SPAWNER
exiting...
on Wed Sep
10 1986 at
15:42:14

(In this example, object #17 is FAL, a request to run the File Access Listener.)
e

The Spawner can now execute batch files. For example,
BATCH.BAT file that contains the following information:

you

can

create

ECHO Executing Batch File——Echoing arguments passed:

Echo %1 %2 %3 %4

In this sample file, %1, %2, %3, and %4 represent the different arguments you can
use (such as ARGI, ARG2, and so on).
Then, define the following in your DECSPAWN.DAT file:
#129

C:\DECNET\BATCH.BAT

ARG1

ARG2

When you run the Spawner, it detects a connect request for object number 129 (#
129) and accepts the request. It then spawns the batch file (BATCH.BAT) with the
command line arguments specified in DECSPAWN.DAT (in this case, the arguments are ARG1 and ARG2). The Spawner also passes a socket number to the batch
file. The socket appears as -USE n, where n is the socket number. The batch file can

use this socket, or it can ignore it.

After the batch file completes processing and control is returned to the Spawner,
the Spawner closes the socket whose number it had previously passed to the batch
file. (This is the default. If you do not close the socket from the batch file, the
Spawner will automatically close the one that was opened at the start of the batch
operation.)
The output looks like this:
press
'!'
to abort
SPAWNER
(Version
1.2)
Connect
15:49:36

request

from

listening...
node

BOCA

for

Wed

object

Sep

#129

1986
on

C:\SPAWNER\T>echo
Executing
Batch
File---Echoing
Executing
Batch
File---Echoing
arguments
passed:

C:\SPAWNER\T>Echo
ARG1 ARG2 -USE 2

ARG1

ARG2

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

DECnet-DOS Changes

Wed

-USE

Sep

Wed

at
Sep

arguments

15:49:33
10

1986

passed:

2
on

Wed

Sep

1986

15:49:54

1986

15:49:40

1-15

The Spawner can also pass command line arguments to the servers. For example,
you can now run FAL and include any of the valid FAL qualifiers. The following is a
sample DECSPAWN.DAT file which includes command line arguments for FAL:
#17

FAL

FAL can now be spawned with the arguments

/ERROR

(/E) and /BINARY

(/B). The

output looks like this:
press
‘'!' to abort
SPAWNER
(Version
1.2)

Connect

request

16:01:32

Executing:

from

fal

-use
FAL

listening...

Wed

Sep

1986

node

object

#17

Wed

Sep

BOCA

for

16:01:23

1986

3...
on Wed Sep
10 1986
at
16:01:32
— File Access
Listener
—- Version
1.2

Network
Driver
Version:
1.2
Current
working
directory:C: \SPAWNER\T
All
files will
be sent
as binary.

Existing

files

access

will

checking

NOT

will

overwritten.

done

(world

FAL
running...
DIRECTORY
access

from

BOCA::

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

Wed

for

Sep

DTR

read/write

privileges).

LOCAL""::*.*

on
1986

The following is a sample DECSPAWN.DAT
the /LOG switch:
#63

has

Wed

Sep

1986

16:01:40

16:01:37

file requesting that DTR be run using

/LOG

Now when you run the Spawner, you will see output that looks like this:
press
SPAWNER

to abort
(Version
1.2)

Connect

request

10:22:15

listening...

from

Executing:

dtr

-use

[Appending

messages

node
2...
to

on
log

1-16

exiting...

Wed

Sep

1986

Wed

Sep

MSDOS

for

object

#63

Wed

Sep

10:22:15

file:

Sep

1986

10:22:10
24

1986

C:\DECNET\DTR.
LOG]

DTR --I-- V1.2 (19-Sep-86)
started
DTR --I-- Terminated
on Wed Sep 24
SPAWNER
(Version
1.2)
listening...
SPAWNER

Wed

on Wed Sep 24 1986
1986
at 10:22:16
on Wed Sep 24 1986

1986

10:22:15

10:22:16

10:22:25

DECnet-DOS Supplemental Information

1.9.3

Enhancements

The on-line help text has been updated to include the new functionality.

1.10

Changes to the DECnet-DOS File Access Listener (FAL)

FAL has implemented the following bug fixes for use with RSTS systems:
In previous versions of DECnet—DOS FAL, wildcard access for DELETE operations
from RSTS systems did not work. This has been corrected so that wildcards can be
used in file specifications to delete more than one file at a time.
In previous versions of FAL, DELETE requests from RSTS systems did not include
any confirmation. All of the files in the request were deleted, with no chance of
changing your mind and saving any of the files. This has been corrected so that any
DELETE requests from an RSTS system will first ask for confirmation before a file is
deleted.

1.11.

Changes to the DECnet-DOS Network File Transfer Utility
(NFT)

1.11.1

Enhancements

In DECnet—DOS Version 1.1, the Network File Transfer utility (NFT) displayed the
following message after successful COPY and APPEND operations:
[7 records]
where n represented the number of records copied or appended.
This has been changed so that NFT now reports the number of bytes transferred
and the transfer rate. (The transfer rate is computed by using the time interval from
a successful OPEN of the remote file through a CLOSE of the remote file. The rate
does not include process startup time on the remote system.) The report appears in
the following format:
[7 bytes at m bytes/second]
where 7 is the number of bytes and m bytes/second is the rate at which the bytes
were transferred.
NFT’s performance has been improved significantly.
NFT now prompts you for confirmation of a DELETE request for any of these file
specifications:
COOH

)

, Or

#29

The prompt is in the MS-DOS style:
Are

you

sure

(Y/N)?

DECnet-DOS Changes

1-17

1.12
1.12.1

Changes to the DECnet-DOS Programming Interface Library

(DNETLIB)
Bug Fixes

The Programming Interface Library (DNETLIB) has implemented bug fixes to correct
the following problems:
¢

The dnet__conn( ) function has been fixed to properly check error returns on all
socket calls.

The bug in dnet__getalias( ) has been fixed to properly
attempting to close the DECALIAS.DAT database file.

1.12.2

check

for —1

before

Enhancements

DNETLIB Version 1.2 includes the following enhancements:
e

Socket calls such as send( ), recv( ), swrite( ), and sread( ) have been modified for
improved performance.

The function dnet__getacc( ) now performs case insensitive comparisons
checking incoming access control information.
|

The Break Source utility (BREAKSRC) has been changed to interpret DNETLIB.SRC
as a compressed binary file instead of an ASCII file.

The sources for 3 sample C programs are now included in the DNETLIB.SRC file.
The source file names are:
—
—
—

when

LOOP.C (asample client program)
MIRROR.C (a sample server program)
TYTXAMPL.C (a sample transparent task-to-task program)

Appendix B contains copies of these sample programs.

1.12.3.

Compiling DNETLIB Sources

When certain C compilers are allocating storage for data structures whose members are
larger than a “‘char’’, they may ordinarily begin this storage on “‘int’’ boundaries.
If DNET library sources are compiled in this way, then calls to the DECnet Network
Process (DNP) may fail with errors (for example, “‘Protocol Family not supported’’).
These errors are due to the fact that the data structures which are being passed down to
DNP have some bad bytes. This results in data not being in places where DNP expects
them, or in data structures that are not of the supported byte sizes.
To avoid these data errors, if your C compiler has a switch which causes data structures
to be packed more tightly, then you should use that compiler and the accompanying
switch for compiling the DNET library sources.

1-18

DECnet-—DOS Supplemental Information

1.12.4

Newly Supported Features

Support has been added to the DNET source library to allow building of medium-model
and small-model programs. (A medium-model program is a program that contains multiple code segments and one data segment. A small-model program is a program that
contains one code segment and one data segment.)

1.13

Changes to the DECnet-DOS Data Link Layer (DLL)

The DECnet—DOS DLL that is used with the MICOM driver has implemented a bug fix
for the following:
e

The MICOM driver now responds with the proper device type for MOP system ID
messages.

1.13.1

Enhancements

1.13.1.1
MICOM Driver — An initialization switch has been added to allow
changes to the interrupt request line (IRQ) for the DLL that is used with the MICOM
driver. The switch is:

JTRQ=n
where 7 is a line number from 1 to 7. (DECnet—DOS only supports 7 lines within the PC
bus structure.)
For example:
DLL C:\DECNET /IRQ = 2
If you do not use the switch to change this setting, the default value is 3.
1.13.1.2

3COM

Driver

—

initialization

switch

has

also

been

added

allow

changes to the interrupt request line (IRQ) for the DLL used with the 3COM driver. The
switch is the same as the one used for the DLL MICOM

driver:

MIRQ=n
where 7 is a line number from 1 to 7. (DECnet—DOS only supports 7 lines within the PC
bus structure.)
For example:
DLL C:\DECNET /IRQ = 4
If you do not use the switch to change this setting, the default value is 3.

1.13.1.3

DEPCA Driver

—

The DEPCA is Digital’s new Ethernet communications

board for personal computers. DECnet—DOS Version 1.2 now includes Data Link layer
support for the DEPCA. (To install the DEPCA board, refer to the installation guide that
was included with it.)
The DEPCA Data Link layer is self-configuring. There are no switches needed to specify
the IRQ setting.
DECnet-DOS Changes

1-19

1.14

Changes to DECnet-DOS DECnet Network Process (DNP)

1.14.1

Bug Fixes

A bug which formerly prevented asynchronous accept calls from working properly has
been fixed.
In the Assembly Language SETSOCKOPT and GETSOCKOPT programming calls for
DNP, the size of the sockopt__dn data structure is 12 bytes (not 14 bytes as previously
mentioned in the DECnet-DOS Programmer’s Reference Manual).
The op__optlen data structure listed in the Data Structure Type
SETSOCKOPT and GETSOCKOPT calls should read sop__optlen.

Summary

for the

The snd__how data structure is documented under the SHUTDOWN call, and should
not be listed in the Data Structure Type Summary for the SETSOCKOPT and
GETSOCKOPT calls.

1.14.2

Newly Supported Features

The DECnet—DOS
Enhanced PC/XT.

Network

Process

(DNP)

Version

1.2

now

supports

the

new

In previous versions of DECnet—-DOS, the size of messages used for non-transparent
task-to-task programming was limited to 2K (or 2048 bytes). DNP now supports mes-

sages of up to 4K (or 4096 bytes).
1.14.3

Enhancements

Changes have been made to make DNP more powerful during times when buffers are in
short supply.

1.15

Changes to the DECnet-DOS Scheduler

The Scheduler takes control of the real-time clock for all operations whenever you
start the DECnet—DOS network. To preserve compatibility with applications that are
not well-behaved or with systems that do not have a CMOS clock, a switch has been
added (/S) to the Scheduler startup. This switch lets you force the Scheduler to use the
system clock instead of the real-time clock.
To use the /S switch, you can enter it at the DOS prompt or you can include it in the
batch (or command) file that you use to start the network.

1-20

DECnet-DOS Supplemental Information

Example 1 (from the DOS prompt):
C> SCH/S

or
C> SCH

Example 2 (a sample AUTOEXEC.BAT batch file):
echo off
set COMSPEC=C
: \COMMAND. COM
PATH C:\DECNET\:C:\TASKS:C:\DOS

REM
SCH

DLL
LAT
DNP

TTT

***
/S

DECnet-DOS

Ethernet

C:\DECNET\
C:\DECNET\

TFA

DECnet-DOS Changes

Configuration

***

DECnet-Rainbow Changes

2.1

Overview

This chapter describes the changes that have been made from DECnet-—Rainbow Version 1.0 and 1.1 to DECnet—Rainbow Version 1.2. The changes are highlighted in the
following list, then broken down by components in later sections.

2.2

Highlight of Changes from Previous Versions of
DECnet-Rainbow

e 6. Bug fixes.
e

Performance improvements to Network File Transfer (NFT).

Functional improvements to the Job Spawner and the DECnet Test Receive utility
(DTR).

Changes to the DECnet-Rainbow
Programming Interface Library sources
(DNETLIB) that provide enhanced performance for programming applications that
use this library.

The following sections describe changes that have been made to the individual components.

2.3

Changes to the DECnet-Rainbow Installation Procedure (DIP)

The DECnet—Rainbow Installation Procedure (DIP) is an automated procedure that lets
you easily install DECnet—Rainbow by responding to a set of questions and making
selections from a series of menus. Refer to the DECnet-—Rainbow Installation Guide
for instructions on how to use DIP, while noting the changes and enhancements that
are described here.
2-1

2.3.1

Enhancements

During installation, DIP now performs the following operations:
e

Checks for the proper version of the DIP.DAT/DIP.SAV database and displays an
error if it is an incompatible version.

Provides enhanced performance for copying files from the kit.

Runs the new
reboot.

Copies the FIXNVD.EXE file automatically from the kit if you have selected the
Network Device utility (NDU) to be installed. (Refer to Section 2.6 for information
about using FIXNVD.EXE with NDU.)

§6©Displays the current EXECUTOR node name and address if DECnet is already
installed and is running on your system. DIP gives you the option of changing the
node name and address at the same time it displays the information.

Creates and/or modifies the Spawner Database File (DECSPAWN DAT).

Creates backup copies of the CONFIG.SYS and AUTOEXEC.BAT files before editing them. The backup files have the extension .BAK. For example:

configuration and verification utility automatically upon
|

system

CONFIG.SYS will have a backup file named CONFIG.BAK
AUTOEXEC.BAT will have a backup file named AUTOEXEC.BAK
If you select the Job Spawner, FAL, or DTR during the installation procedure, DIP
will also create a backup copy of the DECSPAWN.DAT file. For example:
DECSPAWN.DAT will have a backup file named DECSPAWN.BAK

2.4
2.4.1

Changes to DECnet-Rainbow SETHOST
Bug Fixes

The “partial escape sequence seen”’ error observed when running ALL-IN—1
2.0 software over a CTERM link has been fixed.

2.4.2

Version

Newly Supported Features

DECnet—Rainbow now includes support for 8-bit multinational character sets over a
CTERM link. (You should note that full use of 8-bit character sets is limited due to hardware and operating system constraints.)
DECnet—Rainbow also supports 132 columns as a terminal characteristic. You can
set 132-column mode either by using the Rainbow’s Setup menu or by issuinga
terminal command. For example, on VMS systems you would use the command
SET TERM/WIDTH = 132.

2-2

DECnet-DOS Supplemental Information

2.4.3

Enhancements

A new switch has been added to SETHOST,

/SWITCH = n.

The /SWITCH =n switch lets you specify a character to use for accessing the
SETHOST menu during an active session. By default, the
key combination displays this menu. In previous versions, the
key combination
would display this menu. (The
combination was difficult to use with
European keyboards, so the default was changed to
(RET).) Both combinations will display the menu.
|

NOTE
This is a two-step sequence. In order for
to work
properly, you must first press
and (4) simultaneously, then
release the two keys and press (RET).
With /SWITCH, you can replace the
default with a different character. The
variable m can be an ASCII decimal code character from 1 to 28 (where 1 is equivalent to CCTRUA), 2 is equivalent to (CTRUB), and so on).
For example:

SETHOST /SWITCH = 2 would change
Using SETHOST

/SWITCH

to (CTRUBYRET).

with no argument resets the default of (CTRU/4\RET).

NOTE

When you use on-line HELP for SETHOST, you will see other
switches listed (/KEYBOARD, /SERVICE, and /SETUP). These
other switches have no effect on DECnet—Rainbow SETHOST.
Two

files, NVTDEF.DAT

and

NVTVID.DAT, are

created when

using

SETHOST.

These files contain information about the version of SETHOST that you are using.
The NVTDEF.DAT
file is created when you use the /SAVE switch. The
NVTVID.DAT file is created when you save information using the Save Parameters
option in the Setup menu. In previous versions of SETHOST, the files were named
SETHOST.DEF and VT102.DAT. The older versions of the files are still intact if you
want to use them, but you should use the new files.
When you start SETHOST,
it checks for the proper version number in
NVTVID.DAT. If SETHOST determines that this file contains the wrong version, it
will beep and ignore the information in the file. You should use the Save Parameters option to replace the NVI'VID.DAT file with an updated copy that contains the
correct information.

DECnet-Rainbow Changes

2-3

§=6If you are using ALL-IN-1 or WPS-PLUS software on a VT 100 terminal, DEC multinational characters are not displayed. In order to get WPS-—PLUS software to use
the multinational character set (MCS) and to properly display the MCS characters in
the on-line help screens, you need to define the following symbols on your VMS
system:

DEFINE KOA$TERMINAL__xxxx ‘““OUTPUT__SETHOST”’
DEFINE KOA$TERMINAL__MCS__SETHOST “‘Y”’
where xxxx is the terminal name (such as RTA1, VTA32, and so on).

2.5

Changes to the DECnet-Rainbow Mail Utility

Mail no longer uses the access control information that is saved by NCP.
Mail now adds the DECnet node address of the mail sender to the Subject field, just
before the ‘‘Reply to’’ address. In Version 1.1, this address was not included. Now
when other users receive mail from your DECnet—Rainbow node, your node’s address
appears in this field. For example:
Subj:

Finance

Meeting

"From

55.125,

GRAVY:

:NELSON"

2.6

Changes to the DECnet-Rainbow Network Device Utility (NDU)

After you issue an NDU DELETE command, NDU now prompts you for confirmation in
the MS-DOS style:
Are

you

2.6.1

sure

(Y/N)?

Bug Fixes

In DECnet—Rainbow Version 1.1, the virtual disk facility was shipped with the following problems:
1.

A bug caused all DECnet-—Rainbow Version 1.1 32-megabyte disks created as the
first NDU function after a system boot (under MS-DOS or PC DOS Version 2 systems) to have an error in their headers. This error does not affect the performance
or integrity of the virtual disk facility.

32-megabyte disks created under MS-DOS or PC DOS Version 2 systems are not
usable from MS—DOS or PC DOS Version 3 systems. (The opposite of this is also
true: 32-megabyte disks created on MS-DOS or PC DOS Version 3 systems are not
usable from MS—DOS or PC DOS Version 2 systems.)

DECnet—Rainbow Version 1.2 solves both of these problems with the following:
e §=6 All virtual disks created by DECnet—Rainbow Version 1.0 remain usable in all configurations.
e

2-4

§=6All 1.2-, 10-, and 20-megabyte virtual disks created by DECnet—Rainbow Version
1.1 remain usable in all configurations.

DECnet-DOS Supplemental Information

§=6All 32-megabyte virtual disks created by DECnet—Rainbow Version 1.1 under MSDOS or PC DOS Version 3 systems will remain usable on any Version 3 system.
These disks are not usable from MS-DOS or PC DOS Version 2 systems.

32-megabyte virtual disks created by DECnet—Rainbow Version 1.1 under MS—
DOS or PC DOS Version 2 systems are not usable with DECnet—Rainbow Version
1.2 until they are repaired using the FIXNVD utility. The FIXNVD utility is automatically installed by the DECnet—Rainbow Installation Procedure, DIP. The utility’s file name is FIXNVD.EXE.
If you attempt to open a Version 1.1 virtual disk with Version 1.2, NDU generates
the following error message:
Cannot
OPEN
Run FIXNVD

this
disk
first.

created

with

older

release

DECnet.

To use the FIXNVD utility, first make a copy of your virtual disk file. For example:
$ COPY

V1IIDISK1.FIL

V11DISKBU.DSK

Now you can run FIXNVD on the new file. This is the syntax for using FIXNVD:
FIXNVD node[/user/password/account] backup-disk-name
Example 1:

¢ COPY VDISK.DSK

DISK.007

(on VMS node VMSNOD)
C> FIXNVD VMSNOD DISK.007
(on your PC)
Example 2:
$ COPY

VDISK.DSK

DISK$07:

[SMITH. DISKS] PAYROLL

. DAT

(on VMS node REMOTE)
C> FIXNVD

REMOTE/SMITH/HARP

DISK$07:

[SMITH.DISKS] PAYROLL . DAT

(on your PC)

~ DECnet-Rainbow Changes

2-5

FIXNVD will not write to a file unless it is a proper candidate for repair.
NOTE
FIXNVD will make the files and directories allocated in excess of

33,439,744 bytes inaccessible! In fixing the bug and making Ver-

sion 2 and Version 3 disks compatible, FIXNVD must shrink the
maximum size of 32-megabyte disks. Any files or directories written when the disk volume was filled in excess of 33,439,744 bytes
will become inaccessible. Run CHKDSK to determine if this has
happened:
CHKDSK D:
If the disk volume is filled, reinstall DECnet—Rainbow

Version

1.1

(or just NDU.EXE and NDDRV.SYS from DECnet—Rainbow Version 1.1) and restore the backed-up virtual disk. Copy the files
from the backed-up disk to two new virtual disks, then reinstall
DECnet-—Rainbow Version 1.2.

2.7

Changes to DECnet-Rainbow Transparent File Access (TFA)

Transparent file access functions let you open and close a remote file, create or delete a
remote file, read from or write records to a remote file, submit a batch job, or searcha

\\f\node\ \ filespec

COPY

localfile\ \f\node\\remotefile

TYPE

\\f\node\ \remotefile > localfile

You should note that the COPY command only works if the remote file already exists
on the remote node. If the file does not exist on the remote node, the COPY operation
will fail.

2.7.1

Bug Fixes

TFA has implemented bug fixes for the following problems:
e

In previous versions of TFA, a file OPEN operation which specified both read and
write access would only allow writing. Now it only allows reading. TFA cannot
both read and write a file during a single OPEN/CLOSE session.

The Transparent Network Test utility (TNT) previously reported a false error if it
was run right after TFA was installed. An error condition did not exist. This has
been fixed so that a false error is no longer reported.

2-6

DECnet-—DOS Supplemental Information

Read access to a file larger than 64K bytes with null record attributes (such as a
large runoff output file) would appear to succeed, but no data would be returned.
This has been fixed. Data is now returned, indicating whether or not the operation
succeeded.
|

Issuing a file CLOSE with a handle of -1 indicates that the logical link in use for
directory functions be closed. TFA did not check to insure that it was open first.
This caused writing to random locations in memory. This has been fixed.

Ifa FIND FIRST FILE function is performed following a FIND FIRST FILE without
an intervening CLOSE command (using a handle of —1), an error would occur. The
second FIND FIRST FILE function now closes the link automatically.

2.8

Changes to DECnet-Rainbow DTR/DTS

In DECnet—Rainbow Version 1.1, the DECnet Test Receive utility (DTR) would automatically log information to the file DTR.LOG in the DECnet database directory whenever it was run by the Spawner. DTR no longer does this automatically. In DECnet-—
Rainbow Version 1.2, if you want to log information to the DTR.LOG file you must
specify the /LOG switch. For example:
C:\DTR

2.9
2.9.1

/LOG

Changes to the DECnet—Rainbow Spawner
Bug Fixes

There was a previous parsing restriction for DECSPAWN.DAT (the parameter file for
the Spawner utility) that would only allow for a single space between the object name
or number and the parameter associated with it. This restriction has been removed.
There may be multiple spaces and/or tabs between the object name or number and the
parameter.

DECnet-Rainbow Changes

2-7

2.9. 2

Newly Supported Features

The Spawner can now support logging, using the /LOG switch. When you use this
switch, the Spawner creates a file called SPAWNER.LOG in the DECnet database

directory (for example, \DECNET\SPAWNER.LOG). All file accesses are recorded

into this file. The log information will include the name of the connecting node,
the object number, and the time of the request. The information will not include
any actions that occurred as the result of the request.
For example:
SPAWNER /LOG
The following is a sample SPAWNER.LOG file:
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986
at 15:41:52
Connect
request
from
node
BOCA
for
object
#17
on Wed
Sep
10 1986
15:42:02
Executing:
fal
-use
2...
on Wed Sep
10 1986
at 15:42:03
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986 at
15:42:08
SPAWNER
exiting...
on Wed Sep
10 1986 at
15:42:14

(In this example, object #17 is FAL, a request to run the File Access Listener.)
The Spawner can now execute batch files. For example,
BATCH.BAT file that contains the following information:

you

can

create

ECHO Executing Batch File——Echoing arguments passed:

Echo %1 %2 %3 %4
In this sample file, %1,

%2,

%3, and %4 represent the different arguments you can

use (such as ARG1, ARG2, and so on).
Then, define the following in your DECSPAWN.DAT file:
#129

C:\DECNET \BATCH.BAT

ARG1

ARG2

DECnet—DOS Supplemental Information

After the batch file completes processing and control is returned to the Spawner,
the Spawner closes the socket whose number it had previously passed to the batch
file. (This is the default. If you do not close the socket from the batch file, the
Spawner will automatically close the one that was opened at the start of the batch
operation.)
The output looks like this:
press
‘'!'
to abort
SPAWNER
(Version
1.2)
Connect
15:49:36

request

listening...

from

node

BOCA

for

Wed

object

Sep

#129

C:\SPAWNER\T>
echo Executing
Batch
File---Echoing
Executing
Batch
File---Echoing
arguments
passed:

C:\SPAWNER\T>Echo
ARG1 ARG2 -USE 2

ARG1

ARG2

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

Wed

-USE

Sep

1986

Wed

Sep

15:49:33
10

arguments

1986

passed:

Wed

Sep

1986

15:49:54

1986

15:49:40

FAL

FAL can now be spawned with the arguments /ERROR (/E) and /BINARY (/B). The
output looks like this:
press
'!'
to abort
SPAWNER
(Version
1.2)
Connect
16:01:32

request

Executing:

from

fal

Network

Driver

Existing

files

-use
FAL

listening...

Wed

Sep

1986

node

object

#17

Wed

Sep

BOCA

for

16:01:23
10

1986

3...
on Wed Sep
10 1986
at
16:01:32
—- File Access
Listener
—- Version
1.2

Version:

1.2

will

Current
working
directory:C: \SPAWNER\T
All
files will
be sent
as binary.
No

FAL

access

checking

running...

DIRECTORY

NOT

will

overwritten.

done

(world

access

from

BOCA::

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

DECnet-Rainbow Changes

Wed

Sep

for

has

read/write

privileges).

LOCAL""::+*. +*
on

Wed

Sep

1986

16:01:40

1986

16:01:37

2-9

The following is a sample DECSPAWN.DAT file, requesting that DTR be run using
the /LOG switch:
#63

DTR

/LOG

Now when you run the Spawner, you will see output that looks like this:
press

1986

‘!'

abort

SPAWNER

10:22:10

Connect
request
10:22:15

from

Executing:

dtr

-use

[Appending

messages

(Version

node
2...
to

on
log

2.9.3

exiting...

Wed

listening...

MSDOS

for

object

#63

Wed

Sep

10:22:15

file:

Sep

1986

Wed

Sep

1986

C:\DECNET\DTR.LOG]

DTR --I-- V1.2
(19-Sep-86)
started
DTR --I-- Terminated
on Wed Sep 24
SPAWNER
(Version
1.2)
listening...
SPAWNER

1.2)

on Wed Sep 24 1986
1986
at 10:22:16
on Wed Sep 24 1986

1986

10:22:15

10:22:16

10:22:25

Enhancements

The on-line help text has been updated to include the new functionality.

2.10.

Changes to the DECnet-Rainbow File Access Listener (FAL) |

FAL has implemented the following bug fixes for use with RSTS systems:
e

In previous versions of DECnet—Rainbow FAL, wildcard access for DELETE operations from RSTS systems did not work. This has been corrected so that wildcards
can be used in file specifications to delete more than one file at a time.

In previous versions of FAL, DELETE requests from RSTS systems did not include
any confirmation. All of the files in the request were deleted, with no chance of
changing your mind and saving any of the files. This has been corrected so that any
DELETE requests from an RSTS system will first ask for confirmation before a file is
deleted.

2.11

Changes to the DECnet-Rainbow Network File Transfer

Utility (NFT)

2.11.1
e

Enhancements

In DECnet—Rainbow Version 1.1, the Network File Transfer utility (NFT) displayed
the following message after successful COPY and APPEND operations:
[7 records]
where 7 represented the number of records copied or appended.

2-10

DECnet-—DOS Supplemental Information

After the batch file completes processing and control is returned to the Spawner,
the Spawner closes the socket whose number it had previously passed to the batch
file. (This is the default. If you do not close the socket from the batch file, the
Spawner will automatically close the one that was opened at the start of the batch
Operation.)
The output looks like this:
press
'!'
to abort
SPAWNER
(Version
1.2)
Connect
15:49:36

request

listening...

from

node

BOCA

for

Wed

object

Sep

#129

C:\SPAWNER\T>
echo Executing
Batch
File---Echoing
Executing
Batch
File---Echoing
arguments
passed:

C:\SPAWNER\T>Echo
ARG1 ARG2 -USE 2

ARG1

ARG2

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

Wed

-USE

Sep

1986

Wed

Sep

15:49:33
10
|

arguments

1986

passed:

Wed

Sep

1986

15:49:54

1986

15:49:40

FAL

FAL can now be spawned with the arguments /ERROR (/E) and /BINARY (/B). The
output looks like this:
press
SPAWNER

to abort
(Version
1.2)

listening...

Wed

Sep

1986

Connect

request

node

object

#17

Wed

Sep

16:01:32

Executing:

from

fal

Network

Driver

Existing

files

-use
FAL

BOCA

for

16:01:23
10

1986

3...
on Wed Sep
10 1986
at
16:01:32
- File Access
Listener
— Version
1.2

Version:

1.2

will

Current
working
directory:C: \SPAWNER\T
All
files will
be sent
as binary.
No

access

checking

NOT

will

overwritten.

done

(world

FAL
running...
DIRECTORY
access

from

BOCA::

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

DECnet-Rainbow Changes

Wed

Sep

for

has

read/write

privileges).

LOCAL""::*.*
on

Wed

Sep

1986

16:01:40

1986

16:01:37

2-9

The following is a sample DECSPAWN.DAT file, requesting that DTR be run using
the /LOG switch:
#63

DTR

/LOG

Now when you run the Spawner, you will see output that looks like this:
press

1986

‘'!'

abort

SPAWNER

10:22:10

Connect
10:22:15

request

from

Executing:

dtr

-use

[Appending

messages

(Version

node
2...
to

on
log

2.9.3

exiting...

Wed

listening...

MSDOS

for

object

#63

Wed

Sep

10:22:15

file:

Sep

1986

Wed

Sep

1986

C:\DECNET\DTR.LOG]

DTR --I-- V1.2
(19-Sep-86)
started
DTR --I-- Terminated
on Wed Sep 24
SPAWNER
(Version
1.2)
listening...

SPAWNER

1.2)

on Wed Sep 24 1986
1986
at
10:22:16
on Wed Sep 24 1986

1986

10:22:15

10:22:16

10:22:25

Enhancements

The on-line help text has been updated to include the new functionality.

2.10. Changes to the DECnet-Rainbow File Access Listener (FAL)
FAL has implemented the following bug fixes for use with RSTS systems:
e

2.11

Changes to the DECnet-Rainbow Network File Transfer

Utility (NFT)

2.11.1
¢

Enhancements

In DECnet—Rainbow Version 1.1, the Network File Transfer utility (NFT) displayed
the following message after successful COPY and APPEND operations:
[72 records]
where 7 represented the number of records copied or appended.

2-10

—

DECnet-—DOS Supplemental Information

This has been changed so that NFT now reports the number of bytes transferred
and the transfer rate. (The transfer rate is computed by using the time interval from
a successful OPEN of the remote file through a CLOSE of the remote file. The rate
does not include process startup time on the remote system.) The report appears in
the following format:
[72 bytes at m bytes/second]
where 7 is the number of bytes and m bytes/second is the rate at which the bytes
were transferred.
NFT’s performance has improved significantly.
NFT now prompts you for confirmation of a DELETE request for any of these file
specifications:
-

COR

og OR FE
COe

kD?

The prompt is in the MS—DOS style:
Are

you

sure

(Y/N)?

2.12

Changes to the DECnet-Rainbow Programming Interface
Library (DNETLIB)

2.12.1

Bug Fixes

The Programming Interface Library (DNETLIB) has implemented bug fixes to correct
the following problems:
The dnet__conn( ) function has been fixed to properly check error returns on all
socket calls.
The bug in dnet__getalias() has been fixed to properly
attempting to close the DECALIAS.DAT database file.
2.12.2

check

for —1

before

Enhancements

DNETLIB Version 1.2 includes the following enhancements:
Socket calls such as send(), recv( ), swrite( ), and sread( ) have been modified for
improved performance.
The function dnet__getacc( ) now performs case insensitive comparisons
checking incoming access control information.

when

The Break Source utility (BREAKSRC) has been changed to interpret DNETLIB.SRC
as a compressed binary file instead of an ASCII file.

DECnet-Rainbow Changes

2-11

The sources for 3 sample C programs are now included in the DENETLIB.SRC file.
The source file names are:
-

LOOP.C (asample client program)
MIRROR.C (a sample server program)
TTTXAMPL.C (a sample transparent task-to-task program)

Appendix B contains copies of these sample programs.

2.12.3

Compiling DNET Library Sources

When certain C compilers are allocating storage for data structures whose members are
larger than a ‘“‘char’’, they may ordinarily begin this storage on “‘int’’ boundaries.
If DNET library sources are compiled in this way, then calls to the DECnet Network
Process (DNP) may fail with errors (for example, “‘Protocol Family not supported’’).
These errors are due to the fact that the data structures which are being passed down to
DNP have some bad bytes. This results in data not being in places where DNP expects
them, or in data structures that are not of the supported byte sizes.
To avoid these data errors, if your C compiler has a switch which causes data structures
to be packed more tightly, then you should use that compiler and the accompanying
switch for compiling the DNET library sources.

2.12.4

Newly Supported Features

2.13

Changes to DECnet-Rainbow DECnet Network Process (DNP)

2.13.1

Bug Fixes

A bug which formerly prevented asynchronous accept calls from working properly has
been fixed.
In the Assembly Language SETSOCKOPT and GETSOCKOPT programming calls for
DNP, the size of the sockopt__dn data structure is 12 bytes (not 14 bytes as previously
mentioned in the DECnet—DOS Programmer's Reference Manual).
The op__optlen data structure listed in the Data Structure Type
SETSOCKOPT and GETSOCKOPT calls should read sop__optlen.
The snd__how

data structure is documented

not be listed in the
GETSOCKOPT calls.

2-12

Data

Structure

Type

Summary

under the SHUTDOWN

Summary

for

the

for the

call, and should

SETSOCKOPT

and

DECnet-DOS Supplemental Information

2.13.2

Enhancements

Changes have been made to make DNP more powerful during times when buffers are in
short supply.
In previous versions of DECnet—Rainbow, the size of messages used for non-transparent task-to-task programming was limited to 2K (or 2048 bytes). DNP now supports
messages of up to 4K (or 4096 bytes).

DECnet-Rainbow Changes

—

2-13

DECnet-VAXmate Changes

3.1

Overview

This chapter describes the changes that have been made from DECnet-VAXmate Version 1.0 to DECnet-VAXmate Version 1.2 (there is no Version 1.1 for this product).
The changes are highlighted in the following list, then broken down by components in
later sections.

3.2

Highlight of Changes from Version 1.0 of DECnet-VAXmate
Bug fixes.
Performance improvements to Network File Transfer (NFT).
Functional improvements to the Job Spawner and the DECnet Test Receive utility
(DTR).
SETHOST local IBM-style print screen support.
SETHOST support for DEC national character sets (7-bit) and DEC multinational
character sets (8-bit).
Changes to the DECnet-VAXmate
Programming Interface Library sources
(DNETLIB) that provide enhanced performance for programming applications that
use this library.

The following sections describe changes that have been made to the individual components.

3-1

3.3

Changes to the DECnet-VAXmate Installation Procedure (DIP)

The DECnet—VAXmate Installation Procedure (DIP) is an automated procedure that
lets you easily install DECnet-VA Xmate by responding to a set of questions and making
selections from a series of menus. Refer to the DECnet-VAXmate Installation Guide
for instructions on how to use DIP, while noting the changes and enhancements that
are described here.
3.3.1

Enhancements

During installation, DIP now performs the following operations:
Checks for the proper version of the DIP.DAT/DIP.SAV database and displays an
error if it is an incompatible version.
Provides enhanced performance for copying files from the kit.
Checks the communication type of the DECnet-VAXmate Parameter File
(DECPARM.DAT, if one exists). If the new configuration is for a different communications type, DIP deletes the existing DECPARM.DAT. It creates a new
DECPARM.DAT when the network is reloaded and NCP is rerun.
Runs the new
reboot.

configuration and verification utility automatically upon

system

Copies all character translation tables and keyboard screen template files automatically from the kit to the specified DECnet database path (if you select
SETHOST.EXE to be installed).
Copies the FIXNVD.EXE file automatically from the kit if you select the Network
Device utility (NDU) to be installed. (Refer to Section 3.6 for information about
using FIXNVD.EXE with NDU.)
Displays the current EXECUTOR node name and address if DECnet software is
already installed and is running on your system. DIP gives you the option of changing the node name and address at the same time it displays the information.
Creates and/or modifies the Spawner database file (DECSPAWN.DAT).
Creates backup copies of the CONFIG.SYS and AUTOEXEC.BAT files before editing them. The backup files have the extension .BAK. For example:
CONFIG.SYS will have a backup file named CONFIG.BAK
AUTOEXEC.BAT will have a backup file named AUTOEXEC.BAK
If you select the Job Spawner, FAL, or DTR during the installation procedure, DIP
will also create a backup copy of the DECSPAWN.DAT file. For example:
DECSPAWN.DAT will have a backup file named DECSPAWN.BAK

DECnet-DOS Supplemental Information

3.3.2

Using DIP ina VAXmate/VMS Services Environment

If you are installing DECnet-VAXmate into a VAXmate/VMS
you should note the following information:
1.

Services environment,

DIP assumes that an AUTOEXEC.BAT file already exists on the boot
preconfigured by the VAXmate/VMS Services installation procedure).

drive (as

DIP assumes that the NET START RDR command exists in this AUTOEXEC.BAT
file. This is the command that starts up the components that are necessary for running MS—NET software. DIP uses this command as a flag to properly edit the
AUTOEXEC.BAT file for a DECnet-VA Xmate/MS-NET
installation.

3.4

Changes to DECnet-VAXmate SETHOST

3.4.1

Bug Fixes

SETHOST has implemented bug fixes for the following problems:
In the previous version, using the HOLD SCREEN key while connected over a
CTERM link would cause the system to hang. This has been fixed so the HOLD
SCREEN now works properly with CTERM.
In the previous version, if you were logging a session to the disk and the disk
became full, the system would hang. This has been fixed so that instead of hanging
the system when the disk fills up, SETHOST now closes the file and displays an
error message.

DECnet-VAXmate Changes

3-3

3.4.2

Newly Supported Features

SETHOST Version 1.2 includes support for the following:
The DEC LK250 keyboard.
Three new switches (see Section 3.4.3)
DEC national character sets (7-bit) and DEC multinational character sets (8-bit).
The following is a detailed list of the character sets that are available with
SETHOST:
—
—
—
~
—
—
—

DEC Multinational STD 1 Character Set
DEC Multinational STD 2 Character Set
United States/Canada Character Set
Dutch Character Set
Finnish Character Set
French Canadian Character Set
French Character Set

—
—

German Character Set
Italian Character Set

—
—

Swedish Character Set
Swiss Character Set

—
—

—

Norweégian/Danish Character Set
Spanish Character Set

United Kingdom Character Set

(You should note that full use of 8-bit character sets is limited due to hardware and
Operating system constraints.)
You can select or change character sets from the General setup menu, which is now
accessible with the new /SETUP switch. (Refer to the following section which
describes the three new switches for SETHOST.)
Use of 132 columns. To use 142-column support, you must have color enabled on
your monitor (the default is monochrome). To change from the default, use the
Setup menu to enable color. Then, you can set the terminal characteristic to 132
columns by issuing a terminal command (for example, on VMS systems you would
use the command SET TERM/WIDTH = 132). You can easily switch back and forth
between screens by using the
key combination.
The underline character (__) is now visible. Use the Setup menu to change your terminal mode to COLOR ENABLED if you want to display this character. (As an alternative, you can turn up the intensity on your VAXmate workstation monitor to display the underline character.)

DECnet-—DOS Supplemental Information

3.4.3

New Switches

Three new switches have been added to SETHOST. These switches allow you to:
e

§6display the LAT service name table (similar to the SHOW SERVICES command ona
terminal server).

change the setup for the terminal emulator without having to make a network connection first.
:

change the switch character that SETHOST uses for accessing the SETHOST menu.

The switches are:
1.

/SERVICE

/SETUP

/SWITCH=n

3.4.3.1

/SERVICE

—

The /SERVICE switch displays the personal computer LAT

driver’s service name table. This table lists the services that are available for use by LAT.
The services listed are those that have been defined using NCP or those that are advertised on the local area network. You can only connect to a service whose name appears
in the service name table.
The default size of the service name table is 10. You can change the size of the table by
using the LAT switch, /D:n. (The DECnet—VA Xmate Installation Procedure places the
LAT command in the AUTOEXEC.BAT file without any switches. To add the /D switch
and change the value of n, edit the AUTOEXEC.BAT file.) The value of 7 is added to the
default value of 10. For example, if you specify LAT /D:4, the list displayed by
SETHOST /SERVICE can include up to 14 service names.
Once you have seen the list of services that are available, you can connect to any of the
services by issuing the SETHOST service-name command. (You must be using LAT protocol for the connection.)

3.4.3.2

/SETUP

—

The /SETUP switch allows you to invoke the setup menus with-

out having to make a network connection. You can change settings in any of the setup
directories. Use the cursor arrow keys to move between boxes, then press
or
to make a selection in each box. When you have completed all of your selections, use the Save Parameters option in the Action menu to save the new defaults.

DECnet-VAXmate Changes

3-5

3.4.3.3

use

/SWITCH=n

for

—

The /SWITCH=7

switch lets you specify a

character

accessing the SETHOST menu during an active session. By default, the
key combination displays this menu. In the previous version of DECnetVAXmate, the
key combination would display this menu. (The
combination was difficult to use on European keyboards, so the default was changed to
(RET).) Both combinations will display the menu.

NOTE
This is a two-step sequence. In order for
to work properly, you must first press
and (4) simultaneously, then release the
two keys and press (RET).
With /SWITCH =n, you can replace the
default with a different character. The
variable m can be an ASCII decimal code character from 1 to 28 (where 1 is equivalent to
(CTRUA), 2 is equivalent to CCTRUB), and so on).
For example:
SETHOST

/SWITCH

Using SETHOST

= 2 would change

to CCTRL/B XRET ).

/SWITCH with no argument resets the default of (CTRU4)RET).
NOTE

When you use on-line help for SETHOST, you will notice that a fourth
switch (/KEYBOARD) is also listed. This switch allows users to change
keyboards from the default VAXmate (LK250) keyboard. However, it
is not necessary to change keyboards when using DECnet-~VA Xmate
because you should already be using the VAXmate keyboard.
3.4.4

Enhancements

SETHOST Version 1.2 includes the following enhancements:
e

There is anew keyboard handler. It takes over the keyboard interrupt only for the
keys it needs. All other keys are handled or processed by the standard VAXmate
MS-DOS operating system. This allows some software that was not compatible
with DECnet-VAXmate Version 1.0 to run with DECnet-VA Xmate Version 1.2.

§6There is now a way to configure SETHOST for international keyboards. To do this,
follow these steps:

3-6

Tell SETHOST which character set you wish to use (follow steps 3 through 6).

DECnet-DOS Supplemental Information

YY
Oe

Use the arrow keys and the

Type SETHOST/SETUP to get into the Setup menu.

key to get to the General menu.

Select the character set you want to use.
Save this as the new default by using the Save Setup Parameters option on the
Action menu.

SETHOST provides translation only from the ROM character set toa DEC character
set and back again. On the VAXmate workstation, this means that the VAXmate
international key sequences will work to generate a VAXmate IBM-compatible
character code. This code will then be translated by SETHOST into a DEC character.
For example:

—

Two-key
press e.)

compose

sequences.

(To display €, you must first press “and then

—

to toggle back to a US English keyboard layout. (Press all 3 keys at
the same time.)
to toggle back to the country keyboard layout.

—

(AlTinn), where nnn is a 3-digit decimal number. This combination can be used
to generate any IBM ROM character.

SETHOST also has a DEC COMPOSE key. However, the operating system (DOS)
sees the keys first and may choose to preempt some of the keys for the VAXmate
style of international support. If this happens, there are two ways around it:
1.

Use the VAXmate method
or

Use
to switch temporarily back to a US English keyboard, then use
the COMPOSE key.
|

DEC’s multinational STD 2 character set is for use in Norway and other countries
that use character set ROMs that are different from the US character set ROMs.

The character set files that SETHOST uses for translating are stored in the DECnet
database directory (for example, C:\DECNET \*.CHR). These are ASCII text files,
and they contain two 256-character tables. The first table is the DECVM table. The
DEC character looks into this table to find the character it needs, then returns the
VAXmate ROM character (which is then displayed on the screen). The second table
is the VMDEC table. The VAXmate ROM character looks into this table to find the
character that it needs, then returns the DEC character (which is then displayed on
the screen).

DECnet-VAXmate Changes

3-7

Since SETHOST uses the VAXmate ROM character set and not a graphic character
set for displaying characters, you are limited in the use of certain characters. When
you select a character from the character set file, SETHOST tries to determine the
closest match to the character you want to display.
In the General setup menu, leaving or moving out of the character set menu causes
the character set file that you selected to be read to the disk. You can make your
selection while you are still in this menu, but it will not take effect until you move
out of the menu. Once you have left the menu, the file you selected will replace the
internal tables that SETHOST uses. If you hear a beep, then that file was not found.
SETHOST’s default table is for DEC multinational character sets with a US keyboard (this also works for 7-bit US keyboards). SETHOST will not beep if the
DECM1.CHR or US.CHR files cannot be found; it will just use the default tables.
Since the VT100 terminal does not have an escape sequence to tell the remote system that SETHOST can use 8-bit characters, you must tell the remote system and
the SETHOST terminal emulator to use 8-bit characters (if you select the DEC multinational character set). For example, on a remote VMS system, you would add

SET TERM/EIGHT to your LOGIN.COM file.

For the 7-bit national character sets, some keys will display different characters
depending on whether the keyboard is in typewriter mode or in data processing
mode. You can switch from one mode to the other using the General setup menu.
This allows you to get to characters that would normally be available only with
DEC multinational character sets.
The keys that are affected by this are 4, CD, CD, @,

CQ, C), C,

CD, O,

0, and ©.

the file names were SETHOST.DEF

and VT102.DAT.

The older version

of SETHOST will continue to use these files.
When you start SETHOST,
it checks for the proper
NVTVID.DAT. If SETHOST determines that this file contains
will beep and ignore the information in the file. You should
ters option to replace the NVTVID.DAT file with an updated
the correct information.

version number in
the wrong version, it
use the Save Parameversion that contains

DECnet-DOS Supplemental Information |

If you are using ALL-IN-—1 or WPS—PLUS software on a VT 100 terminal, DEC multinational characters are not displayed. In order to get WPS—PLUS software to use
the multinational character set (MCS) and to properly display the MCS characters in
the on-line help screens, you need to define the following symbols on your VMS
system:

DEFINE KOA$TERMINAL_xxxx ““OUTPUT__SETHOST”’
DEFINE KOA$TERMINAL__MCS__SETHOST “‘Y”’
where xxxx is the terminal name (such as RTA1, VTA32, and so on). .

3.5

Changes to the DECnet-VAXmate Mail Utility

Mail no longer uses the access control information that is saved by NCP.
Mail now adds the DECnet node address of the mail sender to the Subject field, just
before the ‘“‘Reply to’’ address. In Version 1.0, this address was not included. Now
when other users receive mail from your DECnet-VA Xmate node, your node’s address
appears in this field. For example:
Subj:

Finance

Meeting

"From

55.125,

GRAVY:

:NELSON"

3.6

Changes to the DECnet-VAXmate Network Device Utility.

(NDU)

3.6.1

Bug Fixes

In DECnet-VAXmate Version 1.0, the virtual disk facility was shipped with the following problems:
1.

A bug caused all DECnet-VAXmate Version 1.0 32-megabyte disks created as the
first NDU function after a system boot (under MS—DOS or PC DOS Version 2 systems) to have an error in their headers. This error does not affect the performance
or integrity of the virtual disk facility.
32-megabyte disks created under MS-DOS or PC DOS Version 2 systems are not
usable from MS-DOS or PC DOS Version 3 systems. (The opposite of this is also
true: 32-megabyte disks created on MS—DOS or PC DOS Version 3 systems are not
usable from MS—DOS or PC DOS Version 2 systems.)

DECnet—VAXmate Version 1.2 solves both of these problems with the following:
All virtual disks created by DECnet-VAXmate Version 1.0 remain usable in all configurations.
All 1.2-, 10-, and 20-megabyte virtual disks created by DECnet-VAXmate Version
1.0 remain usable in all configurations. |

DECnet-VAXmate Changes

3-9

All 32-megabyte virtual disks created by DECnet—VA Xmate Version 1.0 under MS—
DOS or PC DOS Version 3 systems will remain usable on any Version 3 system.
These disks are not usable from MS-DOS or PC DOS Version 2 systems.
342-megabyte virtual disks created by DECnet-VAXmate Version 1.0 under MSDOS or PC DOS Version 2 systems are not usable with DECnet—VAXmate Version
1.2 until they are repaired using the FIXNVD utility. The FIXNVD utility is automatically installed by the DECnet-VAXmate Installation Procedure, DIP. The utility’s file name is FIXNVD.EXE.
If you attempt to open a Version 1.0 virtual disk with Version 1.2, NDU generates
the following error message:
Cannot
OPEN
Run
FIXNVD

this
disk
first.

created

with

older

release

DECnet.

To use the FIXNVD utility, first make a copy of your virtual disk file. For example:
$ COPY

VIODISK1.FIL

V1IODISKBU.DSK

Now you can run FIXNVD on the new file. This is the syntax for using FIXNVD:
FIXNVD node[/user/password/account] backup-disk-name
Example 1:
$ COPY

VDISK.DSK

DISK.007

(on VMS node VMSNOD)
C>

FIXNVD

VMSNOD

DISK.007

VDISK.DSK

DISK$07:

(on your PC)
Example 2:
$ COPY

[SMITH.DISKS] PAYROLL . DAT

(on VMS node REMOTE)
C>

FIXNVD

REMOTE/SMITH/HARP

DISK$07:

[SMITH.DISKS] PAYROLL

. DAT

(on your PC)

3-10

DECnet—DOS Supplemental Information

(or just NDU.EXE and NDDRV.SYS from DECnet—VAXmate Version 1.0) and restore the backed-up virtual disk. Copy the files
from the backed-up disk to two new virtual disks, then reinstall

DECnet—VA Xmate

Version 1.2.

All 32-megabyte virtual disks created by DECnet-VAXmate Version 1.2 will be
usable in all configurations running DECnet-VAXmate Version 1.2 or later.

After you issue an NDU DELETE command, NDU now prompts you for confirmation in the MS-DOS style:
Are

3.7

you

sure

(Y/N)?

Changes to DECnet-VAXmate Transparent File Access (TFA)

Transparent file access functions let you open and close a remote file, create or delete a
remote file, read from or write records to a remote file, submit a batch job, or search a
directory for a specific file or files. Since these functions are performed transparently,
you do not need to use the information in this section unless you are performing network programming tasks.
You can also use TFA to type and copy files to and from remote nodes. Use the following format:
TYPE

TYPE
COPY

\\f\node\ \ filespec

\\f\node\\remotefile > localfile
localfile\ \f\node\ \remotefile

You should note that the COPY command only works if the remote file already exists
on the remote node. If the file does not exist on the remote node, the COPY operation
will fail.

DECnet-VAXmate Changes

3-11

3.7.1

Bug Fixes

TFA has implemented bug fixes for the following problems:
In the previous version of TFA, a file OPEN operation which specified both read
and write access would only allow writing. Now it only allows reading. TFA cannot both read and write a file during a single OPEN/CLOSE session.
The Transparent Network Test utility (TNT) previously reported a false error if it
was run right after TFA was installed. An actual error condition did rot exist. This
has been fixed so that a false error is no longer reported.
Read access to a file larger than 64K bytes with null record attributes (such as a
large runoff output file) would appear to succeed, but no data would be returned.
This has been fixed. Data is now returned, indicating whether or not the operation
succeeded.
Issuing a file close with a handle of —1 indicates that the logical link in use for directory functions be closed. TFA did not check to insure that it was open first. This
caused writing to random locations in memory. This has been fixed. TFA will not
try to perform directory functions if the logical link is closed.
If a FIND FIRST FILE function was performed following a FIND FIRST FILE without an intervening CLOSE command (using a handle of —1), an error would occur.
The second FIND FIRST FILE function now closes the link automatically.

3.8

Changes to DECnet-VAXmate DTR/DTS

In DECnet—VA Xmate Version 1.0, the DECnet Test Receive utility (DTR) would automatically log information to the file DTR.LOG in the DECnet database directory whenever it was run by the Spawner. DTR no longer does this automatically. In DECnet-—
VAXmate Version 1.2, if you want to log information to the DTR.LOG file you must
specify the /LOG switch. For example:

C:\DTR /LOG
3.9

Changes to the DECnet-VAXmate Spawner
There was a previous parsing restriction for DECSPAWN.DAT (the parameter file
for the Spawner utility) that would only allow for a single space between the object
name or number and the parameter associated with it. This restriction has been
removed. There may be multiple spaces and/or tabs between the object name or |
number and the parameter.

3-12

DECnet-DOS Supplemental Information

The Spawner can now support logging, using the /LOG switch. When you use this
switch, the Spawner creates a file called SPAWNER.LOG in the DECnet database
directory (for example, \DECNET\SPAWNER.LOG). All file accesses are recorded
into this file. The log information will include the name of the connecting node,
the object number, and the time of the request. The information will not include
any actions that occurred as the result of the request.
For example:
SPAWNER /LOG
The following is a sample SPAWNER.LOG file:
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986 at
15:41:52
Connect
request
from
node
BOCA
for
object
#17
on Wed
Sep
10
1986
15:42:02
Executing:
fal
-use
2...
on Wed Sep
10 1986
at 15:42:03
SPAWNER
(Version
1.2)
listening...
on Wed Sep
10 1986 at
15:42:08
SPAWNER
exiting...
on Wed Sep
10 1986
at 15:42:14

(In this example, object #17 is FAL, a request to run the File Access Listener.)
e

The Spawner can now execute batch files. For example,
BATCH.BAT file that contains the following information:

you

can

create

ECHO Executing Batch File——Echoing arguments passed:
Echo %1 %2 %3 %4
In this sample file, %1, %2, %3, and %4 represent the different arguments you can
use (such as ARG1, ARG2,

and so on).

Then, define the following in your DECSPAWN.DAT file:
#129

C:\DECNET\BATCH.BAT

ARG1

ARG2

DECnet-VAXmate Changes

3-13

After the batch file completes processing and control is returned to the Spawner,
the Spawner closes the socket whose number it had previously passed to the batch
file. (This is the default. If you do not close the socket from the batch file, the
Spawner will automatically close the one that was opened at the start of the batch
operation. )
:
The output looks like this:
press
‘'!'
to abort
SPAWNER
(Version
1.2)
Connect
15:49:36

request

listening...

from

node

BOCA

for

Wed

object

Sep

#129

C:\SPAWNERt>
echo Executing
Batch
File---Echoing
Executing
Batch
File---Echoing
arguments
passed:

C:\SPAWNERt> Echo
ARG1 ARG2 —-USE 2

ARG1

ARG2

SPAWNER

(Version

1.2)

listening...

SPAWNER

exiting...

Wed

—-USE

Sep

1986

Wed

Sep

arguments

15:49:33
10

1986

passed:

Wed

Sep

1986

15:49:54

1986

15:49:40

FAL

FAL can now be spawned with the arguments /ERROR (/E) and /BINARY (/B). The
output looks like this:
press
'!'
to abort
SPAWNER
(Version
1.2)
Connect
16:01:32

request

Executing:

from

fal

-use
FAL

listening...

Wed

Sep

1986

node

object

#17

Wed

Sep

BOCA

for

16:01:23
10

1986

3...
on Wed Sep
10 1986 at
16:01:32
— File Access
Listener
—- Version
1.2

Network
Driver
Version:
1.2
Current
working
directory:C: \SPAWNERt
All
files will
be sent
as binary.

Existing

FAL

access

will

checking

running...