Re: Memory being reused by %alloc on second call to program.

["hockchai Lim" <lim.hock-chai@xxxxxxxxxxxxxxx>]

You must be pretty luck.  I'm surprise you did not get junk data on the 
first run, which makes me wonder if the problem could be caused by other 
thing.  Could the problem be caused by the StoredProc did not close and 
reopen the sql statement on the second call?




"Bryce Martin" <BMartin@xxxxxxxxxxxx> wrote in message 
news:mailman.10648.1288273092.2702.rpg400-l@xxxxxxxxxxxxxxx
> I have written my first external stored procedure and it uses dynamic
> memory allocation to create a couple of 2D arrays.  The problem that I'm
> seeing is this...
>
> ProgramA using CLI calls StoredProc.  StoredProc %alloc/%realloc/%dealloc
> and uses a regular static array for returning a result set.
>
> ProgramA is two screens.  First screen has fields to search by.  If I
> enter criteria and hit enter ProgramA then calls StoredProc.  ProgramA
> then processes the ResultSet and puts it into a subfile for viewing.  If I
> F12 back to the first screen and change my search criteria to something
> that shouldn't return results it still does but refined by whatever I just
> searched by.  If I F3 out of ProgramA then all the memory used by the
> StoredProc is released even if I don't do a RCLACTGRP of ProgramA's
> activation group.  If I search a second time after doing the full exit by
> the criteria that should not return results then it works and returns no
> results. (no results could also be a search that is too generic to have
> good results, this is handled by the StoredProc).
>
> In the StoredProc I am doing the following Destroy call, the
> DestroyArray() procedure just take a pointer to an array memory address
> and does a     dealloc(n) pWholeArray;
>
>         pArrayElem = *null;
>         DestroyArray(pWholeArray);
>         pWholeArray = *null;
>
> I nulled the pointers for good measure but that didn't do anything.
>
> It looks like the second call is doing an %alloc and starting at the same
> memory address as the previous call had done.  So when I %alloc a block
> the memory already contains the data from the previous call.  How do I
> handle this?
>
> Thanks
> Bryce Martin
> Programmer/Analyst I
> 570-546-4777
> --- This message (including any attachments) is intended only for the use 
> of the individual or entity to which it is addressed and may contain 
> information that is non-public, proprietary, privileged, confidential, and 
> exempt from disclosure under applicable law. If you are not the intended 
> recipient, you are hereby notified that any use, dissemination, 
> distribution, or copying of this communication is strictly prohibited. If 
> you have received this communication in error, please notify us and 
> destroy this message immediately. ---