HP OpenVMS Systems

ask the wizard
Content starts here

Debugging BASIC Program Lost, Sorry (PROLOSSOR)?

» close window

The Question is:

I have a program written in Alpha BASIC which is basically a data server,
 communicating with users and servers via mailboxes. This program  is getting
 the error:
%BAS-F-PROLOSSOR, Internal error in DEC BASIC Run-Time Library.  Please submit
 an SPR
The exact same program is running on 50+ different CPU's which are running
 anything from OpenVMS V7.2-1 to 7.3-2.  On 2 CPU's (both running OpenVMS 7.2-1
 and BASIC V1.4), I am getting this message after the program has been running
 for several hours to da
The program is linked with /TRACEBACK but no other messages a given when the
 program crashes. How can I go about trying to find where/what the problem is?

The Answer is :

  Without additional details, it is not apparent if this error
    Program Lost, Sorry
  is a known problem with BASIC or the BASIC Run-Time Library, or within
  underlying software, or within the application code itself.   Various
  of the more common causes of this error involve application-triggered
  corruptions of memory; bugs in the application code.
  There are ECO kits available for OpenVMS Alpha, and the OpenVMS Wizard
  would encourage applying all available mandatory ECO kits for the OpenVMS
  release in use, and to ensure the most current version of the BASIC
  compiler (V1.5, as of this writing) is in use.
PROLOSSOR, Internal error in Alpha BASIC Run-Time Library.
  Please submit an SPR. (ERR=103)
Explanation: A consistency check in the BASIC run-time support failed.
  Program execution is aborted. This error cannot be trapped with a
  BASIC error handler unless the program contains OPTION HANDLE = SEVERE.
User Action: This error should never occur. Submit a Software Performance
  After taking a look at the debugging information in topic (1661) and
  notes referenced there, please contact the support center, and make
  a formal report.  As referenced in topic (1661), faster systems and
  multiprocessing are some of the more common triggers that can uncover
  latent coding or timing-related, or memory synchronization errors.
  If/when you contact the support center, please expect to be asked for
  the full source code and a way to reproduce the error.

answer written or last revised on ( 30-APR-2004 )

» close window