HP OpenVMS Systems

Causes of ACCVIO?

» close window

The Question is:

 
I HAVE A USR WHO READS A REEL TO REEL AND PLACE'S THE DATA ON DISK
ONCE THE DATA IS CONTAIN ON DISK THE USR CANNOT READ THE DATA COMPLETELY
HE RECIEVES A ACCESS VIOLATION AFTER READING SEVERAL RECORDS. COULD IT BE
THAT THE USER HAS REACHED EOF. OR DOES HE HAVE A SERIOUS PROBLEM EXTRACTING
DATA FROM THE DISK ERROR STATUS
REASON:MASK=!XB. VIRTUAL ADDRESS = !XL,PC=!XL,PSL=!XL
USER IS USING DEC/VAX MACHINE
READING EBCDIC DATA.
 
 

The Answer is :

 
  The user's application appears to contain one or more programming errors.
  Without examination of the entire source code and potentially without a
  test pass or two of the application under the OpenVMS Debugger, the Wizard
  is unable to determine the particular cause of the error -- the particular
  cause of the access violation (ACCVIO) error can often be determined simply
  by using the OpenVMS debugger in conjunction with the program source code.
 
  See HELP/MESSAGE ACCVIO for information on the various items associated
  with the signal -- the items can indicate if the access operation was a
  read or a write access, which program instruction attempted the failed
  access, and on what virtual address the access failed.

  

     

     
answer written or last revised on ( 20-JUL-1998 )
     
» close window