Re: QPROCT and QPRODT

["Richard Thomas" <richard_matthew_thomas@xxxxxxxxxxx>]

Hi Bruce,

Thanks for the link. I'd already trawled the Information Centre and hit upon
this, along with the matpg instruction documentation. There's very little
information regarding the instruction stream component itself - I've been
using the *LIST, *ATR parameters on compiles to work on it in more detail.
Was hoping that I could exploit the info in QPROCT and QPRODT so that I
wouldn't have to build an independent table of all valid op codes, op code
attributes (e.g. does the op code support branching, indicators) etc. as a
reference as I step through the instruction stream.

-----Original Message-----
From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx] On
Behalf Of Bruce Vining
Sent: 04 March 2010 11:40
To: MI Programming on the AS400 / iSeries
Subject: Re: [MI400] QPROCT and QPRODT

I haven't looked at OPM in well over a decade (so this reply may be way off
base), but is
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzatk/MINPO.htm
any
help?

On Thu, Mar 4, 2010 at 5:03 AM, Richard Thomas <
richard_matthew_thomas@xxxxxxxxxxx> wrote:

> Dear all,
>
> I'm in the process of writing a routine to parse the instruction stream
> component of an OPM program and return the IRP. I'm hoping to use the
> information within QPROCT and QPRODT to help my routine anticipate the
> number of operands, operand types etc. for a given op code. I've been able
> to determine the easy parts (e.g. op code, op name, number of parameters)
> from a part of the QPROCT space, but am at a loss as to what an op code's
> associated entry in the QPRODT index is telling me.
>
> Can anyone throw some light on any of the information contained in these
> two
> objects?
>
> Many thanks.
>
> Richard
>
>
>
>
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/mi400
> or email: MI400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.