instruction pointers. calling a module. -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

What I would want to do is to implement external module functionality in mi.

It would work similar to CALLI:

DCL SYSPTR pModule ;

DCL INSPTR pModuleCode, pRtnIp ;

RSLVSP pModule, "module name" ;

SETIPFP pModuleCode, pModule ; /* new instruction. set instruction ptr from ptr. */

CALLM pModuleCode, *, pRtnIp ; /* new instruction. call module. */

I realize there are external factors that prevent this, but the concept is one that I would like to know the feasibility of.

Is there a NOOP in mi?

Could NOOP's be included in the mi code, run thru the QPRCRTPG api, then the pgm is patched with the risc coded needed to set the registers and branch to the code in another module?

The called module would be a similarly coded and patched pgm that would be patched to be able to return or branch back to the caller.

just asking,

Steve Richter

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.