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

Conference vmszoo::rms_openvms

Title:	RMS asks, 'R U Journaled?'

Moderator:	STAR::TSPEERUVEL

Created:	Tue Mar 11 1986
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3031
Total number of notes:	12302

3005.0. "ANALYZE/RMS PROBLEM ON ALPHA VMS" by HGOVC::ROCKYLAM () Fri Jan 24 1997 08:47

    Subject : ANALYZE/RMS_FILE ERROR ON ALPHA VMS
    
    A user only recompiled/linked their VAX BASIC program to ALPHA BASIC 
    program on Alpha 4100. Nothing has been changed in the data definition.
    An Indexed fix-length RMS file copied from VAX/VMS to Alpha/VMS V6.2
    running under this DEC BASIC program has encountered an error during 
    analyse/rms. There are 8 error messages as followings :
    
    . *** VBN 68734: Record at offset %X'0640' has a missing or illegal RRV
               	.         .
    		.	  .
      *** VBN 68854: Key and/or data bytes do not fit in primary data
                     record. 
      Unrecoverable error encountered in structure of file.
    
    Please comment on how to recover this RMS file.

T.R Title User Personal
Name Date Lines

3005.1 Did you DETECT or PRODUCE a problem? FRSBOG::TLAUER "I've been designed multi-asking." Fri Jan 24 1997 11:23 19

T.R	Title	User	Personal Name	Date	Lines
3005.1	Did you DETECT or PRODUCE a problem?	FRSBOG::TLAUER	"I've been designed multi-asking."	`Fri Jan 24 1997 11:23`	19
	So you got errors with that copied file when analyzed through ANAL/RMS. Did you cross-check against the original file if the problem actually existed there also? I think one first has to determine when the file gets corrupted. First prove that the copied file is indeed intact (with ANAL/RMS) before being touched with your BASIC prog, then use that BASIC program, checking again the file's integrity with ANAL/RMS afterwards. If you see errors which haven't been in the file before the appl. run, one can be sure that you actually PRODUCE the problem in running your program. So this would either mean that there's potentially an underlying RMS problem, or you simply got hit by some sort of system failure (crash, nonfatal bugcheck, disk problems etc.). It would also be interesting if this is reproduceable at all. Also i must have missed the section telling which (RMS) ECOs you already have applied... -- Thilo

    So you got errors with that copied file when analyzed through ANAL/RMS.
    Did you cross-check against the original file if the problem actually
    existed there also?
    I think one first has to determine when the file gets corrupted. First
    prove that the copied file is indeed intact (with ANAL/RMS) before being
    touched with your BASIC prog, then use that BASIC program, checking again
    the file's integrity with ANAL/RMS afterwards. If you see errors which
    haven't been in the file before the appl. run, one can be sure that you
    actually PRODUCE the problem in running your program. So this would
    either mean that there's potentially an underlying RMS problem, or you
    simply got hit by some sort of system failure (crash, nonfatal
    bugcheck, disk problems etc.). It would also be interesting if this is
    reproduceable at all.
    
    Also i must have missed the section telling which (RMS) ECOs you
    already have applied...
    
    
    -- Thilo