HP OpenVMS Systems

ask the wizard
Content starts here

Debugging COBOL Access Violation (ACCVIO)?

» close window

The Question is:

 
I have a customer that has two boxes, One an ES40 Dual Processor 1Gb Mem other
 an 2100 4 Processor 512Gb mem. The customer Compiles a Cobol Program in Debug
 mode on the ES40, no Problem, but when he compiles the same Cobol Program on
 the 2100 it Fails wit
h the following error: SYSTEM-F-ACCVIO, access violation, reason mask=00,
 virtual address=0000000000000003, PC=00000000005480EC, PS=0000001B. This only
 happens on the 2100 not the ES40 and only if Debug is on, with nodebug the
 file compiles fine. Both mac
hines are running Open VMS 7.2-1 and both are running Cobol 2.6. Please help
 because the 2100 is their Development machine. Is there any known bug? Patch,
 or something? Please help, Regards Deon Laubscher.
 


The Answer is :

 
  The code at PC=00000000005480EC is attempting to access data at
  virtual address 0000000000000003.  (Please see previous discussions
  of the access violation information, and please see HELP/MESSAGE
  for the ACCVIO return.)  You can sometimes resolve this using the
  full LINK/MAP and the full machine code listings from the compiler.
  You can also often use the debugger to detect this.
 
  This error could be a problem with COBOL, or this problem could be
  a problem with the application code.  Both are equally possible here.
  Please see topic (7552) for information on debugging an application,
  and pointers to related topics.
 
  As for the COBOL environment here, COBOL 2.6 is no longer supported.
  Please move to the current COBOL version (V2.8-1286, as of this
  writing), and please install the current COBOL RTL ECO (if any) for
  the OpenVMS release in use.
 
  The OpenVMS Alpha V7.2-1 release is also outdated, and an upgrade
  to a more current (and supported) release is recommended.
 
  For information on available patches and RTL updates for COBOL and
  other environments, please see the ECO website referenced in the
  FAQ.  The COBOL compiler upgrade is available on the standard layered
  product or product-specific distribution kits, as layered products are
  typically not available for anonymous downloads.)
 

answer written or last revised on ( 19-MAR-2003 )

» close window