RE: URGENT! - Program Error

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

What is the statement giving you the error?  Is this the first time it has
run on V5R1 or has the program just been changed? If either of these then my
guess is that it may be memory corruption that wasn't affecting anything
noticeable previously but now is.  Are any API's called, are data queues
being used?

Scott Mildenberger

> -----Original Message-----
> From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
> Sent: Friday, September 13, 2002 3:17 PM
> To: Midrange - RPG (E-mail)
> Subject: URGENT! - Program Error
> Importance: High
>
>
> We are on V5R1, this subroutine hasn't been changed in the
> program, but now
> it bombs out on us. I ran debug. It first does a
> subproceedure that reads a
> DDM file and then it clears a file via a CL, which both complete
> successfully. Then when it opens a local file, it bombs out with the
> messages bellow.
>
> Here are the messages in the job log:
> Message . . . . :   Pointer not set for location referenced.
> Cause . . . . . :   A pointer was used, either directly or as a basing
>   pointer, that has not been set to an address.
>
>  Message . . . . :   Internal failure in compiler or subroutine.
>  Cause . . . . . :   An internal error was found in the
> compiler or in a