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

Conference clt::dtm

Title:	DEC/Test Manager - 'DTM Classic!'
Notice:	Current version: V3.7-2 (see Note 3.2)
Moderator:	EDSDS6::TOWNSEND

Created:	Sat Jan 25 1986
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2062
Total number of notes:	7720

2062.0. "ACCVIO on Verify on Alpha VMS V7.1 and DTM 3.7" by CSC32::J_HEISLER () Mon Jun 02 1997 21:48

    AlphaServer 4100 5/466 4MB
    OpenVMS v7.1
    DTM v3.7-2
    
    Problem - Customer does a DTM> VERIFY /LOG command and gets a
    tracebacks
    with  ACCVIO.  He created the DTM library directory from a VMS BACKUP
    saveset, restored, and renamed the 00DTM files to 01DTM and generated
    the
    traceback.  He also copied the 01DTM files over from another Alpha
    system
    and generated the traceback.  He also created a new DTM library from
    scratch, created the test and collection descriptions, populated the
    session
    files from existing scripts, and generated the traceback.
    
    I read note 2038 where the suggestion was to drop back to 3.6. 
    Anything
    else?
    Since he is on vms v7.1 technically 3.7 is not supported.  Any help
    would
    be appreciated.
    
    %DTM-S-LIBIS, DEC Test Manager library is MD9:[TEST.DTMTEST]
    %DTM-I-VERFRE, free space list verified
    %DTM-I-VERSTR, string list verified
    %DTM-I-VERCOL, collection list verified
    %DTM-I-VERGRO, group list verified
    %DTM-I-VERTD, test description list verified
    %DTM-I-VERVAR, variables list verified
    %DTM-I-VERARC, archive list verified
    %DTM-I-VERHEAD, user header information verified
    %DTM-I-VERSPACE, contiguous space verified
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=0000000000000000, PC=FFFFFFFF804A194C, PS=0000001B
    
      Improperly handled condition, image exit forced.
        Signal arguments:   Number = 0000000000000005
                            Name   = 000000000000000C
                                     0000000000010000
                                     0000000000000000
                                     FFFFFFFF804A194C
                                     000000000000001B
    
        Register dump:
        R0  = 0000000000010001  R1  = 000000000039C383  R2  =
    00000000000593E8
        R3  = 0000000000000000  R4  = 0000000000000000  R5  =
    0000000000000000
        R6  = 0000000000010001  R7  = 000000000006E9D8  R8  =
    000000000008B2F8
        R9  = 000000000008B310  R10 = 000000000008B318  R11 =
    0000000000000001
        R12 = 000000007AEF1460  R13 = 0FF3FFFF00000000  R14 =
    00000000010E0000
        R12 = 000000007AEF1460  R13 = 0FF3FFFF00000000  R14 =
    00000000010E0000
        R15 = FFFFFFFF0000FFFF  R16 = 0000000000000000  R17 =
    0000000000000004
        R18 = 000000000039C383  R19 = 0000000000000004  R20 =
    0000000000000000
        R21 = 0000000000000000  R22 = 0000000000000029  R23 =
    0000000000000004
        R24 = 0000000001000000  R25 = 0000000000000004  R26 =
    00000000001321DC
        R27 = FFFFFFFF80C872B0  R28 = 0000000000000000  R29 =
    000000007AEF1280
        SP  = 000000007AEF1270  PC  = FFFFFFFF804A194C  PS  =
    300000000000001B
    
    
    Thanks,
    Jim Heisler
    LST Support Team

T.R Title User Personal
Name Date Lines

2062.1 EDSDS6::WANG James - DECset Engineering Tue Jun 03 1997 15:55 9

T.R	Title	User	Personal Name	Date	Lines
2062.1		EDSDS6::WANG	James - DECset Engineering	`Tue Jun 03 1997 15:55`	9
	Hi, ->I read note 2038 where the suggestion was to drop back to 3.6. Anything -> else? They can wait for the next release of DTM ( V3.8 ) since we've fixed this problem in the DECset 12.2, or just ignore this problem since their DTM library may not be broken even they got ACCVIO during DTM VERIFY. If they really want to verify their library then use verification from VAX.

Hi,
->I read note 2038 where the suggestion was to drop back to 3.6. Anything
->    else?

They can wait for the next release of DTM ( V3.8 ) since we've fixed this
problem in the DECset 12.2, or just ignore this problem since their DTM library
may not be broken even they got ACCVIO during DTM VERIFY. If they really want
to verify their library then use verification from VAX.