I have not seen this exactly like what you describe, but I do have some thoughts. The pointer you are using for the ALLOCATE, does it have a value clause, specifically VALUE NULL. If not, the pointer could have an unknown value that does not compare equal to NULL so you would attempt to FREE it.
On Sat, Apr 8, 2023 at 6:05 PM Cameron Conacher <conac...@gmail.com> wrote: > Hello folks > I have written an IMS COBOL program. I have included a couple of ALLOCATE > statements. > At the end of processing I check my pointers and if they are not NULL I > try to FREE. This results in a U4038 abend. At least inside Expediter. > I have not used ALLOCATE/FREE before. > I am thinking it may be related to Expediter somehow. > I mean FREE is pretty darned straight forward. > At the moment I have commented out the statements. Memory should be freed > at the end of processing anyway, but good housekeeping is well good. > Has anyone seen this before? > > Thanks > > Sent from my iPhone > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
