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

James H. H. Lampert wrote:

CRPence wrote:

The pointer stored in the DMEPT has to come from the *SEPT, so
just update the QINSEPT before the file is opened. I would
make the intercept program a CLP that does nothing more than a
TFRCTL to the OS DB program, in order to avoid impacting any
other work that must be done while debugging. Or after the
open, but before the I\O request, the DM EPT could be updated
in the ODP.

Hack the QINSEPT?!? On a production box?!? Uh, even if I knew how
(I had to read the aforementioned tutorial from Leif, just to
know how to dump it!), it's not something I'd care to risk.

Nobody said anything about a production system. :-)

Hacking the ODP would be a little more reasonable, IF I had the slightest idea how to do that in an ILE program.

The ODP has no awareness of ILE. It is a temporary object created by the LIC DB, addressable through the DMCQ. I did not review the document, but if it is what I recall, the addressability to these is documented. However I would just use DMPSYSOBJ and STRSST D/A/D which I would find much simpler.

The first recompilation only yielded a few ideas that DIDN'T
work: If I changed the option list on a .DMCGETD (RPG SETLL) to
"Read First," the program crashed. If I set the target RRN to
zero or a negative value, the OPM RPG test got nothing, and the
MI app got the known-excluded first record.

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.

<<SNIP>>

Regards, Chuck