Newsgroups: comp.os.vms
Subject: Decnet Vax Extensions and PSI problems
From: ja@polar.etsiig.uniovi.es (Jose A. Corrales)
Date: 28 Jan 93 19:39:22 +0100
Organization: Universidad de Oviedo

Hello everyones!

When executing $ @sys$startup:net$startup dnvext

I can see:

Create Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:50.69000 + 00:00 I 00.00000


Set Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:51.21000 + 00:00 I 00.00000

Set Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:51.47000 + 00:00 I 00.00000

Set Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:51.70000 + 00:00 I 00.00000

Set Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:51.90000 + 00:00 I 00.00000

Set Node 0 LAPB Link artix_oviedo
 at 1993-01-28-14:49:52.11000 + 00:00 I 00.00000

%%%%%%%%%%%  OPCOM  28-JAN-1993 14:49:52.57  %%%%%%%%%%%
Message from user SYSTEM on ALEPH
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000008, P4

and the process hangs... at point ======>:

      (file sys$startup:psi$configure.ncl)

      create x25 access
      create x25 access security dte class default
      create x25 protocol
      !
      !
      ! Create and set Line:  artix_oviedo 
      ! to use device: DPV-0-0 
      !
      create modem connect line artix_oviedo communication port DPV-0-0 -
          , profile  "NORMAL"
      set modem connect line artix_oviedo speed 9600
      set modem connect line artix_oviedo modem control full
      set modem connect line artix_oviedo suppress test indicator true
      !
      ! Create and set DTE:  artix_oviedo 
      ! and LAPB link:  artix_oviedo 
      ! using Line:  artix_oviedo 
      !
      create lapb link artix_oviedo profile  "IBERPAC"
      set lapb link artix_oviedo -
          physical line modem connect line artix_oviedo 
      set lapb link artix_oviedo acknowledge timer 1434 
      set lapb link artix_oviedo holdback timer 717 
      set lapb link artix_oviedo maximum data size 261 
      set lapb link artix_oviedo window size 7 
      !
      !
      ! Create and set DTE:  artix_oviedo 
      ! using Line:  artix_oviedo 
      !
      !
====>>create x25 protocol dte artix_oviedo profile  "IBERPAC"
      set x25 protocol dte artix_oviedo -
          link service provider lapb link artix_oviedo 
      set x25 protocol dte artix_oviedo inbound dte class IBERPAC 
      set x25 protocol dte artix_oviedo x25 address 2043145251003 
      set x25 protocol dte artix_oviedo outgoing list  [[1..20]] 
      set x25 protocol dte artix_oviedo minimum packet size 2 
      set x25 protocol dte artix_oviedo maximum packet size 128 
      set x25 protocol dte artix_oviedo default packet size 128 
      set x25 protocol dte artix_oviedo minimum window size 1 
      set x25 protocol dte artix_oviedo maximum window size 2 
      set x25 protocol dte artix_oviedo default window size 2 
      !
      ! Create Local DTE Class: IBERPAC 
      !
      create x25 access dte class IBERPAC type local
      set x25 access dte class IBERPAC local dtes (artix_oviedo) 
      !
      ! Create Local DTE Class: artix_oviedo 
      !
      create x25 access dte class artix_oviedo type local
      set x25 access dte class artix_oviedo local dtes (artix_oviedo) 
      !
   [stuff deleted]

Hints:

1) Prior installing DECNET Vax ExtensionS V5.4, the system was 
running without problems VMS 5.5-2, PSI 4.3 and SYNC 1.1 (WWD)

PSI was configured a lot of times over several PSDN's: the 
Public PSDN of Spain (IBERPAC) with profile IBERPAC, a private
PSDN with profile ISO8208, and the private academic and research
PSDN called ARTIX with several profiles, always without problems.

2) The system is a microVax II with DPV. PSI also fails in a
microVax 3100 with a DST line (at the same point). Both systems
were working fine before DNVEXT 5.4 and both are failing after
DNVEXT. 

3) I have the same processes before and after the error. There
are no inusual states (RWAST like). Probably the error is due to
a module of the LES ACP. 

4) I have tried other profiles .... no success

5) PSI-ACCESS works fine with or without DNVEXT on both systems

6) Of course, DNVEXT was installed with PSI and WWD support, and
WWD (Wan Device Drivers) was configured. Aditionally, the 
microVAX II needs a sys$manager:syconfig.com file with:

$       run sys$system:sysgen
CONNECT SEA0 /ADAPTER=UB0 /CSR=%O760270 /VECTOR=%O000300 /NUMVEC=%O000002
$

(the microVax 3100 driver is autoloadable)



Any idea? Is VMS 5.5-2 very young for DNVEXT 5.4 ?

Please reply by email. I shall summarize. Thanks in advance.

+--------------------------------------+------------------------------------+
| Jose Antonio Corrales Gonzalez       | E-Mail: corrales@etsiig.uniovi.es  |
| ETSI Industriales e Informaticos     |                                    |
| Area de Lenguajes y Sistemas         | HEPNET: 16515::JA                  |
| Informaticos (Universidad de Oviedo) |       : EASTVC::JA   (area 16.131) |
| Carretera de Castiello s/n.          | Phone: (..34-8) 5182050 or 5182049 |
| E-33394 GIJON/SPAIN                  | FAX:   (..34-8) 5338538            |
+--------------------------------------+------------------------------------+
      X400: C=es; ADMD=mensatex; PRMD=iris; O=uniovi; OU=etsiig; S=corrales
Newsgroups: comp.os.vms