On Wed, 6 Jun 2007 12:39:55 -0400 Mark Jacobs <[EMAIL PROTECTED]> wrote:
:>Schramm, Rob wrote: :>> When I change the size of the System Trace Table (i.e. TRACE ST,512K), :>> where is the storage taken from? :> Common Name: Master Trace Table Mapping Macro :> Macro ID: IEEZB806 :> DSECT Name: MTTABLE, MTENTRY :> Owning Component: Master Scheduler (SC1B8) :> Eye-Catcher ID: 'MTT ' :> Offset: 0 :> Length: 4 :> Storage Attributes: Main Storage: Master's Address Space :> Virtual Storage: n/a :> Auxiliary Storage: n/a :> Subpool: 229 :> Key: 0 :> Data Space: n/a :> Residency: Above 31-bit line :> Size: Table Header: 128 bytes :> Entry Header: 10 bytes :> Entry Data : user defined :> Total size varies between 16K and 999K :> Created by: CNZM1TRC :> Pointed to by: BAMTTBL field of the BASEA data area :> Serialization: CONSOLE address space local lock :> Function: Maps the Master Trace Table and an entry in :> the table. Master trace is distinct from system trace. It can pretty much be mapped anywhere, as a CR points to the real address. One hopes IBM was smart enough to map it to a subpool in some system address space (rather than common). -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
