RE: URGENT! - Program Error

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>And the caller and this program all
>runs in batch.

That makes no difference in memory corruption issues.

There is a very high probability that you are seeing memory corruption,
which is why Scott asked about APIs.  It is very possible to write a program
that runs fine when tested and also in production, but when you make a small
change - even unrelated to the API call - it falls over.

Imagine allocating some memory like this:
var1 100
var2 100
var3 100

Get a pointer to var1.  Add 101 to it, either deliberately or by mistake.
You are now touching var2.
Get a pointer to var3.  Add 101 to it.  What are you touching now?  Could be
internal storage used by the compiler, right?  Or maybe not, depending on
the release, PTF and so on at the time you compile it.  Now add some
storage, maybe before var1.  Re-compile the program.  With the same code as
before adding 101 to prt->var3, are you touching the exact same storage as
before?  Who knows?  A change in a distant part of the program made the
reference to var3 fail, even though you never made any changes that refer to
var3.

A very common way to see this happen is some reference like MOVE *BLANKS to
a field the caller defined differently than the callee.  If the callee
defines the field larger than the caller, then the space it wants to clear
goes past the end of the storage allocated by the caller.

Hope this helps.  I'm going out roving in the ARRL microwave contest and
won't be seeing email until Monday.
  --buck