[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ozrock::x25_avms

Title:	DEC X.25 for OpenVMS AXP

Moderator:	OZROCK::MUGGERIDGE

Created:	Mon Jan 18 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	524
Total number of notes:	2218

496.0. "CTF V1.0g access violation problems" by KERNEL::CORNISHP (Paul Cornish, CSC UK-78333374) Wed Feb 05 1997 21:35

Hi,

I have a customer with a problem with CTF.  Basically it intermittently access
violates.

INFO:

OpenVMS 6.2 Alpha
DECnet/OSI 6.3 ECO 5
X25 V1.0g

PROBLEM:

This was a reproductiob of the problem on our machine running the same versions
(except we have ECO6 for DECnet/OSI).

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

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000C,
PC=00015F18, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00000000
                                 0000000C
                                 00015F18
                                 0000001B

    Register dump:
    R0  = 0000000000004450  R1  = 000000007EE5F978  R2  = 0000000000000918
    R3  = 000000007EE5F4EC  R4  = 0000000000000008  R5  = 0000000000000006
    R6  = 0000000000000000  R7  = 0000000000000001  R8  = 00000000000D8832
    R9  = 0000000000000000  R10 = 00000000000D9588  R11 = 000000007EE5F850
    R12 = 000000000000C004  R13 = 000000007EF01400  R14 = 0000000000000000
    R15 = 000000007EEFDDA0  R16 = 0000000000038240  R17 = 000000007EE5F380
    R18 = 0000000000000008  R19 = 0000000000110002  R20 = 0000000000000004
    R21 = 00000000000D882E  R22 = 0000000000000040  R23 = 000000007EE60000
    R24 = 0000000000000000  R25 = 0000000000000002  R26 = FFFFFFFF80495DB8
    R27 = 0000000000004450  R28 = FFFFFFFF8463A570  R29 = 000000007EE5F290
    SP  = 000000007EE5F290  PC  = 0000000000015F18  PS  = 100000000000001B

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

Does anyone know what the problem is or experienced the same problem.


Cheers for your time

Paul Cornish (COMMS/CSC/UK)

T.R	Title	User	Personal Name	Date	Lines
496.1	Suggestion	OZROCK::HARTWIG	Arthur Hartwig, TaN Engineering-Australia	`Thu Feb 06 1997 09:57`	24
	To get anywhere with this (given that its intermittent) it will probably be necessary to get a dump. I suggest you ask the customer to $ set process/dump before running CTF, and then save the dump when CTF ACCVIOs and submit that dump with a copy of the command used to invoke CTF in a problem report (IPMT) against DECnet/Plus. (DECnet own the CTF User Interface and SOME of the protocol analysis code, X.25 owns other parts of the protocol analysis code. Regardless of which component it will be EDS who will have to fix it.) I don't know if privilege or security mechanisms will prevent getting a useful process dump, so this may not work. But, its how I would go about making some progress on this issue. Other suggestions known to work would be welcomed. A quick scan on a running system suggests 15f18 is in the CTF$UI image which is supplied by DECnet/Plus. (Thats not to say CTF$UI is at fault, just thats its probably a useful place to start the investigation.)
496.2		MUNICH::KLOEPPER	Vera Kloepper/Net&Comms-Support	`Mon Feb 10 1997 20:22`	16
	Hi ! Maybe you don't need a dump for this problem - the CTF runs into this access violation (as described in .0) if the used trace command has a syntax error in it. e.g. ctf> show all (a D-Unix command which doesn't work on VMS) ctf> start/live/full routing circuit * (wrong syntax - quotes missing) This happens only - if the syntactical wrong command is given on the CTF prompt - if you typing the whole command on the DCL prompt - the CTF answers as expected with DCL-W-IVKEYW, unrecognized keyword - ... regards Vera
496.3	Problem also seen on certain command lines	OZROCK::HARTWIG	Arthur Hartwig, TaN Engineering-Australia	`Thu Feb 13 1997 00:21`	9
	The following DCL command will also (on VMS V7.1) demonstrate the problem: $ trace start/live "lapb link *"/dis=name/prot=(lapb,x25) Changing "X25" to "X25L3" causes the problem to go away. I suggest you log an IPMT against DECnet/Plus if you want the problem fixed.