Re: Patched Programs - Yet another spin

-----Original Message-----
From: mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected] [mailto:mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]]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 spin


>The 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


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