|
Let us know if it works :-)When the restriction on restoring system state pgms occurs, I guess it would have to be a user state pgm, so it might be limited in what it could do, although it might contain arbitrary machine code.
--Dave Steve Richter wrote:
-----Original Message----- From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx]On Behalf Of Dave McKenzie Sent: Wednesday, February 15, 2006 12:07 PM To: MI Programming on the AS400 / iSeries Subject: Re: [MI400] Patched Programs - Yet another spinThe hardware page table is a table in memory where the hardware keeps track of the pages of memory, and includes the storage protection bits and the NEx bit. You can see the table entry for a given virtual address with STRSST like this:Opt 1 - Start a service tool 4 - Display/Alter/Dump 1 - Display/Alter storage 2 - Licensed Internal Code (LIC) data 14 - Advanced analysis select 1 ADDRESSINFO enter a virtual address, like 1a76b86d3f000000 F10 to page right to see the NEx bit.neat. thank you.I don't think changing object type of a *usrspc to *pgm would have any effect on the NEx bit.what about changing it from *usrspc to *pgm. Then save to savf. Then restore it. The theory being the page table entries are created when an object is restored to the system. If the system sees the *usrspc as a *pgm, then it will create the page table entry for that object as executable. -Steve
As an Amazon Associate we earn from qualifying purchases.
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.