*********************************
* *
* V A X *
* Wide Area Network *
* *
* D e v i c e D r i v e r s *
* V1.1A *
* *
*********************************
Release Notes
DATE: June 1990
The information in this document is subject to change without
notice and should not be construed as a commitment 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 be used or copied only in accordance with the
terms of such license.
Digital Equipment Corporation assumes no responsibility for
the use or reliability of its software on equipment that is not
supplied by Digital or its affiliated companies.
Copyright (C) 1990 by Digital Equipment Corporation. 4 All Rights Reserved. H The following are trademarks of Digital Equipment Corporation: C DEC DECUS DECnet MicroVAX > PDP UNIBUS VAX VMS J IBM is a registered trademark of International Business Machines Corporation
. CONTENTS J 1 Introduction......................................... 1 J 2 The VAX WAN Device Drivers V1.1A Documentation Set... 1 J 3 Reporting Problems................................... 2 J 4 Supported Drivers.................................... 3 J 5 Changes to Documentation............................. 4 J 5.1 Version of VMS Supported.......................... 4 J 5.2 `VAX WAN Device Drivers Specifications Manual'.... 4 J 6 Device Driver Specific Information................... 4 J 6.1 The DMF32 Device.................................. 5 J 6.2 The DSB32 Device.................................. 5 J 6.2.1 Non-paged pool requirements.................... 5 J 6.2.2 Communicating with a DMR11..................... 5 J 6.2.3 How to specify DSB32 lines in NCP.............. 6 J 6.3 The DMB32 Device.................................. 6 J 6.3.1 DMB32 Device Type Register..................... 6 J 6.4 The DST32 Device.................................. 7 A 6.4.1 DDCMP protocol is now supported by the DST32 J driver......................................... 7 J 6.5 The DSH32 Device.................................. 8 G
1 Introduction I Version 1.1A of the VAX WAN Device Drivers kit is a maintenance F release. New versions of the drivers in Version 1.1A fix allG known problems. This maintenance release ensures that the VAX I WAN Drivers support all current VAX processors. See the SSA for * details of processors supported. J These Release Notes accompany Version 1.1A of the VAX WAN DeviceG Drivers kit, and give general guidance on the use of both the H software and the documentation. Please read these notes beforeB using the product, and before reading the documentation. ? 2 The VAX WAN Device Drivers V1.1A Documentation Set F The VAX WAN Device Drivers V1.1A kit uses the VAX WAN DeviceI Drivers V1.1 Documentation Set, which consists of the following manuals: 6 o VAX Wide Area Network Device Drivers V1.1 Installation Guide 6 o VAX Wide Area Network Device Drivers V1.1 Specifications 6 o VAX Wide Area Network Device Drivers V1.1 Programmer's Guide H Use the Installation Guide when you first receive the kit. TheF Specifications manual gives technical information about eachI of the drivers. The Programmer's Guide is an aid to programming device drivers. J 1
3 Reporting Problems H If you find a problem in the software or documentation that isI not covered in these notes, please report it to Digital using a I Software Performance Report (SPR). Describe only one problem on H each form. This simplifies record keeping and ensures that you get a rapid reply. E If the problem occurs when the VAX WAN Device Drivers V1.1A H kit is loaded and running, but involves other software, try toH reproduce the problem without using the VAX WAN Device DriversI V1.1A kit. If the problem occurs during times of high interrupt E loading (for example, many active high-speed communications G lines, or many active terminals) try to reproduce the problem without the load. G If the problem occurs while running user tasks during VAX WAN J Device Drivers V1.1A kit operation, try to reproduce the problemJ without those tasks. User problems are difficult to reproduce inI a different configuration, so define, as precisely as possible, < the state of the system when the problem occurred. F Illustrate a general problem with one or more examples. WhenI an SPR contains precise information, the problem is more likely F to be reproduced, and therefore more likely to be corrected.F In addition, please make your questions direct and simple soG that we can answer them clearly and precisely. When referring G to a problem or error in a manual, specify the full title and H the appropriate section, table, or page number. When reportingG problems involving software that Digital has supplied, please 4 give as much of the following as possible: C 1. Machine-readable media containing the following files: - o A copy of the crash dump file 7 o A source copy of any user task involved ( 2. Any relevant console output E 3. Any information about the reproducibility of the problem 2
D 4. Any information about the operating system or utilities > 5. Details of modem type or type of local connection 4 Supported Drivers J The following is a list of those drivers and their devices which. are fully supported in this version: o SIDRIVER (DMB32) o SLDRIVER (DSB32) o SJDRIVER (DSV11) ' o ZSDRIVER (DST32 and DSH32) ' o XMDRIVER (DMR11 and DMC11) o XGDRIVER (DMF32) o XDDRIVER (DMV11) o XWDRIVER (DUP11) o XJDRIVER (DUP11) o UEDRIVER (DPV11) o UHDRIVER (DPV11) o UFDRIVER (DPV11) o UVDRIVER (KMV1A) o XSDRIVER (KMS11-BD) o XNDRIVER (KMS1P) H Please note that the UGDRIVER and XKDRIVER associated with the= VAX 3271 product are not supported in this release. J 3
% 5 Changes to Documentation ' 5.1 Version of VMS Supported F On all VAX WAN Device Drivers documentation title pages, theH required version of VMS is given as VMS V5.0. Please note thatH the VAX WAN Device Drivers software is also supported by other versions of VMS. H The list of VMS versions supporting the current release of theH VAX WAN Device Drivers is found in the System Support Addendum (SSA) document. = 5.2 `VAX WAN Device Drivers Specifications Manual' G Note the following corrections to the `VAX WAN Device Driversi! Specifications' manual: I o Table 1-1 states that the DSB32 device supports both the VAX.G 2780 and the VAX 3271 products. This is not the case. ThisaI support should be indicated for the DSV11 device and not forr the DSB32 device. J o Table 1-3 states that the DSB32 device supports a single HDLCI line speed of 256K bps. This is not the case. The line speedp" should read 192K bps. / 6 Device Driver Specific Informationo E This section gives specific information about the following E devices (note particularly the secti
on the DSH32 device,CI which is not documented elsewhere in the VAX WAN Device Drivers documentation):d o DMF32 o DSB32 4D
o DMB32 o DST32 o DSH32 6.1 The DMF32 Device J The DMF32 driver shipped with this kit contains changes over theG version of the driver shipped with VMS versions V5.0, V5.0-1, J V5.0-2, V5.1, and V5.1-1. Please reinstall the DMF32 driver fromA this kit after installing any of these versions of VMS.V J A DMF32 device must be at revision J or greater in order to work# correctly with VAX P.S.I.. 6.2 The DSB32 DeviceS , 6.2.1 Non-paged pool requirements F Before loading the DSB32 device driver and microcode, pleaseJ check that there is at least 64K bytes of free non-paged pool on your system. + 6.2.2 Communicating with a DMR11o H When communicating with a DMR11, ensure there is a delay of 20F ms or more between RTS being asserted and CTS being assertedI at the DMR11 end. If the delay is shorter than 20 ms, the DSB32.- does not detect the carrier signal. E To solve this problem, set the modem or modem eliminator at E the DMR11 end to provide at least a 20 ms delay between the J assertion of RTS and the assertion of CTS. Alternatively, if theH DMR11 modem or modem eliminator cannot provide this delay, set4 CD permanently on `high' at the DSB32 end. J 5
. . 2 6.2.3 How to specify DSB32 lines in NCP : Example of setting up a DSB32 line to run DDCMP: # $ RUN SYS$SYSTEM:NCP : SET LINE DSB-0-0 STATE ON RECEIVE BUFFERS 8+ SET CIRCUIT DSB-0-0 STATE ON 9 Example of setting up a DSB32 line to run LAPB: # $ RUN SYS$SYSTEM:NCP L SET LINE DSB-0-0 STATE ON PROT LAPB NET PSS RECEIVE BUFFERS 8 6.3 The DMB32 Devicei J A DMB32 device must be at revision J or greater in order to workI correctly with VAX P.S.I., VMS SNA, and with applications usings HDLC or GENBYTE. H If the line is idle for 30 seconds or more in BISYNC mode, theF line is not dropped as it was in SIDRIVER V1.0. This enablesI dial-up lines to be idle for long periods without being discon-a nected.h + 6.3.1 DMB32 Device Type Registerd G The contents of the DMB32's device type register are saved by H the driver. You can find them by looking at the longword foundI in the DMB32's UCB at offset DTYPE_UCB_OFFSET (= hex 0148). The 0 format of this register's contents is: 6
a t I 31 16 15 0tI ---------------------------------------------------------------WI | REVCODE | DEVTYPE | I --------------------------------------------------------------- H o The DEVTYPE word DTYPE<0:15> contains the DMB32 device code of 0109 hex.a F o The REVCODE word DTYPE<16:32> contains the DMB32 revision level. I o The REVCODE word is subdivided to give the firmware revision > level and the revision level of the T1012 module: = 31 24 23 16e= -------------------------------------a= | HREV | FREV | = -------------------------------------t 1 o FREV is the firmware revision level.e F o HREV is the minimum revision of the T1012 module that can; support the the FREV revision of the firmware. 6.4 The DST32 Devices D 6.4.1 DDCMP protocol is now supported by the DST32 driver I ZSDRIVER has supported the DDCMP protocol since V1.1. This sup-vD port enables a DST32 device to be used directly as a DDCMPF datalink device by DECnet-VAX. However, the following infor-2 mation is not in the V1.1 documentation: C o The maximum supported speed for DDCMP operation is 9.6p kbits/s. J 7
i G o When using the DECnet-VAX Network Control Program (NCP) totH activate the DST32 in DDCMP mode, you must specify the pro-I tocol as "DDCMP POINT". This is because the default protocolo0 for the DST32 is LAPB. For example: & $ RUN SYS$SYSTEM:NCPM SET LINE DST-0-0 PROTO DDCMP POINT STA ON RECEIVE BUFFERS 6s. SET CIRCUIT DST-0-0 STATE ON 6.5 The DSH32 Device I The DSH32 is a communications controller for the MicroVAX 2000, J and supports one synchronous communications port and eight asyn-H chronous terminal ports. The device driver for the synchronousI port is ZSDRIVER, and is included on the VAX WAN Device DriverseI V1.1A kit. The asynchronous ports are driven by YFDRIVER, which is supplied with VMS.o J To install the DSH32 synchronous port driver, select the "DST32"I option from the menu when installing the VAX WAN Device Drivers J V1.1A kit. The programming information and supported line speedsD and layered products for the DSH32 are the same as for the DST32. J VMS versions V5.0 and V5.1 do not contain autoconfiguration sup-H port for the DSH32 drivers. A command file to load the driversG is provided with this kit, and will be installed if the DST32 G device is selected during installation. The file is installedIG as SYS$MANAGER:SYNC$DSH32_LOAD.COM. The system manager should H add an invocation of this file to the site-specific VMS systemG startup procedures, before the startup of any Digital layeredD2 products that will use the DSH32 device. 8