Eric DeLong solves the "Corrupted timestamp" problem and wins the prize!

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
A prototype (ZZR030PR) and subprocedure (ZZR030) had “varying” instead of
“value”, and something overflowed into the timestamp.

This raises an interesting question: should the compiler have spotted this
error, or at least built a large enough buffer to prevent crash-and-burn?
If I was working with pointers, I’d expect to hose myself.  But since the
compiler is (supposed to be) doing the housekeeping, is it reasonable to
expect a safety net from RPG?

Thanks, Eric…
--