Time for some fun. We got:

> :RUN E017910.EXEC01
> NEW SYSTEM DATE IS: 06/06/97
> **** INTERNAL TRAP
> Instruction Memory Protection Trap
> [VSM] Undecoded status.info = -37
> ABORT: E017910.EXEC01.N01

>This looks pretty serious to me. Checking the documentation for "instruction
>memory protection trap", two of the references I found in "MPE/iX Error
>Messages Manual Volume II" were to system halts. And in the Trap Handling
>Programmer's Guide: The instruction memory protection trap is also sometimes
>encountered.  It generally results when an unauthorized, non-operating system
>user calls an operating system procedure running at privilege level 0.
>
The reference to SYSTEM DATE is for the application as a system, not the
3K itself. This program updates dates stored in records. Looking at the
code, I see the one message at the end of it's paragraph, and another
similar message at the end of the next paragraph, so it must be dying
within that next paragraph. But I see no calls to intrinsics, which are
almost unused in this application, or anything else dangerous. In fact,
>with very little tweaking, the same code runs on our LAN.
>