  File Read Error (RER) and Parity Error? 
 The Question is:
 
What is file read error?
   -rms-s-rer
 
How do I clear this up?
Here is the command and result:
 
$ COPY EVTLOG.DAT EVTLOG.SAV
% copy-e-read error, error reading dka0:[scp.dba.evt]
-rms-s-rer, file read error
system-s-parity, parity error
%copy-w-not complete, dka0:[scp.dba.evt]EVTLOG.DAT not completely copied.
 
What to do?
 
Thanks,
 
JOe
 
 
 The Answer is :
 
  The file is written to an area of the disk that has apparently
  failed, and must be recreated or restored from BACKUP.  When a
  disk block containing a hard error is next written, OpenVMS and
  the device mechanisms will transparently revector the block to
  a new and known-good block.
 
  The following output is from the HELP/MESSAGE command:
 
  --
 
 RER,  file read error
 
  Facility:     RMS, OpenVMS Record Management Services
 
  Explanation:  Either the RMS file system cannot read an input file, or a
                terminal read error occurred.
 
  User Action:  If the RMS file system cannot read the input file, the status
                value (STV) field of the RAB contains a system status code
                that provides more information about the condition. Take
                corrective action based on this status code.
 
                If a terminal read error occurred, reenter the input line.
 
  --
 
 PARITY,  parity error
 
  Facility:     SYSTEM, System Services
 
  Explanation:  The exact meaning of this message depends on the device.
 
                If this message is associated with a status code returned by a
                request to a DR11-W interface, a parity error is detected in a
                block mode transfer when the buffered data path of the UNIBUS
                adapter is purged.
 
                If this message is associated with a status code returned
                by a request to a DR32 interface, either the microcode is
                not loaded successfully or the DR32 controller detected a
                parity error and a hardware malfunction is indicated. The
                second longword of the I/O status block contains additional
                information pertaining to this malfunction for the DR32; the
                following bit values are associated with SS$_PARITY:
 
                  XF$V_IOS_WCSPE
                  XF$V_IOS_CIPE
                  XF$V_IOS_DIPE
                  XF$V_IOS_PARERR
 
                If this message is associated with a status code returned
                by a request to a disk driver, one or more of the following
                conditions can cause this error:
 
                o Drive parity error
 
                o ECC hard error
 
                o Header compare error
 
                o Map parity error
 
                o Header CRC error
 
                o MASSBUS control parity error
 
                If this message is associated with a status code returned
                by a request to a magnetic tape driver, one or more of the
                following conditions can cause this error:
 
                  Attempt to read beyond the logical end of volume
                  Control bus parity error
                  Correctable data error (PE only)
                  Correctable skew (PE only)
                  CRC error (NRZI only)
                  Data bus parity error
                  Format error (PE only)
                  Invalid tape mark (NRZI only)
                  Longitudinal parity error (NRZI only)
                  Map parity error
                  MASSBUS control parity error
                  MASSBUS data parity error
                  Nonstandard gap
                  Read data substitute
                  Uncorrectable error (PE only)
                  Vertical parity error (NRZI only)
 
                If this message is associated with a status code returned by
                a request to an LPA11-K driver, a parity error occurred in a
                UBA-buffered data path.
 
                If this message is associated with a status code returned
                by a request to a terminal driver, a parity bit mismatch was
                detected by the device interface during a read operation. The
                I/O operation stopped when the mismatch was detected. (Data
                is received up to this point in the operation.) SS$_PARITY is
                meaningful only on terminal lines that have parity enabled.
 
  User Action:  Your action depends on the type of device to which the I/O
                request is directed.
 
 Answer written or last revised on  14-AUG-2001 
