Re: Machine interface _MATINVS2

Peter Connell wrote:

Help.
I have critical production code which compiles the machine interface
procedure named _MATINVS2.
The reason this MI is used is that it is extremely efficient for the
purpose for which it is used.

This has always worked fine until upgrading to V5R4 where it now throws
a dreaded
Space offset X'40405BEF' or X'0000000000000000' is outside current limit
for job ...................

There is IBM doc for the MI procedure named MATINVS but not for MATINVS2
at
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzatk/inst.h
tm

Strangely, the compiler fails to resolve _MATINVS but it does compile
with _MATINVS1 and _MATINVS2
_MATINVS1 appears to require a pointer as a 2nd argument
_MATINVS2 only requires on argument to receive the returned stack info.

So I've been attempting to use _MATINVS1 but it is throwing a "Pointer
not set for location referenced" error.

Here's some sample code that throws the error
It works fine with _MATINVS2 at V5R2 by changing the procedure name to
_MATINVS2 and dropping the 2nd argument

Peter,

You should take a look at the C header file for MATINVS. It's located
in member MATIVNS in file QSYSINC/MIH. This should clear up some of the
mystery.

The header file (member) defines the _MATINVS1 and _MATINVS2 prototype
variants of MATINVS. _MATINVS1 includes the process pointer where as
_MATINVS2 does not (it assumes the current process).

V5R4 may have changed either of the function prototypes, but it's more
likely, that the definition of the receiver template,
_MATINVS_Template_T changed or the sub structure (_MIS_Inv_Ent) for
returned entries. You should check if there is additional data being
returned that you did not define/allocate space for.


Keith