Re: MATMATR weirdness

I remember dealing with this kind of MATMATR problem
I suspect the cause was pointer alignment or not enough space provided for
big LPAR systems...

Paul




From: Bruce Vining <bvining@xxxxxxxxxxxxxxx>
To: "Bare Metal Programming IBM i (AS/400 and iSeries)"
<c400-l@xxxxxxxxxxxx>
Date: 19/04/2014 14:53
Subject: Re: [C400-L] MATMATR weirdness
Sent by: c400-l-bounces@xxxxxxxxxxxx



Can't really say based on your description, but one scenario would be:

1. Something in your environment changed
2. The MATMATR is taking an exception
3. The exception handler in effect is defined to "carry on"

Conceptually this would be like a CL program with a MONMSG for CPF0000,
MCH0000, etc and no EXEC so no matter what happens the program continues
to
run the next instruction (with unintended data all too often). Or a RPG
monitor around a given statement with a on-error *ALL that does nothing
(or
worse, does nothing except remove the message causing the on-error to get
control (so the job log is "pretty" in terms of appearance and worthless
in
terms of value)). Whether this applies to your situation I have no idea.

Best I can say to answer your question is 'Something went wrong' and more
information is needed.

Bruce


On Fri, Apr 18, 2014 at 7:01 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Can anybody explain why a MATMATR in an MI program would, once in a
great while, return garbage, only to work fine the next time the program
was run?

I'm using it to return processor count and LPAR information.

--
JHHL
--
This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L)
mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.