Re: Oir reference

I think that some of the obj info that I was investigating are stored in the
epa header than i suppose can be LEGALLY accessed with MATSOBJ. (for those
who like MI of course, and - this is the righ forum - I guess).

Also for those who like "obscure" programming and are not afraid of being
fired and want to run at the maximum speed, at V5R3 there is a new MI
builtin that can be used in RPG, that allows to call APIs directly from
SEPT.

Btw thanks for all the suggestions.

Best regards.
Giuseppe.


----- Original Message ----- 
From: "Dan" <dan27649@xxxxxxxxx>
To: "MI Programming on the AS400 / iSeries" <mi400@xxxxxxxxxxxx>
Sent: Friday, October 07, 2005 4:44 PM
Subject: Re: [MI400] Oir reference


On 10/7/05, Bob Cozzi <cozzi@xxxxxxxxx> wrote:
>
> Use the "Scientific Method" to prove it to yourself.
> Use DSPOBJD, add the obj sizes up using SQL or Query or whatever. Then use
> GetLibSize or the API itself and observe the difference. DSPOBJD only
> gives
> you the object sizes, not the size the library uses up on your DASD
> including all objects, directory entires, OIR, etc.


A good exercise for a rainy day, I suppose I'll have to take your word for
it now. Of course, if someone's got the API all dressed up in RPG-IV code,
I'd be willing to have a go at it.

- Dan
_______________________________________________
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.