Re: More fun with native RLA SETLL on an SQL view with a WHERE clause

jamesl-6/ELSmrcqeUu8xhjR5IN5AC/[email protected] wrote:
> CRPence wrote:
>> And I expect an intercepted call should have the value(s) of 
>> interest.  A lot easier than guessing how to specify it, I
>> would think.
> 
> I've got a hunch that just because DMCGETD didn't like 01 for an
> option doesn't mean that DMCGET won't like it.
> 
> (Kind of a pain in the butt talking about these things in
> abstract, without any source in front of me to remind me of what
> things are called).
> 
> (And as for hacking into the SEPT, who do I look like? Leif?) ;-p

   At least get a trace of a valid SETLL *START to find out which of 
the two needs to implement that I\O request; i.e. no reason to play 
with the control or option list of DMCGET processing if according to 
the trace results, the request needs to be handled by the DMCGETD 
processing.

   Updating the EPT for a program is probably the easiest patch 
ever; i.e. replace a pointer with a pointer.  Simple to verify the 
patch too, with a DMPSYSOBJ QINSEPT SPACE( xx 10) and DSPSPLF 
QPSRVDMP SPLNBR(*LAST).

Regards, Chuck
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.