× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Whenever I call an RPG program that uses HTTPAPI to hit a URL and parse an
XML file, my LANSA web job crashes.

One of the LANSA programs returns a CPF9898 message with this text:

Message . . . . : Fatal Error : Statement : 256 Message : Component to be

removed from invocation stack not found. Routine :

X_Rmv_from_Invocation_Stack.

Then this in the joblog
To module . . . . . . . . . : QC2ALLOC

To procedure . . . . . . . : do_free_default__FPv

Statement . . . . . . . . . : 2

Message . . . . : The requested heap space operation is invalid.

Cause . . . . . : The requested heap space operation is invalid. The
heap
space identifier is -1. The activation group mark is 2. The activation
group
mark will be zero if the heap space is not associated with an activation

group. The error type is 2. The error type indicating why the heap space

request is invalid is defined as follows: 0001-Attempt to destroy the

default heap space; 0002-Attempt to free or reallocate heap space
storage
that is not allocated; The heap space identifier and activation group
mark
may not be valid for this error type; 0003-Access to the heap space is
not
allowed; 0004-Attempt to mark a heap space that cannot be marked;


I noticed in the HTTPAPI source code that it's using some dealloc
operations too. Is it possible I need to run these jobs separately or
something? Is it a coincidence they are both doing some dealloc and I'm
completely wrong?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.