OS/2 Shareware BBS: SysTools/SysTools.zip/spm2.zip/theseus2.inf

OS/2 Help File | 1993-11-23 | 349KB | 11,821 lines

ΓòÉΓòÉΓòÉ <hidden> Arena ΓòÉΓòÉΓòÉ

An arena maps a linear address space by way of a doubly linked circular chain
of arena records. Each arena starts with a sentinel record. There are three
separate arenas associated with each process:

private  Maps the linear address space unique to that process. This memory
         holds EXE files and memory objects allocated using the DosAllocMem
         function.
shared   Maps the linear address space shared by all the processes. This memory
         holds DLL files and memory objects allocated using the
         DosAllocSharedMem function.
system   Maps the linear address space which belongs to the OS/2 system.


ΓòÉΓòÉΓòÉ <hidden> Arena Record ΓòÉΓòÉΓòÉ

There is an arena record for each memory object that has linear address space
allocated to it. The handle of the arena record is a har. The arena records are
arranged in arenas.


ΓòÉΓòÉΓòÉ <hidden> Claimable Page ΓòÉΓòÉΓòÉ

A claimable page is one that is not marked present in a particular Page Table
Entry, however, the page is present. On the first reference to the page, the
page will simply be marked "present".


ΓòÉΓòÉΓòÉ <hidden> Clean Page ΓòÉΓòÉΓòÉ

A clean page is one that has not been written to in RAM since being loaded from
disk.


ΓòÉΓòÉΓòÉ <hidden> Committed Memory ΓòÉΓòÉΓòÉ

Committed memory is memory that has been both allocated and committed.
Committed memory has an entry in the Virtual Page Table and can be "backed" by:

o A page of real RAM
o A page of DASD in the SWAPPER.DAT file
o A page of a program file
o Nothing.


ΓòÉΓòÉΓòÉ <hidden> Context ΓòÉΓòÉΓòÉ

Many memory objects are associated with a particular OS/2 process. The context
of a memory object refers to the process with which it is associated.


ΓòÉΓòÉΓòÉ <hidden> Context Record ΓòÉΓòÉΓòÉ

There is a context record for each process that can access a particular memory
object in the shared arena. The handle of the context record is a hco.


ΓòÉΓòÉΓòÉ <hidden> Dirty Page ΓòÉΓòÉΓòÉ

A dirty page is one that has been written to in RAM, but not yet written to the
SWAPPER.DAT file.


ΓòÉΓòÉΓòÉ <hidden> DTE ΓòÉΓòÉΓòÉ

A DTE, or Descriptor Table Entry, is an entry in a Descriptor Table (GDT, LDT,
or IDT). It includes the linear address and size of a segment.


ΓòÉΓòÉΓòÉ <hidden> Exit List ΓòÉΓòÉΓòÉ

The list of routines that are to be executed when a process ends.


ΓòÉΓòÉΓòÉ <hidden> File Handle ΓòÉΓòÉΓòÉ

The handle of a file. There are process handles which are unique for a process
and system handles which are common across the entire system.


ΓòÉΓòÉΓòÉ <hidden> Flat Address ΓòÉΓòÉΓòÉ

A flat address is a virtual offset. Because the selector registers (loaded by
the operating system) have a base address of 00000000, flat is equivalent to
linear.


ΓòÉΓòÉΓòÉ <hidden> Fonts ΓòÉΓòÉΓòÉ

Fonts control the shapes and sizes of the characters being displayed. Only
monospace fonts (all characters the same width) can be used by THESEUS2. Only
display fonts can be selected in THESEUS2. Printer fonts cannot be changed by
THESEUS2.


ΓòÉΓòÉΓòÉ <hidden> Free Page ΓòÉΓòÉΓòÉ

A free page is a page of RAM not currently in use. However, it may be allocated
by the Page Manager and associated with a memory object.


ΓòÉΓòÉΓòÉ <hidden> GDT ΓòÉΓòÉΓòÉ

The Global Descriptor Table contains the descriptor table entries for selectors
that can be accessed by any process.


ΓòÉΓòÉΓòÉ <hidden> Handle ΓòÉΓòÉΓòÉ

Within the OS/2 system, a handle is used to refer from one control block to
another, without using the actual address. A handle is normally a 16-bit word.


ΓòÉΓòÉΓòÉ <hidden> har ΓòÉΓòÉΓòÉ

The handle of an arena record is a har.


ΓòÉΓòÉΓòÉ <hidden> hco ΓòÉΓòÉΓòÉ

The handle of a context record is a hco.


ΓòÉΓòÉΓòÉ <hidden> hmte ΓòÉΓòÉΓòÉ

The handle of an MTE is a hmte.


ΓòÉΓòÉΓòÉ <hidden> hob ΓòÉΓòÉΓòÉ

The handle of an object record is a hob.


ΓòÉΓòÉΓòÉ <hidden> Hyperblock Links ΓòÉΓòÉΓòÉ

Hyperblock* links allow you to navigate from one control block to another by
using the mouse to select the address of the block to be viewed. A hyperblock
link is denoted by its different color. The color of the links can be changed
with the `Link' color option of the Misc menu in the Process Hierarchy window.


ΓòÉΓòÉΓòÉ <hidden> Idle Page ΓòÉΓòÉΓòÉ

An idle pages is a page that has not been recently used. The Page Ager program
runs when the number of free pages becomes small. Idle pages are placed on the
idle list before being removed from the system.


ΓòÉΓòÉΓòÉ <hidden> IDT ΓòÉΓòÉΓòÉ

The Interrupt Descriptor Table contains the descriptor table entries for
selectors used to execute the proper interrupt routine.


ΓòÉΓòÉΓòÉ <hidden> LDT ΓòÉΓòÉΓòÉ

The Local Descriptor Table contains the descriptor table entries for selectors
that can be accessed by a single process. There is one for each process.


ΓòÉΓòÉΓòÉ <hidden> Linear Address ΓòÉΓòÉΓòÉ

A linear address is the intermediate result when the CPU is resolving memory
addresses. They are represented by THESEUS2 as llllllll (in hexadecimal
notation).


ΓòÉΓòÉΓòÉ <hidden> Locked Page ΓòÉΓòÉΓòÉ

A locked page is a page of RAM that has been locked with the DevHlp_Lock...
function. It may be locked either long term or short term.


ΓòÉΓòÉΓòÉ <hidden> Memory Leak ΓòÉΓòÉΓòÉ

When a program allocates memory and then does not free it, that program is said
to be "leaking memory."


ΓòÉΓòÉΓòÉ <hidden> Memory Object ΓòÉΓòÉΓòÉ

A memory object is the logical allocation unit of memory. Applications allocate
memory objects using the DosAllocMem or DosAllocSharedMem functions.


ΓòÉΓòÉΓòÉ <hidden> MTE ΓòÉΓòÉΓòÉ

An MTE, or Module Table Entry, is an in-memory description of an executable
module. The handle of an MTE is an hmte.


ΓòÉΓòÉΓòÉ <hidden> Object Record ΓòÉΓòÉΓòÉ

There is an object record for each memory object in the system. Most objects
are real objects and associated with arena records, containing a linear
address. However, some objects are pseudo-objects, and the linear address is in
the object record. The handle of an object record is a hob.


ΓòÉΓòÉΓòÉ <hidden> Owner ΓòÉΓòÉΓòÉ

All allocated memory has an owner. For system memory, that owner is a
hexadecimal value, starting with hex FF. Each sub-system in the kernel has one
or more unique values for keeping track of allocated memory. For private
memory, the owner is the hob of a PTDA or MTE. For shared memory, the owner may
be either a system owner value, the hob of a PTDA, or the hob of an MTE. The
owner value is in the object record.


ΓòÉΓòÉΓòÉ <hidden> Page Directory ΓòÉΓòÉΓòÉ

The Page Directory is the first-level address translation table used by the
hardware to map a linear address to a physical address. The entries in the Page
Directory point to Page Tables.


ΓòÉΓòÉΓòÉ <hidden> Page Frame Table ΓòÉΓòÉΓòÉ

The Page Frame Table has an entry for each page in the physical address space.
This space includes all the real RAM in the machine, the I/O RAM space, and the
ROM space. This table keeps track of the contents of each physical page.


ΓòÉΓòÉΓòÉ <hidden> Page Table ΓòÉΓòÉΓòÉ

The Page Table is the second-level address translation table used by the
hardware to map a linear address to a physical address. The entries in the Page
Directory point to Page Tables, which in turn point to pages of physical RAM.


ΓòÉΓòÉΓòÉ <hidden> PDE ΓòÉΓòÉΓòÉ

A PDE, or Page Directory Entry, contains the physical address of a particular
Page Table.


ΓòÉΓòÉΓòÉ <hidden> Physical Address ΓòÉΓòÉΓòÉ

A physical address is the final result when the CPU is resolving memory
addresses. They are used to address the memory chips. They are represented by
THESEUS2 as pppppppp (in hexadecimal notation).


ΓòÉΓòÉΓòÉ <hidden> Physical Memory ΓòÉΓòÉΓòÉ

The physical memory in the machine is referenced by a physical address. (As
opposed to virtual memory.)


ΓòÉΓòÉΓòÉ <hidden> PID ΓòÉΓòÉΓòÉ

The process ID is a 16-bit number that uniquely identifies an OS/2 process.


ΓòÉΓòÉΓòÉ <hidden> Popup Menu ΓòÉΓòÉΓòÉ

A popup menu is activated by a single-click of mouse button 2 or by pressing
the Shift-F10 key sequence. A popup menu appears next to the item selected.


ΓòÉΓòÉΓòÉ <hidden> Present Pages ΓòÉΓòÉΓòÉ

Present pages are those pages currently in RAM.


ΓòÉΓòÉΓòÉ <hidden> Process ΓòÉΓòÉΓòÉ

In the OS/2 system, processes are the owners of resources. One or more
cooperating processes make up each application. Each process takes its name
from EXE file it is associated with. Each process is uniquely identified within
the OS/2 system by its PID.

(In other systems, processes are called "tasks.")


ΓòÉΓòÉΓòÉ <hidden> Process Page Directory ΓòÉΓòÉΓòÉ

Each process is associated with a Process Page Directory. This directory
contains the PDEs for the first 512MB of linear address space. The Process Page
Directory is copied into the first 128 entries of the System Page Directory
when the process is dispatched.


ΓòÉΓòÉΓòÉ <hidden> Pseudo-Objects ΓòÉΓòÉΓòÉ

Pseudo-objects are areas of memory allocated from kernel heap space. Because
they have hobs, they can be accessed the same way as normal memory objects.
MTEs and PTDAs are pseudo-objects.


ΓòÉΓòÉΓòÉ <hidden> PTDA ΓòÉΓòÉΓòÉ

The PTDA, or Per Task Data Area, describes the resources owned by a process.


ΓòÉΓòÉΓòÉ <hidden> PTE ΓòÉΓòÉΓòÉ

The PTE, or Page Table Entry, contains the physical address of a page.


ΓòÉΓòÉΓòÉ <hidden> RAM ΓòÉΓòÉΓòÉ

RAM, or Random Access Memory, is the modifiable memory in the computer used by
programs. See Physical Memory.


ΓòÉΓòÉΓòÉ <hidden> Resident Pages ΓòÉΓòÉΓòÉ

Resident pages are pages of RAM that cannot be swapped.  They must remain in
RAM at all times until freed.


ΓòÉΓòÉΓòÉ <hidden> ROM ΓòÉΓòÉΓòÉ

ROM, or Read Only Memory, is the unchangeable memory in the computer used by
permanent programs. See Physical Memory.


ΓòÉΓòÉΓòÉ <hidden> SFT ΓòÉΓòÉΓòÉ

The System File Table entry contains information about each unique instance of
an open file.


ΓòÉΓòÉΓòÉ <hidden> Swappable Pages ΓòÉΓòÉΓòÉ

Swappable pages are pages of RAM that can be swapped. They may be in RAM or on
disk.


ΓòÉΓòÉΓòÉ <hidden> Swapped Pages ΓòÉΓòÉΓòÉ

Swapped pages are those pages currently in the SWAPPER.DAT file.


ΓòÉΓòÉΓòÉ <hidden> SWAPPER.DAT ΓòÉΓòÉΓòÉ

The SWAPPER.DAT file is the disk file where pages are kept after being swapped
out.


ΓòÉΓòÉΓòÉ <hidden> TCB ΓòÉΓòÉΓòÉ

The TCB, or Thread Control Block, contains information unique to a thread.


ΓòÉΓòÉΓòÉ <hidden> Thread ΓòÉΓòÉΓòÉ

A thread is the dispatchable entity within the OS/2 system. A thread is
identified within a process by its TID. It is uniquely identified within the
OS/2 system by a thread number.


ΓòÉΓòÉΓòÉ <hidden> Thread Number ΓòÉΓòÉΓòÉ

A thread number is the system wide unique identifier for a thread. A thread
number is used within the OS/2 dispatcher, for example. Do not confuse the
thread number with thread ID.


ΓòÉΓòÉΓòÉ <hidden> TIB ΓòÉΓòÉΓòÉ

The TIB, or Thread Information Block, contains information about the currently
running thread and is accessible by the application program.


ΓòÉΓòÉΓòÉ <hidden> TID ΓòÉΓòÉΓòÉ

The TID, or Thread ID, is a 16-bit number that uniquely identifies a thread
within a process.


ΓòÉΓòÉΓòÉ <hidden> TSD ΓòÉΓòÉΓòÉ

The TSD, or Thread Swappable Data, is the portion of a thread control block
that is swappable.


ΓòÉΓòÉΓòÉ <hidden> TSS ΓòÉΓòÉΓòÉ

The TSS, or Task State Segment, is a 386 control block used by the processor to
control its multi-tasking functions.


ΓòÉΓòÉΓòÉ <hidden> UVirt Page ΓòÉΓòÉΓòÉ

A UVirt page is a page that has been defined by a device driver or the kernel
by using one of their special functions. The device driver function is
DevHlp_PhysToUVirt. The "physical address" in the Page Table Entry may not
point to a real page of RAM. It may point to an I/O adapter card or some other
"pseudo-memory."


ΓòÉΓòÉΓòÉ <hidden> Virtual Address ΓòÉΓòÉΓòÉ

Virtual addresses have both selectors and offsets. They are represented by
THESEUS2 as ssss:oooo or ssss:oooooooo (selector:offset) (all in hexadecimal
notation).


ΓòÉΓòÉΓòÉ <hidden> Virtual Memory ΓòÉΓòÉΓòÉ

Virtual memory is memory as seen by the program. It is referenced by a virtual
address or a flat address. (As opposed to physical memory.)


ΓòÉΓòÉΓòÉ <hidden> Virtual Page Table ΓòÉΓòÉΓòÉ

The Virtual Page Table keeps track of committed memory. This table contains an
entry for each page of committed memory.


ΓòÉΓòÉΓòÉ <hidden> Working Set ΓòÉΓòÉΓòÉ

The working set is the set of memory (pages) referenced in the last n time
intervals. The working set includes both resident and locked pages.


ΓòÉΓòÉΓòÉ 1. Notices ΓòÉΓòÉΓòÉ

References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates.

Any reference to an IBM product, program, or service is not intended to state
or imply that only IBM's product, program, or service may be used.

Any functionally equivalent product, program, or service that does not infringe
any of IBM's intellectual property rights or other legally protectible rights
may be used instead of the IBM product, program, or service.

Evaluation and verification of operation in conjunction with other products,
programs, or services, except those expressly designated by IBM, are the user's
responsibility.

IBM may have patents or pending patent applications covering subject matter in
this document.  The furnishing of this document does not give you any rights to
these patents.

You can inquire, in writing, to the IBM Director of Commercial Relations, IBM
Corporation, Purchase, NY 10577 - USA, or to the IBM Director of Commercial
Relations, IBM World Trade Asia Corporation, IBM Kamiya-cho Building, 4-3-9
Toranomon, Minato-ku, Tokyo, Japan.

The following terms, denoted by an asterisk (*) in this reference, are
trademarks of the IBM Corporation in the United States and/or other countries:

IBM   THESEUS2    Operating System/2    System Performance Monitor/2
Hyperblock   OS/2   SystemView   Presentation Manager   CSet/2

The following terms, denoted by a double asterisk (**) in this reference, are
trademarks of other companies as follows:

Microsoft   Microsoft Corporation

The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS INFORMATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain
transactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the information.  IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
information at any time.

It is possible that this information may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country.  Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.

Requests for copies of this information and for technical information about IBM
products should be made to your IBM Authorized Dealer or your IBM Marketing
Representative.

(C) Copyright International Business Machines Corporation 1992.  All rights
reserved.

Note to U.S. Government Users:  Documentation and programs related to
restricted rights.  Use, duplication, or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.


ΓòÉΓòÉΓòÉ 2. Introduction ΓòÉΓòÉΓòÉ

THESEUS2* is a memory analysis program for the OS/2* 2.x system to:

 1. look at selected machine registers and control blocks (formatted)
 2. look at selected OS/2 system control blocks (formatted)
 3. look at application memory (in hexadecimal notation)
 4. determine the amount of memory consumed by each active process.

THESEUS2 uses two classes of windows:

Process Hierarchy     Shows the hierarchy of processes as they currently exist
                      in memory. There is only 1 window of this class.
Detail                Shows information about specific areas in either the OS/2
                      system or application memory. There can be up to 16
                      windows of this class.

Other topics include:

Demonstration               demonstrating some of THESEUS2's functions
How to use THESEUS2         understanding how to use THESEUS2
Memory Explanations         understanding how memory is managed in OS/2 2.x
Glossary                    meanings of terms.


ΓòÉΓòÉΓòÉ 3. Who Was Theseus? ΓòÉΓòÉΓòÉ

Theseus (pronounced Thee'-see-us) was one of the Attic heroes of Greek
mythology. According to legend, he was one of the young Greeks chosen to be
sacrificed to the Minotaur, the mythical half man/half bull confined in the
Labyrinth. Instead, Theseus killed the Minotaur. One of the local girls,
Ariadne, gave him a thread, which he used to mark his trail into and out of the
Labyrinth. He then married Ariadne and they sailed off into the sunset.

The analogy of the labyrinth is appropriate, because assigning memory to a user
in the OS/2 environment is quite complex, much like the Labyrinth of old.
However, this program knows its way through the labyrinth and can assist you in
determining the amount of memory used by your programs.


ΓòÉΓòÉΓòÉ 4. A Short Demonstration ΓòÉΓòÉΓòÉ

THESEUS2 is totally different from THESEUS*. THESEUS2 is a PM windowed
application with hyperblock linking between the OS/2 control blocks. To try it
out:

 1. Bring up THESEUS2.
 2. Select the Registers pull-down.
 3. Select Control Registers.
 4. Double-click mouse button 1 while pointing at the GDT base value (which is
    in green).
 5. What you are seeing is the formatted GDT.
 6. Close that window.
 7. Double-click mouse button 2 while pointing at the GDT base value (which is
    in green).
 8. What you are seeing is a "description" of the GDT memory object.
 9. Press the F1 key to obtain a help panel that explains what you are looking
    at.


ΓòÉΓòÉΓòÉ 5. Glossary ΓòÉΓòÉΓòÉ

Word       Definition
Arena      An arena maps a linear address space by way of a doubly linked
           circular chain of arena records. Each arena starts with a sentinel
           record. There are three separate arenas associated with each
           process:

   private  Maps the linear address space unique to that process. This memory
            holds EXE files and memory objects allocated using the DosAllocMem
            function.
   shared   Maps the linear address space shared by all the processes. This
            memory holds DLL files and memory objects allocated using the
            DosAllocSharedMem function.
   system   Maps the linear address space which belongs to the OS/2 system.
Arena Record There is an arena record for each memory object that has linear
           address space allocated to it. The handle of the arena record is a
           har. The arena records are arranged in arenas.
Claimable Page A claimable page is one that is not marked present in a
           particular Page Table Entry, however, the page is present. On the
           first reference to the page, the page will simply be marked
           "present".
Clean Page A clean page is one that has not been written to in RAM since being
           loaded from disk.
Committed Memory Committed memory is memory that has been both allocated and
           committed. Committed memory has an entry in the Virtual Page Table
           and can be "backed" by:

   o A page of real RAM
   o A page of DASD in the SWAPPER.DAT file
   o A page of a program file
   o Nothing.
Context    Many memory objects are associated with a particular OS/2 process.
           The context of a memory object refers to the process with which it
           is associated.
Context Record There is a context record for each process that can access a
           particular memory object in the shared arena. The handle of the
           context record is a hco.
Dirty Page A dirty page is one that has been written to in RAM, but not yet
           written to the SWAPPER.DAT file.
DTE        A DTE, or Descriptor Table Entry, is an entry in a Descriptor Table
           (GDT, LDT, or IDT). It includes the linear address and size of a
           segment.
Exit List  The list of routines that are to be executed when a process ends.
File Handle The handle of a file. There are process handles which are unique
           for a process and system handles which are common across the entire
           system.
Flat Address A flat address is a virtual offset. Because the selector registers
           (loaded by the operating system) have a base address of 00000000,
           flat is equivalent to linear.
Fonts      Fonts control the shapes and sizes of the characters being
           displayed. Only monospace fonts (all characters the same width) can
           be used by THESEUS2. Only display fonts can be selected in THESEUS2.
           Printer fonts cannot be changed by THESEUS2.
Free Page  A free page is a page of RAM not currently in use. However, it may
           be allocated by the Page Manager and associated with a memory
           object.
GDT        The Global Descriptor Table contains the descriptor table entries
           for selectors that can be accessed by any process.
Handle     Within the OS/2 system, a handle is used to refer from one control
           block to another, without using the actual address. A handle is
           normally a 16-bit word.
har        The handle of an arena record is a har.
hco        The handle of a context record is a hco.
hmte       The handle of an MTE is a hmte.
hob        The handle of an object record is a hob.
Hyperblock Links Hyperblock* links allow you to navigate from one control block
           to another by using the mouse to select the address of the block to
           be viewed. A hyperblock link is denoted by its different color. The
           color of the links can be changed with the `Link' color option of
           the Misc menu in the Process Hierarchy window.
Idle Page  An idle pages is a page that has not been recently used. The Page
           Ager program runs when the number of free pages becomes small. Idle
           pages are placed on the idle list before being removed from the
           system.
IDT        The Interrupt Descriptor Table contains the descriptor table entries
           for selectors used to execute the proper interrupt routine.
LDT        The Local Descriptor Table contains the descriptor table entries for
           selectors that can be accessed by a single process. There is one for
           each process.
Linear Address A linear address is the intermediate result when the CPU is
           resolving memory addresses. They are represented by THESEUS2 as
           llllllll (in hexadecimal notation).
Link       see Hyperblock Link.
Locked Page A locked page is a page of RAM that has been locked with the
           DevHlp_Lock... function. It may be locked either long term or short
           term.
Memory Leak When a program allocates memory and then does not free it, that
           program is said to be "leaking memory."
Memory Object A memory object is the logical allocation unit of memory.
           Applications allocate memory objects using the DosAllocMem or
           DosAllocSharedMem functions.
MTE        An MTE, or Module Table Entry, is an in-memory description of an
           executable module. The handle of an MTE is an hmte.
Object Record There is an object record for each memory object in the system.
           Most objects are real objects and associated with arena records,
           containing a linear address. However, some objects are
           pseudo-objects, and the linear address is in the object record. The
           handle of an object record is a hob.
Owner      All allocated memory has an owner. For system memory, that owner is
           a hexadecimal value, starting with hex FF. Each sub-system in the
           kernel has one or more unique values for keeping track of allocated
           memory. For private memory, the owner is the hob of a PTDA or MTE.
           For shared memory, the owner may be either a system owner value, the
           hob of a PTDA, or the hob of an MTE. The owner value is in the
           object record.
Page Directory The Page Directory is the first-level address translation table
           used by the hardware to map a linear address to a physical address.
           The entries in the Page Directory point to Page Tables.
Page Frame Table The Page Frame Table has an entry for each page in the
           physical address space. This space includes all the real RAM in the
           machine, the I/O RAM space, and the ROM space. This table keeps
           track of the contents of each physical page.
Page Table The Page Table is the second-level address translation table used by
           the hardware to map a linear address to a physical address. The
           entries in the Page Directory point to Page Tables, which in turn
           point to pages of physical RAM.
PDE        A PDE, or Page Directory Entry, contains the physical address of a
           particular Page Table.
Physical Address A physical address is the final result when the CPU is
           resolving memory addresses. They are used to address the memory
           chips. They are represented by THESEUS2 as pppppppp (in hexadecimal
           notation).
Physical Memory The physical memory in the machine is referenced by a physical
           address. (As opposed to virtual memory.)
PID        The process ID is a 16-bit number that uniquely identifies an OS/2
           process.
Popup Menu A popup menu is activated by a single-click of mouse button 2 or by
           pressing the Shift-F10 key sequence. A popup menu appears next to
           the item selected.
Present Pages Present pages are those pages currently in RAM.
Process    In the OS/2 system, processes are the owners of resources. One or
           more cooperating processes make up each application. Each process
           takes its name from EXE file it is associated with. Each process is
           uniquely identified within the OS/2 system by its PID. (In other
           systems, processes are called "tasks.")
Process Page Directory Each process is associated with a Process Page
           Directory. This directory contains the PDEs for the first 512MB of
           linear address space. The Process Page Directory is copied into the
           first 128 entries of the System Page Directory when the process is
           dispatched.
Pseudo-Object Pseudo-objects are areas of memory allocated from kernel heap
           space. Because they have hobs, they can be accessed the same way as
           normal memory objects. MTEs and PTDAs are pseudo-objects.
PTDA       The PTDA, or Per Task Data Area, describes the resources owned by a
           process.
PTE        The PTE, or Page Table Entry, contains the physical address of a
           page.
RAM        RAM, or Random Access Memory, is the modifiable memory in the
           computer used by programs. See Physical Memory.
Resident Pages Resident pages are pages of RAM that cannot be swapped.  They
           must remain in RAM at all times until freed.
ROM        ROM, or Read Only Memory, is the unchangeable memory in the computer
           used by permanent programs. See Physical Memory.
SFT        The System File Table entry contains information about each unique
           instance of an open file.
Swappable Pages Swappable pages are pages of RAM that can be swapped. They may
           be in RAM or on disk.
Swapped Pages Swapped pages are those pages currently in the SWAPPER.DAT file.
SWAPPER.DAT The SWAPPER.DAT file is the disk file where pages are kept after
           being swapped out.
TCB        The TCB, or Thread Control Block, contains information unique to a
           thread.
Thread     A thread is the dispatchable entity within the OS/2 system. A thread
           is identified within a process by its TID. It is uniquely identified
           within the OS/2 system by a thread number.
Thread Number A thread number is the system wide unique identifier for a
           thread. A thread number is used within the OS/2 dispatcher, for
           example. Do not confuse the thread number with thread ID.
TIB        The TIB, or Thread Information Block, contains information about the
           currently running thread and is accessible by the application
           program.
TID        The TID, or Thread ID, is a 16-bit number that uniquely identifies a
           thread within a process.
TSD        The TSD, or Thread Swappable Data, is the portion of a thread
           control block that is swappable.
TSS        The TSS, or Task State Segment, is a 386 control block used by the
           processor to control its multi-tasking functions.
UVirt Page A UVirt page is a page that has been defined by a device driver or
           the kernel by using one of their special functions. The device
           driver function is DevHlp_PhysToUVirt. The "physical address" in the
           Page Table Entry may not point to a real page of RAM. It may point
           to an I/O adapter card or some other "pseudo-memory."
Virtual Address Virtual addresses have both selectors and offsets. They are
           represented by THESEUS2 as ssss:oooo or ssss:oooooooo
           (selector:offset) (all in hexadecimal notation).
Virtual Memory Virtual memory is memory as seen by the program. It is
           referenced by a virtual address or a flat address. (As opposed to
           physical memory.)
Virtual Page Table The Virtual Page Table keeps track of committed memory. This
           table contains an entry for each page of committed memory.
Working Set The working set is the set of memory (pages) referenced in the last
           n time intervals. The working set includes both resident and locked
           pages.


ΓòÉΓòÉΓòÉ 6. How to use THESEUS2 ΓòÉΓòÉΓòÉ

The following aspects of using THESEUS2 are explored:

o Hyperblock Links
o Mouse Usage
o Memory Analysis Using THESEUS2
o How to Do Things with THESEUS2


ΓòÉΓòÉΓòÉ 6.1. Hyperblock (tm) links ΓòÉΓòÉΓòÉ

Hyperblock* links allow you to navigate from one control block to another by
using the mouse to select the address of the block to be viewed. A hyperblock
link is denoted by its different color. The color of the links can be changed
with the `Link' color option of the Misc menu in the Process Hierarchy window.


ΓòÉΓòÉΓòÉ 6.2. Mouse usage and item selection ΓòÉΓòÉΓòÉ

The usage of the Mouse is dependent on the context, as follows:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéItem\Context  ΓöéMain Window   ΓöéDetail Window       ΓöéDetail Window Γöé
Γöé              Γöé              Γöé(normal usage)      Γöé(selecting an Γöé
Γöé              Γöé              Γöé                    Γöéarea)         Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPointer       ΓöéPoints to the ΓöéPoints to the       ΓöéMarks off     Γöé
Γöé              Γöédesired       Γöédesired hyperblock  Γöéopposite      Γöé
Γöé              Γöéprocess.      Γöélink.               Γöécorners of theΓöé
Γöé              Γöé              Γöé                    Γöéarea to be    Γöé
Γöé              Γöé              Γöé                    Γöéselected.     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéButton 1      ΓöéSelects the   ΓöéSelects the         ΓöéStarts/stops  Γöé
Γöé(single-click)Γöéprocess that  Γöéhyperblock link thatΓöéselecting the Γöé
Γöé              Γöéthe pointer isΓöéthe pointer is over.Γöéarea.         Γöé
Γöé              Γöéover.         Γöé                    Γöé              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéButton 1      ΓöéDisplays      ΓöéDisplays the linked Γöé              Γöé
Γöé(double-click)Γöégeneral       Γöémemory object that  Γöé              Γöé
Γöé              Γöéinformation   Γöéthe pointer is over.Γöé              Γöé
Γöé              Γöéabout the     Γöé                    Γöé              Γöé
Γöé              Γöéprocess that  Γöé                    Γöé              Γöé
Γöé              Γöéthe pointer isΓöé                    Γöé              Γöé
Γöé              Γöéover.         Γöé                    Γöé              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéButton 2      Γöé              ΓöéDisplays a popup    Γöé              Γöé
Γöé(single-click)Γöé              Γöémenu customized for Γöé              Γöé
Γöé              Γöé              Γöéthe hyperblock link Γöé              Γöé
Γöé              Γöé              Γöéwhich is selected.  Γöé              Γöé
Γöé              Γöé              ΓöéIf there is not a   Γöé              Γöé
Γöé              Γöé              Γöéhyperblock link     Γöé              Γöé
Γöé              Γöé              Γöéselected, then      Γöé              Γöé
Γöé              Γöé              Γöédisplays a general  Γöé              Γöé
Γöé              Γöé              Γöépopup menu.         Γöé              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéButton 2      Γöé              ΓöéDescribes the linkedΓöé              Γöé
Γöé(double-click)Γöé              Γöémemory object that  Γöé              Γöé
Γöé              Γöé              Γöéthe pointer is over.Γöé              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

There is a pause between releasing mouse button 2 and the display of the popup
menu. As a result, the program can distinguish between a single-click and a
double-click. The time used is the system-maintained time for double-clicks
(SV_DBLCLKTIME).


ΓòÉΓòÉΓòÉ 6.3. Memory Analysis Using THESEUS2 ΓòÉΓòÉΓòÉ

We have found it necessary to look at memory usage in several different ways.
Sometimes we need to see how much memory has been allocated, sometimes we need
to see how much has been committed, sometimes we need to see how much is in
use. The various memory analysis functions of THESEUS2 were created to satisfy
these needs.

Analysis of memory usage can be done by THESEUS2 as follows:

o Memory Usage for the Entire System
o Kernel Memory Usage
o Memory Usage by a Single Process
o Working Set of the Entire System
o Working Set of a Single Process


ΓòÉΓòÉΓòÉ 6.3.1. Memory Usage for the Entire System ΓòÉΓòÉΓòÉ

The amount of memory (RAM) consumed by each process is determined and then a
summary of consumption by all processes is displayed by the RAM Usage by
Process function. Memory is considered consumed if it is allocated and marked
present in the Page Table Entry.

This is done for the entire system and the display includes data for all
processes.

This gives an overall indication of memory consumption. However, since this
does not consider which pages are being used, only present, the actual amount
of memory needed by each process may be less than the amount shown.


ΓòÉΓòÉΓòÉ 6.3.2. Kernel Memory Usage ΓòÉΓòÉΓòÉ

The amount of memory consumed by the operating system is determined by system
owner code by the Kernel Memory Usage function. The information is displayed
sorted by system owner code.

This is useful to determine how much memory is consumed by:

o Device driver allocated (owner = FF6B - allocated via devhlp AllocPhys),
  which includes any "RAM disk" allocated
o Kernel code (owner = FFAA - os2krnl load image)
o Any object allocated by the kernel, device drivers and IFSs.


ΓòÉΓòÉΓòÉ 6.3.3. Memory Usage by a Single Process ΓòÉΓòÉΓòÉ

Details about the memory usage by the selected process is displayed by the
Memory Utilization function. This data is computed as if there were no other
processes in the system. When multiple copies of a particular program are
running, each of them would show the EXE file as being consumed by that
process.

This is done for only the selected process. Some detail for the process is
shown.

This is useful for determining if a process is accumulating memory. See Is a
Process Accumulating Memory? (method 1) for a description of how to do this.


ΓòÉΓòÉΓòÉ 6.3.4. Working Set of the Entire System ΓòÉΓòÉΓòÉ

The working set memory utilization of the entire system can be determined by
the Working Set for the Entire System function.

This is most useful if the working set of all the programs you normally run can
be held in RAM at the same time.

To see how to use this function, please see:

o Working Set of the Entire System?
o Working Set When it does not all fit?


ΓòÉΓòÉΓòÉ 6.3.5. Working Set of a Single Process ΓòÉΓòÉΓòÉ

The working set memory utilization of a single process can be determined by the
Working Set for a Single Process function.

This is useful if you are only interested in a single process or if all of your
the programs you normally run do not fit in RAM.

To see how to use this function, please see:

o Working Set of a Single Process?
o Working Set When it does not all fit?


ΓòÉΓòÉΓòÉ 6.4. How to Do Things with THESEUS2 ΓòÉΓòÉΓòÉ

It is possible to do a number of different program analysis functions in
addition to the memory analysis functions. Some of them are:

o What is at an Address?
o Valid Contexts for a Shared Linear Address?
o Where is Code Loaded?
o Is a Process Accumulating Memory? (programatic method)
o Is a Process Accumulating Memory? (old method 1)
o Is a Process Accumulating Memory? (old method 2)
o Working Set of the Entire System?
o Working Set of a Single Process?
o Working Set When it does not all fit?


ΓòÉΓòÉΓòÉ 6.4.1. What is at an Address? ΓòÉΓòÉΓòÉ

To determine what memory object is at a specific address:

 1. Select the process in whose context the address lies.
 2. Select the General Process Information option of the Process pull-down.
 3. Select the Show Description option of the Functions pull-down.
 4. Enter the desired address type and value.
 5. The object description is shown.


ΓòÉΓòÉΓòÉ 6.4.2. Valid Contexts for a Shared Linear Address? ΓòÉΓòÉΓòÉ

To determine what processes have access to a shared linear address:

 1. Select the `sysinit' process.
 2. Select the Shared Object Summary option of the Process pull-down.
 3. Select the Show Description option.
 4. Enter the desired address type and value.
 5. The object description is shown, including all the processes' Page Table
    Entries for the object. The Context Records also show which processes have
    access and the type of access allowed.


ΓòÉΓòÉΓòÉ 6.4.3. Where is Code Loaded? ΓòÉΓòÉΓòÉ

To determine where code objects are loaded (so you can program a tool like the
"Intel In-Circuit Analyzer" (ICE):

 1. Select the process in whose context the program is running.
 2. Select the Modules option of the System pull-down.
 3. Find the module you are interested in. (You can use the Find dialog to have
    THESEUS2 find the module for you.)
 4. Double-click the left mouse button while pointing at the MTE @ (first
    column) value. This will display the formatted MTE.
 5. Move to the Object/Segment Table, at the bottom of the display.
 6. Double-click the right mouse button while pointing at the address of the
    particular object/segment you want to map. The Page Table Entries map the
    virtual/logical address of the module into the physical addresses needed.


ΓòÉΓòÉΓòÉ 6.4.4. Is a Process Accumulating Memory? (programatic method) ΓòÉΓòÉΓòÉ

To determine which process is accumulating memory, use the Memory Leak
Detection option on the System pull-down.

To determine which memory object is accumulating memory for a specific process,
use the Memory Leak Detection option on the Process pull-down.


ΓòÉΓòÉΓòÉ 6.4.5. Is a Process Accumulating Memory? (old method 1) ΓòÉΓòÉΓòÉ

To determine if a process is accumulating memory:

 1. Select the process you wish to examine.
 2. Perform the function that you wish to examine. (This will cause all the
    related pages of program and data to be loaded.)
 3. Select the Memory Utilization option of the Process pull-down. Do not close
    this window.
 4. Perform the function that you wish to examine.
 5. Select the Memory Utilization option of the Process pull-down, again.
 6. Compare the results in the two Memory Utilization displays. Look at the
    Total Shared originated and the Total Private lines, as these are the ones
    that will change if accumulation is taking place. (If you forget which
    display is which, the time and date of display generation are displayed on
    the last line of the display.)


ΓòÉΓòÉΓòÉ 6.4.6. Is a Process Accumulating Memory? (old method 2) ΓòÉΓòÉΓòÉ

To determine if a process is accumulating memory, when the SWAPPER.DAT file is
growing:

 1. Select the Swapper display.
 2. Look at the entries at the bottom of the display. If a process is
    accumulating memory, it will usually have a lot of pages in the SWAPPER.DAT
    file which are the same type of  memory object as the one which is being
    accumulated.


ΓòÉΓòÉΓòÉ 6.4.7. Working Set of the Entire System? ΓòÉΓòÉΓòÉ

To determine the working set of the entire system:

 1. Select the Working Set option of the System pull-down.
 2. Select the Working Set Parameters option of the Functions pull-down.
 3. Make any changes that you want to the default data collection parameters.
 4. Select the Working Set Start option of the Functions pull-down.
 5. Perform the functions (in your application) that you want measured.
 6. Return to THESEUS2's working set window and select the Working Set Stop
    option of the Functions pull-down.
 7. A summary of the working set for the entire system is displayed.
 8. Detail working set information may be obtained by:

   o Selecting the Show Detail by Page option of the Functions pull-down
   o Selecting the Show Detail by Object option of the Functions pull-down

If you want to know the working sets of individual processes, see the section
Working Set of a Single Process.


ΓòÉΓòÉΓòÉ 6.4.8. Working Set of a Single Process? ΓòÉΓòÉΓòÉ

To determine the working set of memory for a particular process:

 1. Select the process you wish to measure.
 2. Select the Working Set option of the Process pull-down.
 3. Select the Working Set Parameters option of the Functions pull-down.
 4. Make any changes that you want to the default data collection parameters.
 5. Select the Working Set Start option of the Functions pull-down.
 6. Perform the functions (in your application) that you want measured.
 7. Return to THESEUS2's working set window and select the Working Set Stop
    option of the Functions pull-down.
 8. A summary of the working set for the specified process is displayed.
 9. Detail working set information may be obtained by:

   o Selecting the Show Detail by Page option of the Functions pull-down
   o Selecting the Show Detail by Object option of the Functions pull-down

If you want to know the working set of the entire system, see the section
Working Set of the Entire System.


ΓòÉΓòÉΓòÉ 6.4.9. Working Set When it does not all fit? ΓòÉΓòÉΓòÉ

To determine the working set of memory of a group of processes that do not all
fit into RAM at the same time:

 1. Start your system without any of your applications.
 2. Do Working Set of the Entire System to determine the working set of the
    base system with your configuration.
 3. Do Working Set of a Single Process for each of your applications, one at a
    time.
 4. Do the following calculation:

      Recommended amount of memory from step 2
   +  Recommended amount of memory from each case of step 3
   -  188K (THESEUS2's working set while taking the measurement)
   =  Total working set for your case.


ΓòÉΓòÉΓòÉ 7. Memory Explanations ΓòÉΓòÉΓòÉ

The following aspects of memory under the OS/2 2.x system are explored:

o Memory Addressing in the OS/2 2.x System
o Memory States
o Memory Management Control Blocks
o Cost of Memory Objects


ΓòÉΓòÉΓòÉ 7.1. Memory Addressing in the OS/2 2.x System ΓòÉΓòÉΓòÉ

The OS/2 2.x system uses four types of addresses:

Virtual    Virtual addresses have both selectors and offsets. They are
           represented by THESEUS2 as ssss:oooo or ssss:oooooooo
           (selector:offset) (all in hexadecimal notation). These are sometimes
           referred to as "16:16" addresses. This is the address type that
           "16-bit / segmented" programs use. The system uses the Global and
           Local Descriptor Tables to convert a virtual address to a linear
           address.

Flat       A flat address is a virtual offset. Because the selector registers
           (loaded by the operating system) have a base address of 00000000,
           flat is equivalent to linear. These are sometimes referred to as
           "0:32" addresses. This is the address type that "32-bit / flat"
           programs use.

Linear     A linear address is the intermediate result when the CPU is
           resolving memory addresses. They are represented by THESEUS2 as
           llllllll (in hexadecimal notation).

Physical   A physical address is the final result when the CPU is resolving
           memory addresses. They are used to address the memory chips. They
           are represented by THESEUS2 as pppppppp (in hexadecimal notation).

See the Thunking Addresses section for conversion of "16:16" and "0:32"
addresses.

Because linear and physical addresses are both presented by THESEUS2 as eight
hexadecimal digits, the particular type must be deduced from context. However,
if THESEUS2 presents the address as a hyperblock link, it will do the proper
processing if the link is used.

Refer to the Intel 80386 Programmer's Reference Manual, Chapter 5 for more
information about how the processor handles addressing.


ΓòÉΓòÉΓòÉ 7.1.1. Thunking Addresses ΓòÉΓòÉΓòÉ

The process of converting virtual addresses from one form to another is
referred to as thunking.

Addresses can be converted from the "0:32" flat address form to the "16:16"
virtual address form by:

selector = ((flat >> 16) << 3) | 7;
offset = flat & 0x0000FFFF;

Addresses can be converted from the "16:16" virtual address form to the "0:32"
flat address form by:

flat = ((selector >> 3) << 16) | offset;

Where:

Symbol    Meaning
>> n      Right shift n bits, filling on the left with zeros.
<< n      Left shift n bits, filling on the right with zeros.
|         Bitwise or.
&         Bitwise and.


ΓòÉΓòÉΓòÉ 7.1.2. Translation Lookaside Buffer ΓòÉΓòÉΓòÉ

The 80386 and i486 processors use a Translation Lookaside Buffer (TLB) to
improve the instruction execution rate when doing paging. The TLB is a four-way
set-associative memory which maps linear addresses to physical addresses.

Each time a linear address without a TLB entry is translated, the appropriate
TLB entry is loaded and this "...will add 13, 21 or 28 clocks to the
instruction depending on whether the Accessed and/or Dirty bit in neither, one
or both of the page entries needs to be set in memory" (Intel i486
Microprocessor Programmer's Reference Manual, 1990, page E-2).

The bottom three bits of the linear address page number (bits 12-14 of the
linear address) are used to select the set of four data entries. Because most
memory objects start on 64K boundaries, these bits are zeros and the same set
of data entries is used for all address translation. TLB "thrashing" can occur
if the first page of more than four memory objects are being referenced by the
program. This causes the program execution time to substantially increase.
Because the programmer has little control over where the variables used in
high-level languages are stored, this problem is likely to occur.


ΓòÉΓòÉΓòÉ <hidden> page entries ΓòÉΓòÉΓòÉ

Page Directory or Page Table


ΓòÉΓòÉΓòÉ 7.2. Memory States ΓòÉΓòÉΓòÉ

Memory in OS/2* 2.x has several states. The states are explored:

o Physical Memory States
o Physical Memory State Change Table
o Virtual Memory States
o Virtual Memory State Change Table
o Memory State Venn Diagram


ΓòÉΓòÉΓòÉ 7.2.1. Physical Memory States ΓòÉΓòÉΓòÉ

Physical memory pages have three states:

State      Explanation
Free       A page that is not in use.  A free page can be attached to a virtual
           page.
Attached   A page that is in use. The physical page is attached to a virtual
           page, and one or more Page Table Entries point directly to it.
Idle       A page that has not been used recently. The Page Table Entry is not
           connected directly to the physical page. Instead, the Page Table
           Entry is connected to the physical page by way of the Virtual Page
           Table.

Attached pages have three substates:

State        Explanation
Swappable    The page is swappable or discardable.
Locked       The memory has been locked by a Device Driver. The lock may be
             either long-term or short-term.
Resident     The page must remain in RAM at all times and cannot be swapped or
             discarded.

Idle pages have two substates:

State   Explanation
Dirty   The page contents have been modified and must be written to the swap
        file before attaching the page to another virtual page.
Clean   The page contents have not been modified. The page can, therefore, be
        given to another virtual page without the Page Manager writing the
        contents to disk.

(Attached pages have the substates of Dirty and Clean, also. However, the
Dirty/Clean substate is interesting only if the page is in the Idle state.)

Physical Memory State Change Table


ΓòÉΓòÉΓòÉ 7.2.2. Physical Memory State Change Table ΓòÉΓòÉΓòÉ

Following are the primary physical page state transitions:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFrom StateΓöéTo State ΓöéReason                                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFree      ΓöéAttached ΓöéA virtual page is referenced that has no    Γöé
Γöé          Γöé         Γöéphysical page attached to it. The page is   Γöé
Γöé          Γöé         Γöézeroed before being given to the            Γöé
Γöé          Γöé         Γöéapplication.                                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAttached  ΓöéFree     ΓöéThe application performs a DosFreeMem       Γöé
Γöé          Γöé         Γöéfunction on the memory object.              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAttached  ΓöéIdle     ΓöéThe page ager "idles" the page if it has notΓöé
Γöé          Γöé         Γöébeen accessed recently.                     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIdle      ΓöéAttached ΓöéEither: 1. the application references the   Γöé
Γöé          Γöé         Γöépage, or 2. another application needs a     Γöé
Γöé          Γöé         Γöépage, so this one is paged out and then     Γöé
Γöé          Γöé         Γöéattached. The page is zeroed before being   Γöé
Γöé          Γöé         Γöégiven to the application.                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIdle      ΓöéFree     ΓöéThe application performs a DosFreeMem       Γöé
Γöé          Γöé         Γöéfunction on the memory object.              Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

Following are the substate transitions:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFrom StateΓöéTo State ΓöéReason                                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSwappable ΓöéLocked   ΓöéA device driver performs a DevHlp_Lock      Γöé
Γöé          Γöé         Γöéfunction on the page.                       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLocked    ΓöéSwappableΓöéA device driver performs a DevHlp_Unlock    Γöé
Γöé          Γöé         Γöéfunction on the page.                       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéResident  Γöé         ΓöéSubstate changes not allowed for resident   Γöé
Γöé          Γöé         Γöépages.                                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéClean     ΓöéDirty    ΓöéThe page is modified by a program.          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDirty     ΓöéClean    ΓöéThe page is written to disk by the Memory   Γöé
Γöé          Γöé         ΓöéManager.                                    Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.2.3. Virtual Memory States ΓòÉΓòÉΓòÉ

Virtual memory pages have three states:

State           Explanation
Free            The virtual memory is not allocated to the application.
Decommitted     Linear address space is allocated, but it is not valid for the
                program to reference the page.
Committed       Linear address space is allocated, and it is valid for the
                program to reference the page.

Committed pages have six substates:

State       Explanation
Guard       Guard pages are used to manage stacks, linearly expanding objects
            or sparse objects. When referenced, a `guard page entered'
            condition is raised.
AOD         (Allocate On Demand)  The page has not been referenced and does not
            have a page of physical memory attached. This is the normal state
            of a page after being committed and before being referenced. When
            referenced, a physical page is zeroed and attached to the virtual
            page.
TBL         (To Be Loaded)  The page has not been referenced and does not have
            a page of physical memory attached. This page was created by the
            loader. When referenced, the page is retrieved from the appropriate
            disk file.
Present     A physical page is attached to the virtual page, and the
            appropriate Page Table Entry points directly to it. This is the
            state of a page that is in active use.
Idle        A page which has not been used recently. The Page Table Entry is
            not connected directly to the physical page. Instead, the Page
            Table Entry is connected to the physical page by way of the Virtual
            Page Table. When referenced, the page is returned to the present
            state.
Swapped     The contents of the page have been swapped to disk. When
            referenced, the page is loaded from disk and returned to the
            present state.

Present pages have the same substates as attached physical memory. See the
Physical Memory States section for an explanation.

Virtual Memory State Change Table


ΓòÉΓòÉΓòÉ 7.2.4. Virtual Memory State Change Table ΓòÉΓòÉΓòÉ

Following are the primary virtual page state transitions:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFrom State ΓöéTo State   ΓöéReason                                   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFree       ΓöéDecommittedΓöéDosAllocMem or DosAllocSharedMem w/o     Γöé
Γöé           Γöé           ΓöéPAG_COMMIT                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFree       ΓöéCommitted  ΓöéDosAllocMem or DosAllocSharedMem w/      Γöé
Γöé           Γöé           ΓöéPAG_COMMIT                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDecommittedΓöéFree       ΓöéDosFreeMem                               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDecommittedΓöéCommitted  ΓöéDosSetMem w/ PAG_GUARD or PAG_COMMIT     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCommitted  ΓöéFree       ΓöéDosFreeMem or the program terminates     Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCommitted  ΓöéDecommittedΓöéDosSetMem w/ PAG_DECOMMIT. If a page is  Γöé
Γöé           Γöé           Γöéattached, it is freed.                   Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

Following are the substate transitions within the committed state:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFrom StateΓöéTo StateΓöéReason                                       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGuard     ΓöéAOD     ΓöéDosSetMem w/ PAG_COMMIT                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAOD       ΓöéGuard   ΓöéDosSetMem w/ PAG_GUARD                       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAOD       ΓöéPresent ΓöéThe page is referenced.                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTBL       ΓöéPresent ΓöéThe page is referenced.                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPresent   ΓöéTBL     ΓöéThe page is discarded by the Swapper.        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPresent   ΓöéIdle    ΓöéThe Page Ager "idles" the page if it has not Γöé
Γöé          Γöé        Γöébeen accessed recently.                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIdle      ΓöéPresent ΓöéThe page is referenced.                      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIdle      ΓöéSwapped ΓöéThe Swapper writes the page contents to disk Γöé
Γöé          Γöé        Γöébecause it needs the physical page.          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSwapped   ΓöéPresent ΓöéThe page is referenced.                      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 7.2.5. Memory State Venn Diagram ΓòÉΓòÉΓòÉ

The Venn diagram for the states of physical and virtual memory is:


ΓòÉΓòÉΓòÉ 7.3. Memory Management Control Blocks ΓòÉΓòÉΓòÉ

The memory management control blocks are presented in three methods:

o The Different Views of Memory
o Table of Memory Management Control Blocks
o Pictures of Memory Control Blocks


ΓòÉΓòÉΓòÉ 7.3.1. The Different Views of Memory ΓòÉΓòÉΓòÉ

The Memory Manager uses several control blocks to keep track of all the
different views of memory. The views are:

View       Control Blocks
Virtual    The GDT and LDT are used to convert virtual addresses to linear
           addresses.
Linear     The arena is used to manage the linear address space.
Physical   The Page Directory and Page Tables are used to convert linear
           addresses to physical addresses.
Modules    The MTE is used to manage modules.

For a tabular summary, see Table of Memory Management Control Blocks.


ΓòÉΓòÉΓòÉ 7.3.1.1. Virtual View Control Blocks ΓòÉΓòÉΓòÉ

The GDT and LDT are used to convert virtual addresses to linear addresses.

GDT   (Global Descriptor Table) The GDT has selectors which are valid in any
      process context. These include selectors for device drivers, system
      tables, kernel code, and the flat selectors that are loaded by the system
      for 32-bit flat programs.
LDT   (Local Descriptor Table) Each process has an LDT, which is used only for
      16-bit segmented applications.


ΓòÉΓòÉΓòÉ 7.3.1.2. Linear View Control Blocks ΓòÉΓòÉΓòÉ

The arena is used to manage the linear address space.

arena           The arena keeps track of what linear addresses are being used.
                The arena contains arena records, object records, and context
                records. See sections starting with Arenas with Arena Records
                for a pictorial representation of their relationships of these
                control blocks. See section Arena Relationships for a pictorial
                representation of the relationships between the various types
                of arenas.
arena header    There is an arena header for each arena. They are doubly
                linked. The Arena Header picture shows this graphically.
private arena   The PTDA contains the arena header for the private arena for
                that process. The arena header has a pointer to the sentinel
                arena record for the private arena for that Process. The
                private arena is usable only in the context of that process.
                The Arena Header picture shows this graphically.
shared arena    The shared arena tracks all of the shared memory objects in the
                system. The shared arena is context-sensitive, because the
                backing memory (pages of real RAM) may be process-unique. (This
                is the case for the instance data in a DLL file.) The context
                records keep track of which processes can access each memory
                object.
system arena    The system arena maps the linear address space which belongs to
                the OS/2 system. The system memory objects are not addressable
                by application programs.
VPT             (Virtual Page Table) The Virtual Page Table has an entry for
                each committed page. Each entry also includes the hob of the
                memory object that is attached to the page.


ΓòÉΓòÉΓòÉ 7.3.1.3. Physical View Control Blocks ΓòÉΓòÉΓòÉ

The Page Directory and Page Tables are used to convert linear addresses to
physical addresses.

PD    (Page Directory) The Page Directory is the first-level address
      translation table used by the hardware to map a linear address to a
      physical address. The entries in the Page Directory point to Page Tables.
PT    (Page Table) The Page Table is the second-level address translation table
      used by the hardware to map a linear address to a physical address. The
      entries in the Page Directory point to Page Tables, which in turn point
      to pages of physical RAM.
PPD   (Process Page Directory) Each PTDA contains a pointer to a Process Page
      Directory which points to Page Tables that track the physical pages that
      may be referenced by that Process. The PPD maps the area for both the
      private and shared arenas.
PFT   (Page Frame Table) The Page Frame Table keeps track of physical memory.
      There is an entry for each addressable page of RAM in the machine. Each
      in-use entry in this table has a pointer to an entry in the Virtual Page
      Table, which effectively links physical and linear memory.
PRT   (Page Range Table) The Page Range Table tells which pages are
      addressable.


ΓòÉΓòÉΓòÉ 7.3.1.4. Module View Control Blocks ΓòÉΓòÉΓòÉ

The MTE is used to manage modules.

MTE   (Module Table Entry) Each module that is loaded has an MTE that is used
      to manage the memory objects that make up the module. The MTEs are linked
      together. The PTDA points to the MTE for the EXE file for that process.

      The MTE is split into resident and swappable portions. There are several
      subtates in each category, including the object/segment table that has
      the actual object/segment information for the module.


ΓòÉΓòÉΓòÉ 7.3.2. Table of Memory Management Control Blocks ΓòÉΓòÉΓòÉ

A summary of how the various Memory Management Control Blocks refer to each
other:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéControl Block ----->ΓöéPointer Type ------>ΓöéControl Block       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéarena record        Γöéhar                 Γöénext arena record inΓöé
Γöé                    Γöé                    Γöéthe arena           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéarena record        Γöéhob                 Γöéobject record       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéarena record        Γöéhco                 Γöécontext record      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéobject record       Γöéhar                 Γöéarena record        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéobject record       Γöéhob                 Γöéowner               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéobject record       Γöéhob                 Γöéthe EXE or DLL file Γöé
Γöé                    Γöé                    Γöéwhich allocated the Γöé
Γöé                    Γöé                    Γöémemory              Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöécontext record      Γöéhob                 ΓöéPTDA with access to Γöé
Γöé                    Γöé                    Γöéthe shared object   Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöécontext record      Γöéhco                 Γöénext context record Γöé
Γöé                    Γöé                    Γöéin the access chain Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöéarena header        Γöélinear address      Γöéarena sentinel      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPTDA                Γöélinear address and  ΓöéLDT                 Γöé
Γöé                    Γöéhob                 Γöé                    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPTDA                Γöélinear address      ΓöéProcess Page        Γöé
Γöé                    Γöé                    ΓöéDirectory           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPTDA                Γöéhob                 ΓöéMTE of the EXE file Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMTE                 Γöélinear address      Γöénext MTE in the listΓöé
Γöé                    Γöé                    Γöéof MTEs             Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPage Directory      Γöéphysical address    ΓöéPage Table          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPage Table Entry    ΓöéImplied by the      ΓöéPage Frame Entry    Γöé
Γöé                    Γöéphysical address    Γöé                    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPage Frame Entry    ΓöéLinear address      ΓöéVirtual Page Entry  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVirtual Page Entry  Γöéhob                 ΓöéObject Record       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVirtual Page Entry  Γöéframeid             ΓöéPhysical page       Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

This is all the information that is gathered together by:

o Description of Linear Object,
o Description of Segment, and
o Description of Physical Object.


ΓòÉΓòÉΓòÉ 7.3.3. Pictures of Memory Control Blocks ΓòÉΓòÉΓòÉ

The memory manager control block pictures are:

o Arena Header picture
o Arena Relationships
o Arenas with Arena Records
o Arenas with Object Records
o Arenas with Context Records


ΓòÉΓòÉΓòÉ 7.3.3.1. Arena Header picture ΓòÉΓòÉΓòÉ

Most arena headers are within PTDAs and all are linked together:

Next picture: Arena Relationships.


ΓòÉΓòÉΓòÉ 7.3.3.2. Arena Relationships ΓòÉΓòÉΓòÉ

The arenas are related by linear address:

Adjacent pictures: Arenas with Arena Records, Arena Headers.


ΓòÉΓòÉΓòÉ 7.3.3.3. Arenas with Arena Records ΓòÉΓòÉΓòÉ

The arenas are made up of doubly linked arena records:

Adjacent pictures: Arenas with Object Records, Arena Relationships.


ΓòÉΓòÉΓòÉ 7.3.3.4. Arenas with Object Records ΓòÉΓòÉΓòÉ

All the arena records, except the sentinel, have object records:

Adjacent pictures: Arenas with Context Records, Arenas with Arena Records.


ΓòÉΓòÉΓòÉ 7.3.3.5. Arenas with Context Records ΓòÉΓòÉΓòÉ

The arena records in the shared arena have context records:

Previous picture: Arenas with Object Records.


ΓòÉΓòÉΓòÉ 7.4. Cost of Memory Objects ΓòÉΓòÉΓòÉ

The cost of a memory object can be summarized as follows:

Item                    Cost in bytes (decimal)
DTE                     8
PTE                     4 * total number of pages
Arena Record            22
Object Record           16
Context Record          5 * number of Processes that have access to the object
Page Frame Record       12 * number of pages in RAM
Virtual Page Record     12 * number of committed pages

If the object is loaded from a 32-bit EXE/DLL file, then add:

Item                    Cost in bytes (decimal)
MTE object entry        24

If the object is loaded from a 16-bit EXE/DLL file, then add:

Item                    Cost in bytes (decimal)
MTE segment entry       16

Remember that this is a per-object/segment cost. Each object/segment loaded
from the module must be included.


ΓòÉΓòÉΓòÉ 8. Changes ΓòÉΓòÉΓòÉ

Version 2.0 is the initial product version of THESEUS2.

o Changes between v2.0 and v2.0.1:


ΓòÉΓòÉΓòÉ 8.1. Changes between v2.0 and v2.0.1 ΓòÉΓòÉΓòÉ

 1. Added a second section on memory accumulation determination, using the
    SWAPPER.DAT contents to determine the problem.

 2. Added the locked memory state to the Memory State Venn Diagram.

 3. Fixed an error in the Virtual Memory Display dialog for expand down
    segments.

 4. Made the program work correctly with OS/2 2.1 beta 1 (6.479). The mte
    format changed. The data displayed has not been changed.

 5. Added some decoding of flag fields in the MTE display.

 6. Added file flags to Open Files portion of the General Process Information
    display.

 7. Fixed a trap when there was more than about 70 processes.

 8. Generated separate totals for the private and owned shared columns on the
    RAM Usage by Process display.

 9. Fixed a loop caused when the program was started with a minimized window.

10. Changed the values shown in the type column of the Modules display from
    16/32 to NE/LX. This was done because LX modules are not all 32-bit, some
    are 16-bit and some are mixed 16 & 32-bit.

11. Fixed a Hyperblock link error on the SFT entry display.

12. Fixed an error which caused the last entry to not show on the Open Files
    display.

13. Added "memory" of following functions from one invocation to the next:

   o Process Hierarchy window position, size, and state
   o Font for Process Hierarchy window
   o Default font for Detail windows
   o `Link' color

14. Fixed an error which caused a trap when entering an invalid file name in
    the SaveAs dialog.

15. Enabled long file names for the program.

16. Fixed an error in the column summations on the RAM Usage by Process display
    which was introduced with the changes for item 8 above.

17. Made the program work correctly with OS/2 2.1 (6.488+). The mte format
    changed, again.

18. Fixed an error which caused the top of the `link' list to not be
    "unchecked" which was introduced with the changes for item 13 above.

19. Changed the window trailer line to include the program name and version and
    deleted the hundredths of seconds value.

20. Changed where the program version is picked up. It was picked up from the
    dialog DLL and is now picked up from the EXE file.

21. Fixed an error in the RAM Usage by Process display which was caused by
    trying to assign pages which are not valid (pages not in the Page Range
    Table).

22. Removed diagnostic lines from the RAM Usage by Process display. The only
    information remaining is the summary.

23. Fixed an error which caused memory accumulation when using pop up menus.

24. Added the total machine run time in hours, minutes, and seconds to the
    General System Information display.  This is a formatted version of the
    QSV_MS_COUNT value.

25. Fixed an error in GDT selector validation caused when the GDT segment was
    expanded during the run.

26. Fixed an error on the Memory Utilization display that was caused when
    analyzing a process that does not have an LDT, such as a VDM process.

27. Changed the order of the output on the General System Information display
    to make it more usable.

28. Modified the working set algorithm description to better explain how the
    calculations occur.

29. Added Memory Leak Detection to the System and Process pull-downs.

30. Made the program work correctly with OS/2 2.1 (6.504+). The mte format
    changed, again.

31. Added the process environment to the General Process Information display.

32. Fixed an error in the Detail of Working Set (by Object) report which caused
    incorrect values to be shown (sometimes negative) in the accessed - no
    column in the Objects from the `shared' arena section.

33. Added an Illustration section to the Working Set panels.

34. Changed the avg. time values on the Detail of Working Set (by Object)
    report to make it easier to tell if all the pages were accessed at the same
    time.

35. Added logic to detect that the process requested for periodic update has
    terminated.

36. Added additional thread states to the General Process Information displays
    thread status area.

37. Changed the behavior of the single click of mouse button 2 so that it no
    longer will do an "item selection."

38. Added code to the initialization phase to try to make the program less
    prone to killing the whole system when the version of OS/2 is not
    recognized.

39. Reworded some of the initialization failure error messages.

40. Added Memory Object Leak Detection to the Functions pull-down.

41. Fixed a memory leak in the General Process Information display.

42. Fixed a memory leak in the T2FreeMemory API function.

43. Added an interface for REXX for some of the API functions.

44. Fixed a problem with the Memory displays which occurred when crossing page
    boundaries.

45. Added an output of the source of the base information in the Leak Detector
    displays.

46. Fixed a problem with the time interval output when starting working set
    after changing the time interval.

47. Made it work with 2.0's Service Pak2.

48. Fixed an error in the T2AnalyzeSwapper API which caused incorrect results
    to be returned.

49. Fixed errors in the Open Files display when there are more than 500 files
    open.

50. Fixed errors in the disassembler.

51. Removed the Environment output from the General Process Information display
    for VDM processes. (The environment hob which is in the PTDA is not valid
    and caused problems when trying to display the environment.)

52. Added display of the requested Arena Record to the Har Description display.

53. Added display of the requested Object Record and its referenced Arena
    Record to the Hob Description display.

54. Added allocated memory to the System Leak Detection and Process Leak
    Detection displays.

55. Added the Trace control flags to the Global Info Seg display.

56. Fixed an error during initialization on an OS/2 2.0 GA machine.

57. Fixed an error which was caused in opening the sixteenth window.

58. Changed the pointer management during periodic updates, because it was
    causing a leak in PMGRE memory.

59. Fixed a problem which caused the segment number of 16-bit objects to be
    reported as 0000 in the object description.

60. Added a code or data indicator to the shared part of an object description.

61. Fixed a problem which caused a trap in Working Set calculations when a
    process terminated during the data collection processing. This caused a
    change in the device driver THESEUS2.SYS. The change causes the device
    driver to disable interrupts during part of its processing and validate all
    the addresses it uses for data collection each time it goes disabled.

62. Fixed a problem with the code changed in the previous fix, which caused a
    trap in a user of THESEUS0.DLL.

63. Added total threads to the Process List display.

64. Fixed an error in the Swapper display which caused the number of used disk
    frames to be underreported.

65. Added code to load certain system pages which might be swapped out.

66. Changed RT2LoadFuncs so that multiple calls to it will not cause multiple
    initializations of the underlying functions.

67. Added a column for the number of pages in the working set to the Detail of
    Working Set (by Object) display.

68. Added a summary line for each arena and each process on the Detail of
    Working Set (by Object) display.

69. Added a Summary by Process display for System Working Set information.

70. Fixed a memory leak in RT2WSSystemTick and RT2WSProcessTick REXX API
    functions.

71. Deleted the code in RT2FindProcesses and RT2RamUseByProcess which attempted
    to drop the stem variable before constructing the new values. SysFileTree
    (part of the RexxUtil package) does not drop the stem, so it was decided
    that THESEUS0.DLL should not, either.

72. Fixed an error in the Memory Utilization display which did not properly
    count TSD pages when running on a machine with Kernel Debugger installed.

73. Fixed an error in several displays when processing a private arena which
    had only a sentinel.

74. Changed the method of specifying the update interval for Detail windows.
    There was a problem when specifying an interval of longer than 65 seconds.

75. Fixed an error in the Swapper window processing which occurred when a page
    is swapped out and no longer has a copy in RAM.


ΓòÉΓòÉΓòÉ 9. Process Hierarchy Window ΓòÉΓòÉΓòÉ

The Process Hierarchy window shows the parent/child relationships of processes
as they currently exist in memory.

After a process has been selected, you may then move on to a Detail window.

Options available on the Process Hierarchy window are:

System      Lists the displays applicable to the system as a whole.
Process     Lists the displays applicable to the selected process.
Registers   Lists the displays applicable to the processor.
Misc        Lists the miscellaneous functions.
Window      Lists the existing THESEUS2 Detail windows.
Help        Lists the help functions.


ΓòÉΓòÉΓòÉ 9.1. Selecting a Process ΓòÉΓòÉΓòÉ

You may select a process in either of two ways:

o Place the mouse pointer over a process name, then press mouse button 1.

o Use the arrow keys:

   Left    Moves to the parent of the current process.
   Right   Moves to the oldest child of the current process.
   Up      Moves to the next younger sibling of the current process.
   Down    Moves to the next older sibling of the current process.

If no process is selected, pressing any arrow key makes "sysinit" the selected
process.


ΓòÉΓòÉΓòÉ 9.2. Keys ΓòÉΓòÉΓòÉ

The key usage in the Process Hierarchy window is:

Left            Moves to the parent of the current process.
Right           Moves to the oldest child of the current process.
Up              Moves to the next younger sibling of the current process.
Down            Moves to the next older sibling of the current process.
Alt+Left        Scrolls the window information left.
Alt+Right       Scrolls the window information right.
Alt+Up          Scrolls the window information up.
Alt+Down        Scrolls the window information down.
Page Up         Scrolls the window information up 1/2 the screen height.
Page Down       Scrolls the window information down 1/2 the screen height.
Print Screen    Prints the contents of the window.
F1              Requests contextual help.
F3              Exits THESEUS2.
Enter           Displays General Process Information for the selected process.
                (This is the same as double-clicking mouse button 1.)


ΓòÉΓòÉΓòÉ 9.3. System ΓòÉΓòÉΓòÉ

The System pull-down contains displays applicable to the system as a whole. A
process does not have to be selected in order to select one of these displays.

Functions available are:

Working Set
          Displays the working set of memory for the entire system.
RAM Usage by Process
          First determines and then displays the amount of RAM consumed my each
          process.
Memory Leak Detection
          Displays the number of pages of memory that each process is
          accumulating.
Free, Idle and Locked Memory
          Generates the summary information about free, idle and locked pages.
Swapper
          Displays information about the contents of the SWAPPER.DAT file.
General System
          A set of displays containing general system information.
Kernel Information
          A set of displays containing kernel information.


ΓòÉΓòÉΓòÉ 9.3.1. Working Set ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Algorithm

Illustration

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Working Set Display ΓòÉΓòÉΓòÉ

When you select the Working Set option of the System pull-down on the Process
Hierarchy window, the memory working set of the entire System is computed and
displayed.

There are optional values that can be shown in realtime.


ΓòÉΓòÉΓòÉ <hidden> Example of the Working Set Display ΓòÉΓòÉΓòÉ

Working Set for the entire System:
Use the 'Functions' pull-down or the 'Popup Menu'
  to start and stop the data collection.
Collection started: interval = 5, Working Set is 3 intervals.
current time  --------- Total ----------   ------   ------ ---- Process -----
hh:mm:ss.tt      now       ws   accessed     Free     Idle contributed  total
10:49:02.84    4.789M   4.789M     4.789M   3.191M   0.008M          7      7
10:49:07.84    4.664M   4.828M     4.828M   3.191M   0.008M          7      7
10:49:12.84    4.664M   4.828M     4.828M   3.191M   0.008M          7      7
10:49:17.84    4.664M   4.664M     4.828M   3.191M   0.008M          7      7
10:49:22.84    4.664M   4.664M     4.828M   3.191M   0.008M          7      7
10:49:27.84    4.664M   4.664M     4.828M   3.191M   0.008M          7      7
10:49:32.84    4.734M   4.734M     4.898M   3.191M   0.008M          7      7
10:49:37.87    5.172M   5.184M     5.199M   3.180M   0.008M          7      7

8 samples collected.
                                    Total
Absolute minimum amount of memory:  5.172M
Recommended amount of memory:       5.184M
Total amount of accessed memory:    5.199M


ΓòÉΓòÉΓòÉ <hidden> Contents of the Working Set Display ΓòÉΓòÉΓòÉ

The following values are computed and optionally presented in realtime.

Column      Meaning

current time The time of the sample, presented in
            hours:minutes:seconds.hundredths.

now         The amount of memory referenced in the current interval.

ws          The working set, which is the amount of memory referenced in the
            past n intervals.

accessed    The total amount of memory accessed since the start of the
            collection run.

Free        The amount of free memory.

Idle        The amount of idle memory.

Process contributed The number of processes that had memory accessed during the
            interval. This value indicates the number of processes which are
            both running and touching non-system memory.

Process total The total number of processes found during the interval. This
            number changes as processes are created or destroyed.

When the Stop option is selected:

ii samples collected.
          The number of samples collected is reported (in decimal notation).
Absolute minimum amount of memory
          The maximum value from the now column. This is the amount of memory
          absolutely required to run the application without "thrashing"
          memory.
Recommended amount of memory
          The maximum value from the ws column. This is the recommended amount
          of memory for the application to run with minimum impact on paging.
Total amount of accessed memory
          The maximum value from the accessed column. This is the amount of
          memory required to run the application with no paging activity.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory Management Control Blocks

o Memory Analysis Techniques

o Detail of Working Set (by Page)

o Detail of Working Set (by Object)

o Summary by Process


ΓòÉΓòÉΓòÉ <hidden> System Working Set Algorithm ΓòÉΓòÉΓòÉ

To compute the working set for the entire OS/2 system, you need to know:

o Which pages have been referenced
o When the pages were touched.

The algorithm is:

 1. The accessed flags are cleared from the Page Tables of all processes
    running in the system.

 2. A timer is started, and on each timer tick:

    a. The pages which have been accessed are noted.
    b. The accessed flags are cleared.
    c. The number of pages which have been accessed anytime within the
       specified number of intervals is counted.
    d. Summary information for the interval is generated.
    e. The interval information is displayed, if requested.

 3. When the Stop option is selected:

    a. Summary numbers for the entire run are generated. They are:

      Absolute minimum amount of memory
                The maximum of all the now entries.
      Recommended amount of memory
                The maximum of all the ws entries.
      Total amount of accessed memory
                The maximum of all the accessed entries.

    b. The results are displayed.


ΓòÉΓòÉΓòÉ <hidden> Working Set Illustration ΓòÉΓòÉΓòÉ

To illustrate how the working set algorithm works, the follow table will be
used:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöétick  Γöéwhich pagesΓöépage 1Γöépage 2Γöépage 3Γöénow   Γöéws    ΓöéaccessedΓöé
Γöé      Γöéaccessed   Γöé      Γöé      Γöé      Γöé      Γöé      Γöé        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 0    Γöé           Γöé 255  Γöé 255  Γöé 255  Γöé      Γöé      Γöé        Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1    Γöé 1         Γöé 1    Γöé 255  Γöé 255  Γöé 1    Γöé 1    Γöé 1      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2    Γöé 2         Γöé 2    Γöé 1    Γöé 255  Γöé 1    Γöé 2    Γöé 2      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 3    Γöé 1 3       Γöé 1    Γöé 2    Γöé 1    Γöé 2    Γöé 3    Γöé 3      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4    Γöé 1         Γöé 1    Γöé 3    Γöé 2    Γöé 1    Γöé 3    Γöé 3      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 5    Γöé 1         Γöé 1    Γöé 4    Γöé 3    Γöé 1    Γöé 2    Γöé 3      Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 6    Γöé 1         Γöé 1    Γöé 5    Γöé 4    Γöé 1    Γöé 1    Γöé 3      Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

The number of intervals in the working set is 3 for this illustration.

The meanings of the columns are:

Column            Meaning
tick              The interval number.
pages accessed    Indicates which page numbers were accessed during this
                  interval.
page n            The number of intervals since the page was accessed. (255
                  indicates the page has never been accessed. The value is not
                  allowed to be incremented above 254, so that value simply
                  means that the page was accessed "a long time ago.") This
                  corresponds to the time column in the detail displays.
now               The number of pages accessed in this interval. This
                  corresponds to the now column in the displays.
ws                The number of pages considered to be in the working set. This
                  corresponds to the ws column in the displays.
accessed          The number of pages which have been accessed since the run
                  began. This corresponds to the accessed column in the
                  displays.

Explanation at each tick:

0  At initialization all pages are marked as "never been accessed."
1  Page 1 was accessed. Since it was the only page accessed in the last
   interval, the now column has 1. Page 1 has been accessed within the last 3
   intervals, so the ws column has 1.
2  Page 2 was accessed. Since it was the only page accessed in the last
   interval, the now column has 1. Pages 1 and 2 have been accessed within the
   last 3 intervals, so the ws column has 2.
3  Pages 1 and 3 were accessed. They were the only pages accessed in the last
   interval, so the now column has 2. Pages 1, 2 and 3 have been accessed
   within the last 3 intervals, so the ws column has 3.
4  Page 1 was accessed. Since it was the only page accessed in the last
   interval, the now column has 1. Pages 1, 2 and 3 have been accessed within
   the last 3 intervals, so the ws column has 3.
5  Page 1 was accessed. Since it was the only page accessed in the last
   interval, the now column has 1. Pages 1 and 3 have been accessed within the
   last 3 intervals, so the ws column has 2. (Page 2 was accessed 4 intervals
   ago.)
6  Page 1 was accessed. Since it was the only page accessed in the last
   interval, the now column has 1. Page 1 has been accessed within the last 3
   intervals, so the ws column has 1. (Page 2 was accessed 5 intervals ago and
   page 3 was accessed 4 intervals ago.)


ΓòÉΓòÉΓòÉ 9.3.2. RAM Usage by Process ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the RAM Usage by Process Display ΓòÉΓòÉΓòÉ

When you select the RAM Usage by Process option of the System pull-down on the
Process Hierarchy window, information about RAM utilization for the entire
system is computed and displayed. All pages of RAM are assigned to a process,
after which summaries are provided.

The display generation takes about 7 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the RAM Usage by Process Display ΓòÉΓòÉΓòÉ

RAM Usage by Process:
--------- private --------   ------ owned shared ------
   bytes   Kbytes   Mbytes      bytes   Kbytes   Mbytes   who
00409000     4132    4.035   0026A000     2472    2.414   system
00000000        0    0.000                                sysinit
00031000      196    0.191   000D5000      852    0.832   PMSHL32
00009000       36    0.035   00005000       20    0.020   HARDERR
000BE000      760    0.742   00047000      284    0.277   PMSHL32
00018000       96    0.094   0000A000       40    0.039   PULSE
00061000      388    0.379                                VDM
00025000      148    0.145   00008000       32    0.031   CMD
0004B000      300    0.293   00008000       32    0.031   THESEUS2
--------   ------   ------   --------   ------   ------
001E1000     1924    1.879   0013B000     1260    1.230   total RAM in use
00611000     6212    6.066   free RAM
--------   ------   ------
00FA0000    16000   15.625   total of all RAM pages found


ΓòÉΓòÉΓòÉ <hidden> Contents of the RAM Usage by Process Display ΓòÉΓòÉΓòÉ

The information presented on the RAM Usage by Process display is as follows,
with one line displayed for each process:

Column           Meaning
private          Memory from the private arena of this process. If multiple
                 processes have the same page in their private arenas, the
                 process with the lowest PID value is charged with the memory.
owned shared     Memory from the shared arena that is owned by this process.
bytes            The amount of memory in bytes.
Kbytes           The amount of memory in kilobytes.
Mbytes           The amount of memory in megabytes.
who              Name of the process whose data appears on the line.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory Management Control Blocks

o Memory Analysis Using THESEUS2


ΓòÉΓòÉΓòÉ <hidden> RAM Usage by Process Algorithm ΓòÉΓòÉΓòÉ

 1. An array having an entry for each page in the machine is allocated, and
    backing RAM is forced for it. This array is called PF-parallel. This array
    keeps track of the state of each page and which process is charged with the
    page.

 2. Memory for a private copy of the Page Frame Table is allocated, and the
    Page Frame Table is copied into it. This table is called private-PF.

 3. The free pages (as indicated in private-PF) are marked in PF-parallel and
    counted.

 4. The idle pages (as indicated in private-PF) are marked in PF-parallel and
    counted.

 5. For each process:

    a. For each arena record in its private arena:

       1. Execute the MarkPresentPages routine (below).

 6. For each arena record in the shared arena:

    a. If there is an hco in the arena record:

       1. Determine the process indicated as the originator by looking at the
          context records.

       2. Execute the MarkPresentPages routine for the originator process.

    b. If there is no hco in the arena record:

       1. For each process:

          a. Execute the MarkPresentPages routine for the non-shared DLL
             object.

 7. For each arena record in the system arena:

    a. Execute the MarkPresentPages routine.

 8. For each entry in PF-parallel that has not been assigned or that is marked
    idle:

    a. Get the hob from private-PF.

    b. The object record and the linear address (from the arena record) can be
       used to determine which process should be charged with the page. The
       method used is similar to what occurred in preceding steps for normal
       objects.

 9. For each entry in PF-parallel:

    a. Add a page to the proper counter being charged. This will either be the
       free counter or a process counter.

10. Display the counters, showing both private and shared memory.

The MarkPresentPages routine is passed a range of pages and a thing to assign
them to. The algorithm is:

 1. For each page in the object which is present and not UVirt:

    a. If the page has not been assigned to something and this is a shared
       page, then assign it to this thing.

    b. If the page is a shared page and is already assigned to something and
       the linear addresses do not match, there is a conflict.

    c. If the page is not a shared page and is already assigned to something or
       the linear addresses do not match, there is a conflict.

    d. If system pages are being assigned and if the owner code indicates
       INFOSEGOWNER, then assign the page to the system.

    e. If system pages are being assigned and if the owner code indicates
       VDMALIASOWNER or VDHOWNER, do not assign the page. It will be assigned
       to the VDM that really owns it when the VDM is processed.

    f. If a conflict was detected, print out both the old and new information
       about the page.

    g. If there was no conflict, modify PF-parallel to indicate what the page
       was assigned to and the type of memory (shared, private, or system).


ΓòÉΓòÉΓòÉ 9.3.3. Memory Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

When you select the Memory Leak Detection option of the System pull-down on the
Process Hierarchy window, information about memory accumulation for each
process in the system is computed and shown.

This can be done either on a periodic basis or under user control. See Related
Topics for the references for specifying control.


ΓòÉΓòÉΓòÉ <hidden> Example of the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

Memory leak detection:
< End of THESEUS2 (v 2.0s) output @ 13:21:01 on 8/5/1993 >
Use the 'Function' pull-down to start and stop the data collection.
Leak data captured.
Periodic update started with interval of 10 seconds.
Previous sample will be used as the base.
< End of THESEUS2 (v 2.0s) output @ 13:21:10 on 8/5/1993 >
----------Private-----------  -----------Shared-----------
Allocated  Committed  Actual  Allocated  Committed  Actual   PID   Name
      +16        +17     +17         +0         +0      +0  0000   System
       +0         +0      +0        +64         +0      +0  0001   sysinit
       +0         +0      +0        +64         +0      +0  0002   LOGDAEM
       +0         +0      +0        +64         +0      +0  0003   SPMNBL
      +16         +1      +1        +64         +0      +0  0004   PMSHL32
       +0         +0      +0        +64         +0      +0  0005   HARDERR
       +0         +0      +0        +64         +0      +0  0006   SPMSNAPL
       +0         +0      +0        +64         +0      +0  0007   PMSHL32
       +0         +0      +0        +64         +0      +0  0008   PULSE
       +0         +0      +0        +64         +0      +0  0009   VDM
       +0         +0      +0        +64         +0      +0  004F   VIEWDOC
       +0         +0      +0        +64         +0      +0  0053   CMD
       +0         +0      +0        +64         +0      +0  0060   THESEUS2
     +160        +56     +39     +16000      +1540    +774  0061  +CMD
< End of THESEUS2 (v 2.0s) output @ 13:21:21 on 8/5/1993 >
----------Private-----------  -----------Shared-----------
Allocated  Committed  Actual  Allocated  Committed  Actual   PID   Name
      -16        -17     -17         +0         +0      +0  0000   System
       +0         +0      +0        -64         +0      +0  0001   sysinit
       +0         +0      +0        -64         +0      +0  0002   LOGDAEM
       +0         +0      +0        -64         +0      +0  0003   SPMNBL
      -16         -1      -1        -64         +0      +0  0004   PMSHL32
       +0         +0      +0        -64         +0      +0  0005   HARDERR
       +0         +0      +0        -64         +0      +0  0006   SPMSNAPL
       +0         +0      +0        -64         +0      +0  0007   PMSHL32
       +0         +0      +0        -64         +0      +0  0008   PULSE
       +0         +0      +0        -64         +0      +0  0009   VDM
       +0         +0      +0        -64         +0      +0  004F   VIEWDOC
       +0         +0      +0        -64         +0      +0  0053   CMD
       +0         +0      +0        -64         +0      +0  0060   THESEUS2
     -160        -56     -39     -16000      -1540    -774  0061  -CMD
< End of THESEUS2 (v 2.0s) output @ 13:21:31 on 8/5/1993 >
Periodic updated stopped.
< End of THESEUS2 (v 2.0s) output @ 13:21:32 on 8/5/1993 >


ΓòÉΓòÉΓòÉ <hidden> Contents of the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

One line is displayed for each process whose allocated, committed, or actual
(present + swapped) memory values have changed:

Column      Meaning
Private Allocated The change in the number of pages of allocated (virtual)
            memory in the private arena.
Private Committed The change in the number of pages of committed memory in the
            private arena.
Private Actual The change in the number of pages of actual memory in the
            private arena.
Shared Allocated The change in the number of pages of allocated (virtual)
            memory in the shared arena.
Shared Committed The change in the number of pages of committed memory in the
            shared arena.
Shared Actual The change in the number of pages of actual memory in the shared
            arena.
PID         The PID of the process for this line.
Name        The name of the process on this line. If the process is new (not
            present in the base data), then a prefix '+' is shown. If the
            process has terminated, then a prefix '-' is shown.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory states

o Leak detection control

o Manual data capture

o Manual data compare


ΓòÉΓòÉΓòÉ 9.3.4. Free, Idle, and Locked Memory ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Free, Idle, and Locked Memory display ΓòÉΓòÉΓòÉ

When you select the Free, Idle, and Locked Memory option of the System
pull-down on the Process Hierarchy window, information about free, idle, and
locked memory is displayed.

If the list of pages making up a category is desired, double-click mouse button
1 with the pointer over the page count. (This procedure is similar to "display
a control block" processing.)


ΓòÉΓòÉΓòÉ <hidden> Example of the Free, Idle, and Locked Memory Display ΓòÉΓòÉΓòÉ

Free, Idle, and Locked Memory:
Free                RAM = 000BD000 bytes (  756K) ( 0.738M).
Idle                RAM = 00076000 bytes (  472K) ( 0.461M).
        (Dirty idle RAM = 00068000 bytes (  416K) ( 0.406M)).
Long  Term Locked   RAM = 0001C000 bytes (  112K) ( 0.109M).
Short Term Locked   RAM = 00000000 bytes (    0K) ( 0.000M).
Short & Long Locked RAM = 00000000 bytes (    0K) ( 0.000M).


ΓòÉΓòÉΓòÉ <hidden> Contents of the Free, Idle, and Locked Memory Display ΓòÉΓòÉΓòÉ

The information presented on the Free, Idle, and Locked Memory display is as
follows:

Free RAM = xxxxxxxx
          Amount of free memory.
Idle RAM = xxxxxxxx
          Amount of idle memory.
Dirty idle RAM
          Amount of idle memory which is marked dirty.
Long  Term Locked RAM = xxxxxxxx
          Amount of Long Term Locked memory.
Short Term Locked RAM = xxxxxxxx
          Amount of Short Term Locked memory.
Short & Long Locked RAM = xxxxxxxx
          Amount of memory that is both Long Term and Short Term Locked. This
          memory is not included in the Short and Long values on the previous
          lines. (There are three separate counts of locked memory.)


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Physical addresses


ΓòÉΓòÉΓòÉ 9.3.5. Swapper ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Swapper Display ΓòÉΓòÉΓòÉ

When you select the Swapper option of the System pull-down on the Process
Hierarchy window, information about the contents of the SWAPPER.DAT file will
be displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Swapper Display ΓòÉΓòÉΓòÉ

Analysis of the SWAPPER.DAT file:
There are 1152 disk frames in SWAPPER.DAT (each is 4K bytes).
There are  715 frames used.  (2860K => 2.793M)
There are  437 frames free.  (1748K => 1.707M)
There are 1152 frames total. (4608K => 4.500M)


ΓòÉΓòÉΓòÉ <hidden> Contents of the Swapper Display ΓòÉΓòÉΓòÉ

The information presented on the Swapper display is as follows:

There are iiii disk frames in SWAPPER.DAT (each is 4K bytes).
          The number of 4KB disk frames currently allocated for the SWAPPER.DAT
          file.
There are iiii frames used.
          The number of 4KB disk frames that are currently being used. The
          amount is also given in kilobytes and megabytes of space.
There are iiii frames free.
          The number of 4KB disk frames that are currently free. The amount is
          also given in kilobytes and megabytes of space.
There are iiii frames total.
          The total number of 4KB disk frames that were found. (The sum of the
          previous two lines.) The amount is also given in kilobytes and
          megabytes of space.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o SWAPPER.DAT contents (by page)


ΓòÉΓòÉΓòÉ 9.3.6. General System ΓòÉΓòÉΓòÉ

The General System option contains:

General System Information
          Displays selected general system information.
Device Drivers
          Displays information about all Device Drivers currently loaded.
GDT
          Displays the Global Descriptor Table.
Modules
          Displays information about all modules currently loaded.
System Anchor Segment
          Displays the System Anchor Segment.
Global Info Seg
          Displays the Global Information Segment.
Open Files
          Displays information about the files that are open.
Process List
          Displays a list of all processes that are running.


ΓòÉΓòÉΓòÉ 9.3.6.1. General System Information ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the General System Information Display ΓòÉΓòÉΓòÉ

When you select the General System Information option of the General System
option of the System pull-down on the Process Hierarchy window, information
that THESEUS2 discovers during its initialization is displayed. The values
returned by DosQuerySysInfo are displayed, also.


ΓòÉΓòÉΓòÉ <hidden> Example of the General System Information Display ΓòÉΓòÉΓòÉ

General System Information:
OS/2 version = 2.0, revision = 0.
  This looks like the 2.0 Service Pak.
BIOS date = 01/30/91.
RAM available to OS/2 = 00FA0000 bytes (15.625M).

Following are the values from DosQuerySysInfo:
 1. QSV_MAX_PATH_LENGTH   = 260.
 2. QSV_MAX_TEXT_SESSIONS = 16.
 3. QSV_MAX_PM_SESSIONS   = 16.
 4. QSV_MAX_VDM_SESSIONS  = 4096.
 5. QSV_BOOT_DRIVE        = 3.
 6. QSV_DYN_PRI_VARIATION = 1.
 7. QSV_MAX_WAIT          = 3.
 8. QSV_MIN_SLICE         = 32.
 9. QSV_MAX_SLICE         = 32.
10. QSV_PAGE_SIZE         = 4096.
11. QSV_VERSION_MAJOR     = 20.
12. QSV_VERSION_MINOR     = 0.
13. QSV_VERSION_REVISION  = 0.
14. QSV_MS_COUNT          = 17602280 (4:53:22).
15. QSV_TIME_LOW          = 732892760.
16. QSV_TIME_HIGH         = 0.
17. QSV_TOTPHYSMEM        = 16384000 (16000K -> 15.625M).
18. QSV_TOTRESMEM         = 3780608 (3692K -> 3.605M).
19. QSV_TOTAVAILMEM       = 52428800 (51200K -> 50.000M).
20. QSV_MAXPRMEM          = 267976704 (261696K -> 255.563M).
21. QSV_MAXSHMEM          = 406585344 (397056K -> 387.750M).
22. QSV_TIMER_INTERVAL    = 310.
23. QSV_MAX_COMP_LENGTH   = 255.

System Anchor Segment (SAS) selector = 0070.
Size of PTDA                 = 0824 bytes.
Size of Arena        record  = 0016 bytes.
Size of Object       record  = 0010 bytes.
Size of Context      record  = 0005 bytes.
Size of Page Frame   record  = 000C bytes.
Size of Virtual Page record  = 000A bytes.
har of System Arena Sentinel = 0004.
har of Shared Arena Sentinel = 0005.
har of Page Frame table      = 0019.
har of Virtual Page table    = 001C.


ΓòÉΓòÉΓòÉ <hidden> Contents of the General System Information display ΓòÉΓòÉΓòÉ

The following information appears on the General System Information display:

The first group of values is "discovered" by THESEUS2 during its
initialization:

OS/2 version = i.i, revision = i.
          The major and minor version numbers, followed by the revision.
This looks like...
          Based on several parameters, THESEUS2 determines which level of OS/2
          2.x you are running.
BIOS date = mm/dd/yy.
          The date from the ROM BIOS chip at physical memory location 0xFFFF5.
RAM available to OS/2 = hhhhhhhh bytes (dd.dddM).
          The amount of RAM available to the OS/2 system. This may be less than
          the total RAM in your system by 128KB (.125MB), because, on some
          systems, 128KB is used to copy the BIOS from ROM into RAM. This is
          because ROM is too slow to keep the processor running at full speed.

          Note:  This is presented as a cross-check. If the amount is different
          than what you expect, then OS/2 may not be using memory on a memory
          board installed in your machine.

The second group is retrieved from DosQuerySysInfo. The following QSV_
descriptions come from the on-line documentation of the DosQuerySysInfo system
call.

QSV_MAX_PATH_LENGTH
          Maximum length, in bytes, of a path name.
QSV_MAX_TEXT_SESSIONS
          Maximum number of text sessions.
QSV_MAX_PM_SESSIONS
          Maximum number of PM sessions.
QSV_MAX_VDM_SESSIONS
          Maximum number of DOS sessions.
QSV_BOOT_DRIVE
          Drive from which the system was started (1 means drive A, 2 means
          drive B, and so on).
QSV_DYN_PRI_VARIATION
          Dynamic priority variation flag (0 means absolute priority, 1 means
          dynamic priority).
QSV_MAX_WAIT
          Maximum wait in seconds.
QSV_MIN_SLICE
          Minimum time slice in milliseconds.
QSV_MAX_SLICE
          Maximum time slice in milliseconds.
QSV_PAGE_SIZE
          Memory page size in bytes.  This value is 4096 for the 80386
          processor.
QSV_VERSION_MAJOR
          Major version number.
QSV_VERSION_MINOR
          Minor version number.
QSV_VERSION_REVISION
          Revision letter.
QSV_MS_COUNT
          Value of a 32-bit, free-running millisecond counter. This value is
          zero when the system is started. This value does not reflect the
          "suspended" time for Thinkpads; it is only that time that the
          processor is running. It is also formatted as hours, minutes, and
          seconds.
QSV_TIME_LOW
          Low-order 32 bits of the time in seconds since January 1, 1970 at
          0:00:00.
QSV_TIME_HIGH
          High-order 32 bits of the time in seconds since January 1, 1970 at
          0:00:00.
QSV_TOTPHYSMEM
          Total amount of physical memory in the system.
QSV_TOTRESMEM
          Total amount of resident memory in the system.
QSV_TOTAVAILMEM
          Maximum amount of memory that can be allocated by all processes in
          the system. This number is advisory and is not guaranteed, since
          system conditions change constantly.
QSV_MAXPRMEM
          Maximum amount of memory that this process can allocate in its
          private arena. This number is advisory and is not guaranteed, since
          system conditions change constantly.
QSV_MAXSHMEM
          Maximum amount of memory that this process can allocate in the shared
          arena. This number is advisory and is not guaranteed, since system
          conditions change constantly.
QSV_TIMER_INTERVAL
          Timer interval in tenths of a millisecond.
QSV_MAX_COMP_LENGTH
          Maximum length, in bytes, of one component in a path name.

The last group of values is also "discovered" by THESEUS2 during its
initialization:

System Anchor Segment (SAS) selector = ssss.
          The selector that points to the System Anchor Segment is located from
          the GDT.
Size of PTDA = hhhh bytes.
          The PTDA is different sizes on different systems.
Size of Arena record = hhhh bytes.
          The size of the Arena record, as mapped by a .H file.
Size of Object record = hhhh bytes.
          The size of the Object record, as mapped by a .H file.
Size of Context record = hhhh bytes.
          The size of the Context record, as mapped by a .H file.
Size of Page Frame record = hhhh bytes.
          The size of the Page Frame record, as mapped by a .H file.
Size of Virtual Page record = hhhh bytes.
          The size of the Virtual Page record, as mapped by a .H file.
har of System Arena Sentinel = hhhh.
          The System Arena's Sentinel is not pointed to by anything and must be
          discovered.
har of Shared Arena Sentinel = hhhh.
          The Shared Arena's Sentinel is pointed to from the process's
          sentinel.
har of Page Frame table = hhhh.
          The Page Frame table's har is discovered, based on its address.
har of Virtual Page table = hhhh.
          The Virtual Page Table's har is discovered, based on its owner value.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Handles


ΓòÉΓòÉΓòÉ 9.3.6.2. Device Drivers ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Device Drivers display ΓòÉΓòÉΓòÉ

When you select the Device Drivers option of the General System option of the
System pull-down on the Process Hierarchy window, information about all Device
Drivers currently loaded is displayed. Device Drivers defined in the CONFIG.SYS
file, but which did not load are not shown.


ΓòÉΓòÉΓòÉ <hidden> Example of the Device Drivers Display ΓòÉΓòÉΓòÉ

Device Drivers:
Header addr Limit  Strategy   Limit  Name/Units Attr ...
 0070:08EC  06A4C  0F00:06A0  09A0F  NUL        8084 CHR NUL LVL=OS/2
 0400:0908  06A4C  0F00:06A8  09A0F  CON        8083 CHR SCR KBD LVL=OS/2
 0778:0000  00040  0798:0000  0022A  THESEU2$   8080 CHR LVL=OS/2
 0550:0000  01CD7  0558:0E00  02603         5   2080 IBM LVL=OS/2
 04D0:0000  0010A  04D8:0002  00790  CLOCK$     8188 CHR CLK LVL=3 ??


ΓòÉΓòÉΓòÉ <hidden> Contents of the Device Drivers Display ΓòÉΓòÉΓòÉ

One line is displayed for each Device Driver:

Column          Meaning
Header addr     The virtual address (selector:offset) of the header for the
                Device Driver.
Limit           Limit value for the header segment. (This value is 1 less than
                the size of the segment.)
Strategy        The virtual address (selector:offset) of the Strategy Routine
                of the Device Driver.
Limit           Limit value for the Strategy Routine segment. (This value is 1
                less than the size of the segment.)
Name/Units      For character devices, the name of the device.
                For block devices, the number of units supported by the device.
Attr            The device attributes in hexadecimal notation.
...             The device attributes decoded and presented in English:

   CHR       Bit 15 - The device is a "character" device. Otherwise, it is a
             "block" device.
   IDC       Bit 14 - The device supports "Inter-device Driver Communication".
             If this option is set, the IDC Entry Point must be valid.
   IBM       Bit 13 - The device is non-IBM block format.
   SHR       Bit 12 - The device supports "shared device access checking."
   OPN       Bit 11 - The device supports removable media (block devices) or
             device open/close (character devices).
   LVL       Bits 9-7 - Function level of support.

      PC/DOS    000 - PC/DOS device driver.  (This should never be seen in OS/2
                2.0.)
      OS/2      001 - OS/2 device driver, that does not support DosDevIOCTL2
                packets.
      IOCTL2    010 - OS/2 device driver, that supports DosDevIOCTL2 and
                SHUTDOWN request packets.
      BitStrip  011 - OS/2 device driver, with a Capabilities Bit Strip in the
                header.
      ??        Level was not one of the above. The level value is printed.
   CLK       Bit 3 - The device is the CLOCK device.
   NUL       Bit 2 - The device is the NULL device.
   SCR       Bit 1 - The device is the SCREEN (STDOUT).
   KBD       Bit 0 - The device is the KEYBOARD (STDIN).


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses


ΓòÉΓòÉΓòÉ 9.3.6.3. GDT ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Descriptor Table Entry Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the GDT Display ΓòÉΓòÉΓòÉ

When you select the GDT option of the General System option of the System
pull-down on the Process Hierarchy window, the contents of the GDT is
displayed.

The display generation takes about 3 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the GDT Display ΓòÉΓòÉΓòÉ

Global Descriptor Table:
GDT(0010) BTSS32  Base=FFE42DC8 Limit=00067 DPL=0               P=1 G=0
GDT(0018) Data    Base=FFE42966 Limit=003FF DPL=0 ED=0  W=1 A=1 P=1 G=0 B=0 Alias
GDT(0020) Data    Base=FFEDA000 Limit=003FF DPL=0 ED=0  W=1 A=1 P=1 G=0 B=0 Alias
GDT(0028) LDT     Base=7C6D5000 Limit=0FFFF DPL=0               P=1
┬╖┬╖┬╖
GDT(0038) Data    Base=7CAD5DAC Limit=000F3 DPL=3 ED=0  W=1 A=0 P=1 G=0 B=0
┬╖┬╖┬╖
GDT(0058) Code    Base=00000000 Limit=1BFFF DPL=2 CF=1  R=1 A=1 P=1 G=1 D=1 Alias
┬╖┬╖┬╖
GDT(05B8) CallG   Selector=DFEE Offset=0292 DPL=3 WordCount=03  P=1
┬╖┬╖┬╖
GDT(07A8) CallG32 Selector=07C0 Offset=01A0 DPL=3 WordCount=00  P=1
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the GDT Display ΓòÉΓòÉΓòÉ

One line is displayed for each valid entry in the GDT.

Please see the Descriptor Table Entry for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses


ΓòÉΓòÉΓòÉ 9.3.6.4. Modules ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Modules Display ΓòÉΓòÉΓòÉ

When you select the Modules option of the General System option of the System
pull-down on the Process Hierarchy window, information about all modules
currently loaded is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Modules Display ΓòÉΓòÉΓòÉ

Modules currently loaded:
  MTE @    hob    Name    type  Full Path
FEB63770  0252  THESEUS2   LX   D:\THESEUS2\THESEUS2.EXE
FEB43AC0  026E  VIEWDOC    LX   C:\OS2\VIEWDOC.EXE
FEB3BB34  0220  CMD        LX   C:\OS2\CMD.EXE
FEB60584  01F8  PMEXEC     LX   C:\OS2\PMEXEC.EXE
FEB5ABB0  014B  HARDERR    NE   C:\OS2\SYSTEM\HARDERR.EXE
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the Modules Display ΓòÉΓòÉΓòÉ

One line is displayed for each module currently loaded:

Column          Meaning
MTE @           Linear address of the Module Table Entry (MTE) of the module.
hob             The hob of the MTE.
Name            The name of the module.
type            Specifies the type of module:

   NE  The module was generated by the linker on the OS/2 1.x system. The
       module is all 16-bit.
   LX  The module was generated by the linker on the OS/2 2.x system. The
       module may be any combination of 16 & 32-bit.
Full Path       The fully qualified path name of the file.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Handles


ΓòÉΓòÉΓòÉ 9.3.6.5. System Anchor Segment ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the System Anchor Segment Display ΓòÉΓòÉΓòÉ

When you select the System Anchor Segment option of the General System option
of the System pull-down on the Process Hierarchy window, the contents of the
System Anchor Segment are displayed.

Many of the tables and control block chains used by the OS/2 system have their
anchors in the System Anchor Segment.


ΓòÉΓòÉΓòÉ <hidden> Example of the System Anchor Segment Display ΓòÉΓòÉΓòÉ

System Anchor Segment (SAS), selector = 0070
tables_area @ 0016
                  GDT      = 0008 (selector) - ERROR
                  LDT      = 0000 (selector) - ERROR
                  IDT      = 0018 (selector)
                  GDT pool = 0100 (starting selector)
flat_sel    = 0158 (selector) (this is for the Kernel Data)
config_area @ 001E
                  Config table @ 09D6 (offset into SAS) (?)
dd_area     @ 0020
                  bimodal chain          @ 094F (offset into SAS)
                  real    chain          @ 0000 (offset into SAS)
                  Drive Parameter Block  = 04E8 (selector) (?)
                  ABIOS Common Data Area = 0430 (selector) (?)
                  ABIOS Common Data Area = 6A00 (segment) (?)
                  FSC Common Data Area   = 00C8 (selector) (?)
vm_area     @ 002C
                  arena records      @ FEF29020 (flat)
                  object records     @ FF08A020 (flat)
                  context records    @ FFEC8020 (flat)
                  kernel MTE records @ FFF2F46C (flat)
                  linked MTE list    @ FFF2E9A8 (flat)
                  page frame table   @ FFE20000 (flat)
                  page range table   @ FFE1F000 (flat)
                  swap frame table   @ 7C7C3144 (flat), length = 512
                  idle head          @ FFE2078C (flat) (within 'page frame table')
                  free head          @ FFE20780 (flat) (within 'page frame table')
                  heap array         @ 00000000 (flat) (?)
task_area   @ 0058
                  PTDA           = 0030 (selector)
                  Process tree   @ FFE518DC (flat)
                  Thread array   @ FFE318B9 (flat) (array of TCB linears)
                  Current Thread @ FFE2B802 -> 002E
                  Thread Count   @ FFE2B806 -> 0031
ras_area    @ 006A
                  System Trace Data area = 0000 (selector) (?)
                  System Trace Data area = 0000 (segment) (?)
                  Trace enable table     @ 07CC (offset into SAS) (?)
file_area   @ 0070
                  Master File Table           = FEB30FC0 (flat) (?)
                  System File Table           = 00C0 (selector)
                  Volume Parameter Block      = 03E8 (selector) (?)
                  Current Directory Structure = 0608 (selector)
                  Buffer Segment              = 00A8 (selector) (?)
info_area   @ 007C
                  Global Info Segment       = 0428 (selector)
                  Local Info Segment        = 03B8 (selector)
                  3xBox Info Segment        = FFFFFFFF (?)
                  Codepage Data Info Block  = 061B (selector)


ΓòÉΓòÉΓòÉ <hidden> Contents of the System Anchor Segment Display ΓòÉΓòÉΓòÉ

There are some fields within the System Anchor Segment (SAS) which I have been
unable to verify. They are all marked with a (?) on the display and are also
explicitly indicated in the descriptions below.

The fields of the System Anchor Segment are displayed as follows:

System Anchor Segment (SAS), selector = ssss
          The GDT selector that points to the SAS.

tables_area @ oooo
          The offset within the SAS that contain selectors to certain system
          tables.
GDT = ssss (selector) - ERROR
          The selector of the Global Descriptor Table (GDT). The value
          displayed is incorrect.
LDT = ssss (selector) - ERROR
          The selector of the Local Descriptor Table (LDT). The value displayed
          is incorrect.
IDT = ssss (selector)
          The selector of the Interrupt Descriptor Table (IDT).
GDT pool = ssss (starting selector)
          Starting selector of a pool of GDT selectors used by the OS/2 kernel.

flat_sel = ssss (selector) (this is for the Kernel Data)
          Selector used by the kernel as the flat addressing selector for its
          data.

config_area @ oooo
          The offset within the SAS that contains the configuration pointers.
Config table @ oooo (offset into SAS) (?)
          The Configuration table itself is at this offset within the SAS.
          (This is unverified.)

dd_area @ oooo
          The offset within the SAS that contains the information about Device
          Drivers.
bimodal chain @ oooo (offset into SAS)
          The offset within the SAS that contains the start of the chain of
          "bimodal" device drivers. (This is the device header for the NUL
          device.)
real chain @ oooo (offset into SAS)
          The offset within the SAS that contains the start of the chain of
          "real mode" device drivers. (This appears to be a hold over from
          1.x.)
Drive Parameter Block = ssss (selector) (?)
          The segment with the Driver Parameter Block information. (This is
          unverified.)
ABIOS Common Data Area = ssss (selector) (?)
          The segment with the ABIOS Common Data Area. This selector is valid
          for Protect mode. (This is unverified.)
ABIOS Common Data Area = ssss (segment) (?)
          The segment with the ABIOS Common Data Area. This segment is valid
          for Real mode. (This is unverified.)
FSC Common Data Area = ssss (selector) (?)
          The segment with the File System Control (FSC) Common Data Area.
          (This is unverified.)

vm_area @ oooo
          The offset within the SAS that contains the information about Memory
          Management.
arena records @ llllllll (flat)
          The linear address of the Arena Table.
object records @ llllllll (flat)
          The linear address of the Object Table.
context records @ llllllll (flat)
          The linear address of the Context Table.
kernel MTE records @ llllllll (flat)
          The linear address of the last MTE which is a DLL. This points to
          DOSCALLS.DLL.
linked MTE list @ llllllll (flat)
          The linear address of the linear address of the first MTE which is a
          DLL.
page frame table @ llllllll (flat)
          The linear address of the Page Frame Table.
page range table @ llllllll (flat)
          The linear address of the Page Range Table.
swap frame table @ llllllll (flat), length = iii
          The linear address of the table of bits that indicate the
          free/allocated state of the SWAPPER.DAT page frames. The length is
          given as the number of bits in the table.
idle head @ llllllll (flat) (within 'page frame table')
          The head of the "idle chain" of pages. This head is within the Page
          Frame Table and points to an entry that has no physical memory
          associated with it.
free head @ llllllll (flat) (within 'page frame table')
          The head of the "free chain" of pages. This head is within the Page
          Frame Table and points to an entry that has no physical memory
          associated with it.
heap array @ llllllll (flat) (?)
          This value is always zero.

task_area @ oooo
          The offset within the SAS that contains the information about
          processes and threads.
PTDA = ssss (selector)
          The selector points to the active process's PTDA. This segment is
          "sparse" and contains the PTDA, TCB and TSD.
Process tree @ llllllll (flat)
          The linear address of the top process (sysinit) in the process tree.
Thread array @ llllllll (flat) (array of TCB linears)
          The linear address of the Thread Table. There is one entry for each
          thread defined in the system. The index into this table is the thread
          number.
Current Thread @ llllllll -> hhhh
          The linear address of the word containing the current thread number.
          This is followed by the actual value. This will always be a thread in
          THESEUS2.
Thread Count @ llllllll -> hhhh
          The linear address of the word containing the actual number of
          threads in the system. This is not the maximum number of threads.

ras_area @ oooo
          The offset within the SAS that contains the information about trace.
System Trace Data area = ssss (selector)
          The selector of the System Trace buffer. (This is unverified.)
System Trace Data area = ssss (segment) (?)
          The selector of the System Trace buffer. (This is unverified.)
Trace enable table @ oooo (offset into SAS) (?)
          ??? (This is unverified.)

file_area @ oooo
          The offset within the SAS that contains the information about File
          System.
Master File Table = llllllll (flat) (?)
          Linear address of the Master File Table. (This is unverified.)
System File Table = ssss (selector)
          This is the selector of the segment containing the System File Table
          selectors
Volume Parameter Block = ssss (selector) (?)
          ??? (This is unverified.)
Current Directory Structure = ssss (selector)
          This is the selector of the segment containing the current directory.
Buffer Segment = ssss (selector) (?)

info_area @ oooo
          The offset within the SAS that contains the information about Info
          Segments.
Global Info Segment = ssss (selector)
          The selector of the Global Information Segment. This selector is for
          "ring 0" and is not usable by an application program.
Local Info Segment = ssss (selector)
          The selector of the Local Information Segment. This selector is for
          "ring 0" and is not usable by an application program.
3xBox Info Segment = hhhhhhhh (?)
          ??? (This is unverified.)
Codepage Data Info Block = ssss (selector)
          This selector points to the code page table currently loaded.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses

o Linear addresses


ΓòÉΓòÉΓòÉ 9.3.6.6. Global Info Seg ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Global Info Seg Display ΓòÉΓòÉΓòÉ

When you select the Global Info Seg option of the General System option of the
System pull-down on the Process Hierarchy window, the contents of the Global
Information Segment is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Global Info Seg Display ΓòÉΓòÉΓòÉ

Global Info Seg:
Time since 1/1/1970  = 289D662A (hex secs)
Time since ipl       = 0151A406 (hex msecs)
Current time         = 14:52:26.53
Time zone            = undefined
Timer interval       = 31.0 (msec)
Date                 = 8/5/1991
Day of week          = 1 (Monday)
OS/2 version         = 20.0, revision = ' '
Current screen group = 1
Maximum number of screen groups = 16
HugeShift            = 3
ProtectOnly          = 0 (No)
Current PID          = 0005
Dynamic Scheduling   = 1 (Dynamic)
MaxWait              = 3 (sec)
Min time slice       = 32, Max time slice = 32 (msec)
Boot drive           = 3 (C:)
Trace control flags:
   0-15: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  16-31: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Max VIO windowable sessions = 16
Max PM  windowable sessions = 16
Error logging status = 0
MMPH selector        = 0000, linear = 00000000


ΓòÉΓòÉΓòÉ <hidden> Contents of the Global Info Seg Display ΓòÉΓòÉΓòÉ

The following information is taken from the Control Program Programming
Reference, version 1.2.

The information presented on the Global Info Seg display is as follows:

Time since 1/1/1970 = hhhhhhhh (hex secs)
          Time in seconds since January 1, 1970.
Time since ipl = hhhhhhhh (hex msecs)
          Time in milliseconds.
Current time = hh:mm:ss.hh
          Current time as hours:minutes:seconds.hundredths.
Time zone = undefined
          Minutes from UTC; if the value is hex FFFF, the time zone is
          undefined.
Timer interval = dd.d (msec)
          Timer interval in milliseconds.
Date = m/d/yyyy
          Date as month/day/year.
Day of week = i (aaaaaa)
          Day of the week. The number is given, followed by the day in ASCII.
OS/2 version = vv.v, revision = 'c'
          OS/2 version, given as major version then minor version. The revision
          is a letter.
Current screen group = d
          Current foreground full-screen session.
Maximum number of screen groups = dd
          Maximum number of full-screen sessions, in decimal notation.
HugeShift = d
          Shift count for huge segments.
ProtectOnly = d (aa)
          Protect-mode-only indicator. The number is given, followed by yes or
          no. This is controlled by the PROTECTONLY command in the CONFIG.SYS
          file.
Current PID = hhhh
          Process ID of the current foreground process.
Dynamic Scheduling = d (aaaaaaa)
          Dynamic variation flag. The number is given, followed by Absolute or
          Dynamic. This is controlled by the PRIORITY command in the CONFIG.SYS
          file.
MaxWait = d (sec)
          Maximum wait in seconds. This is controlled by the MAXWAIT command in
          the CONFIG.SYS file.
Min time slice = dd, Max time slice = dd (msec)
          Minimum and maximum time-slice values. These are controlled by the
          TIMESLICE command in the CONFIG.SYS file.
Boot drive = d (c:)
          Drive from which the system was booted. The number is given, followed
          by the drive letter and a colon.
Trace control flags:
          The flags used to control what trace events are being generated.
Max VIO windowable sessions = dd
          Maximum number of VIO windowable sessions.
Max PM  windowable sessions = dd
          Maximum number of Presentation Manager sessions.
Error logging status = d
          Error-logging status value.
MMPH selector = ssss, linear = llllllll
          The selector and linear address to be used when doing MMPH hooks.
          MMPH is the OS/2 2.x name given to the same type hooks designated as
          MMIO in the OS/2 1.x system.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses

o Linear addresses


ΓòÉΓòÉΓòÉ 9.3.6.7. Open Files ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Open Files Display ΓòÉΓòÉΓòÉ

When you select the Open Files option of the General System option of the
System pull-down on the Process Hierarchy window, information about all files
that are open is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Open Files Display ΓòÉΓòÉΓòÉ

Open Files:
System File Table - (table of selectors) selector = 00C0
System File Table - Selector = 03F8
            Ref  System
 Address  Count  Handle   PID   --Chain--  --MFT---  name
03F8:0008     1   0000   0002              FEB563C8  D:\EA DATA. SF
03F8:0087     1   0001  System             FEB5632C  C:\OS2\DLL\PMSHAPIM.DLL
03F8:0106     1   0002  System             FEB562E4  C:\OS2\DLL\PMSDMRI.DLL
┬╖┬╖┬╖
03F8:31A4     1   0064  System             FEB619A4  C:\THESEUS2\THESEUS2.EXE
03F8:3223     1   0065   0017              FEB6172C  \DEV\THESEU2$
03F8:32A2     1   0066  System             FEB6160C  C:\THESEUS2\THESEUSR.DLL

There were 99 open files found.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Open Files Display ΓòÉΓòÉΓòÉ

The information presented on the Open Files display is as follows:

System File Table - (table of selectors) selector = ssss
          This is the selector of the table of selectors which make up the
          System File Table (SFT).
System File Table - Selector = ssss
          This is the selector of the segment of the SFT which follows.

One line is displayed for each file that is open:

Column            Meaning
Address           Virtual address of the SFT entry for this file.
Ref Count         Number of processes that reference this file.
System Handle     The system wide handle for this file.
PID               Process ID of the process that opened this file This has
                  `System' if it was opened by the system instead of a process.
Chain             The virtual address of an SFT which is opened for the same
                  file.
MFT               The linear address of the Master File Table (MFT) entry for
                  this file.
name              The name of the file.

This is followed by a line which gives the total number of SFT entries which
are used.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses

o System File Table entries


ΓòÉΓòÉΓòÉ 9.3.6.8. Process List ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Process List Display ΓòÉΓòÉΓòÉ

When you select the Process List option of the General System option of the
System pull-down on the Process Hierarchy window, information about all
processes currently running is displayed. Also shown are the total number of
threads in the system and the PID of the current selected process.


ΓòÉΓòÉΓòÉ <hidden> Example of the Process List Display ΓòÉΓòÉΓòÉ

       PTDA       PTDA      # of   Parent
 PID    hob     Linear   Threads      PID   Name
0001   006E   FFE537DC         5     0000   sysinit
0002   0090   7D3D5020        20     0001   PMSHL32
0003   018C   7D3D5844         3     0002   HARDERR
0005   0245   7D3D688C        11     0002   PMSHL32
0006   02CA   7D3D6068         3     0002   PULSE
0007   02F7   7D3D70B0         1     0002   VDM
0008   030D   7D3D78D4         1     0002   CMD
011C   033D   7D3DA188         1     0002   THESEUS2
45 threads were found.
Current PID qualifier = 0000.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Process List Display ΓòÉΓòÉΓòÉ

One line is displayed for each process:

Column          Meaning
PID             Process ID of the process.
PTDA hob        Hob of the PTDA.
PTDA Linear     The linear address of the PTDA.
# of Threads    The number of threads in the process.
Parent PID      PID of the parent process.
Name            Name of the process.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing


ΓòÉΓòÉΓòÉ 9.3.7. Kernel Information ΓòÉΓòÉΓòÉ

The Kernel Information option contains:

Kernel Memory Usage
          First determines and then displays the amount of memory consumed by
          the Operating System.
System Object Summary
          Displays the System Object Summary.
System Arena Table
          Displays the System Arena Table.
System Page Table
          Displays the System Page Table.
Page Frame Table
          Displays the Page Frame Table.


ΓòÉΓòÉΓòÉ 9.3.7.1. Kernel Memory Usage ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Kernel Memory Usage Display ΓòÉΓòÉΓòÉ

When you select the Kernel Memory Usage option of the Kernel Information option
of the System pull-down on the Process Hierarchy window, information about
kernel memory usage is computed and displayed. The memory is accumulated by
system owner code, sorted by system owner code.

The display generation takes about 2 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the Kernel Memory Usage Display ΓòÉΓòÉΓòÉ

Memory Usage for System Memory (memory in the 'System' Arena):
allocated committed   present  resident  owner
 00010000  00002000  00002000  00002000  FF31 (Named pipe NP segment)
 00010000  00001000  00001000  00001000  FF33 (DD strat2 request packets)
 00001000  00001000  00001000  00001000  FF37 (ROM data)
 00010000  00001000  00001000  00001000  FF40 (DD strat1 request packets)
 00020000  00020000  00020000  00020000  FF41 (Allocated via DevHlp AllocPhys)
 00400000  00002000  00002000  00002000  FF43 (Resident R/W 1Meg mem heap owner)
 00100000  00002000  00002000  00002000  FF44 (Resident R/W 1Meg mem heap owner)
 00010000  00001000  00001000  00001000  FF47 (record lock record owner)
 --------  --------  --------  --------
 00561000  0002A000  0002A000  0002A000  Subtotal for 'Miscellaneous' group 1
┬╖┬╖┬╖
allocated committed   present  resident  Totals
 --------  --------  --------  --------
 8383E000  005B1000  00533000  003BE000  Total (in bytes)
  2154744      5828      5324      3832  Total (in Kbytes)
 2104.242     5.691     5.199     3.742  Total (in Mbytes)


ΓòÉΓòÉΓòÉ <hidden> Contents of the Kernel Memory Usage Display ΓòÉΓòÉΓòÉ

One line is displayed for each system owner with allocated memory:

Column        Meaning
allocated     The total amount of linear address space allocated.
committed     The amount of committed memory for this owner.
present       The actual amount of RAM which is present for the owner. This is
              real RAM.
resident      The amount of resident memory for this owner.
owner         The system owner, presented as a hexadecimal value followed by a
              short ASCII name.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory Management Control Blocks

o Detail for System Owner


ΓòÉΓòÉΓòÉ <hidden> Kernel Memory Usage Algorithm ΓòÉΓòÉΓòÉ

 1. For each arena record in the system arena:

    a. Determine the amount of linear space allocated by looking at the page
       count in the arena record.
    b. Check the Page Directory and Page Tables to determine how many pages
       within the linear address range represented by this entry are committed
       and how many are present.

 2. Display the results, sorted by system owner value.


ΓòÉΓòÉΓòÉ 9.3.7.2. Object Summary ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Object Summary Display ΓòÉΓòÉΓòÉ

The Object Summary display can be selected in several ways:

o When you select the System Object Summary option of the Kernel Information
  option of the System pull-down on the Process Hierarchy window, a summary of
  all the memory objects defined in the system arena is displayed.

o When you select the Private Object Summary option of the Process pull-down on
  the Process Hierarchy window, a summary of all the memory objects defined in
  the private arena for the selected process is displayed.

o When you select the Shared Object Summary option of the Process pull-down on
  the Process Hierarchy window, a summary of all the memory objects defined in
  the shared arena for the selected process is displayed.

o When you select the hyperblock link from the bytes allocated column of the
  Process Memory Utilization display, a summary of all the memory objects
  defining that memory type is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of an Object Summary Display ΓòÉΓòÉΓòÉ

  Object  Allocated  Committed   Present   Swapped
 address     memory     memory    memory    memory  Description
7BC00000   00400000   00112000  00004000  00000000  'VDM Alias' (decoded owner from object record)
7C2D5000   00010000   00003000  00003000  00000000  'SEL LDT' (decoded owner from object record)
┬╖┬╖┬╖
FFF4C000   0000F000   0000F000  0000F000  00000000  'os2krnl load image' (decoded owner from object record)
FFF5B000   00065000   0005D000  00053000  00000000  'os2krnl load image' (decoded owner from object record)
           --------   --------  --------  --------
Totals:    83AC5000   007D8000  005DF000  00000000  (in bytes)
            2157332       8032      6012         0  (in Kbytes)
           2106.770      7.844     5.872     0.000  (in Mbytes)
Number of objects = 207.


ΓòÉΓòÉΓòÉ <hidden> Contents of an Object Summary Display ΓòÉΓòÉΓòÉ

One line is displayed for each memory object in the selected arena or area:

Column                  Meaning
Object address          Linear address of the memory object.
Allocated memory        Amount of allocated memory (in bytes).
Committed memory        Amount of committed memory (in bytes).
Present memory          Amount of RAM in use (in bytes).
Swapped memory          Amount of memory (in bytes) that has been written to
                        the swap file.
Description             Description in English of the object.

Totals of all the "amount" columns are given in hexadecimal bytes, decimal
kilobytes, and decimal megabytes. The number of objects found is also
indicated.

Note:  It is possible for a page to be both present and swapped. The following
is one way this can occur:

 1. A read/write page is written into (becomes "dirty").
 2. The page is not used for a long time and is swapped out to disk.
 3. When the page is referenced, it is brought back into RAM. Until the RAM
    page is written into, both pages are valid. If the RAM page gets aged, it
    will not need to be written to disk, because the copy there is still valid.
    Once the RAM page is written into, the swapped page is discarded.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Memory Management Control Blocks


ΓòÉΓòÉΓòÉ 9.3.7.3. System Arena Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Arena Record Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the System Arena Table display ΓòÉΓòÉΓòÉ

When you select the System Arena Table option of the Kernel Information option
of the System pull-down on the Process Hierarchy window, the contents of the
System Arena is displayed.

The display generation takes about 2 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the System Arena Table Display ΓòÉΓòÉΓòÉ

System Arena Table:
 har    pages   linear flg next prev link hash hob  hal  sel  / Decoded flags
0004 00000000 60000000 003 01E1 0010 0000 0000 Sentinel, max pages=000FFFC0
01E1 00000400 7C000000 001 020E 0004 0000 007A 022D 0000 0000 /
020E 00000010 7C705000 121 01D5 01E1 0000 0000 0238 0000 0000 / Write Read
┬╖┬╖┬╖
0006 00000003 FFF36000 009 000F 000E 0000 0000 0007 0000 0100 / Mapped
000F 00000009 FFF39000 001 0010 0006 0000 0000 0010 0000 0000 /
0010 0000007E FFF42000 001 0004 000F 0000 0000 0011 0000 0000 /


ΓòÉΓòÉΓòÉ <hidden> Contents of the System Arena Table Display ΓòÉΓòÉΓòÉ

One line is displayed for each entry in the system arena.

Please see the arena record for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Handles


ΓòÉΓòÉΓòÉ 9.3.7.4. System Page Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Page Table Entry Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the System Page Table Display ΓòÉΓòÉΓòÉ

When you select the System Page Table option of the Kernel Information option
of the System pull-down on the Process Hierarchy window, the contents of the
System Page Table is displayed.

The display generation takes about 8 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the System Page Table Display ΓòÉΓòÉΓòÉ

System Page Table:
*Linear=7C000000 Physical=0065D000 D=1 A=1 User  R/W P=1 Resident
 Linear=7C000000 Physical=0002F000 D=1 A=1 User  R/W P=1
 Linear=7C001000 Physical=00183000 D=1 A=1 User  R/W P=1
┬╖┬╖┬╖
 Linear=7C0F4000 FrameId=000F4     D=0 A=0 User  R/W P=0 UVirt
 Linear=7C0F5000 Physical=000F5000 D=0 A=1 User  R/W P=1 UVirt
 Linear=7C0F6000 FrameId=000F6     D=0 A=0 User  R/W P=0 UVirt
┬╖┬╖┬╖
 Linear=7C852000 Physical=00668000 D=0 A=1 Super R/O P=1 Resident
 Linear=7C875000 Physical=005D3000 D=1 A=1 User  R/W P=1
 Linear=7C876000 FrameId=00001     D=0 A=0 User  R/W P=0
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the System Page Table Display ΓòÉΓòÉΓòÉ

One line is displayed for each valid entry in the System Page Table.

Please see the Page Table Entry for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Physical addresses


ΓòÉΓòÉΓòÉ 9.3.7.5. Page Frame Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Page Frame Table Display ΓòÉΓòÉΓòÉ

When you select the Page Frame Table option of the Kernel Information option of
the System pull-down on the Process Hierarchy window, the contents of the Page
Frame Table is displayed.

The display generation takes about 6 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the Page Frame Table Display ΓòÉΓòÉΓòÉ

Page Frame table:
 Free head = 000A0000, flink = 005BC, blink = 00409
 Idle head = 000A1000, flink = 0065F, blink = 0065F
                        ---lock---
physical    vp   pteCnt long short flink blink block flags
00000000 FF421000 0001  0000 0000              00000 0000
00001000 FF42105A 0001  0000 0000              00000 0000
00002000 FF421064 0001  0000 0000              00000 0000
┬╖┬╖┬╖
0009F000 FF40B2BC 0002  0000 0000              00000 0000

The Page Range Table indicates a break in the physical memory.

00100000 FF40B2C6 0001  0000 0000              00000 0000
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the Page Frame Table Display ΓòÉΓòÉΓòÉ

The heads of the free and idle lists are shown. They consist of only a flink
and blink fields.

Breaks in the contiguous range of pages are noted with the sentence, "The Page
Range Table indicates a break in the physical memory."

One line is displayed for each entry in the table:

Column          Meaning
physical        The physical address for the page on this line.
vp              The linear address of the Virtual Page Table entry for this
                page.
pteCnt          The number of PTEs that refer to this page as being present.
lock long       The number of long term locks outstanding for this page.
lock short      The number of short term locks outstanding for this page.
flink           Forward link.  Used when a page is on the free or idle list.
blink           Backward link.  Used when a page is on the free or idle list.
block           Pager disk frame or Loader Block number
flags           Flags indicating the status of the page. They are shown as hex
                and then decoded into ASCII:

   fast        Page is in fast memory.
   busy        Page is busy.
   free        Page is on the free chain.
   reserved?   Reserved bit.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing


ΓòÉΓòÉΓòÉ 9.4. Process ΓòÉΓòÉΓòÉ

The Process pull-down contains displays which are applicable to the selected
process.

For information on selecting a process, see Selecting a Process.

Functions available are:

Working Set
          Displays the working set of memory for the process.
Memory Utilization
          Displays details of memory usage for the process.
Memory Leak Detection
          Displays the number of pages of memory that each object is
          accumulating.
General Process Information
          Displays general information about the process.
Per Task Data Area (PTDA)
          Displays the PTDA.
LDT
          Displays the LDT.
Page Table
          Displays the process unique Page Table.
Private Object Summary
          Displays a summary of the private arena memory objects.
Shared Object Summary
          Displays a summary of the shared arena memory objects.
Private Arena Table
          Displays the process unique arena table.
Shared Arena Table
          Displays the shared arena, in the process' context.


ΓòÉΓòÉΓòÉ 9.4.1. Working Set ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Algorithm

Illustration

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Working Set Display ΓòÉΓòÉΓòÉ

When you select the Working Set option of the Process pull-down on the Process
Hierarchy window, memory working set of the selected process is computed and
displayed.

There are optional values which can be shown in realtime.


ΓòÉΓòÉΓòÉ <hidden> Example of the Working Set Display ΓòÉΓòÉΓòÉ

Working Set for the Process with PID = 0100, name = 'THESEUS2':
Use the 'Functions' pull-down to start and stop the data collection.
Collection started: interval = 5, Working Set is 3 intervals.
current time ------ Process -------   ------ System DLL -----
hh:mm:ss.tt     now      ws   acc'd       now      ws   acc'd
16:54:53.16   0.180M  0.180M  0.180M    0.406M  0.406M  0.406M
16:54:58.00   0.184M  0.195M  0.195M    0.379M  0.438M  0.438M
16:55:03.03   0.184M  0.195M  0.195M    0.379M  0.438M  0.438M
16:55:08.00   0.180M  0.188M  0.195M    0.414M  0.414M  0.438M
16:55:13.00   0.188M  0.195M  0.199M    0.449M  0.449M  0.473M
16:55:18.03   0.184M  0.195M  0.199M    0.379M  0.449M  0.473M
16:55:23.00   0.176M  0.195M  0.199M    0.379M  0.449M  0.473M
16:55:28.00   0.176M  0.184M  0.199M    0.379M  0.379M  0.473M
16:55:33.03   0.176M  0.176M  0.199M    0.379M  0.379M  0.473M
16:55:38.00   0.176M  0.176M  0.199M    0.375M  0.379M  0.473M

10 samples collected.
                                 Process      DLL    Total
Absolute minimum amount of memory: 0.188M   0.449M   0.637M
Recommended amount of memory:      0.195M   0.449M   0.645M
Total amount of accessed memory:   0.199M   0.473M   0.672M


ΓòÉΓòÉΓòÉ <hidden> Contents of the Working Set Display ΓòÉΓòÉΓòÉ

Three values are computed for each of two areas during each data collection
cycle. The data can be presented in real-time.

The values are:

now         The number of pages referenced in the current interval.

ws          The working set. This is the number of pages referenced in the past
            n intervals.

acc'd       The total number of pages accessed since the start of the
            collection run.

The areas are:

Process        The pages that are: in the private arena, DLL instance data
               pages, non-system DLLs, and system pages used by this process.

System DLL     The pages that are in system DLLs.

The totals are computed on each data collection cycle, but not displayed due to
lack of space in the window.

When the Stop option is selected, the following is presented:

ii samples collected.
          The number of samples collected is reported (in decimal).

The following are reported for Private, System DLL, and Total:

Absolute minimum number of pages
          The maximum value from the now column. This is the number of pages
          absolutely required to run the application without "thrashing"
          memory.
Recommended amount of memory
          The maximum value from the ws column. This is the recommended amount
          of memory for the application to run with minimum impact on paging.
Total amount of accessed memory
          The maximum value from the accessed column. This is the number of
          pages required to run the application with no paging activity.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory Management Control Blocks

o Memory Analysis Techniques

o Detail of Working Set (by Page)

o Detail of Working Set (by Object)


ΓòÉΓòÉΓòÉ <hidden> Memory Working Set Algorithm ΓòÉΓòÉΓòÉ

To compute the working set for a particular OS/2 process, you need to know:

o Which pages have been referenced
o Whether or not a particular page "belongs" to the specified process
o When the pages were touched.

The algorithm is:

 1. The accessed flags are cleared from the Page Tables of the selected
    process.

 2. A timer is started, and on each timer tick:

    a. The pages which have been accessed are noted.
    b. The accessed flags are cleared.
    c. For each newly accessed page, determine its owning memory object.
    d. Classify the object (and, therefore, the page) by type:

      o Private
      o System DLL
      o System.

    e. The number of pages which have been accessed anytime within the
       specified number of intervals is counted.
    f. Generate summary information for this interval.
    g. Display the interval information, if requested.

 3. When the Stop option is selected:

    a. A final data collection cycle is performed.
    b. Summary numbers for the entire run are generated. They are:

      Absolute minimum number of pages
                The maximum of all the now entries.
      Recommended number of pages
                The maximum of all the ws entries.
      Total number of accessed pages
                The maximum of all the accessed entries.

    c. The results are displayed.

Note:  Even though the "infosegs" are in the shared arena, they are counted as
system pages. They are, in fact, shared pages.


ΓòÉΓòÉΓòÉ 9.4.2. Memory Utilization ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Memory Utilization Display ΓòÉΓòÉΓòÉ

When you select the Memory Utilization option of the Process pull-down on the
Process Hierarchy window, information about the memory used by the selected
process is computed and displayed.

The display generation takes about 3 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the Memory Utilization Display ΓòÉΓòÉΓòÉ

Memory Utilization for Process with PID = 005C, name = 'THESEUS2':
    bytes      bytes    number  bytes      bytes
allocated  committed   present   each    present  description
 0000071C   0000071C         1   071C   0000071C  PTDA
 000001AC   000001AC         1   01AC   000001AC  TCB
 00001000   00001000         1   1000   00001000  TSD
 00010000   00003000         3   1000   00003000  LDT
 00000200   00000200         1   0200   00000200  Process Page Directory
 00080000   0000B000        11   1000   0000B000  Page Tables
 01110000   00471000       547   1000   00223000  Accessible Shared memory
 001A0000   00031000        14   1000   0000E000  Originated Shared memory
 00B40000   00072000        83   1000   00053000  Private memory
 --------   --------                    --------
 00091AC8   0000FAC8                    0000FAC8  Total System
 001A0000   00031000                    0000E000  Total Shared originated
 00B40000   00072000                    00053000  Total Private
 --------   --------                    --------
 00D71AC8   000B2AC8                    00070AC8  Total RAM for the Process
    13767        715                         451  (in Kbytes)
   13.445      0.698                       0.441  (in Mbytes)

The following values are taken directly from the PTDA:
Allocated PTEs: private = 00072, shared = 00471, total = 004E3.
Present   PTEs: private = 00054, shared = 00223, total = 00277.
Resident  PTEs: private = 00000, shared = 00000, total = 00000.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Memory Utilization Display ΓòÉΓòÉΓòÉ

One line is displayed for each type of memory associated with a process:

Column              Meaning
bytes allocated     The amount of linear address space allocated for the memory
                    type on this line.
bytes committed     The amount of committed memory for the memory type on this
                    line
number present      The number of instances of the memory type on this line
                    present in RAM for this process. (This column is in decimal
                    notation; all others are hexadecimal.)
bytes each          The size of one of the memory types on this line.
bytes present       The actual amount of real RAM used by the memory type on
                    this line.
description         The name of the memory type reported on this line.

The "Accessible Shared memory" is not added into the summaries. It is the total
amount of shared memory which is accessible by the process. It includes:
originated shared memory, DLLs used by the process, memory given to it by
another process (using DosGiveSharedMem), and memory gotten by it (using
DosGetSharedMem).

Summaries are provided and shown as hex bytes:

Total System
          The system RAM consists of the lines for PTDA, TCB, TSD, LDT, Process
          Page Directory, and Page Tables.
Total Shared originated
          The shared memory that was not originated by this process is ignored.
Total Private
          This entry includes the .EXE file and all privately allocated memory.
          This memory is computed as if there were no other processes in the
          system. So, if there are multiple copies of a particular program
          running, each of them would show the .EXE file as being consumed by
          that process.
Total RAM for the Process
          The total of the above three values, presented in bytes, kilobytes
          and megabytes.

The last set of 3 lines are values taken directly from the PTDA. They are
included here to assist in the validation of PerfView data. The values are:

Allocated PTEs      The number of PTEs allocated in the Process Page Directory.
                    This would represent the number of pages which are
                    committed.
Present PTEs        The number of PTEs having pages that are present.
Resident PTEs       The number of PTEs having pages that are either locked or
                    resident.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory Management Control Blocks

o Memory Analysis Using THESEUS2

o Object Summary


ΓòÉΓòÉΓòÉ <hidden> Memory Utilization Algorithm ΓòÉΓòÉΓòÉ

 1. There is one PTDA for the process. Its size is determined during THESEUS2
    initialization.

 2. There is one TCB for each thread being used by the process. Its size is
    determined by a mapping structure.

 3. There is one TSD for each thread being used by the process. Its allocated
    size is 4KB. The number of pages actually in use is counted.

 4. There is one LDT for the process. Its allocated size is 64KB. The number of
    pages actually in use is counted.

 5. There is one Process Page Directory for the process. Its size is 512 bytes.

 6. There is a group of Page Tables for the process. The number of Page Tables
    in use is determined by looking at the Process Page Directory and then
    determining what pages are present.

 7. For each arena record in the private arena:

    a. Determine the number of allocated pages.
    b. Count the number of pages actually in use.

 8. For each arena record in the shared arena for which the process has access
    to the memory object (by looking at the context records):

    a. Determine the number of allocated pages.
    b. Count the number of pages actually in use.

 9. For each arena record in the shared arena for which the process was the
    originator, (by looking at the context records):

    a. Determine the number of allocated pages.
    b. Count the number of pages actually in use.


ΓòÉΓòÉΓòÉ 9.4.3. Memory Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

When you select the Memory Leak Detection option of the Process pull-down on
the Process Hierarchy window, information about memory accumulation for each
object in the process is computed and shown.

This can be done either on a periodic basis or under user control. See Related
Topics for the references for specifying control.


ΓòÉΓòÉΓòÉ <hidden> Example of the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

Memory leak detection for Process with PID = 0039, name = THESEUS2:
< End of THESEUS2 (v 2.0s) output @ 10:42:49 on 8/5/1993 >
Use the 'Function' pull-down to start and stop the data collection.
Leak data captured.
Periodic update started with interval of 10 seconds.
Previous sample will be used as the base.
< End of THESEUS2 (v 2.0s) output @ 10:43:06 on 8/5/1993 >
Allocated   Committed   Actual    har     Address   P/S   Description
       +0          +1       +1   0342    01100000   Pvt   THESEUS2 allocated it
       +0          +0       +1   0343    01130000   Pvt   THESEUS2 allocated it
< End of THESEUS2 (v 2.0s) output @ 10:43:16 on 8/5/1993 >
Allocated   Committed   Actual    har     Address   P/S   Description
       +0          +1       +1   0343    01130000   Pvt   THESEUS2 allocated it
      +96          +1       +1   034B   +019B0000   Pvt   THESEUS2 allocated it
     +688          +1       +1   034C   +01A10000   Pvt   THESEUS2 allocated it
      +16          +2       +2   034D   +01CC0000   Pvt   PMWIN    allocated it
      +16          +1       +1   034E   +01CD0000   Pvt   PMGPI    allocated it
      +16          +1       +0   034F   +01CE0000   Pvt   PMGPI    allocated it
    +1024          +1       +1   0350   +01CF0000   Pvt   PMGPI    allocated it
    +1024          +1       +1   0351   +020F0000   Pvt   PMGPI    allocated it
       +0          +2       +2   0185    16070000   Shr   PMGRE    allocated it
< End of THESEUS2 (v 2.0s) output @ 10:43:26 on 8/5/1993 >
Allocated   Committed   Actual    har     Address   P/S   Description
      -96          -1       -1   034B   -019B0000   Pvt
     -688          -1       -1   034C   -01A10000   Pvt
      -16          -2       -2   034D   -01CC0000   Pvt
      -16          -1       -1   034E   -01CD0000   Pvt
      -16          -1       +0   034F   -01CE0000   Pvt
    -1024          -1       -1   0350   -01CF0000   Pvt
    -1024          -1       -1   0351   -020F0000   Pvt
< End of THESEUS2 (v 2.0s) output @ 10:43:36 on 8/5/1993 >
Periodic updated stopped.
< End of THESEUS2 (v 2.0s) output @ 10:43:38 on 8/5/1993 >


ΓòÉΓòÉΓòÉ <hidden> Contents of the Memory Leak Detection Display ΓòÉΓòÉΓòÉ

One line is displayed for each memory object whose committed or actual (present
+ swapped) memory values have changed:

Column      Meaning
Allocated   The change in the number of pages of allocated (virtual) memory in
            this object. This will be non-zero only when the memory object is
            allocated or freed.
Committed   The change in the number of pages of committed memory in this
            object.
Actual      The change in the number of pages of actual memory in this object.
har         The har of this object.
Address     The linear address of this object.
P/S         An indicator as to the type of memory object:

   Pvt  The memory object is in the private arena.
   Shr  The memory object is in the shared arena.
Description Description in English of the object.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory states

o Leak detection control

o Manual data capture

o Manual data compare


ΓòÉΓòÉΓòÉ 9.4.4. General Process Information ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the General Process Information Display ΓòÉΓòÉΓòÉ

When you select the General Process Information option of the Process pull-down
on the Process Hierarchy window, general information about the process is
shown:

 1. Linear address of the PTDA.
 2. Number of threads, if THESEUS2 found a number different from what the PTDA
    indicates.
 3. General information about each thread, including:

    a. Thread number;
    b. Addresses of the TCB and TSD;
    c. Scheduling priority and state.

 4. The Exit List.
 5. The open files.
 6. The environment strings.


ΓòÉΓòÉΓòÉ <hidden> Example of the General Process Information Display ΓòÉΓòÉΓòÉ

General Information about the Process with PID = 010A, name = 'THESEUS2':
PTDA address = 7D3E821C

Threads for this Process:
                                    ---- priority ----
 TID   Th_#        TCB        TSD  class  level actual  state
0001   002F   7D3CEB5C   7D2F8000     02     00   0500   0005  Running

Exit List:
  Class   RtnAddress  Description
   0010   BF6F:015E   DISPLAY  #0007 (shared)
   0010   D44F:02C4   PMGRE    #0006 (shared)
   0010   D0FF:0A54   PMWIN    #0005 (shared)
   0010   D18F:A1E6   PMSHAPI  #0001 (shared)
   00C0   D067:27A8   OS2CHAR  #0001 (shared)
   0100   1A393454    HELPMGR  #0001 (shared)
   0100   0003A7DB    THESEUS2 #0001 (shared)
   0100   1A4B6188    PMCTLS   #0002 (shared)
   0100   D2B7:9D1C   PMSPL    #0004 (shared)
   01A5   D0FF:04A6   PMWIN    #0005 (shared)
   01AB   D44F:02CE   PMGRE    #0006 (shared)
   01C0   D067:27B5   OS2CHAR  #0001 (shared)
   01FF   1A4B61E4    PMCTLS   #0002 (shared)
   01FF   D44F:0308   PMGRE    #0006 (shared)

Open Files (MaxFH=20):
  ---- handles ---
  Process   System   File name
     0000     0027   \DEV\CON
     0001     0027   \DEV\CON
     0002     0027   \DEV\CON
     0003     0080   \DEV\THESEU2$
     0004     002C   \DEV\KBD$
     0005     0059   C:\THESEUS2\THESEUS2.HLP
     0006     0081   C:\OS2\HELP\HMHELP.HLP
     000C     0050   \DEV\KBD$

Environment:
  "WP_OBJHANDLE=113848"
  "USER_INI=C:\OS2\OS2.INI"
  "SYSTEM_INI=C:\OS2\OS2SYS.INI"
  "OS2_SHELL=C:\OS2\CMD.EXE"
  "AUTOSTART=PROGRAMS,TASKLIST,FOLDERS"
  "RUNWORKPLACE=C:\OS2\PMSHELL.EXE"
  "COMSPEC=C:\OS2\CMD.EXE"
  "PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;E:\TOOLKT20\OS2BIN"
  "DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS"
  "PROMPT=$i[$p]"
  "HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;E:\TOOLKT20\OS2HELP"
  "GLOSSARY=C:\OS2\HELP\GLOSS;"
  "KEYS=ON"
  "DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;"
  "BOOKSHELF=C:\OS2\BOOK;E:\TOOLKT20\BOOK"
  "EPATH=C:\OS2\APPS"
  "VIDEO_DEVICES=VIO_VGA"
  "VIO_VGA=DEVICE(BVHVGA)"
  "TMP=E:\"
  "PROGREF20=GUIREF20.INF"
  "PMREF=PMFUN.INF+PMGPI.INF+PMMSG.INF+PMWIN.INF"
  "WORKPLACE__PROCESS=NO"
  Program (actual)    = "E:\THESEUS2\THESEUS2.EXE"
  Program (specified) = "E:\THESEUS2\THESEUS2.EXE"
  Parameters = ""


ΓòÉΓòÉΓòÉ <hidden> Contents of the General Process Information Display ΓòÉΓòÉΓòÉ

The information presented on the General Process Information display is as
follows:

General Information about the Process with PID = hhhh
          The PID of the specified process.
name = 'aaaaaaaa'
          The name of the .EXE file that is the module for the process.
PTDA address = llllllll
          The linear address of the PTDA being shown.
Thread count (as discovered by THESEUS2) = i,
          The number of threads that THESEUS2 found for this process when it
          scanned the thread table. This number is shown only if this and the
          following value are not the same.
as claimed by PTDA = i.
          The number that is in the PTDA.

One line is displayed for each thread:

Column           Meaning
TID              Thread ID of the thread.
Th_#             Thread number of the thread.
TCB              Linear address of the Thread Control Block of the thread.
TSD              Linear address of the Thread Swappable Data of the thread.
Priority class   Declared priority class of the thread.
Priority level   Declared priority level of the thread.
Priority actual  Actual priority being used by the scheduler, after all the
                 dynamic calculations have been applied.
state            Dispatch state of the thread. The following decoded states are
                 shown:

   Ready      The thread is ready to run, but is not the highest priority that
              is ready.
   Blocked    The thread is blocked, waiting on some event.
   Suspended  The thread has been suspended by the system.
   Critical section The thread has done a DosEnterCritSec and not completed.
   Running    The thread is running.
   Ready, but apply an IO boost The thread is ready to run, but needs to be
              "boosted" because it has just completed some I/O.
   Thread waiting for TSD The thread is waiting for a TSD to become available.
   Delayed TKWakeup (Almost Ready) The thread has been delayed by the system.
   Frozen Thread The thread has been "frozen" by the system, waiting on its
              parent.
   Incoming TSD ???
   TSD failed to swap in A disk error occurred trying to swap the TSD in.

One line is displayed for each entry in the Exit List:

Column         Meaning
Class          The class/priority of the Exit Routine. See the description of
               the DosExitList function for the meaning of this.
RtnAddress     The address of the Exit Routine. This is either a 16:16 virtual
               address or a 0:32 flat address.
Description    The name of the module and the segment/object number this
               routine is in.

The Open Files are displayed. The maximum number of process file handles
(MaxFH) is shown. Then, the open files are shown, with 1 line for each open
file:

Column             Meaning
Process handle     The value of the process file handle. These are unique to
                   the process.  That is, process file handle 5 in the process
                   with PID = 5 is not the same as process file handle 5 in the
                   process with PID = 6.
System handle      The corresponding system file handle. These are common
                   across the entire system. That is, system file handle 5 in
                   the process with PID = 5 is the same as system file handle 5
                   in the process with PID = 6.
Flags              The file state flags. They are decoded into English at the
                   end of the line.
File name          This can be:

   o Fully qualified file name.
   o "anonymous pipe" = an anonymous pipe is opened on this handle.
   o "named pipe" = a named pipe is opened on this handle.

The process environment is displayed. Each string is displayed on a line,
surrounded by quote marks. The fully qualified program file name is displayed,
surrounded by quote marks. The program name as input is displayed, surrounded
by quote marks. The parameters passed to the program are displayed, surrounded
by quote marks.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o PTDA

o Open Files


ΓòÉΓòÉΓòÉ 9.4.5. Per Task Data Area (PTDA) ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Per Task Data Area (PTDA) Display ΓòÉΓòÉΓòÉ

When you select the Per Task Data Area (PTDA) option of the Process pull-down
on the Process Hierarchy window, the Per Task Data Area (PTDA) for the selected
process is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Per Task Data Area (PTDA) Display ΓòÉΓòÉΓòÉ

Per Task Data Area (PTDA) for Process with PID = 0088, name = 'THESEUS2':
parent PTDA     @ 7D31E020, this PTDA          @ 7D320A80
first child     @ 00000000, exec child         @ 00000000
next sibling    @ 7D31FC60, previous sibling   @ 00000000
EXE pointer     @ FE5A2934, name = D:\THESEUS2\THESEUS2.EXE
last TCB        @ FD422E10, first TCB          @ FD422E10
# of threads    = 0001,     tib count          = 0055
TIB 0           = 00050000, TIB 1              = FFFFFFFF
TIB 2           = FFFFFFFF, TIB 3              = FFFFFFFF
debug data      @ 00000000, debug flag         = 00000000

Virtual Memory Manager information:
Next Arena      @ 7D31FCA0, Previous Arena     @ FFF408FC
Arena sentinel  @ FEF31ECA, Hint of first free @ FEF3244A
bitmap dir (?)  @ FEF2D650, hash table         @ FEF2D8CC
per-type info   @ FFF3C23C, VM flags           = 00000002
min address     = 00010000, max address        = 00810000
arena count     = 00000000, need bitmap        = 00000000
max bitmap      = 00000003, max bitmap entry   = 00000000
max hash index  = 00000081, arena header hob   = 0275

Physical Memory Manager information:
page tables                       @ 7D680000
Process Page Directory (1st 512M) @ FF215A00
allocated page counts             @ 7D320B28
present page counts               @ 7D320C28
locked/resident page counts       @ 7D320D28
base virtual page number          = 00000000
base vdm alias region             = 00000000
max potential pdes for this arena = 0080
count of low  in-use pdes         = 0003
count of high in-use pdes         = 0015
page table context                = 0006
per-process page manager flags    = 0000
   process was aged in this sweep.

Environment hob = 0352 (linear = 00060000, selector = 0037)

PerfView data @ 00000000

Exit List @ FE5B55C0

hob of PTDA = 026C, hob of MTE = 024C
hob of LDT  = 0278, LDT        @ 7C705000
PID         = 0088, parent PID = 0002
selector    = 0E48, signature  = TD


ΓòÉΓòÉΓòÉ <hidden> Contents of the Per Task Data Area (PTDA) Display ΓòÉΓòÉΓòÉ

The information presented on the Per Task Data Area (PTDA) display is as
follows:

Per Task Data Area (PTDA) for Process with PID = hhhh
          The PID of the specified process.
name = 'aaaaaaaa'
          The name of the .EXE file that is the module for the process.

The following items concern the process lineage and its threads:
parent PTDA @ llllllll
          The processes have a parent/child relationship. This entry is the
          linear address of the parent process' PTDA.
this PTDA @ llllllll
          The linear address of this PTDA.
first child @ llllllll
          The linear address of the PTDA of the youngest child of this process.
exec child @ llllllll
          The linear address of the PTDA of the child process, while the child
          is being created.
next sibling @ llllllll
          The linear address of the next oldest sibling in the structure.
previous sibling @ llllllll
          The linear address of the next youngest sibling in the structure.
EXE pointer @ llllllll
          The linear address of the fully qualified .EXE file name.
name = aaaaaaaa
          The fully qualified file name of the .EXE file for this process.
last TCB @ llllllll
          The linear address of the last TCB in the TCB chain for this process.
first TCB @ llllllll
          The linear address of the first TCB in the TCB chain for this
          process.
# of threads = hhhh
          The number of threads that the PTDA claims to own.
tib count = hhhh
          The number of TIBs that have been allocated.
TIB 0 = llllllll
          Linear address of the first group of TIBs.
TIB 1 = llllllll
          Linear address of the second group of TIBs.
TIB 2 = llllllll
          Linear address of the third group of TIBs.
TIB 3 = llllllll
          Linear address of the fourth group of TIBs.
debug data @ hhhhhhhh
          Unknown
debug flag = hhhhhhhh
          Unknown

The following items concern the Virtual Memory Manager:
Next Arena @ llllllll
          The linear address of the next arena header.
Previous Arena @ llllllll
          The linear address of the previous arena header.
Arena sentinel @ llllllll
          The linear address of the sentinel arena record that starts the
          process' arena.
Hint of first free @ llllllll
          The linear address of the arena record which may be followed by an
          area of linear space that is not allocated.
bitmap dir (?) @ llllllll
          Unknown
hash table @ llllllll
          Unknown
per-type info @ llllllll
          Unknown
VM flags = hhhhhhhh
          Unknown
min address = hhhhhhhh
          The minimum linear address used by this process.
max address = hhhhhhhh
          The maximum linear address used by this process.
arena count = hhhhhhhh
          Unknown
need bitmap = hhhhhhhh
          Unknown
max bitmap = hhhhhhhh
          Unknown
max bitmap entry = hhhhhhhh
          Unknown
max hash index = hhhhhhhh
          Unknown
arena header hob = oooo
          The hob of the pseudo-object for this arena header.

The following items concern the Physical Memory Manager:
page tables @ llllllll
          The linear address of the start of the Page Tables for this process.
Process Page Directory (1st 512M) @ llllllll
          The linear address of the Process Page Directory for this process.
allocated page counts @ llllllll
          The linear address of a table having one entry for each potential
          Page Table. Each entry states the number of pages that are allocated
          within that Page Table.
present page counts @ llllllll
          The linear address of a table having one entry for each potential
          Page Table. Each entry states the number of pages that are present
          within that Page Table.
locked/resident page counts @ llllllll
          The linear address of a table having one entry for each potential
          Page Table. Each entry states the number of pages that are
          locked/resident within that Page Table.
base virtual page number = hhhhhhhh
          Unknown
base vdm alias region = hhhhhhhh
          Unknown
max potential pdes for this arena = hhhh
          The size of the process' Process Page Directory.
count of low  in-use pdes = hhhh
          Unknown
count of high in-use pdes = hhhh
          Unknown
page table context = hhhh
          Unknown
per-process page manager flags = hhhh
          Unknown
  process was aged in this sweep.

Environment hob = oooo (linear = llllllll, selector = ssss)
          The hob, linear address and selector of the environment object.

PerfView data @ llllllll
          The linear address of the PerfView data for this process.

Exit List @ llllllll
          The linear address of the Exit List for this process.

hob of PTDA = oooo
          The hob of the PTDA pseudo-object.
hob of MTE = oooo
          The hob of the MTE for the .EXE file for the process.
hob of LDT = oooo
          The hob of the process' LDT.
LDT @ llllllll
          The linear address of the process' LDT.
MaxFileHandles = iii
          The maximum number of files that can be opened at one time by this
          process.
Open File table @ ssss:oooo
          The virtual address of the Open File table. There is one entry for
          each process file handle.
PID = hhhh
          The PID of this process.
parent PID = hhhh
          The PID of the parent process.
selector = ssss
          The GDT selector that points to this PTDA.
signature = TD
          Several of the OS/2 kernel control blocks have signature characters
          at the beginning (the PTDA was inverted in OS/2 1.2). The signature
          of the PTDA is 'TD'.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Memory Management Control Blocks

o General Process Information


ΓòÉΓòÉΓòÉ 9.4.6. LDT ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Descriptor Table Entry Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the LDT Display ΓòÉΓòÉΓòÉ

When you select the LDT option of the Process pull-down on the Process
Hierarchy window, the contents of the LDT for the selected process is
displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the LDT Display ΓòÉΓòÉΓòÉ

Local Descriptor Table for process 'THESEUS2', PID = 0033:
LDT(0004) Data    Base=7C705000 Limit=0FFFF DPL=3 ED=0  W=0 A=0 P=1 G=0 B=0
LDT(000C) Code    Base=00010000 Limit=0FFFF DPL=3 CF=0  R=1 A=0 P=1 G=0 D=0
LDT(0014) Code    Base=00020000 Limit=0E2B5 DPL=3 CF=0  R=1 A=0 P=1 G=0 D=0
LDT(001C) Data    Base=00030000 Limit=0EADF DPL=3 ED=0  W=1 A=1 P=1 G=0 B=0
LDT(0024) Data    Base=00040000 Limit=002A8 DPL=3 ED=0  W=1 A=1 P=1 G=0 B=0
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the LDT Display ΓòÉΓòÉΓòÉ

One line is displayed for each valid entry in the LDT.

Please see the Descriptor Table Entry for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses

o General Process Information

o PTDA


ΓòÉΓòÉΓòÉ 9.4.7. Page Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Page Table Entry Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Process Page Table Display ΓòÉΓòÉΓòÉ

When you select the Page Table option of the Process pull-down on the Process
Hierarchy window, the contents of the Process Page Table is displayed.

The display generation takes about 3 seconds on an 8MB 20Mhz P70.


ΓòÉΓòÉΓòÉ <hidden> Example of the Process Page Table Display ΓòÉΓòÉΓòÉ

Page Table for 'THESEUS2':
*Linear=00000000 Physical=002D2000 D=1 A=1 User  R/W P=1 Resident
 Linear=00010000 FrameId=0083D     D=0 A=0 User  R/O P=0
 Linear=00011000 Physical=001AE000 D=0 A=1 User  R/O P=1
 Linear=00012000 Physical=002DA000 D=0 A=1 User  R/O P=1
 Linear=00013000 FrameId=00840     D=0 A=0 User  R/O P=0
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the Process Page Table Display ΓòÉΓòÉΓòÉ

One line is displayed for each valid entry in the Process Page Table.

Please see the Page Table Entry for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Physical addresses


ΓòÉΓòÉΓòÉ 9.4.8. Private Object Summary ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Private Object Summary Display ΓòÉΓòÉΓòÉ

When you select the Private Object Summary option of the Process pull-down on
the Process Hierarchy window, a summary of all the memory objects defined in
the private arena for the selected process is displayed.


ΓòÉΓòÉΓòÉ 9.4.9. Shared Object Summary ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Shared Object Summary Display ΓòÉΓòÉΓòÉ

When you select the Shared Object Summary option of the Process pull-down on
the Process Hierarchy window, a summary of all the memory objects defined in
the shared arena for the selected process is displayed.


ΓòÉΓòÉΓòÉ 9.4.10. Private Arena Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Arena Record Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Private Arena Table Display ΓòÉΓòÉΓòÉ

When you select the Private Arena Table option of the Process pull-down on the
Process Hierarchy window, the contents of the process' private arena is
displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Private Arena Table Display ΓòÉΓòÉΓòÉ

Private Arena Table for 'THESEUS2':
 har    pages   linear flg next prev link hash hob  hal  ptda / Decoded flags
020E 00000000 00010000 003 020A 0229 0005 0000 Sentinel, max pages=00004000
020A 00000020 00010000 1D9 020B 020E 0000 0000 0238 0000 0235 / Mapped Reload User Exec Read
020B 00000010 00030000 179 0211 020A 0000 0000 0263 0000 0235 / Mapped Reload Write User Read
┬╖┬╖┬╖
024A 00000010 006E0000 169 020D 0219 0000 0000 0243 0000 0235 / Mapped Write User Read
020D 00000010 006F0000 169 0229 024A 0000 0000 023A 0000 0235 / Mapped Write User Read
0229 000000D0 00700000 169 020E 020D 0000 0000 0278 0000 0235 / Mapped Write User Read


ΓòÉΓòÉΓòÉ <hidden> Contents of the Private Arena Table Display ΓòÉΓòÉΓòÉ

One line is displayed for each entry in the private arena.

Please see the arena record for the format of an entry.


ΓòÉΓòÉΓòÉ 9.4.11. Shared Arena Table ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Arena Record Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Shared Arena Table Display ΓòÉΓòÉΓòÉ

When you select the Shared Arena Table option of the Process pull-down on the
Process Hierarchy window, the contents of the shared arena is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Shared Arena Table Display ΓòÉΓòÉΓòÉ

Shared Arena Table for 'THESEUS2':
 har    pages   linear flg next prev link hash hob  hal  hco  / Decoded flags
0005 00016F10 04000000 007 023D 0021 0000 0000 Boundary Sentinel
023D 00000010 1AF10000 349 0247 0005 0000 0000 0248 0000 03AA / Mapped User Read Hco
0247 00000010 1AF20000 369 0236 023D 0000 0000 0251 0000 032C / Mapped Write User Read Hco
┬╖┬╖┬╖
006D 00000010 1BFE0000 349 006B 0095 0000 0000 006E 0000 030B / Mapped User Read Hco
006B 00000010 1BFF0000 349 0021 006D 0000 0000 006C 0000 02BB / Mapped User Read Hco
0021 00000010 1C000000 001 0005 006B 0000 0000 0000 0000 0000 /


ΓòÉΓòÉΓòÉ <hidden> Contents of the Shared Arena Table Display ΓòÉΓòÉΓòÉ

One line is displayed for each entry in the shared arena.

Please see the arena record for the format of an entry.


ΓòÉΓòÉΓòÉ 9.5. Registers ΓòÉΓòÉΓòÉ

The Registers pull-down contains displays of certain of the hardware related
registers and tables.

Functions available are:

Control Registers
          Displays the iAPX 386 control registers.
Current IDT
          Displays the current Interrupt Descriptor Table.
Current TSS
          Displays the current Task State Segment.


ΓòÉΓòÉΓòÉ 9.5.1. Control Registers ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Control Registers Display ΓòÉΓòÉΓòÉ

When you select the Control Registers option of the Registers pull-down on the
Process Hierarchy window, information about the current values of the
iAPX 386/486 internal control registers is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the Control Registers Display ΓòÉΓòÉΓòÉ

Processor Control Registers:
GDT base = FFEC6000, limit = 1FFF
IDT base = FFE42966, limit = 03FF
LDT selector = 0028
TSS selector = 0010
CR0 = FFFFFFFD, PG=1, ET=1, TS=1, EM=1, MP=0, PE=1
CR2 = 004E0000  (Page Fault Linear address)
CR3 = 0018F000  (Page Directory Physical address)
DR0 = 00000000  (Breakpoint 0 Linear address)
DR1 = 00000000  (Breakpoint 1 Linear address)
DR2 = 00000000  (Breakpoint 2 Linear address)
DR3 = 00000000  (Breakpoint 3 Linear address)
DR6 = FFFF4FF0, B0-3=0000, BD=0, BS=1, BT=0
DR7 = 00000400, LE=0, GE=0, GD=0
      Len0=0, R/W0=0, L0=0, G0=0
      Len1=0, R/W1=0, L1=0, G1=0
      Len2=0, R/W2=0, L2=0, G2=0
      Len3=0, R/W3=0, L3=0, G3=0


ΓòÉΓòÉΓòÉ <hidden> Contents of the Control Registers Display ΓòÉΓòÉΓòÉ

The information presented on the Control Registers display is as follows:

GDT base = llllllll, limit = hhhh
          The base and limit values for the GDT, obtained by doing an SGDT
          instruction.
IDT base = llllllll, limit = hhhh
          The base and limit values for the IDT, obtained by doing an SIDT
          instruction.
LDT selector = ssss
          The selector for the LDT, obtained by doing an SLDT instruction.
TSS selector = ssss
          The selector for the current TSS, obtained by doing an STR
          instruction.
CR0 = hhhhhhhh
          Control Register 0.  The bits that are used are decoded as follows:

   PG   Paging enabled.  0 = no, 1 = yes.
   ET   Extension Type.  0 = 16-bit 387 protocol, 1 = 32-bit 387 protocol.
   TS   Task Switched.  0 = no, 1 = yes.
   EM   Emulation (of 387).  0 = no, 1 = yes.
   MP   Math Present.  0 = no 387 is attached, 1 = a 387 is attached.
   PE   Protection Enable.  0 = no, 1 = yes.
CR2 = llllllll  (Page Fault Linear address)
          The linear address of the last page fault.
CR3 = pppppppp  (Page Directory Physical address)
          The physical address of the Page Directory. There is only one Page
          Directory for the entire system.
DR0 = llllllll  (Breakpoint 0 Linear address)
          Debug Register 0.  This is the linear address of Breakpoint 0.
DR1 = llllllll  (Breakpoint 1 Linear address)
          Debug Register 1.  This is the linear address of Breakpoint 1.
DR2 = llllllll  (Breakpoint 2 Linear address)
          Debug Register 2.  This is the linear address of Breakpoint 2.
DR3 = llllllll  (Breakpoint 3 Linear address)
          Debug Register 3.  This is the linear address of Breakpoint 3.
DR6 = hhhhhhhh
          Debug Register 6.  See the Intel 80386 Programmer's Reference Manual
          for the definitions of the bits.
DR7 = hhhhhhhh
          Debug Register 7.  See the Intel 80386 Programmer's Reference Manual
          for the definitions of the bits.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing


ΓòÉΓòÉΓòÉ 9.5.2. IDT ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Descriptor Table Entry Description

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the IDT Display ΓòÉΓòÉΓòÉ

When you select the IDT option of the Registers pull-down on the Process
Hierarchy window, the contents of the IDT is displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the IDT Display ΓòÉΓòÉΓòÉ

Interrupt Descriptor Table:
Trap(00) TrapG32 Selector=0160 Offset=FFF6BF58 DPL=0               P=1
Trap(01) IntG32  Selector=0160 Offset=FFF6C004 DPL=3               P=1
Trap(02) TaskG   Selector=1D18                 DPL=0               P=1
Trap(03) IntG32  Selector=0160 Offset=FFF6C1A8 DPL=3               P=1
Trap(04) TrapG32 Selector=0160 Offset=FFF6C1F0 DPL=3               P=1
Trap(05) TrapG32 Selector=0160 Offset=FFF6C1FC DPL=0               P=1
Trap(06) TrapG32 Selector=0160 Offset=FFF6C208 DPL=0               P=1
Trap(07) TrapG32 Selector=005A Offset=1BF60AD0 DPL=0               P=1
Trap(08) TaskG   Selector=0088                 DPL=0               P=1
Trap(09) TrapG32 Selector=0160 Offset=FFF6C2E0 DPL=0               P=1
┬╖┬╖┬╖
Int (00) IntG32  Selector=0160 Offset=FFF37214 DPL=0               P=1
Int (01) IntG32  Selector=0160 Offset=FFF37228 DPL=0               P=1
┬╖┬╖┬╖
Int (0E) IntG32  Selector=0160 Offset=FFF37354 DPL=0               P=1
Int (0F) IntG32  Selector=0160 Offset=FFF37368 DPL=0               P=1
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the IDT Display ΓòÉΓòÉΓòÉ

One line is displayed for each valid entry in the IDT.

Please see the Descriptor Table Entry for the format of an entry.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses


ΓòÉΓòÉΓòÉ 9.5.3. Current TSS ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Current TSS Display ΓòÉΓòÉΓòÉ

When you select the Current TSS option of the Registers pull-down on the
Process Hierarchy window, information about the current Task State Segment is
displayed.


ΓòÉΓòÉΓòÉ <hidden> Example of the TSS Display ΓòÉΓòÉΓòÉ

Busy 386 Task State Segment for selector = 0010:
Back Link Selector to TSS = 0000
SS:ESP for ring 0 = 0030:00005E14
SS:ESP for ring 1 = 0000:00000000
SS:ESP for ring 2 = 0036:00001000
Current Task State:
CR3 = 0018F000  EIP = 00000000  Flag = 00000000
EAX = 00000000  EBX = 00000000  ECX = 00000000  EDX = 00000000
EDI = 00000000  ESI = 00000000  EBP = 00000000  ESP = 00000000
CS = 0000  SS = 0000  DS = 0000  ES = 0000  FS = 0000  GS = 0000
Task LDT Selector = 0028  I/O Map Base = DFFF  Debug Trap bit = 0


ΓòÉΓòÉΓòÉ <hidden> Contents of the TSS Display ΓòÉΓòÉΓòÉ

Please refer to the Intel 80386 Programmer's Reference Manual or Intel i486
Microprocessor Programmer's Reference Manual for the fields in the TSS.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses


ΓòÉΓòÉΓòÉ 9.6. Misc ΓòÉΓòÉΓòÉ

The Misc pull-down contains options applicable to the system as a whole.

Functions available are:

Refresh Diagram
          Refreshes the process hierarchy diagram.
Unselect Process
          Unselects the currently selected process.
`Link' Color
          Changes the color of the hyperblock links.
Font for this window...
          Specifies an alternate font for this window.
Default font for Detail Windows...
          Specifies an alternate default font for the Detail windows.


ΓòÉΓòÉΓòÉ 9.6.1. Refresh Diagram ΓòÉΓòÉΓòÉ

When you select the Refresh Diagram option of the Misc pull-down on the Process
Hierarchy window, the process hierarchy diagram on the Process Hierarchy window
is redetermined and redisplayed. This also happens each time any part of the
window is painted.


ΓòÉΓòÉΓòÉ 9.6.2. Unselect Process ΓòÉΓòÉΓòÉ

When you select the Unselect Process option of the Misc pull-down on the
Process Hierarchy window, the currently selected process is unselected. No
process will be selected.


ΓòÉΓòÉΓòÉ 9.6.3. `Link' Color ΓòÉΓòÉΓòÉ

When you select the `Link' Color option of the Misc pull-down on the Process
Hierarchy window, you can change the color of the hyperblock links displayed on
the Detail window.

The Dark Blue and Dark Red offer the best contrast for both normal and reverse
video information displayed on both a color and monochrome display. However,
the color defaults to Dark Cyan so the hyperblock links will be the same color
as the hypertext links in the help panels.

The pop-out menu lists all available colors.

Window Text is a color chosen by the system to be neutral on both color and
monochrome displays. It is normally black.

The current setting is checked in the list.


ΓòÉΓòÉΓòÉ 9.6.4. Font for this Window... ΓòÉΓòÉΓòÉ

When you select the Font for this Window... option of the Misc pull-down on the
Process Hierarchy window, you can specify a different monospace font  for the
Process Hierarchy window.


ΓòÉΓòÉΓòÉ 9.6.5. Default font for Detail Windows... ΓòÉΓòÉΓòÉ

When you select the Default font for Detail Windows... option of the Misc
pull-down on the Process Hierarchy window, you can specify a different default
monospace font for Detail windows which are created.


ΓòÉΓòÉΓòÉ <hidden> List of Selectable Fonts ΓòÉΓòÉΓòÉ

Select a font from this list. Only monospaced fonts are displayed.


ΓòÉΓòÉΓòÉ 9.7. Window ΓòÉΓòÉΓòÉ

The Window pull-down contains the list of existing THESEUS2 Detail windows.
When you select one, it is brought to the foreground. If it has been minimized,
it is also restored to the size and position it had before being minimized.

The list is updated as Detail windows are created and destroyed. The order of
the windows listed reflects the order of creation, with the newest being on the
bottom of the list.

The last window viewed is indicated by a check mark.


ΓòÉΓòÉΓòÉ 9.8. Help ΓòÉΓòÉΓòÉ

The Help pull-down contains the list of the help functions available for the
Process Hierarchy window.


ΓòÉΓòÉΓòÉ 9.8.1. Help Index ΓòÉΓòÉΓòÉ

The Help Index option of the Help pull-down displays the index of the help
document.


ΓòÉΓòÉΓòÉ 9.8.2. Keys help ΓòÉΓòÉΓòÉ

The Keys help option of the Help pull-down displays the key definitions for
this window.


ΓòÉΓòÉΓòÉ 9.8.3. Mouse ΓòÉΓòÉΓòÉ

The Mouse option of the Help pull-down displays information about using the
mouse.


ΓòÉΓòÉΓòÉ 9.8.4. General Help ΓòÉΓòÉΓòÉ

The General Help option of the Help pull-down displays information about the
contents of this window.


ΓòÉΓòÉΓòÉ 9.8.5. Product Information ΓòÉΓòÉΓòÉ

The Product Information option of the Help pull-down displays a dialog box
which tells the version of the program.


ΓòÉΓòÉΓòÉ 10. Detail Window ΓòÉΓòÉΓòÉ

The Detail window shows information about specific areas in either OS/2 system
or application memory. There are a number of different window contents, all
displayed in this same generic window class. The initial window size computed
by the program is:

o The width of the longest line (not to exceed the screen width)
o The height of the data (not more than 3/4 of the screen height).

THESEUS2 knows how to format many control blocks. These are pointed to by
hyperblock links. The section Selecting a Hyperblock Link tells how to use the
hyperblock links. The section Keys tells how to use the keyboard.

Options available on the Detail window are:

Functions     Viewing memory in various hex formats or control working set
              computations.
Output        Sending output to a file or printer.
Mark/Find     Doing the clipboard and general string finding functions.
Misc          Changing window processing controls and font specification.
Help          Lists the help functions.


ΓòÉΓòÉΓòÉ 10.1. Selecting a Hyperblock Link ΓòÉΓòÉΓòÉ

You may select a hyperblock link address in either of two ways:

o Place the mouse pointer over a hyperblock link address and press button 1.

o Use the arrow keys:

   Left Arrow       Moves to the previous hyperblock link address.
   Right Arrow      Moves to the next hyperblock link address.
   Up Arrow         Moves to the hyperblock link address in the previous line.
                    This attempts to stay in the same data column. If not
                    possible, then the last hyperblock link address on the line
                    is selected.
   Down Arrow       Moves to the hyperblock link address in the next line. This
                    attempts to stay in the same data column. If not possible,
                    then the last hyperblock link address on the line is
                    selected.

If no hyperblock link address is selected, pressing any arrow key will select
the first one.


ΓòÉΓòÉΓòÉ 10.2. Keys ΓòÉΓòÉΓòÉ

The key assignments in a Detail window are:

Left Arrow       Moves to the previous hyperblock link address.
Right Arrow      Moves to the next hyperblock link address.
Up Arrow         Moves to the hyperblock link address in the previous line.
                 This attempts to stay in the same data column. If not
                 possible, then the last hyperblock link address on the line is
                 selected.
Down Arrow       Moves to the hyperblock link address in the next line. This
                 attempts to stay in the same data column. If not possible,
                 then the last hyperblock link address on the line is selected.
Alt+Left         Scrolls the window information left.
Alt+Right        Scrolls the window information right.
Alt+Up           Scrolls the window information up.
Alt+Down         Scrolls the window information down.
Page Up          Scrolls the window information up 1/2 the screen height.
Page Down        Scrolls the window information down 1/2 the screen height.
Home             Moves the window so that the top left corner is displayed.
End              Moves the window so that the bottom right corner is displayed.
Print Screen     Prints the contents of the window.
Ctrl-A           Performs the "Find again" function.
Ctrl-F           Displays the "Find..." dialog.
Ctrl-S           Displays the "Save As..." dialog.
F1               Requests contextual help.
F3               Closes the Detail window.
Shift-F10        Displays a popup menu.
Enter            Formats the data at the selected address. (This is the same as
                 double-clicking mouse button 1.)


ΓòÉΓòÉΓòÉ 10.3. Functions ΓòÉΓòÉΓòÉ

The Functions pull-down has options that allow displaying more information
about items in the current display.

Functions available are:

Show memory at linear address...
          Presents a dialog to allow display of memory at a specified linear
          address.
Show memory at virtual address...
          Presents a dialog to allow display of memory at a specified virtual
          address.
Show memory at physical address...
          Presents a dialog to allow display of memory at a specified physical
          address.
Show selected address formatted
          Shows the selected address as a formatted control block.
Show description...
          Displays a "description" of the memory object.
Memory Object Leak Detection
          Performs memory leak detection on a single memory object.
Working Set Parameters...
          Presents a dialog to specify data collection parameters.
Working Set Start
          Starts collecting the working set information.
Working Set Stop
          Stops collecting the working set information and provide a summary.
Show detail by Page
          Shows which pages made up the summary data in the window.
Show detail by Object
          Shows which objects made up the summary data in the window.
Show summary by Process
          Show a summary of the working set information, summarized by process.
Leak Detection Control...
          Presents a dialog to specify leak detection parameters.
Start Periodic Leak Detection
          Starts performing leak detection on a periodic basis.
Stop Periodic Leak Detection
          Stops the periodic leak detection.
Capture Leak Reference Data
          Manually captures leak detection data.
Compare Present Leak Data
          Compares current leak detection data with last captured data.


ΓòÉΓòÉΓòÉ 10.3.1. Show memory at linear address... ΓòÉΓòÉΓòÉ

The Show memory at linear address dialog of the Functions pull-down on the
Detail window allows you to display memory at a specified linear address for a
specified number of bytes. Various formatting options are available:

o bytes
o words
o doublewords
o disassembled instructions.


ΓòÉΓòÉΓòÉ <hidden> Address (in hex) of the area to display. ΓòÉΓòÉΓòÉ

This option specifies the linear address (in hexadecimal) of the memory to be
displayed.

The default value is the selected hyperblock link, if one is selected.


ΓòÉΓòÉΓòÉ <hidden> Number of bytes (in hex) to display. ΓòÉΓòÉΓòÉ

This option specifies the number of bytes (in hexadecimal) you wish displayed.


ΓòÉΓòÉΓòÉ <hidden> Show the memory as "bytes". ΓòÉΓòÉΓòÉ

This option displays the memory as bytes. Each byte is formatted in
hexadecimal.

Additionally, the memory is formatted in ASCII. Unprintable characters are
printed as a period (.).

The width specification controls the number of bytes presented on each line.


ΓòÉΓòÉΓòÉ <hidden> Show the memory as "words". ΓòÉΓòÉΓòÉ

This option displays the memory as words (2 bytes). Each word is "byte
reversed" and then formatted in hexadecimal.

Additionally, the memory is formatted in ASCII, without "byte reversal."
Unprintable characters are printed as a period (.).


ΓòÉΓòÉΓòÉ <hidden> Show the memory as "doublewords". ΓòÉΓòÉΓòÉ

This option displays the memory as doublewords (4 bytes). Each doubleword is
"byte reversed" and then formatted in hexadecimal.

Additionally, the memory is formatted in ASCII, without "byte reversal."
Unprintable characters are printed as a period (.).


ΓòÉΓòÉΓòÉ <hidden> Show the memory as disassembled instructions. ΓòÉΓòÉΓòÉ

This option displays the memory as disassembled instructions.

The memory is presented:

 1. in bytes
 2. in ASCII
 3. as disassembled instructions.

The default instruction type may be specified with the Code is 32-bit option.


ΓòÉΓòÉΓòÉ <hidden> Code is 32-bit. ΓòÉΓòÉΓòÉ

This option specifies that the instructions being disassembled are 32-bit
instructions. If this option is not selected, the instructions are assumed to
be 16-bit.


ΓòÉΓòÉΓòÉ <hidden> Number of bytes (in hex) per line. ΓòÉΓòÉΓòÉ

If you choose to "format in bytes," you can additionally select the number of
bytes to be displayed on each line. This makes it easier to look at arrays,
since each entry can be placed on a separate line.

The default is 10 (hexadecimal) bytes per line.


ΓòÉΓòÉΓòÉ 10.3.2. Show memory at virtual address... ΓòÉΓòÉΓòÉ

The Show memory at virtual address dialog of the Functions pull-down on the
Detail window allows you to display memory at a specified selector:offset for a
specified number of bytes. Various formatting options are available:

o bytes
o words
o doublewords
o disassembled instructions


ΓòÉΓòÉΓòÉ <hidden> Selector (in hex) of Segment. ΓòÉΓòÉΓòÉ

This option specifies the selector portion (in hexadecimal) of the virtual
address of the memory to be displayed.

The default value is the selector portion of the selected hyperblock link, if
one is selected.


ΓòÉΓòÉΓòÉ <hidden> Offset (in hex) of Segment. ΓòÉΓòÉΓòÉ

This option specifies the offset portion (in hexadecimal) of the virtual
address of the memory to be displayed.

The default value is the offset portion of the selected hyperblock link, if one
is selected.


ΓòÉΓòÉΓòÉ <hidden> Number of bytes (in hex) to display. ΓòÉΓòÉΓòÉ

This option specifies the number of bytes (in hex) you wish displayed.

If a hyperblock link has been selected and the selector is valid, the length
will default to the length of the segment.

If a hyperblock link has not been selected, the length will default to the
"double-click length" for the window.


ΓòÉΓòÉΓòÉ <hidden> Show the memory as "bytes". ΓòÉΓòÉΓòÉ

This option displays the memory as bytes. Each byte is formatted in
hexadecimal.

Additionally, the memory is formatted in ASCII. Unprintable characters are
printed as a period (.).


ΓòÉΓòÉΓòÉ <hidden> Show the memory as disassembled instructions. ΓòÉΓòÉΓòÉ

This option displays the memory as disassembled instructions.

The memory is presented:

 1. in bytes
 2. in ASCII
 3. as disassembled instructions.

The default instruction type may be specified with the Code is 32-bit option.


ΓòÉΓòÉΓòÉ <hidden> Code is 32-bit. ΓòÉΓòÉΓòÉ

Select this option if the instructions being disassembled are 32-bit
instructions. If this option is not selected, the instructions are assumed to
be 16-bit.

If a hyperblock link has been selected and the selector is valid, the type will
default to the type of the segment.


ΓòÉΓòÉΓòÉ 10.3.3. Show memory at physical address... ΓòÉΓòÉΓòÉ

The Show memory at physical address dialog of the Functions pull-down on the
Detail window allows you to display memory at a specified physical address for
a specified number of bytes. Various formatting options are available:

o bytes
o words
o doublewords
o disassembled instructions


ΓòÉΓòÉΓòÉ <hidden> Address (in hex) of the area to display. ΓòÉΓòÉΓòÉ

This option specifies the physical address (in hexadecimal) of the memory to be
displayed.

The default value is the selected hyperblock link, if one is selected.


ΓòÉΓòÉΓòÉ 10.3.4. Show selected address formatted ΓòÉΓòÉΓòÉ

When a hyperblock link address is selected, the memory may be displayed either
by double-clicking mouse button 1 or by selecting this option on the menu. The
memory is displayed formatted by its control block type, if THESEUS2 knows the
format.


ΓòÉΓòÉΓòÉ <hidden> Show selected address in hex ΓòÉΓòÉΓòÉ

When a hyperblock link address is selected, this option displays the memory in
hexadecimal.


ΓòÉΓòÉΓòÉ <hidden> Describe the selected address ΓòÉΓòÉΓòÉ

When a hyperblock link address has been selected, this option displays the
"description" of the memory represented by the address.


ΓòÉΓòÉΓòÉ 10.3.5. Show description... ΓòÉΓòÉΓòÉ

The Show description of an object option of the Functions pull-down on the
Detail window allows you to display the "description" of a memory object.

The object address can be specified as being referenced by:

o linear address
o virtual address
o physical address
o har
o hob.


ΓòÉΓòÉΓòÉ <hidden> Address of object to be described ΓòÉΓòÉΓòÉ

Specify the address of the object to be "described." It can be:

o linear address
o virtual address
o physical address
o har
o hob.


ΓòÉΓòÉΓòÉ <hidden> Describe a linear object ΓòÉΓòÉΓòÉ

The address specified is a linear address.


ΓòÉΓòÉΓòÉ <hidden> Describe a virtual object ΓòÉΓòÉΓòÉ

The address specified is a virtual address. Specify the selector of the
segment.


ΓòÉΓòÉΓòÉ <hidden> Describe a physical object ΓòÉΓòÉΓòÉ

The address specified is a physical address.


ΓòÉΓòÉΓòÉ <hidden> Describe an object, given the HAR ΓòÉΓòÉΓòÉ

The address specified is a har.


ΓòÉΓòÉΓòÉ <hidden> Describe an object, given the HOB ΓòÉΓòÉΓòÉ

The address specified is a hob.


ΓòÉΓòÉΓòÉ 10.3.6. Memory Object Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Memory Object Leak Detection Display ΓòÉΓòÉΓòÉ

When you select the Memory Object Leak Detection option of the Functions
pull-down on a Detail window, information about the changes of state of
individual pages of the specified memory object are shown.

This option is available only if you have selected a Hyperblock link linear
address.


ΓòÉΓòÉΓòÉ <hidden> Example of the Memory Object Leak Detection Display ΓòÉΓòÉΓòÉ

Leak detection for Process with PID = 067C, name = THESEUS2,
  memory object linear = 00010000, object has 48 pages:
< End of THESEUS2 (v 2.0p) output @ 15:57:38 on 5-16-1993 >
Use the 'Function' pull-down to start and stop the data collection.
Leak data captured.
Periodic update started with interval of 10 seconds.
< End of THESEUS2 (v 2.0p) output @ 15:57:41 on 5-16-1993 >
address    old state     new state
00026000   not-present   present
< End of THESEUS2 (v 2.0p) output @ 15:57:51 on 5-16-1993 >

If the Show all page states option is chosen, then the following is produced:

old pppppppppppppllllpplpppllllllplllplpplpppppppp
new pppppppppppppllllpplpppppllllplllplpplpppppppp
dif .......................AB.....................
dif address    old state     new state
A:  00027000   to be loaded  present
B:  00028000   to be loaded  present
< End of THESEUS2 (v 2.0p) output @ 15:58:01 on 5-16-1993 >


ΓòÉΓòÉΓòÉ <hidden> Contents of the Memory Object Leak Detection Display ΓòÉΓòÉΓòÉ

The information presented on the Memory Object Leak Detection display is as
follows:

If the Show all page states option is chosen, then the following information is
produced:

old  The states of each page in the memory object in the reference data:

   .  The page was uncommitted.
   ?  The page was a special system page.
   a  The page was an "allocate on demand" page.
   c  The page was claimable.
   i  The page was idle.
   l  The page was a "to be loaded" page.
   p  The page was present.
   r  The page was resident.
   s  The page was swapped.
   u  The page was a UVirt page.
new  The states of each page in the memory object in the current data. The
     state codes are the same as the old line.
dif  The pages which have different states are marked with a letter:

   .  The page state did not change.
   A  The page changed state. The letter shown is different for each page which
      changed state. The letter is repeated on the appropriate line of the
      summary information.

Uncommitted pages at the end of the memory object are not shown, in order to
reduce clutter on the screen.

Summary information is always presented:

Column       Meaning
address      The linear address of the page which has changed state.
old state    The state the page had in the reference data.

   uncommitted    The page was uncommitted.
   special        The page was a special system page.
   allocate on demand The page was an "allocate on demand" page.
   claimable      The page was claimable.
   idle           The page was idle.
   to be loaded   The page was a "to be loaded" page.
   present        The page was present.
   resident       The page was resident.
   swapped        The page was swapped.
   UVirt          The page was a UVirt page.
new state    The state the page has in the current data. The states are the
             same as the old state column.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Memory states

o Leak detection control

o Manual data capture

o Manual data compare


ΓòÉΓòÉΓòÉ 10.3.7. Working Set Parameters... ΓòÉΓòÉΓòÉ

The Working Set Parameters dialog of the Functions pull-down on the Working Set
Detail window allows you to specify the data-collection parameters used during
working set calculations. The parameters that can be specified are:

o Data collection interval
o Number of intervals in Working Set
o Include 'System' pages
o Show data at each interval
o Save as defaults
o Results presented in.


ΓòÉΓòÉΓòÉ <hidden> Number of seconds per sample interval ΓòÉΓòÉΓòÉ

This option specifies the number of seconds for each working set data
collection interval.

The default is 5 seconds. The maximum value is 99 seconds.

This value is specified in decimal.


ΓòÉΓòÉΓòÉ <hidden> Specify the number of intervals for Working Set ΓòÉΓòÉΓòÉ

This option specifies the number of intervals (n) that constitute the working
set. If a page has been accessed within the last n intervals, then it is
considered to be within the working set.

The default is 12 intervals (times the default interval of 5 seconds = 60
seconds).

This value is specified in decimal.

This value can be changed while the data collection is running.


ΓòÉΓòÉΓòÉ <hidden> Include 'System' pages ΓòÉΓòÉΓòÉ

If this option is selected, the system arena is included in the calculations.

CAUTION:
This option is not recommended. Many system pages are referenced by THESEUS2
while it is doing the data collection and reduction, and it is impossible to
differentiate between them and the ones referenced by the application of
interest, so this tends to confuse the actual answers.


ΓòÉΓòÉΓòÉ <hidden> Show data at each interval ΓòÉΓòÉΓòÉ

This option displays the results each interval.

The changes in the working set during the running of a scenario are usually
more interesting than the summary results.

This option can be changed while the data collection is occurring.


ΓòÉΓòÉΓòÉ <hidden> Save as defaults ΓòÉΓòÉΓòÉ

When this option is selected, the input values become the defaults for the
working set parameters on subsequent creations of the working set window.


ΓòÉΓòÉΓòÉ <hidden> Results presented in: ΓòÉΓòÉΓòÉ

The results can be presented in either:

o Pages
o Kilobytes
o Megabytes


ΓòÉΓòÉΓòÉ <hidden> Pages ΓòÉΓòÉΓòÉ

This option presents the results as the number of pages of memory used.


ΓòÉΓòÉΓòÉ <hidden> Kilobytes ΓòÉΓòÉΓòÉ

This option presents the results as the number of kilobytes of memory used.


ΓòÉΓòÉΓòÉ <hidden> Megabytes ΓòÉΓòÉΓòÉ

This option presents the results as the number of megabytes of memory used.


ΓòÉΓòÉΓòÉ 10.3.8. Working Set Start ΓòÉΓòÉΓòÉ

This option starts collecting the information required to determine memory
working set.


ΓòÉΓòÉΓòÉ 10.3.9. Working Set Stop ΓòÉΓòÉΓòÉ

This option stops collecting the information required to determine memory
working set. A final data-collection cycle occurs before the results are
analyzed and displayed.


ΓòÉΓòÉΓòÉ <hidden> Detail of Working Set (by Page) ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detail of Working Set (by Page) display ΓòÉΓòÉΓòÉ

When you select the Show detail by Page option of the Functions pull-down on
the Working Set Detail window, detail information about the working set is
shown. Specifically, the pages referenced since the working set sampling began
are shown.


ΓòÉΓòÉΓòÉ <hidden> Example of the Detail of Working Set (by Page) Display ΓòÉΓòÉΓòÉ

Working Set detail for the Process with PID = 000E, name = 'THESEUS2':
Physical   hob  Time  State   Type     Description
00060000  0382     1  A       DLL      SYSMONO  #0004 (shared)
00068000  0383     1  A       Private  THESEUS2 allocated it
0006C000  0362     1  A       Private  THESEUS2 #0001 (shared)
┬╖┬╖┬╖
00DCA000  00B3     1  A       DLL      DOSCALL1 #0005 (shared)
00DE4000  031E     1  A       DLL      PMGRE    allocated it

  142 pages were marked 'A' (Accessed).
   17 pages were marked 'L' (Locked).
    0 pages were marked 'R' (Resident).
There were a total of 145 pages reported.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Detail of Working Set (by Page) display ΓòÉΓòÉΓòÉ

One line is displayed for each page in the working set:

Column        Meaning
Physical      The physical address of the page.
hob           The hob of the memory object that this page is a part of.
Time          Number of time intervals (in decimal) since the page was
              referenced. A value of 1 indicates that the page was touched in
              the last interval before data capturing was stopped. A value of 2
              indicates that the page was touched in the next-to-last interval
              before data capturing was stopped.
State         The state of this page:

   A  The page has been accessed during the run.
   L  The page is locked.
   R  The page is resident.
   F  The page is now free.
   I  The page is idle
   B  The page has a "bad hob" The hob value is too large to be able to access
      the Object Record in the Object Table.
Type          (This is only on the display if it was generated from a Working
              Set for a Process display.) The type of object that this page is
              a part of. The values are:

   System         The page is from the system arena.
   Private        The page is from the private arena, is an instance object
                  from a system DLL, or is an object from a DLL which is not a
                  system DLL.
   DLL            The page is from the shared arena and is for a system DLL.
                  The system DLLs are those that are part of the system and are
                  not considered to be part of the application.
   Error          An error has occurred while processing the page. The hob may
                  be out of range. The page was assigned to the system.
Description   A description in English of the object that the page is a part
              of.

A summary of the number of pages in each page State is given. Then the total
number of pages reported is given. (Since a page may be in multiple states, the
total of the pages in each state is probably not the same as the total
reported.)


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory analysis

o Memory addressing

o System Working Set


ΓòÉΓòÉΓòÉ <hidden> Detail of Working Set (by Object) ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detail of Working Set (by Object) display ΓòÉΓòÉΓòÉ

When you select the Show detail by Object option of the Functions pull-down on
the Working Set Detail window, detail information about the working set is
shown. Specifically, all the memory objects from the private arena are shown,
along with ones from the shared and system arenas that have had pages
referenced since the run began.


ΓòÉΓòÉΓòÉ <hidden> Example of the Detail of Working Set (by Object) Display ΓòÉΓòÉΓòÉ

Working Set detail for the Process with PID = 0060, name = 'THESEUS2':
Objects from the 'private' arena:
                 ---accessed---     pages in   avg.
  linear   hob      no      yes  working set   time  Description
00010000  04CF      32       18           18    1.1  THESEUS2 #0001 (shared code)
00050000  047C      21        8            8    1    THESEUS2 #0002 (private)
00070000  0475       1        0            0          User Environment (hmte)
┬╖┬╖┬╖
01C80000  048F       1        0            0          THESEUS2 allocated it
                    92       44           44    1.0  Total

Objects from the 'shared' arena:
                 ---accessed---     pages in   avg.
  linear   hob      no      yes  working set   time  Description
16350000  04DF       0        1            1    1    THESEUS2 allocated it
163E0000  04BB       1        1            1    1    SYSMONO  #0004 (shared data)
16420000  04AE       0        1            1    1    PMGRE    allocated it
┬╖┬╖┬╖
1BFF0000  0074       0        1            1    1    infoseg (local or global) (owner)
                  1052      254          254    1.0  Total

Objects from the 'system' arena:
                 ---accessed---     pages in   avg.
  linear   hob      no      yes  working set   time  Description
7DC00000  002A       5       13           13    1    PG Compat. region page table (owner)
                     5       13           13    1.0  Total


ΓòÉΓòÉΓòÉ <hidden> Contents of the Detail of Working Set (by Object) Display ΓòÉΓòÉΓòÉ

One line is displayed for each object:

Column            Meaning
linear            The linear address of the memory object.
hob               The hob of the memory object.
accessed - no     The number of pages that are committed in the object that
                  were not accessed since the start of the run.
accessed - yes    The number of pages that are committed in the object that
                  were accessed since the start of the run.
pages in working set The number of pages that were in the working set.
avg. time         The average number of intervals since the pages were
                  accessed. If all the pages were accessed at the same time,
                  the time is output without a decimal point.
Description       A description in English of the object.

The totals for each arena is shown at the end of the arena's output.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory analysis

o Memory addressing

o System Working Set

o Summary by Process


ΓòÉΓòÉΓòÉ 10.3.10. Show detail by Page ΓòÉΓòÉΓòÉ

Which display is presented depends on the Detail window from which this option
is selected:

Working Set window
Swapper window


ΓòÉΓòÉΓòÉ 10.3.11. Show detail by Object ΓòÉΓòÉΓòÉ

Which display is presented depends on the Detail window from which this option
is selected:

Working Set window


ΓòÉΓòÉΓòÉ 10.3.12. Summary by Process ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Summary by Process display ΓòÉΓòÉΓòÉ

When you select the Show summary by process option of the Functions pull-down
on the System Working Set Detail window, summary information about the working
set is shown. Specifically, the amount of memory, both private and shared, used
by each process is shown, along with the amount used from the system and shared
arenas.


ΓòÉΓòÉΓòÉ <hidden> Example of the Summary by Process Display ΓòÉΓòÉΓòÉ

Working Set summary for the System (by Process):
-------- Private --------- ---------- Shared ---------
- Accessed - Working  Avg. - Accessed - Working  Avg.
    No    Yes    set  time     No    Yes    set  time  PID Process name
     0      2      2   1.0      0      0      0       0002 LOGDAEM
    21      8      8   1.3      0      4      4   1.5 0004 PMSHL32
     4      2      2   2.0      0      0      0       0006 SPMSNAPL
    41     37     37   1.5      0      0      0       0009 VDM
    50     10     10   1.0      0      0      0       000A SPM
    32     43     43   1.9      1      6      6   2.0 000C SPMMON
   103     19     19   1.6      0      0      0       000D SPMILOG
    81     20     20   2.0      0      0      0       000E SPMDCF
     9     23     23   1.2      0      3      3   2.0 001F IPFCPREP
    57     41     41   1.3      0      3      3   1.0 0020 THESEUS2
   268   1370   1370   1.0   1071    292    292   1.7      System
------ ------ ------       ------ ------ ------
   666   1575   1575         1072    308    308            Totals
            2      2   Free RAM
------ ------ ------
  1738   1885   1885   Pvt + Shr + Free


ΓòÉΓòÉΓòÉ <hidden> Contents of the Summary by Process Display ΓòÉΓòÉΓòÉ

One line is displayed for each process:

Column            Meaning
Private           Memory from the private arena. For the System line, this is
                  memory from the system arena.
Shared            Instance data from the shared arena. For the System line,
                  this is shared memory from the shared arena.
Accessed - No     The number of pages that are committed in the objects for
                  this process that were not accessed since the start of the
                  run.
Accessed - Yes    The number of pages that are committed in the objects for
                  this process that were accessed since the start of the run.
Working set       The number of pages that were in the working set.
Avg. time         The average number of intervals since the pages were
                  accessed.
PID               The PID of the process for this line.
Process name      The name of the process on this line.

Totals for each column are generated and shown.

The line labeled Free RAM is memory that has been accessed during the run, but
is currently marked Free.

The line labeled Pvt + Shr + Free is a total of all the data.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory analysis

o Memory addressing

o System Working Set

o Detail by Object


ΓòÉΓòÉΓòÉ <hidden> Detail of SWAPPER.DAT (by Page) ΓòÉΓòÉΓòÉ

Select one:

Selecting

Example Output

Contents of Display

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detail of SWAPPER.DAT (by Page) display ΓòÉΓòÉΓòÉ

When you select the Show detail by Page option of the Functions pull-down on
the SWAPPER.DAT Analysis Detail window, detail information about the make up of
the SWAPPER.DAT file will be shown. Specifically, the pages that have been
paged out are shown.


ΓòÉΓòÉΓòÉ <hidden> Example of the SWAPPER.DAT contents (by page) Display ΓòÉΓòÉΓòÉ

SWAPPER.DAT contents by page:
frame        vp   hob    linear  Process  Description
 0000  FF4132EE  01C1  00030000     01BB  HARDERR  #0003 (private)
 0001  FF417966  039F  000C1000     0379  PMD      #000C (private)
┬╖┬╖┬╖
 0020  FF41916C  03DE  00047000     03D4  THESEUS2 #0002 (private)
 0021 free
 0022  FF419194  03DE  0004B000     03D4  THESEUS2 #0002 (private)
┬╖┬╖┬╖
 003B  FF419720  0421  18523000   shared  THESEUSR #0003 (shared)
 003C to 003F (4 frames) are free
 0040  FF40E7EE  0016  FFFB0000   system  os2krnl load image (owner)
┬╖┬╖┬╖
 0229  FF412146  017C  19F40000 inst0114  OS2CHAR  #0000 (private)


ΓòÉΓòÉΓòÉ <hidden> Contents of the SWAPPER.DAT contents (by page) display ΓòÉΓòÉΓòÉ

One line is displayed for each frame in the SWAPPER.DAT file:

Column         Meaning
frame          Disk frame number.  Each frame is 4KB.
vp             The linear address of the Virtual Page Table entry for this
               page.
hob            The hob of the page.
linear         The linear address of the page.
Process        The content of this column is dependent on the type of page:

   hob            This is a page from a private arena. The value is the hob of
                  the PTDA of the process that owns the page.
   shared         This is a shared page from the shared arena.
   insthob        This is an instance data page from the shared arena. The hob
                  is for the PTDA of the process.
   system         This is a page from the system arena.
Description    A description in English of the object.

Frames that are not in use have "free" after the frame number. If there are
multiple free frames together, only one line is shown with the starting and
ending frame numbers. The number of frames is also shown.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory analysis

o Memory addressing


ΓòÉΓòÉΓòÉ 10.3.13. Leak Detection Control... ΓòÉΓòÉΓòÉ

The Leak Detection Control dialog of the Functions pull-down on the Memory Leak
Detection Detail window allows you to control the characteristics of the leak
detection that is taking place. The parameters that can be specified are:

o Use previous sample as base.
o Show data from next collection cycle.
o Show all pages states.


ΓòÉΓòÉΓòÉ <hidden> Use previous sample as base ΓòÉΓòÉΓòÉ

When this option is selected, each periodic update will use the data collected
on the previous cycle as the base data against which the comparison is done.

When this option is not selected, the reference data comes from:

o The data collected when Start Periodic Leak Detection was selected.
o The data collected when Capture Leak Reference Data was selected.


ΓòÉΓòÉΓòÉ <hidden> Show data from next collection cycle ΓòÉΓòÉΓòÉ

When this option is selected, all the data collected is displayed, as well as
any differences.

When this option is not selected, only the differences are shown.


ΓòÉΓòÉΓòÉ <hidden> Show all pages states ΓòÉΓòÉΓòÉ

When this option is selected, the state of every page in the object is shown.
The previous state, the new state and differences are shown on three separate
lines.  There 128 page states shown on each group of three lines.

When this option is not selected, only the page differences are shown.


ΓòÉΓòÉΓòÉ 10.3.14. Start Periodic Leak Detection ΓòÉΓòÉΓòÉ

This option starts a periodic update of the Memory Leak Detection window. The
Options dialog of the Contents Update sub-menu of the Misc pull-down can be
used to select the update interval and window update characteristics.


ΓòÉΓòÉΓòÉ 10.3.15. Stop Periodic Leak Detection ΓòÉΓòÉΓòÉ

This option stops the periodic update of the Memory Leak Detection window.


ΓòÉΓòÉΓòÉ 10.3.16. Capture Leak Reference Data ΓòÉΓòÉΓòÉ

This option causes memory leak detection data to be captured. It can be used
for a later Compare Present Leak Data to generate memory leak detection data.

This option can be used at any time, even when periodic updates are being done.
This data then becomes the reference data for the next update cycle.


ΓòÉΓòÉΓòÉ 10.3.17. Compare Present Leak Data ΓòÉΓòÉΓòÉ

This option causes memory leak detection data to be generated.

This option can be used at any time, even when periodic updates are being done.


ΓòÉΓòÉΓòÉ 10.4. Output ΓòÉΓòÉΓòÉ

The Output pull-down includes options that allow saving or printing the current
display.

Functions available are:

Save as...
          Allows saving the display to a file.
Print all
          Allows printing the display.


ΓòÉΓòÉΓòÉ 10.4.1. Save as... ΓòÉΓòÉΓòÉ

The Save as dialog of the Output pull-down on the Detail window allows you to
save the contents of the window to a file.

To make your selections, either:

o Use the mouse to point to the disk, directory, or file name
o Use the tab key to move between the lists and the up/down arrow keys to move
  within the list.


ΓòÉΓòÉΓòÉ <hidden> Filename: ΓòÉΓòÉΓòÉ

Use this option to specify a file name. If you do not specify a fully qualified
file name, it is qualified with the "Current Directory" displayed above it.

Note:  The name is converted to upper case before using.


ΓòÉΓòÉΓòÉ <hidden> Directories ΓòÉΓòÉΓòÉ

This field displays the list of disks and directories available for selection.
Select one by either:

o Double-clicking mouse button 1
o Moving the cursor (using the up/down arrow keys) and then pressing the Enter
  key.
The file or directory names are retrieved and displayed.


ΓòÉΓòÉΓòÉ <hidden> Files ΓòÉΓòÉΓòÉ

This field displays the list of files in the selected directory. Select one by
single-clicking mouse button 1.

Double-clicking mouse button 1 is equivalent to selecting the file name and
pressing the "Save" key.


ΓòÉΓòÉΓòÉ <hidden> Save ΓòÉΓòÉΓòÉ

When you press the Save button, the window is saved to the specified file.


ΓòÉΓòÉΓòÉ 10.4.2. Print all ΓòÉΓòÉΓòÉ

The Print all option of the Output pull-down on the Detail window allows you to
print the contents of the window.

The output goes to the printer identified as PRN.

If the longest line is more than 80 characters, then a "go to condensed mode"
command (hex 15) is the first character output to the printer. Likewise, a "go
to normal mode" command (hex 18) is the last character output to the printer.


ΓòÉΓòÉΓòÉ 10.5. Mark/Find ΓòÉΓòÉΓòÉ

The Mark/Find pull-down includes options that allow text scans of the display
window and clipboard operations.

Functions available are:

Find...
          Allows finding a specified ASCII string on the display.
Find again
          Repeats the previous find operation, starting with the current cursor
          location.
Mark an area
          Marks an area for storing into the clipboard or printing.
Copy selection to clipboard
          Copies the current marked area into the clipboard.
Print selection
          Prints only the current marked area.


ΓòÉΓòÉΓòÉ 10.5.1. Find... ΓòÉΓòÉΓòÉ

The Find dialog of the Mark/Find pull-down on the Detail window allows you to
find a specified ASCII text string in the information displayed in the window.

There is one entry field on the dialog:

Specify the text to be found:
          Specify the text you wish to search for.

There are two options on the dialog:

Case sensitive?
          Specify case sensitivity of the search.
Move pointer onto found text?
          Specify if the pointer is to be moved.


ΓòÉΓòÉΓòÉ <hidden> Specify the text to be found: ΓòÉΓòÉΓòÉ

Specify the text which you wish to search for. The text must all be on one line
in the window. There are no "wild card" nor "don't care" characters.


ΓòÉΓòÉΓòÉ <hidden> Case sensitive? ΓòÉΓòÉΓòÉ

If this check box is selected, the text is searched using the supplied case.

If this check box is not selected, the text is searched without regard to the
case in both the supplied text and the window text.


ΓòÉΓòÉΓòÉ <hidden> Move pointer onto found text? ΓòÉΓòÉΓòÉ

If this check box is selected, the pointer is moved to the center of the text
which is found.

If this check box is not selected, the pointer is not moved.


ΓòÉΓòÉΓòÉ 10.5.2. Find again ΓòÉΓòÉΓòÉ

The Find again option of the Mark/Find pull-down on the Detail window allows
you to continue the ASCII text scan previously started.

The text scan continues from the current cursor location.


ΓòÉΓòÉΓòÉ 10.5.3. Mark an area ΓòÉΓòÉΓòÉ

The Mark an area option of the Mark/Find pull-down on the Detail window allows
you to mark a rectangle, which can then be copied into the clipboard or
printed.

The current status of this mode is denoted by a check mark on the pull-down.
Selecting this option reverses the setting.

When you select this option, the operation of the buttons on the mouse change.
Position the pointer to one of the corners of the area to be marked. When you
press the button, it marks one corner of the rectangle. As you drag the
pointer, the rectangle is marked out, using the current pointer position as the
"opposite" corner. When you release the button, the rectangle is frozen and the
operation of the buttons reverts back to the default mode.


ΓòÉΓòÉΓòÉ 10.5.4. Copy selection to clipboard ΓòÉΓòÉΓòÉ

The Copy selection to clipboard option of the Mark/Find pull-down on the Detail
window allows you to copy the marked rectangle into the clipboard. The area can
be either the one marked with the Mark an area option or a hyperblock link that
has been selected.

The "text" portion of the clipboard is the only one updated.


ΓòÉΓòÉΓòÉ 10.5.5. Print selection ΓòÉΓòÉΓòÉ

The Print selection option of the Mark/Find pull-down on the Detail window
allows you to send the marked rectangle to the printer. The area can be either
the one marked with the Mark an area option or a hyperblock link that has been
selected.

The output goes to the printer identified as PRN.

If the rectangle is more than 80 characters wide, then a "go to condensed mode"
command (hex 15) is the first character output to the printer. Likewise, a "go
to normal mode" command (hex 18) is the last character output to the printer.


ΓòÉΓòÉΓòÉ 10.6. Misc ΓòÉΓòÉΓòÉ

The Misc pull-down includes options that allow control of double-click
operations and font specification.

Functions available are:

Send output to the same window
          Controls where the output from the mouse button "double-click" is
          sent.
Double-click options...
          Allows control of the action taken when mouse button 1 is
          double-clicked.
Font for this window...
          Specifies an alternate font for this window.
Contents Update
          Specifies control, start and stop of periodic updates.


ΓòÉΓòÉΓòÉ 10.6.1. Send output to the same window ΓòÉΓòÉΓòÉ

The Send output to the same window option of the Control pull-down on the
Detail window allows you to control where the output from mouse button
"double-click" will go.

When this option is chosen, "double-click" output is added to the current
window. A check mark on the pull-down indicates this mode is active.

If this option is not chosen, then "double-click" output is sent to a new
window. No check mark appears on the pull-down when this mode is active.

Initially, the option is not set.


ΓòÉΓòÉΓòÉ 10.6.2. Double-click options... ΓòÉΓòÉΓòÉ

The Double-click options dialog of the Control pull-down on the Detail window
allows you to specify the action taken when you double-click mouse button 1
while the pointer is over the address of a control block that THESEUS2 cannot
format.

The display generated is referred to in the helps as a "General memory
display."


ΓòÉΓòÉΓòÉ <hidden> Modify only this window ΓòÉΓòÉΓòÉ

If you press this button, only the current window has its defaults changed.


ΓòÉΓòÉΓòÉ <hidden> Modify all new windows ΓòÉΓòÉΓòÉ

If you press this button, the current window and all new windows have their
defaults changed.


ΓòÉΓòÉΓòÉ 10.6.3. Font for this Window... ΓòÉΓòÉΓòÉ

When you select the Font for this Window option of the Misc pull-down on the
Detail window, you can specify a different monospace font for the Detail window
being displayed.

THESEUS2 will automatically resize the window if you have not manually changed
the size.


ΓòÉΓòÉΓòÉ 10.6.4. Contents Update ΓòÉΓòÉΓòÉ

When you select the Contents Update option of the Misc pull-down on the Detail
window, you are presented with a sub-menu for specification of control, start
and stop of periodic updates to this window.

Note:  Not all detail windows allow periodic update. Only those that do have
this option enabled.

Functions available are:

Options...
          Presents a dialog to allow control of the update rate and window
          update characteristics.
Start
          Starts the periodic update of the window contents.
Stop
          Stops the periodic update of the window contents.
Refresh now
          Causes an immediate update of the window contents.


ΓòÉΓòÉΓòÉ 10.6.4.1. Options... ΓòÉΓòÉΓòÉ

The Options dialog of the Periodic Update option of the Misc pull-down on the
Detail window allows you to control the update rate and window update
characteristics. The options are:

o Time between updates.
o Replace window contents each time.
o Change cursor shape while updating.
o Scroll the screen when it is updated.
o End of Output control:

   - Never output it.
   - Output it if data was generated.
   - Always output it.


ΓòÉΓòÉΓòÉ 10.6.4.1.1. Time between updates ΓòÉΓòÉΓòÉ

This option specifies the number of minutes and seconds for the detail window
update interval.

The default is 30 seconds. The maximum value is 999 minutes.

The seconds value cannot be typed, only the spin buttons work. The granularity
of the seconds value is determined by the minutes value as follows:

Minutes     Seconds granularity
0           Any second, except 0.
1-4         5.
5-9         10.
10-999      Minutes only.


ΓòÉΓòÉΓòÉ 10.6.4.1.2. Replace window contents each time ΓòÉΓòÉΓòÉ

If this option is selected, the window contents are replace at each interval.
If this option is not selected, the update information is added to the end of
the existing window contents.


ΓòÉΓòÉΓòÉ 10.6.4.1.3. Change cursor shape while updating ΓòÉΓòÉΓòÉ

If this option is selected, the cursor is changed from the "pointer" to the
"clock" whenever the window contents are being recomputed.


ΓòÉΓòÉΓòÉ 10.6.4.1.4. Scroll the screen when it is updated ΓòÉΓòÉΓòÉ

If this option is selected, the window is scrolled so that the last line of
data generated is displayed.


ΓòÉΓòÉΓòÉ 10.6.4.1.5. Never output the End of Output ΓòÉΓòÉΓòÉ

If this option is selected, the End of Output message is never output at the
end of the newly generated information in the window.


ΓòÉΓòÉΓòÉ 10.6.4.1.6. Output the End of Output if data was generated ΓòÉΓòÉΓòÉ

If this option is selected, the End of Output message is output if there were
other information generated in the window.


ΓòÉΓòÉΓòÉ 10.6.4.1.7. Always output the End of Output ΓòÉΓòÉΓòÉ

If this option is selected, the End of Output message is always output, even if
there were no other information generated in the window.


ΓòÉΓòÉΓòÉ 10.6.4.2. Start ΓòÉΓòÉΓòÉ

This option starts a periodic update of the contents of the window. The Options
dialog of the Periodic Update sub-menu of the Misc pull-down can be used to
select the update interval and window update characteristics.


ΓòÉΓòÉΓòÉ 10.6.4.3. Stop ΓòÉΓòÉΓòÉ

This option stops the periodic update of the contents of the window.


ΓòÉΓòÉΓòÉ 10.6.4.4. Refresh now ΓòÉΓòÉΓòÉ

This option causes the window contents to be updated now. The behavior is the
same as if a periodic update had occurred.


ΓòÉΓòÉΓòÉ 10.7. Help ΓòÉΓòÉΓòÉ

The Help pull-down contains the list of the help functions available for the
Detail window.


ΓòÉΓòÉΓòÉ 10.7.1. Explanation of the contents of this window ΓòÉΓòÉΓòÉ

The Explanation of the contents of this window option of the Help pull-down
displays information about the contents of this window.


ΓòÉΓòÉΓòÉ 11. Detail Window Contents ΓòÉΓòÉΓòÉ

The following panels show the content of the various displays presented in the
Detail window.

The following displays are selectable from several sources:

System                  Lists the displays available from the System pull-down.
Process                 Lists the displays available from the Process
                        pull-down.
Registers               Lists the displays available from the Registers
                        pull-down.
Functions               Lists the displays available from the Functions
                        pull-down.
Links                   Lists the displays available only from hyperblock
                        links.
Common Elements         Lists the displays which occur in a variety of places.


ΓòÉΓòÉΓòÉ 11.1. From the System Pull-Down ΓòÉΓòÉΓòÉ

The following panels show the content of the various displays selectable from
the System pull-down on the Process Hierarchy window.

These displays are:

Working Set
          Displays the working set of memory for the entire system.
RAM Usage by Process
          Determines and displays the amount of RAM consumed my each process.
Memory Leak Detection
          Displays the number of pages of memory that each process is
          accumulating.
Free, Idle, and Locked Memory
          Generates the summary information about free, idle and locked pages.
Swapper
          Displays information about the contents of the SWAPPER.DAT file.
General System
          A set of displays containing general system information.
Kernel Information
          A set of displays containing kernel information.


ΓòÉΓòÉΓòÉ 11.1.1. Working Set ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Algorithm

Illustration

Related Topics


ΓòÉΓòÉΓòÉ 11.1.2. RAM Usage by Process ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ 11.1.3. Memory Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.4. Free, Idle, and Locked Memory ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.5. Swapper ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6. General System ΓòÉΓòÉΓòÉ

The General System option contains:

General System Information
          Displays selected general system information.
Device Drivers
          Contains information about all Device Drivers currently loaded.
GDT
          Displays the Global Descriptor Table.
Modules
          Contains information about all modules currently loaded.
System Anchor Segment
          Displays the System Anchor Segment.
Global Info Seg
          Displays the Global Information Segment.
Open Files
          Displays information about the files that are open.
Process List
          Displays a list of all processes that are running.


ΓòÉΓòÉΓòÉ 11.1.6.1. General System Information ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.2. Device Drivers ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.3. GDT ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Descriptor Table Entry Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.4. Modules ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.5. System Anchor Segment ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.6. Global Info Seg ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.7. Open Files ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.6.8. Process List ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.7. Kernel Information ΓòÉΓòÉΓòÉ

The Kernel Information option contains:

Kernel Memory Usage
          Determines and displays the amount of memory consumed by the
          Operating System.
System Object Summary
          Displays the System Object Summary.
System Arena Table
          Displays the System Arena Table.
System Page Table
          Displays the System Page Table.
Page Frame Table
          Displays the Page Frame Table.


ΓòÉΓòÉΓòÉ 11.1.7.1. Kernel Memory Usage ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ 11.1.7.2. Object Summary ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.7.3. System Arena Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Arena Record Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.7.4. System Page Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Page Table Entry Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.1.7.5. Page Frame Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2. From the Process Pull-Down ΓòÉΓòÉΓòÉ

The following panels show the content of the various displays selectable from
the Process pull-down on the Process Hierarchy window.

These displays are:

Working Set
          Displays the working set of memory for the process.
Memory Utilization
          Displays details of memory usage for the process.
Memory Leak Detection
          Displays the number of pages of memory that each object is
          accumulating.
General Process Information
          Displays general information about the process.
Per Task Data Area (PTDA)
          Displays the PTDA.
LDT
          Displays the LDT.
Page Table
          Displays the process unique Page Table.
Private Object Summary
          Displays a summary of the private arena memory objects.
Shared Object Summary
          Displays a summary of the shared arena memory objects.
Private Arena Table
          Displays the process unique arena table.
Shared Arena Table
          Displays the shared arena, in the process' context.


ΓòÉΓòÉΓòÉ 11.2.1. Working Set ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Algorithm

Illustration

Related Topics


ΓòÉΓòÉΓòÉ 11.2.2. Memory Utilization ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Algorithm

Related Topics


ΓòÉΓòÉΓòÉ 11.2.3. Memory Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.4. General Process Information ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.5. Per Task Data Area (PTDA) ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.6. LDT ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Descriptor Table Entry Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.7. Page Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Page Table Entry Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.8. Private Object Summary ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.9. Shared Object Summary ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.10. Private Arena Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Arena Record Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.2.11. Shared Arena Table ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Arena Record Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.3. From the Registers Pull-Down ΓòÉΓòÉΓòÉ

The following panels show the content of the various displays selectable from
the Registers pull-down on the Process Hierarchy window.

These displays are:

Control Registers
          Displays the iAPX 386 control registers.
Current IDT
          Displays the current Interrupt Descriptor Table.
Current TSS
          Displays the current Task State Segment.


ΓòÉΓòÉΓòÉ 11.3.1. Control Registers ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.3.2. IDT ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Descriptor Table Entry Description

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.3.3. Task State Segment ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Task State Segment ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the TSS Display ΓòÉΓòÉΓòÉ

You may either select the Current TSS option of the System pull-down on the
Process Hierarchy window to see the current TSS or select a hyperblock link
from another window to see a specific TSS.


ΓòÉΓòÉΓòÉ 11.4. From Functions Pull-Down ΓòÉΓòÉΓòÉ

The following panels show the content of the various displays selectable from
the Functions pull-down on the Detail window.

Displays are:

General Linear Memory
          Displays memory at a specified linear address.
General Virtual Memory
          Displays memory at a specified virtual address.
General Physical Memory
          Displays memory at a specified physical address.
Show Working Set detail (by Page)
          Shows which pages made up the working set.
Show Working Set detail (by Object)
          Shows which objects made up the working set.
Show summary by Process
          Show a summary of the working set information, summarized by process.
Show SWAPPER.DAT detail (by Page)
          Shows which pages make up the SWAPPER.DAT file.
Memory Object Leak Detection
          Performs memory leak detection on a single memory object.


ΓòÉΓòÉΓòÉ 11.4.1. General Linear Memory Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the General Linear Memory Display ΓòÉΓòÉΓòÉ

You may either select the Show memory at linear address option on the Functions
pull-down on the Detail window to get a dialog so that you may enter a specific
linear address or select a linear address hyperblock link from another window
that THESEUS2 cannot explicitly format.


ΓòÉΓòÉΓòÉ <hidden> Example of the General Linear memory display ΓòÉΓòÉΓòÉ

Memory from Linear address FEB5F498 for 40 bytes for process 'system':
FEB5F498 (0000)  00 00 50 07 80 80 00 00  00 00 54 48 45 53 45 55 *..P.......THESEU*
FEB5F4A8 (0010)  32 24 98 07 78 07 00 00  00 00 54 00 C8 0F 92 03 *2$..x.....T.....*
FEB5F4B8 (0020)  B8 04 82 00 EA 9D 1F 00  00 00 17 04 00 14 A0 07 *................*
FEB5F4C8 (0030)  A8 07 B0 07 B8 07 C0 07  40 00 FF 1F 00 60 EC FF *........@....`..*

The above is the same memory as the Device Driver Header example.

Memory from Linear address FE984D84 for E bytes for process 'system':
FE984D84 (0000) 89 1E 1E 00       *....*   mov      [1E],bx
FE984D88 (0004) 8C 06 20 00       *.. .*   mov      [20],es
FE984D8C (0008) 26 8A 47 02       *&.G.*   mov      al,es:[bx+2]
FE984D90 (000C) 3C 00             *<.*     cmp      al,0


ΓòÉΓòÉΓòÉ <hidden> Contents of the General Linear memory display ΓòÉΓòÉΓòÉ

For hex mode, the memory is presented as follows:

address    The linear address of the byte that begins the line.
hex        There are three formats for this data:

   byte           Each byte is formatted individually.
   word           Each word (2 bytes) is formatted individually. "Byte
                  reversal" is done.
   doubleword     Each doubleword (4 bytes) is formatted individually. "Byte
                  reversal" is done.
ASCII      The character representation of the memory area. "Byte reversal" is
           not done.

For disassemble mode, the memory is presented as follows:

address      The linear address of the byte that begins the line.
hex          Each byte is formatted individually.
ASCII        The character representation of the memory area.
instruction  The disassembled instruction, using MASM mnemonics.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Description of Linear Object


ΓòÉΓòÉΓòÉ 11.4.2. General Virtual Memory Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the General Virtual Memory Display ΓòÉΓòÉΓòÉ

You may either select the Show memory at virtual address option on the
Functions pull-down on the Detail window to get a dialog so that you may enter
a specific virtual address or select a virtual address hyperblock link from
another window that THESEUS2 cannot explicitly format.


ΓòÉΓòÉΓòÉ <hidden> Example of the General Virtual Memory Display ΓòÉΓòÉΓòÉ

Memory from Virtual address 0778:00000000 for 1A bytes for process 'system':
0778:0000  00 00 50 07 80 80 00 00  00 00 54 48 45 53 45 55 *..P.......THESEU*
0778:0010  32 24 98 07 78 07 00 00  00 00                   *2$..x.....*

The above is the same memory as the Device Driver Header example.

Memory from Virtual address 0798:00000000 for 22B bytes for process 'system':
0798:0000 89 1E 1E 00       *....*   mov      [1E],bx
0798:0004 8C 06 20 00       *.. .*   mov      [20],es
0798:0008 26 8A 47 02       *&.G.*   mov      al,es:[bx+2]
0798:000C 3C 00             *<.*     cmp      al,0


ΓòÉΓòÉΓòÉ <hidden> Contents of the General Virtual Memory Display ΓòÉΓòÉΓòÉ

For hex mode, the memory is presented as follows:

address    The virtual address of the byte that begins the line.
hex        There are three formats for this data:

   byte           Each byte is formatted individually.
   word           Each word (2 bytes) is formatted individually. "Byte
                  reversal" is done.
   doubleword     Each doubleword (4 bytes) is formatted individually. "Byte
                  reversal" is done.
ASCII      The character representation of the memory area. "Byte reversal" is
           not done.

For disassemble mode, the memory is presented as follows:

address      The virtual address of the byte that begins the line.
hex          Each byte is formatted individually.
ASCII        The character representation of the memory area.
instruction  The disassembled instruction, using MASM mnemonics.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses


ΓòÉΓòÉΓòÉ 11.4.3. General Physical Memory Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the General Physical Memory Display ΓòÉΓòÉΓòÉ

You may either select the Show memory at physical address option on the
Functions pull-down on the Detail window to get a dialog so that you may enter
a specific physical address or select a physical address hyperblock link from
another window that THESEUS2 cannot explicitly format.


ΓòÉΓòÉΓòÉ <hidden> Example of the General Physical Memory Display ΓòÉΓòÉΓòÉ

Memory from Physical address 006A7498 for 40 bytes for process 'system':
006A7498 (0000)  00 00 50 07 80 80 00 00  00 00 54 48 45 53 45 55 *..P.......THESEU*
006A74A8 (0010)  32 24 98 07 78 07 00 00  00 00 54 00 C8 0F 72 03 *2$..x.....T...r.*
006A74B8 (0020)  B8 04 82 00 36 A1 1F 00  00 00 0F 04 00 14 A0 07 *....6...........*
006A74C8 (0030)  A8 07 B0 07 B8 07 C0 07  40 00 FF 1F 00 60 EC FF *........@....`..*

The above is the same memory as the Device Driver Header example.

Memory from Physical address 0068FD84 for E bytes for process 'system':
0068FD84 (0000) 89 1E 1E 00       *....*   mov      [1E],bx
0068FD88 (0004) 8C 06 20 00       *.. .*   mov      [20],es
0068FD8C (0008) 26 8A 47 02       *&.G.*   mov      al,es:[bx+2]
0068FD90 (000C) 3C 00             *<.*     cmp      al,0


ΓòÉΓòÉΓòÉ <hidden> Contents of the General Physical Memory Display ΓòÉΓòÉΓòÉ

For hex mode, the memory is presented as follows:

address    The physical address of the byte that begins the line.
hex        There are three formats for this data:

   byte           Each byte is formatted individually.
   word           Each word (2 bytes) is formatted individually. "Byte
                  reversal" is done.
   doubleword     Each doubleword (4 bytes) is formatted individually. "Byte
                  reversal" is done.
ASCII      The character representation of the memory area. "Byte reversal" is
           not done.

For disassemble mode, the memory is presented as follows:

address      The physical address of the byte that begins the line.
hex          Each byte is formatted individually.
ASCII        The character representation of the memory area.
instruction  The disassembled instruction, using MASM mnemonics.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Physical addresses


ΓòÉΓòÉΓòÉ 11.4.4. Detail of Working Set (by Page) Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.4.5. Detail of Working Set (by Object) Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.4.6. Detail of Summary by Process Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.4.7. SWAPPER.DAT Contents (by Page) Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.4.8. Memory Object Leak Detection ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ 11.5. From Links ΓòÉΓòÉΓòÉ

The following panels show the content of displays that are displayed only from
hyperblock links.

Displays are:

Device Driver Header
          Displays the contents of a single Device Driver's header.
Virtual Address Memory
          Displays the contents of a segment in memory.
Show description of an object
          Displays the "description" of a memory object.
Show description of a segment
          Displays the "description" of a segment.
Physical description
          Displays the "description" of a physical page of memory.
Detail for System Owner
          Displays the list of memory objects that make up a particular system
          owner.
Arena Record
          Displays a single Arena Record.
Object Record
          Displays a single Object Record.
Context Record
          Displays a single Context Record.
Virtual Page Table entry
          Shows a single Virtual Page Table entry.
MTE display
          Displays a single MTE.
TCB display
          Displays a single TCB.
Detail Working Set information for an Object
          Displays the pages that make up the object and their relation in the
          working set.
SFT display
          Displays a single System File Table entry.
Detailed Memory Assignment Information
          Displays detail of several memory analysis displays.


ΓòÉΓòÉΓòÉ 11.5.1. Device Driver Header Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Device Drivers Header Display ΓòÉΓòÉΓòÉ

This is selected by the hyperblock link of the Header addr field on the Device
Drivers display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Device Driver Header Display ΓòÉΓòÉΓòÉ

Device Driver header located at 0778:0000:
Next DD header @ 0750:0000
Device attribute = 8080 => CHR LVL=OS/2
Offset to Strategy Routine = 0000
Offset to IDC Routine      = 0000
Device name = 'THESEU2$'
Code Selector = 0798
Data Selector = 0778
Reserved_3 = 0000
Reserved_4 = 0000


ΓòÉΓòÉΓòÉ <hidden> Contents of the Device Driver Header Display ΓòÉΓòÉΓòÉ

The fields of the device driver header are displayed as follows:

Device Driver header located at ssss:oooo:
          The address of this device driver header.
Next DD header @ ssss:oooo
          The device drivers are linked together. This is the address of the
          next one.
Device attribute = hhhh => decoded attributes
          The attributes are printed in hex and then presented in English as
          follows:

   CHR   Bit 15 - The device is a character device. Otherwise, it is a block
         device.
   IDC   Bit 14 - The device supports "Inter-device Driver Communication". If
         this is set, then the IDC Entry Point value must be valid.
   IBM   Bit 13 - The device is non-IBM block format.
   SHR   Bit 12 - The device supports "shared device access checking".
   OPN   Bit 11 - The device supports removable media (block devices) or device
         open/close (character devices).
   LVL   Bits 9-7 - Function level of support:

      PC/DOS    000 - PC/DOS device driver.  (This should never be seen in OS/2
                2.0.)
      OS/2      001 - OS/2 device driver, which does not support DosDevIOCTL2
                packets.
      IOCTL2    010 - OS/2 device driver, which supports DosDevIOCTL2 and
                SHUTDOWN request packets.
      BitStrip  011 - OS/2 device driver, with a Capabilities Bit Strip in the
                header.
      ??        Level was not one of the above. The level value is printed.
   CLK   Bit 3 - The device is the CLOCK device.
   NUL   Bit 2 - The device is the NULL device.
   SCR   Bit 1 - The device is the SCREEN (STDOUT).
   KBD   Bit 0 - The device is the KEYBOARD (STDIN).
Offset to Strategy Routine = hhhh
          The offset into the device driver's code segment where the Strategy
          Routine starts.
Offset to IDC Routine = hhhh
          The offset into the device driver's code segment where the IDC
          Routine starts.
Device name = 'name'
          The name of the (character) device.
Number of units supported = i (integer)
          The number of units supported by the (block) device.
Code Selector = ssss
          The selector of the code segment.
Data Selector = ssss
          The selector of the data segment.
Reserved_3 = hhhh
          The third "reserved word" in the device driver header.
Reserved_4 = hhhh
          The fourth "reserved word" in the device driver header.
Bit Strip = hhhhhhhh
          The hex value of the Bit Strip and then presented in English:

   parallel        The physical device driver supports parallel ports.
   32-bit          For character device drivers, this bit is set to 1 if memory
                   addressing above 16MB is supported; that is, support for
                   full 32-bit memory addressability instead of 24-bit memory
                   addressability. For block device drivers, this bit is
                   reserved and must be set to 0.
   DosDevIOCtl2    The DosDevIOCtl2 and SHUTDOWN request packets are supported.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Device Drivers


ΓòÉΓòÉΓòÉ 11.5.2. Description of Linear Object Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Description of Linear Object Display ΓòÉΓòÉΓòÉ

The Description of Linear Object display is selected by double-clicking mouse
button 2, with the pointer over any linear address for which a hyperblock link
is defined.

If the linear address is not a system arena address, then a process context
should be set (by selecting a particular process).

If a context is not specified, or the context is sysinit, then the Page Tables
for all processes are shown.


ΓòÉΓòÉΓòÉ <hidden> Example of the Description of Linear Object Display ΓòÉΓòÉΓòÉ

Description of Linear Object 1B4A0000, process = 'THESEUS2':
It is object # 0002 from module PMDRAG.

Arena Record:
 har    pages   linear flg next prev link hash hob  hal  hco  / Decoded flags
016F 00000010 1B4A0000 3D9 016E 0170 0000 0000 019D 0000 03D9 / Mapped Reload User Exec Read Hco

Object Record:
 hob   har next  flgs ownr hmte  sown,cnt lt ld st sd / owner / decoded_flags
019D  016F 0000  0838 019B 019B  0000 00  00 00 00 00 / m-PMDRAG / shared exec read user

Context Record(s):
 hco  next ptda flgs / process / decoded_flags
03D9  01FB 0290  1C  / THESEUS2 / read exec user
01FB  0113 01D4  1C  / PMEXEC / read exec user
0113  0000 00EF  1D  / PMSHELL / read exec user originator

Page Table, from 1B4A0000 to 1B4AFFFF:
*Linear=1B400000 Physical=0019C000 D=1 A=1 User  R/W P=1 Resident
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0001 fast
  hob=0067 refCount=0001 relPage=02ED block#=0019C flag=0010 / pf
 Linear=1B4A0000 FrameId=005CB     D=0 A=0 User  R/O P=0
  hob=019D refCount=0003 relPage=0000 block#=00008 flag=0800 / discardable
 Linear=1B4A1000 FrameId=005CC     D=0 A=0 User  R/O P=0
  hob=019D refCount=0003 relPage=0001 block#=00009 flag=0800 / discardable
 Linear=1B4A2000 Invalid page      D=0 A=0 Super R/O P=0
   Linear addresses 1B4A2000 to 1B4AF000 (14 pages) as last PTE above.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Description of Linear Object Display ΓòÉΓòÉΓòÉ

The information presented on the Description of Linear Object display follows:

 1. The linear address and context (denoting a particular process) of the
    memory object.
 2. A high-level statement describing the memory object:

   It is object # hhhh from module aaaaaaaa.
             The name of the module (either .EXE or .DLL) and the relative
             object number within the module. This object number will match the
             one produced and printed by the linker.
   It was allocated by aaaaaaaa.
             This memory was allocated by the indicated module.
   It is 'aaaaaaaa' (decoded hmte from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the hmte.
   It is 'aaaaaaaa' (decoded owner from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the owner.

 3. The decoded arena record.
 4. The decoded object record.
 5. The decoded context record(s) (if this is a shared arena address).
 6. The decoded Page Table over the linear address range of the object. For
    each page in the object (PDEs are shown when displaying from a new Page
    Table), the following items are shown:

   o The PTE.
   o The Page Frame Table entry for the PTE (if the page is present).
   o The Virtual Page Table entry for the PTE.

    If a context has not been specified, or the context is sysinit, then the
    Page Tables for all processes are shown.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Handles

o Memory Management Control Blocks


ΓòÉΓòÉΓòÉ <hidden> Page Frame Table entry ΓòÉΓòÉΓòÉ

The fields of the Page Frame Table entry are decoded:

Term                Meaning
pteCnt=hhhh         The number of PTEs that refer to this page as being
                    present.
long_lock=hhhh      The number of long-term locks outstanding for this page.
short_lock=hhhh     The number of short-term locks outstanding for this page.
block=hhhhh         Pager disk frame or loader block number
flags=hhhh          Flags indicating the status of the page. They are shown as
                    hex and then decoded into ASCII:

   fast        Page is in fast memory.
   busy        Page is busy.
   free        Page is on the free chain.
   reserved?   Reserved bit.


ΓòÉΓòÉΓòÉ 11.5.3. Description of Segment Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Description of Segment Display ΓòÉΓòÉΓòÉ

The Description of Segment display is selected by double-clicking mouse
button 2, with the pointer over any virtual address or selector for which a
hyperblock link is defined.

If the virtual address is not a system arena address, then a process context
must be set (by selecting a particular process).


ΓòÉΓòÉΓòÉ <hidden> Example of the Description of Segment Display ΓòÉΓòÉΓòÉ

Description of Segment w/ selector = 0010, process = 'system'

Descriptor Table Entry:
GDT(0010) BTSS32  Base=FFE42DC8 Limit=00067 DPL=0               P=1 G=0

Description of Linear Object FFE42DC8, process = 'system':
It is object # 0001 from module DOSCALLS.

Arena Record:
 har    pages   linear flg next prev link hash hob  hal  sel  / Decoded flags
0007 0000000B FFE3D000 009 0008 0014 0000 0000 0008 0000 0400 / Mapped

Object Record:
 hob   har next  flgs ownr hmte  sown,cnt lt ld st sd / owner / decoded_flags
0008  0007 0000  0000 FFAA 0006  0000 00  00 00 00 00 / os2krnl load image /

Page Table, from FFE42DC8 to FFE42E2F:
*Linear=FFC00000 Physical=00190000 D=0 A=1 User  R/W P=1 Resident
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0000
  hob=0019 refCount=0001 relPage=027F block#=00190 flag=0410 / pf resident
 Linear=FFE42000 Physical=00009000 D=1 A=1 User  R/W P=1 Resident
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0000
  hob=0008 refCount=0001 relPage=0005 block#=00009 flag=0410 / pf resident


ΓòÉΓòÉΓòÉ <hidden> Contents of the Description of Segment Display ΓòÉΓòÉΓòÉ

The information presented on the Description of Segment display follows:

 1. The selector and context (denoting a particular process) of the segment.
 2. The Descriptor Table Entry for the selector.
 3. The linear address and context (denoting a particular process) of the
    memory object.
 4. A high-level statement describing the memory object:

   It is object # hhhh from module aaaaaaaa.
             The name of the module (either .EXE or .DLL) and the relative
             object number within the module. This object number will match the
             one produced and printed by the linker.
   It was allocated by aaaaaaaa.
             This memory was allocated by the indicated module.
   It is 'aaaaaaaa' (decoded hmte from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the hmte.
   It is 'aaaaaaaa' (decoded owner from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the owner.

 5. The decoded arena record.
 6. The decoded object record.
 7. The decoded context record(s) (if this is a shared arena address).
 8. The decoded Page Table over the linear address range of the object. For
    each page in the object (PDEs are shown when displaying from a new Page
    Table), the following items are shown:

   o The PTE.
   o The Page Frame Table entry for the PTE (if the page is present).
   o The Virtual Page Table entry for the PTE.

    If a context has not been specified, or the context is sysinit, then the
    Page Tables for all processes are shown.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Virtual addresses

o Linear addresses

o Handles

o Memory Management Control Blocks


ΓòÉΓòÉΓòÉ 11.5.4. Description of Physical Object Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Description of Physical Object Display ΓòÉΓòÉΓòÉ

The Description of Physical Object display is selected by double-clicking mouse
button 2, with the pointer over any physical address for which a hyperblock
link is defined.


ΓòÉΓòÉΓòÉ <hidden> Example of the Description of Physical Object Display ΓòÉΓòÉΓòÉ

Description of Physical Object 0018F000:

Start from the bottom (Page Frame Table) and go up:

Page Frame Table entry:
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0000

Virtual Page Table entry (FrameId=00A9):
  hob=0014 refCount=0001 relPage=0000 block#=0018F flag=0410 / pf resident

Object Record:
 hob   har next  flgs ownr hmte  sown,cnt lt ld st sd / owner / decoded_flags
0014  0013 0000  0000 FFB1 0000  0000 00  00 00 00 00 / PG Page directory /

Arena Record:
 har    pages   linear flg next prev link hash hob  hal  sel  / Decoded flags
0013 00000001 FF420000 001 0017 0018 0000 0000 0014 0000 0000 /

=============================================================================
Now, go from the top (Arena's) down:

See if it is a page in the 'system' arena.
-----------------------------------------------------------------------------
Description of Linear Object FF420000, process = 'system':

Arena Record:
 har    pages   linear flg next prev link hash hob  hal  sel  / Decoded flags
0013 00000001 FF420000 001 0017 0018 0000 0000 0014 0000 0000 /

Object Record:
 hob   har next  flgs ownr hmte  sown,cnt lt ld st sd / owner / decoded_flags
0014  0013 0000  0000 FFB1 0000  0000 00  00 00 00 00 / PG Page directory /

Page Table, from FF420000 to FF420FFF:
*Linear=FF400000 Physical=00191000 D=0 A=1 User  R/W P=1 Resident
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0000
  hob=0019 refCount=0001 relPage=027D block#=00191 flag=0410 / pf resident
 Linear=FF420000 Physical=0018F000 D=1 A=1 User  R/W P=1 Resident
  pteCnt=0001 long_lock=0000 short_lock=0000 block=00000 flags=0000
  hob=0014 refCount=0001 relPage=0000 block#=0018F flag=0410 / pf resident
=============================================================================
The page in each Process context in which it exists.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Description of Physical Object Display ΓòÉΓòÉΓòÉ

The page address specified is described in three ways:

o From the Page Frame Table, looking up through the Virtual Page Table to an
  object record to an arena record.
o From the system arena, looking down through the arena record to the object
  record and Page Table.
o From the shared and private arenas of each process, looking down through the
  arena record to the object record and Page Table.

The information presented on the Description of Physical Object display
follows:

 1. The physical address of the page being "described."
 2. The Page Frame Table entry for the page.
 3. The Virtual Page Table entry for the page.
 4. The decoded object record.
 5. The decoded arena record.
 6. The linear address and context (denoting a particular process) of the
    memory object.
 7. A high-level statement describing the memory object:

   It is object # hhhh from module aaaaaaaa.
             The name of the module (either .EXE or .DLL) and the relative
             object number within the module. This object number will match the
             one produced and printed by the linker.
   It was allocated by aaaaaaaa.
             This memory was allocated by the indicated module.
   It is 'aaaaaaaa' (decoded hmte from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the hmte.
   It is 'aaaaaaaa' (decoded owner from object record).
             `aaaaaaaa' is the name of a system resource, obtained by decoding
             the owner.

 8. The decoded arena record.
 9. The decoded object record.
10. The decoded context record(s) (if this is a shared arena address).
11. The decoded Page Table over the linear address range of the object. For
    each page in the object (PDEs are shown when displaying from a new Page
    Table), the following items are shown:

   o The PTE.
   o The Page Frame Table entry for the PTE (if the page is present).
   o The Virtual Page Table entry for the PTE.

Items 6-11 are repeated for every process that has the specified page in its
Page Tables.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Physical addresses

o Handles

o Memory Management Control Blocks


ΓòÉΓòÉΓòÉ 11.5.5. Detail for System Owner Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detail for System Owner Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link from the owner column of the Kernel
Memory Usage display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Detail for System Owner Display ΓòÉΓòÉΓòÉ

Detail Kernel Memory assignment information, owner = FF6B:
This owner is 'allocated via devhlp AllocPhys'.
There are 2 objects which make up this System Owner.
  1. Object at linear address 7C673000, pages present = 640.
  2. Object at linear address 7D0BD000, pages present = 16.


ΓòÉΓòÉΓòÉ <hidden> Contents of the Detail for System Owner Display ΓòÉΓòÉΓòÉ

One line is displayed for each memory object that makes up the specified system
owner:

i. Object at linear address llllllll, pages present = nnn.
          The base linear address of the memory object. The letter i indicates
          the line number in the list. The nnn is the number of pages that are
          present in RAM for this object.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Linear addresses

o Memory Management Control Blocks

o System Memory Usage


ΓòÉΓòÉΓòÉ 11.5.6. Arena Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Arena Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Arena Record Display ΓòÉΓòÉΓòÉ

Arena records are displayed by selecting a hyperblock link from a har field of
some display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Arena Record Display ΓòÉΓòÉΓòÉ

A private arena record looks like:

 har    pages   linear flg next prev link hash hob  hal  ptda / Decoded flags
0252 00000020 00010000 1D9 0243 024D 0000 0000 025F 0000 0301 / Mapped Reload User Exec Read

A shared arena record looks like:

 har    pages   linear flg next prev link hash hob  hal  hco  / Decoded flags
02C5 00000010 1AB60000 369 02AE 0005 0000 0000 030F 0000 04E2 / Mapped Write User Read Hco

A system arena record looks like:

 har    pages   linear flg next prev link hash hob  hal  sel  / Decoded flags
0210 00000400 7C000000 001 0272 0004 0000 007A 0270 0000 0000 /


ΓòÉΓòÉΓòÉ <hidden> Contents of the Arena Record Display ΓòÉΓòÉΓòÉ

The arena record displayed contains the following entries:

Column           Meaning
har              The har of the displayed arena record.
pages            The number of pages allocated in the memory object. The number
                 of committed pages may be less than this.
linear           The linear address of the start of the memory object.
flg              Flags to indicate the status of the memory Object. They are
                 decoded into English at the end of the line.
next             The next arena record in the doubly linked chain. The arena
                 records are linked in ascending order of the linear address of
                 the memory object.
prev             The previous arena record in the doubly linked chain.
link             The har of an arena record that is an alias for the memory
                 object.
hash             Link to hash table.
hob              The hob of the object record associated with this memory
                 object.
hal              Alias record handle.
ptda             (private arena) The hob of the PTDA of the process that owns
                 the memory object.
hco              (shared arena) The first hco in a chain of context records for
                 the memory object.
sel              (system arena) The GDT selector that points to the memory
                 object.
Decoded flags    The flags are decoded into readable form:

   Mapped    A selector maps this memory object.
   Reload    Loader flag.
   Write     The object is writable.
   User      The object has user pages
   Exec      The object has executable pages.
   Read      The object has readable pages
   Hco       For a shared arena record, this indicates that there is an entry
             in the hco field.
   Guard     The object has guard pages.
   SGS       The object is registered under Screen Group Switch control.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory Management Control Blocks

o Handles


ΓòÉΓòÉΓòÉ 11.5.7. Object Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Object Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Object Record Display ΓòÉΓòÉΓòÉ

Object records are displayed by selecting a link from a hob field of some
display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Object Record Display ΓòÉΓòÉΓòÉ

A real memory object looks like:

 hob   har next  flgs ownr hmte  sown,cnt lt st / owner / decoded_flags
0252  0259 0000  0838 025F 025F  0000 00  00 00 / m-THESEUS2 / shared exec read user

A pseudo-object looks like:

 hob   linear    flgs ownr hmte  sown,cnt lt st / owner / decoded_flags
0294  7D3211D0   8000 FFE1 025F  0000 00  00 00 / VM arena header / Pseudo-object


ΓòÉΓòÉΓòÉ <hidden> Contents of the Object Record Display ΓòÉΓòÉΓòÉ

The object record displayed contains the following entries:

Column           Meaning
hob              The hob of the displayed object record.
har              The har of the arena record associated with this object
                 record.
next             The next object record in the chain for this memory object.
linear           The linear address of the pseudo-object.
flgs             Flags to indicate the status of the memory object. They are
                 decoded into English at the end of the line.
ownr             Objects have owners. This is the hob of the owner.
hmte             The hmte that allocated the memory object.
sown             ID of thread owning the semaphore.
cnt              Counter and waiting flag associated with sown.
lt               Number of long-term locks that are outstanding.
st               Number of short-term locks that are outstanding.
owner            The name of the owner in ASCII.
decoded_flags    The flags are decoded into readable form:

   Pseudo-object The object is a pseudo-object. The linear address of the
              object is contained in the object record.
   API_allocated_object Object was allocated by an application.
   lock       Some thread to wake in VMUnlock.
   aliases    The object has aliases.
   shared     The object's contents are shared.
   UVirt      UVirt object.
   zero-init  Object is zero-initialized.
   resident   The object is to remain resident. It is not allowed to be paged
              out.
   low memory The object's memory is to be allocated from low memory.
   guard      The object has guard pages.
   exec       The object has executable pages
   read       The object has readable pages
   user       The object has user pages.
   write      The object has writable pages.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory Management Control Blocks

o Handles


ΓòÉΓòÉΓòÉ 11.5.8. Context Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Context Record Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Context Record Display ΓòÉΓòÉΓòÉ

Context records are displayed by selecting a hyperblock link from an hco field
of some display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Context Record Display ΓòÉΓòÉΓòÉ

 hco  next ptda flgs / process / decoded_flags
0472  02C6 0283  16  / THESEUS2 / read user write


ΓòÉΓòÉΓòÉ <hidden> Contents of the Context Record Display ΓòÉΓòÉΓòÉ

The context record displayed contains the following entries:

Column            Meaning
hco               The hco of the displayed context record.
next              The hco of the next context record in the chain. The last
                  context record has a next field of 0000.
ptda              The hob of the PTDA which has access to the shared memory
                  object.
flgs              The flag byte is presented in hex. It is decoded into English
                  at the end of the line.
process           The name of the process referred to by the PTDA handle.
decoded_flags     The flags are decoded into readable form:

   privatized  The context is privatized.
   guard       The object has guard pages.
   read        Object is readable from this process.
   exec        Object is executable from this process.
   user        The object has user pages.
   write       Object is writable from this process.
   originator  This process that originally allocated the object.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory Management Control Blocks

o Handles


ΓòÉΓòÉΓòÉ 11.5.9. Virtual Page Table Entry Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Virtual Page Table Entry Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Virtual Page Table Entry Display ΓòÉΓòÉΓòÉ

Virtual Page Table entries are displayed by selecting a hyperblock link from a
vp field of the Page Frame display.

They also appear a number of other displays.


ΓòÉΓòÉΓòÉ <hidden> Example of the Virtual Page Table Entry Display ΓòÉΓòÉΓòÉ

Virtual Page Table entry at FF40F064:
  hob=0007 refCount=0001 relPage=0001 block#=00002 flag=0410 / pf resident


ΓòÉΓòÉΓòÉ <hidden> Contents of the Virtual Page Table entry display ΓòÉΓòÉΓòÉ

The fields of the Virtual Page Table entry are decoded:

Term             Meaning
hob=oooo         The hob of the memory object that this page is a part of.
refCount=hhhh    The number of objects that refer to this page.
relPage=hhhh     The relative page number within the object.
block#=hhhhh     Pager disk frame or loader block number for pages which are
                 not in RAM. The physical page number of pages which are in
                 RAM.
flag=hhhh        Flags indicating the status of the virtual page. They are
                 shown as hex and then decoded into ASCII:

   busy          Page semaphore is taken.
   wanted        Page semaphore has been requested.
   cache         Search page cache for the page.
   pfidle        Cross linked to an idle page frame.
   pf            Cross linked to a page frame.
   swapped       Has a swap file disk frame.
   dirty         Page contents have been written to.
   shdirty       Shadow dirty bit (for VDMs).
   sow           Change to swappable on write.
   resident      Cannot be moved or paged.
   discardable   Page is discardable.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Handles


ΓòÉΓòÉΓòÉ 11.5.10. MTE Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the MTE Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link from the MTE @ column of the Modules
display.


ΓòÉΓòÉΓòÉ <hidden> Example of the MTE Display ΓòÉΓòÉΓòÉ

Resident portion of MTE (@ FEB717E8):
Use count = 1
Number of entries in Imp Mod Name Tbl = 5
Module name @ FEB71820 -> THESEUS2
Module pointers table @ FEB71808
Handle of the mte = 0345
File system number for open file = 0077
Link to next mte = FEB71B18
Link to swappable mte = FE5BA250
Signature = LX
Flags = 04903142
  Class = Program
  File Media permits discarding
  Program module

Swappable portion of MTE (@ FE5BA250):
Module # pages = 0000003C
Initial instruction pointer = 0001:00026634
Initial stack       pointer = 0002:0001B100
Fixup section size = 00009440
Object table offset = FE5BA305
Number of objects in module = 00000002
Object page map offset = FE5BA335
Object iterated data map offset = 00000000
Offset of Resource Table = 00000000
Number of resource entries = 00000000
Offset of resident name table = FE5BA515
Offset of Entry Table = FE5BA521
Offset of Fixup Page Table = FE5BA522
Offset of Fixup Record Table = FE5BA616
Offset of Import Module Name Table = FE5C393D
Offset of Imp Procedure Name Table = FE5C3962
Offset of Enumerated Data Pages = 00009800
Number of preload pages = 00000000
Offset of Non-resident Names Table = 00044400
Size of Non-resident Name Table = 00000042
Object # for automatic data object = 00000002
Offset of the debugging info = 00000000
The length of the debug info in bytes = 00000000
Number of instance pages in preload section = 00000000
Use for converted 16-bit modules = 00000000 (heapsize)
Full pathname = FE5BA2EC -> E:\THESEUS2\THESEUS2.EXE
Length of pathname = 0018
Used by dynamic trace = 0000
Count of threads waiting on MTE semaphore = 0
Slot number of the owner of the MTE semaphore = 0000
Pointer to preload pages = 00000000
Start of object with preload pages = FDD09000
Size  of object with preload pages = 00000000
Pointer to file cache for Dos32CacheModule= 00000000
Use for converted 16-bit modules = 0000 (alignshift)
Use for converted 16-bit modules = 0000 (stacksize)
Original flags from NE header = 0000
expver from NE header = 0000
exetype from NE header = 0000
Original other flags from NE header = 0000
Number of preload pages used = 00

Object Table:
Obj#   address      size   hob   sel  page map  map size     flags / flags...
0001  00010000  0002A579  035D  000F  00000001  0000002B  80002025 / readable executable shared 32-bit
0002  00040000  0001B100  0000  0027  0000002C  00000011  80002003 / readable writeable 32-bit


ΓòÉΓòÉΓòÉ <hidden> Contents of the MTE Display ΓòÉΓòÉΓòÉ

The MTE is in two sections: resident and swappable. They are displayed as
follows:

The resident portion of the MTE is as follows:

Resident portion of MTE (@ llllllll):
          The linear address of the resident portion of the MTE.
Use count = i
          Number of times a DosLoadModule function has been done for this
          module.
Number of entries in Imp Mod Name Tbl = i
          Number of entries in Import Module Name Table.
Module name @ llllllll -> 'name'
          The linear address of the module name, followed by the name in ASCII.
          (Only the linear address is in the MTE; THESEUS2 retrieves the
          contents of the ASCII string that is pointed to.)
Module pointers table @ llllllll
          Pointer to the Module Pointers Table.
Handle of the mte = oooo
          The hob of this MTE.
File system number for open file = hhhh
          System file number for the open .EXE or .DLL program file.
Link to next mte = llllllll
          Linear address of the next MTE in the chain.
Link to swappable mte = llllllll
          Linear address of the swappable portion of this MTE.
Signature = aa
          The signature indicates the type of the module.
          NE = 16-bit segmented module.  (Built by the old linker.)
          LX = 16 or 32-bit module.  (Build by the new linker.)
Flags = hhhhhhhh
          Module flags.  The relevant flags are decoded on the following lines.

The swappable portion of the MTE is as follows:

Swappable portion of MTE (@ llllllll):
          The linear address of the swappable portion of the MTE.
Module # pages
          The number of pages in the module.
Initial instruction pointer = ssss:oooooooo
          ssss is the module-relative segment/object number where the initial
          entry point is located. oooooooo is the offset within the
          segment/object of the entry point. (The module type determines
          whether the ssss is segment or object.) This address will match the
          address on the .MAP file produced by the linker.
Initial stack    pointer = ssss:oooooooo
          ssss is the module-relative segment/object number where the initial
          stack is located. oooooooo is the offset within the segment/object of
          the stack. (The module type determines whether the ssss is segment or
          object.) This address will match the address on the .MAP file
          produced by the linker.
Fixup section size = hhhhhhhh
          Number of bytes in the "fixup" section of the module.
Object table offset = llllllll
          Linear address of the Object Table.
Number of objects in module = hhhhhhhh
          Number of segments/objects in the module.
Object page map offset = llllllll
          Linear address of the Object Page Map.
Object iterated data map offset = hhhhhhhh
          ???
Offset of Resource Table = llllllll
          Linear address of the modules Resource Table.
Number of resource entries = hhhhhhhh
          Number of entries in the Resource Table.
Offset of resident name table = llllllll
          Linear address of the Resident Name Table.
Offset of Entry Table = llllllll
          Linear address of the Entry Table.
Offset of Fixup Page Table = llllllll
          Linear address of the Fixup Page Table.
Offset of Fixup Record Table = llllllll
          Linear address of the Fixup Record Table.
Offset of Import Module Name Table = llllllll
          Linear address of the Import Module Name Table.
Offset of Imp Procedure Name Table = llllllll
          Linear address of the Import Procedure Name Table.
Offset of Enumerated Data Pages = hhhhhhhh
          ???
Number of preload pages = hhhhhhhh
          Number of pages which have been marked "preload" by the linker.
Offset of Non-resident Names Table = hhhhhhh
          ???
Size of Non-resident Name Table = hhhhhhhh
          ???
Object # for automatic data object = ssssssss
          Segment/object number that contains the automatic data object.
Offset of the debugging info = hhhhhhhh
          ???
The length of the debug info in bytes = hhhhhhhh
          The size of the debug information in bytes.
Number of instance pages in preload section = hhhhhhhh
          Number of instance pages that are to be preloaded.
Use for converted 16-bit modules = hhhhhhhh (heapsize)
          Size of the heap.
Full pathname = llllllll -> 'file name'
          Linear address of the fully qualified file name, followed by the
          fully qualified file name. (Only the linear address is in the MTE;
          THESEUS2 retrieves the contents of the ASCIIZ string that is pointed
          to.)
Length of pathname = hhhh
          Length (in bytes) of the path name.
Used by dynamic trace = hhhh
          ???
Count of threads waiting on MTE semaphore = i
          ???
Slot number of the owner of the MTE semaphore = hhhh
          ???
Pointer to preload pages = hhhhhhhh
          ???
Start of object with preload pages = hhhhhhhh
          ???
Size  of object with preload pages = hhhhhhhh
          ???
Pointer to file cache for Dos32CacheModule= hhhhhhhh
          ???
Use for converted 16-bit modules = hhhh (alignshift)
          ???
Use for converted 16-bit modules = hhhh (stacksize)
          ???
Original flags from NE header = hhhh
          ???
expver from NE header = hhhh
          ???
exetype from NE header = hhhh
          ???
Original other flags from NE header = hhhh
          ???
Number of preload pages used = hh
          ???

Following this is either a Segment Table or Object Table, depending on the
module type.

Each line of an Object Table contains the following:

Obj#        Module relative number of the object. This will match the linker's
            output.
address     Linear address of the object in memory.
size        Size of the object in bytes.
hob         The hob assigned to the object.
sel         Selector in the LDT assigned to this object. (This is only for
            16-bit compatibility.)
page map    ???
map size    ???
flags       Flags for this object.  They are decoded to the right.

Each line of a Segment Table contains the following:

Seg#        Module relative number of the segment. This will match the linker's
            output.
file offset Location of the segment in the file on disk. The interpretation of
            this depends on the "file granularity" specified to the linker.
file size   The size, in bytes, of the segment within the file.
flag        Flags for this segment.  They are decoded to the right.
ram size    The size, in bytes, of the segment after being loaded into RAM.
hob         The hob assigned to the segment.
sel         Selector in the LDT assigned to this object.
fixups      ???


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory Management Control Blocks

o Memory addressing


ΓòÉΓòÉΓòÉ 11.5.11. TCB Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the TCB Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link from the TCB column of a display.


ΓòÉΓòÉΓòÉ <hidden> Example of the TCB Display ΓòÉΓòÉΓòÉ

Thread Control Block at FD423E78:

TCB Linkage Information:
TID = 0001, Thread slot number = 0028
Forced action bit vector = 00000000
PTDA @ 7D3234E0
TSD @ 7D145000, TIB @ 00060030
Forward link to next (active) TCB = 00000000

Dos32CreateThread stack parameters:
Virtual   size of stack object = 00000000
Committed size of stack object = 00000000
Virtual   base of stack object = FFFFFFFF
Libi load data area link head    @ 00000000
Libi load data area link current @ 00000000
Libi load data area link free    @ 00000000
Stack frame type = FFF3CCCC
Stack frame base pointer = 7D145F3C
Local context hook head = FD423EB0, 00000000

Information needed for context switching:
KStack page 0 of TCB  = 0065D203
KStack page 1 of TCB  = 0063C203
KStack TSD page       = 005AA203
KStack page 0 of PTDA = 00000000
KStack page 1 of PTDA = 00000000
KStack page 2 of PTDA = 00623203
SS-relative offset of Current TCB = 00009288
SS-relative offset of Current TSD = 00004410
stack-to-flat TCB conversion value = FD41ABF0
stack-to-flat TSD conversion value = 7D140BF0

Variables used in the file system:
User's I/O transfer address = 03F05E70
Position of first sector accessed within the file = 00000000
Pointer to SFT we're working with = 00000000
Number of valid (previously written) sectors = 0000005E
Redirector TCB (Used by LANMAN) = 05C10000
Process ID for file sharing checks = 0000
User    ID for file sharing checks = 0000
non-zero ==> no redirection = 00
see SetAttrib/file.asm = 00
JFN flag bits for current file handle = 1C
Allowed I 24 answers (see allowed_) = 00
Fields to support opportunistic locks.  These are set by the server.
    Server's per file cookie = 00120000
    Whether server wants oplock, etc. = FFFFEF4F
Variables used by the FAT file system.  These are specific for the FAT
 file system and are not used for any IFS.
    Currently assigned buffer = FFFF0000
    Handle of current VPB = 0005
    TCBNextAdd = 001D
    Position of first byte within sector = 0000
    TCBClusNum = 0000
    TCBLastPos = 0101
    Number of bytes in 1st sector = 0000
    # of bytes in last sector = 003E
    Number of whole sectors = 0000
    Position of first sector within cluster = FFFFFFF4
How to handle a HardError = 02
Action response from user on HardError = 01
NZ if TCBLockHndl is valid = 00
Lock Handle of user mem = D9 02 0C 06 D4 50 30 00 40 FF 00 00
Address of current CDS = 000051FA
Address of current FSC = 000051F4
NZ if user did FAIL on I 24 = 0000

16bit addr of the ramsem blocked upon = 072306E0
Debugger display address fo ksems = FFFFFFFF

Per-thread NPX Information:
buffer @ 7CAD5EA0

TKWaitThread fields:
Next waiting TCB = 00000000
Threads waiting for me to die = 00000000

Scheduler fields:
Scheduler queue location (actual) = 05
Current scheduler state (desired) = 05
TKSleep/TKWakeup flags = 00
Window Boost count = 01
Priority Class (user) = 02
Priority Level (user) = 00
Priority Class modifier bits = 60
Misc. Scheduler flags = 00
Calculated Priority = 0500
Minimum Scheduling priority = 0000
Kernel Boost Lock nesting count = 00000000
Next     priority queue in chain = FD423E78
Previous priority queue in chain = FD423E78
Higher priority thread = FD423E78
Lower  priority thread = FD423E78
Next     same-priority thread = FD423E78
Previous same-priority thread = FD423E78
TKQueryWakeup TCB list = 00000000
Sleep ID this TCB is sleeping on = FFFE0064
Timeout/Starvation Timeout element = ????
Used by the loader (TCBCheckedSig) = 01

Per-thread Swapper Information:
Status of swapping = 00

Info about nesting level in FSH_DoVolIO:
Nesting level of FSH_DoVolIO = 00

Device I/O fields:
Flag to indicate if request pkt in use = 00
I/O request packet for thread = 01000000


ΓòÉΓòÉΓòÉ <hidden> Contents of the TCB Display ΓòÉΓòÉΓòÉ

No additional explanation is available.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory Management Control Blocks

o Memory addressing


ΓòÉΓòÉΓòÉ 11.5.12. Detail Working Set Information for an Object Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detail Working Set Information for an Object Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link from the accessed - yes column of the
Detail of Working Set (by Object) display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Detail Working Set Information for an Object Display ΓòÉΓòÉΓòÉ

Details of Working Set for Object with hob = 0429, Process = 'THESEUS2':
It is (shared) object # 0001 of module THESEUS2.
  linear   physical  time   status
00010000   00639000     1   in Working Set
00011000   00060000         not in Working Set
00012000   003BF000     1   in Working Set
00013000   0047E000     1   in Working Set
00014000   00058000     1   in Working Set
00015000   00895000     1   in Working Set
00016000   0070B000     3   in Working Set
00017000   001F6000     1   in Working Set
00018000   006B0000         not in Working Set
00019000   00096000         not in Working Set
0001A000   00072000         not in Working Set
0001B000   003BC000         not in Working Set
0001C000   0048A000         not in Working Set
0001D000                    not in memory
0001E000                    not in memory
0001F000                    not in memory
00020000                    not in memory
00021000   005C3000     1   in Working Set
00022000                    not in memory
00023000                    not in memory
  linear   physical  time   status
00024000                    not in memory
00025000   0043D000         not in Working Set
00026000                    not in memory
00027000                    not in memory
00028000   00488000     1   in Working Set
00029000   0024E000     1   in Working Set
0002A000   002E3000     1   in Working Set
0002B000   002D9000         not in Working Set
0002C000   005F0000         not in Working Set
0002D000   00186000         not in Working Set
0002E000   005CD000     1   in Working Set
0002F000                    not in memory
00030000   00444000         not in Working Set
00031000   00363000         not in Working Set
00032000   0004B000     1   in Working Set
00033000   00487000     1   in Working Set
00034000   00474000     1   in Working Set
00035000   00340000         not in Working Set
00036000   00190000     1   in Working Set
00037000   0018E000     1   in Working Set
  linear   physical  time   status
00038000   009E7000     1   in Working Set
00039000   0034D000     1   in Working Set
0003A000   004C3000     1   in Working Set
0003B000   00699000         not in Working Set
0003C000   009F2000     1   in Working Set


ΓòÉΓòÉΓòÉ <hidden> Contents of the Detail Working Set Information for an Object Display ΓòÉΓòÉΓòÉ

One line is displayed for each committed page within the object:

Column     Meaning
linear     The linear address of the page.
physical   The physical address of the page.
time       The number of intervals since the page was last accessed.
status     The status of the page relative to the working set:

   in Working Set        The page was in memory and was accessed sometime
                         within the working set interval.
   not in Working Set    The page was in memory but was last accessed outside
                         the working set interval.
   not in memory         This is a committed page that was not in RAM during
                         the run.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory analysis

o Memory addressing


ΓòÉΓòÉΓòÉ 11.5.13. SFT Entry Display ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the SFT Entry Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link of the SFT address field on the Open
Files display.


ΓòÉΓòÉΓòÉ <hidden> Example of the SFT Entry Display ΓòÉΓòÉΓòÉ

System File Table Entry located at 03F8:30A6:

Base portion of the SFT entry:
  Reference count = 1
  User count = 0
  Flag word 1 = 0040 / local file 40
  Flag word 2 = 0000 /
  Device pointer = 00000012
  File System Control (FSC) block @ 0000FF40
  'cookie' = 00000000
  Next in chain = 0000:0000
  Master File Table (MFT) entry @ FEB62FA0

File system dependent portion of the SFT:

File system independent portion of the SFT:
  Access mode = 00A0
  Additional openmode bits for DosOpen2 = 0000
  handle of volume = 0012
  Creation time of file = 0000
  Creation date of file = 0000
  Time of last access of file 0000
  Date of last access of file 0000
  Time of last modification of file = 5C4A
  Date of last modification of file = 1913
  Size associated with file = 0003910D
  Read/Write pointer or LRU count for FCBs = 000060A1
  User ID = 0000
  Process ID = 00FF
  Process Data Block = 0000
  SFN of this sf_entry = 0062
  update time stamp flags = 00
  file/device/named-pipe/FCB = 0000
  performance counter data block pointer = 00000000
  DOS attributes of file(sys,hid,r/o,arch = 20

Used for spooling:
  16 bit offset to first pending LOCK record = 0000
  SFN of named pipe for spooled files = 0000
  Current codepage (font) for data in file = 0


ΓòÉΓòÉΓòÉ <hidden> Contents of the SFT Entry Display ΓòÉΓòÉΓòÉ

No additional explanation is available.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing


ΓòÉΓòÉΓòÉ 11.5.14. Detailed Memory Assignment Information ΓòÉΓòÉΓòÉ

Select one:

Contents of Display

Selecting

Example Output

Related Topics


ΓòÉΓòÉΓòÉ <hidden> Selecting the Detailed Memory Assignment Information Display ΓòÉΓòÉΓòÉ

This is selected by a hyperblock link of the RAM amount field on the Free,
Idle, and Locked Memory display or the RAM Usage by Process display.


ΓòÉΓòÉΓòÉ <hidden> Example of the Detailed Memory Assignment Information Display ΓòÉΓòÉΓòÉ

There are two different formats of the information displayed, one for Locked
memory and one for all the other types.

The detail of locked memory is:

Detail memory assignment information, PID = 0000, Process = system:
 giving detail about Long  Term Locked memory:
0012F000 is Long Term Locked, count = 1.
004EB000 is Long Term Locked, count = 1.
00510000 is Long Term Locked, count = 5.
00670000 is Long Term Locked, count = 1.
┬╖┬╖┬╖

The detail of other type memory is:

Detail memory assignment information, PID = 0000, Process = system,
 giving detail about IDLE memory:
0009C000 is assigned as IDLE
001D1000 is assigned as IDLE
001E8000 is assigned as IDLE
001ED000 is assigned as IDLE, page is dirty
┬╖┬╖┬╖


ΓòÉΓòÉΓòÉ <hidden> Contents of the Detailed Memory Assignment Information Display ΓòÉΓòÉΓòÉ

The free and idle detail lists are presented in the order they are linked into
the chain. If an idle page is dirty, it is indicated as such.

The locked detail lists are presented in physical page address order. The lock
count from the Page Frame Table is given. This count specifies the number of
times that Device Drivers have locked the particular page.


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o Memory addressing

o Physical Memory States


ΓòÉΓòÉΓòÉ 11.6. Common Elements ΓòÉΓòÉΓòÉ

This section describes items common to several of the displays.

Displays are:

Descriptor Table Entry
          Displays fields of the entries in the GDT, LDT, and IDT displays.
Page Table Entry/Page Directory Entry
          Displays fields of the entries in the Page Table Entry/Page Directory
          Entry displays.


ΓòÉΓòÉΓòÉ 11.6.1. Descriptor Table Entry ΓòÉΓòÉΓòÉ

The fields of the Descriptor Table Entry are decoded. (See the Intel 80386
Programmer's Reference Manual for details about each field.)

Term           Meaning
Table          This is either GDT, LDT, Trap, or Int.
(number)       For GDT and LDT, this is the selector referring to this entry.
               For Trap, this is the trap number referring to this entry.
               For Int, this is the interrupt number referring to this entry.
Type           Type of selector:

   Code           Code segment
   Data           Data segment
   ATSS16         Available Task State Segment - 286 mode
   ATSS32         Available Task State Segment - 386 mode
   BTSS16         Busy Task State Segment - 286 mode
   BTSS32         Busy Task State Segment - 386 mode
   LDT            Selector that points to an LDT
   CallG          Call Gate - 286 mode
   CallG32        Call Gate - 386 mode
   TaskG          Task Gate
   IntG           Interrupt Gate - 286 mode
   IntG32         Interrupt Gate - 386 mode
   TrapG          Trap Gate - 286 mode
   TrapG32        Trap Gate - 386 mode.
Base           Base address (linear) of the segment.
Limit          Length (-1) of the segment. (For "expand up" segments, this is
               the largest offset that may be used. For "expand down" segments,
               this is the smallest offset that may be used.)
DPL            Descriptor Privilege Level (2 bits).
CF             Code segment is "Conforming" (0=not conforming, 1=conforming).
R              Code segment is "Readable" (0=not readable, 1=readable).
ED             Data segment is "Expand Down" (0=expand up, 1=expand down).
W              Data segment is "Writable" (0=not writable, 1=writable).
A              Segment has been Accessed (0=not accessed, 1=accessed)
P              Segment is Present (0=not present, 1=present).
G              Granularity of limit value (0=byte (64K segment), 1=page (4G
               segment)).
D              Code segment default operand size (0=16-bit, 1=32-bit).
B              Data segment default size (0=16-bit, 1=32-bit).
Selector       Selector of gate's target segment.
Offset         Offset within selector of target code.
Word Count     Number of words on stack to be copied.
Alias          The selector is an "alias".


ΓòÉΓòÉΓòÉ 11.6.2. Page Table Entry/Page Directory Entry ΓòÉΓòÉΓòÉ

The fields of the Page Table Entry or Page Directory Entry are decoded. (See
the Intel 80386 Programmer's Reference Manual for details about each field.)

Term           Meaning
*              The asterisk (*) in the first column indicates a PDE.
Linear         The linear address associated with the entry.
Physical       The physical address of the page in memory. (The page is
               present.)
Invalid page   The entry indicates that there is no committed page for this
               address.
Guard          The page is a "guard page".
FrameId        The index into the Virtual Page Table for the page. (The page is
               not present.)
D              The page is "Dirty" (0=clean, 1=dirty).
A              The page has been "Accessed" (0=not accessed, 1=accessed).
User           The page is a "User page". The page can be accessed from any
               protection ring.
Super          The page is a "Supervisor page". The page can only be accessed
               from ring 0.
R/W            The page can be written.
R/O            The page can only be read.
P              The page is "Present" (0=not present, 1=present).
Resident       The page is not to be paged out nor discarded.
UVirt          The page is a UVirt page.
Cache_disabled ???
Cache_write-through ???


ΓòÉΓòÉΓòÉ 12. Application Programming Interface ΓòÉΓòÉΓòÉ

THESEUS2 provides an Application Programming Interface (API) for certain of its
functions. These are provided with the THESEUS0.DLL file.

CAUTION:
These functions should only be used by a single thread of an application. They
use the Microsoft** compiler's DLL library and it is probably not compatible
with CSet/2*'s multi-thread environment.

The functions provided by THESEUS0.DLL can be accessed from either a 'C'
program or REXX.


ΓòÉΓòÉΓòÉ 12.1. Restriction ΓòÉΓòÉΓòÉ

You may not distribute the THESEUS0.DLL program unless you have a Software
Technology License Agreement with IBM for the THESEUS0.DLL program.


ΓòÉΓòÉΓòÉ 12.2. 'C' Application Programming Interface ΓòÉΓòÉΓòÉ

The functions provided by THESEUS0.DLL are divided into the following
categories:

Error Handling, Initialization/Termination, and Handle Management
          Functions to handle errors, cause THESEUS0.DLL to initialize and
          terminate and THESEUS0 handle management.
Free Memory, Swapper, and Process Functions
          Functions to determine information about the system as a whole.
Working Set Functions
          Functions to perform working set analysis.

Note:  THESEUS0.DLL has 32-bit interfaces ONLY. If you want to interface to it
from a 16-bit compiler, then you must provide the THUNKS yourself.


ΓòÉΓòÉΓòÉ 12.2.1. Error Handling, Initialization/Termination, and Handle Management ΓòÉΓòÉΓòÉ

These functions apply to all the APIs.

Error handling function:

error handler        Specify the error handler provided by the user.

Initialization/termination functions:

T2Initialize         Initialize THESEUS0.DLL for use.
T2Terminate          Terminate the use of THESEUS0.DLL.

Handle management functions:

T2GetHandle0         Get an instance handle.
T2ReleaseHandle0     Release an instance handle.


ΓòÉΓòÉΓòÉ 12.2.1.1. error handler ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - error handler ΓòÉΓòÉΓòÉ

The error handler is provided by the user to format and display errors
generated by the routines in THESEUS0.DLL. It must be provided by the user
program because the lower level routines do not know what the output
environment is.

#include "THESEUS0.h"

VOID EXPENTRY error_handler0( T2HANDLE0 t2handle0,
                              ULONG     error_code,
                              ULONG     p1,
                              ULONG     p2)
{
  /* error handler code */
}


ΓòÉΓòÉΓòÉ <hidden> Parameters - error handler ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          The instance handle that was being used by the lower level routine
          when the error was detected. This is given to the error routine in
          case the output is handle specific.

error_code (ULONG) - input
          The values of the error_code and meanings of the other two parameters
          are:

                    ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
                    Γöéerror_codeΓöép1    Γöép2    Γöéexplanation                      Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé1         ΓöélinearΓöén/a   ΓöéThe starting address (linear) hasΓöé
                    Γöé          Γöé      Γöé      Γöéno page table.                   Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé2         ΓöélinearΓöélengthΓöéThe ending address               Γöé
                    Γöé          Γöé      Γöé      Γöé(linear+length-1) has no page    Γöé
                    Γöé          Γöé      Γöé      Γöétable.                           Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé3         ΓöélinearΓöén/a   ΓöéThe page at the starting address Γöé
                    Γöé          Γöé      Γöé      Γöéis not present.                  Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé4         ΓöélinearΓöélengthΓöéThe page at the ending address   Γöé
                    Γöé          Γöé      Γöé      Γöé(linear+length-1) is not present.Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé5         ΓöélinearΓöélengthΓöéThe address+length is greater    Γöé
                    Γöé          Γöé      Γöé      Γöéthan 32 bits.                    Γöé
                    Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
                    Γöé6         ΓöélinearΓöén/a   ΓöéThe header for the System Arena  Γöé
                    Γöé          Γöé      Γöé      Γöéwas not located. The value found Γöé
                    Γöé          Γöé      Γöé      Γöéis returned, but is not valid.   Γöé
                    Γöé          Γöé      Γöé      ΓöéSystem Working Set cannot be     Γöé
                    Γöé          Γöé      Γöé      Γöémeasured.                        Γöé
                    ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ

p1 (ULONG) - input
          see above

p2 (ULONG) - input
          see above


ΓòÉΓòÉΓòÉ <hidden> Example - error handler ΓòÉΓòÉΓòÉ

This example will print error messages to the STDOUT device.

#include <os2.h>
#include <stdio.h>
#include "THESEUS0.h"

VOID EXPENTRY error_handler0( T2HANDLE0 t2handle0,
                              ULONG     error_code,
                              ULONG     p1,
                              ULONG     p2)
{
 switch (error_code)
 {
  case 1:
   printf( "Linear address: no Page Table, linear=%0.8X.\n", p1);
   break;
  case 2:
   printf( "Linear address+length: no Page Table, linear=%0.8X, length=%0.8X.\n",
           p1, p2);
   break;
  case 3:
   printf( "Linear address: page not present, linear=%0.8X.\n", p1);
   break;
  case 4:
   printf( "Linear address+Length: page not present, linear=%0.8X, length=%0.8X.\n",
           p1, p2);
   break;
  case 5:
   printf( "Linear address+Length: > 32 bits, linear=%0.8X, length=%0.8X.\n",
           p1, p2);
   break;
  case 6:
   printf( "SystemArenaHeaderLinear = %0.8X.\n", p1);
   printf( "SystemArenaHeaderLinear was not properly located.\n");
   printf( "System Working Set cannot be measured.\n");
   break;
  default:
   printf( "unknown error to error_handler0: t2handle0=%0.8X, error_code=%i, p1=%i, p2=%i.\n",
           t2handle0, error_code, p1, p2);
   break;
 }
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2Initialize

o T2GetHandle0


ΓòÉΓòÉΓòÉ 12.2.1.2. T2Initialize ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2Initialize ΓòÉΓòÉΓòÉ

T2Initialize is used to cause THESEUS0 to initialize all its internal
information that is required for later use.

#include "THESEUS0.h"

PULONG ulDDVersion;
ULONG  ulrc;

ulrc = T2Initialize0( ulDDVersion, error_handler0);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2Initialize ΓòÉΓòÉΓòÉ

ulDDVersion (PULONG) - output
          The address of a ULONG where the version of the THESEUS2.SYS device
          driver installed in CONFIG.SYS is returned. The upper USHORT is the
          version found and the lower USHORT is the version required.

          Note:  It is returned only if the return code is Theseus2WrongDD.

error_handler0 (function) - input
          The address (name) of the error handler provided by the user program.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2Initialize ΓòÉΓòÉΓòÉ

ulrc (ULONG)
          return code

   Theseus2OK
             Initialization completed successfully.

   Theseus2NoDD
             There is no THESEUS2.SYS installed in CONFIG.SYS. The program
             cannot continue.

   Theseus2WrongDD
             The version of THESEUS2.SYS installed in CONFIG.SYS is not the
             version expected.  ulDDVersion contains the versions found and
             required. The program cannot continue.

   Theseus2BadPTDA
             The initialization code could not determine the size of the PTDA.
             The program cannot continue.

   Theseus2NoMte
             The initialization code could not determine the format for the
             resident portion of the MTE. The program cannot continue.


ΓòÉΓòÉΓòÉ <hidden> Example - T2Initialize ΓòÉΓòÉΓòÉ

This example will cause T2Initialize to perform the initialization of the
internal functions.

VOID EXPENTRY error_handler0( ULONG error_code, ULONG p1, ULONG p2)
{
┬╖┬╖┬╖
}

ULONG ulDDVersion;

switch (T2Initialize0( &ulDDVersion, error_handler0) )
{
 case Theseus2NoDD:
  printf( "THESEUS2.SYS was not installed in your CONFIG.SYS.\n");
  break;
 case Theseus2WrongDD:
  printf( "The THESEUS2.SYS that was found is not the required version.\n");
  printf( "Version %i was found and %i is required.\n",
          ulDDVersion >> 16,
          ulDDVersion & 0xFFFF);
  printf( "Please acquire the correct version.\n");
  break;
 case Theseus2BadPTDA:
  printf( "PTDA_findSize did not determine the size of a PTDA.\n");
  break;
 case Theseus2OK:
  printf( "Initialization completed normally.\n");

  /* Execute program functions. */

  T2Terminate0();
  break;
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o error handler

o T2Terminate


ΓòÉΓòÉΓòÉ 12.2.1.3. T2Terminate ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2Terminate ΓòÉΓòÉΓòÉ

T2Terminate is used to cause THESEUS0 to close the device driver.

#include "THESEUS0.h"

T2Terminate0( VOID );


ΓòÉΓòÉΓòÉ <hidden> Example - T2Terminate ΓòÉΓòÉΓòÉ

This example will cause T2Terminate to close out all the processing of
THESEUS0.DLL.

ULONG ulDDVersion;

switch (T2Initialize0( &ulDDVersion, error_handler0) )
{
┬╖┬╖┬╖
 case Theseus2OK:
  printf( "Initialization completed normally.\n");

  /* Execute program functions. */

  T2Terminate0();
  break;
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2Initialize


ΓòÉΓòÉΓòÉ 12.2.1.4. T2GetHandle0 ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2GetHandle0 ΓòÉΓòÉΓòÉ

T2GetHandle0 is used to cause THESEUS0 to allocate an instance handle.

#include "THESEUS0.h"
VOID EXPENTRY error_handler0( ULONG error_code, ULONG p1, ULONG p2)
{
┬╖┬╖┬╖
}

T2HANDLE0 t2handle0;

t2handle0 = T2GetHandle0( error_handler0);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2GetHandle0 ΓòÉΓòÉΓòÉ

error_handler0 (function) - input
          The address (name) of the error handler provided by the user program.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2GetHandle0 ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0)
          The new instance handle. This handle must be passed to other
          functions.


ΓòÉΓòÉΓòÉ <hidden> Example - T2GetHandle0 ΓòÉΓòÉΓòÉ

This example will allocate an instance handle.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;

t2handle0 = T2GetHandle0( error_handler0);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o error handler

o T2ReleaseHandle0


ΓòÉΓòÉΓòÉ 12.2.1.5. T2ReleaseHandle0 ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2ReleaseHandle0 ΓòÉΓòÉΓòÉ

T2ReleaseHandle0 is used to cause THESEUS0 to release an instance handle and
free the resources associated with it.

#include "THESEUS0.h"
T2HANDLE0 *pT2Handle0;

T2ReleaseHandle0( pT2Handle0);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2ReleaseHandle0 ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input/output
          An instance handle acquired from T2GetHandle0. It is zeroed by the
          function.


ΓòÉΓòÉΓòÉ <hidden> Example - T2ReleaseHandle0 ΓòÉΓòÉΓòÉ

This example will release the instance handle previously acquired.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;

T2ReleaseHandle0( &t2handle0);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0


ΓòÉΓòÉΓòÉ 12.2.2. Free Memory, Swapper, and Process Functions ΓòÉΓòÉΓòÉ

These functions are used to acquire specific information about the system as a
whole.

Free memory function:

T2FreeMemory            Determine the amount of free, idle, and locked memory.

SWAPPER.DAT analysis function:

T2AnalyzeSwapper        Determine the amount of free and used space in the
                        SWAPPER.DAT file.

Process functions:

T2FindProcesses         Returns an array with the current processes.
T2RamUseByProcess       Returns an array with the current RAM usage by each
                        process.


ΓòÉΓòÉΓòÉ 12.2.2.1. T2FreeMemory ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2FreeMemory ΓòÉΓòÉΓòÉ

T2FreeMemory is used to cause THESEUS0 to calculate the amount of free, idle,
and locked memory.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
PULONG pFreeRam,
       pIdleRam,
       pDirtyRam,
       pLLockRam,
       pSLockRam,
       pBLockRam;

T2FreeMemory( t2handle0,
              pFreeRam, pIdleRam, pDirtyRam,
              pLLockRam, pSLockRam, pBLockRam);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2FreeMemory ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          An instance handle previously allocated by T2GetHandle0.

pFreeRam (PULONG) - output
          Address of the ULONG where the amount of free memory is returned.

pIdleRam (PULONG) - output
          Address of the ULONG where the amount of idle memory is returned.

pDirtyRam (PULONG) - output
          Address of the ULONG where the amount of dirty memory is returned.
          This memory is included in the idle memory.

pLLockRam (PULONG) - output
          Address of the ULONG where the amount of long-term locked memory is
          returned.

pSLockRam (PULONG) - output
          Address of the ULONG where the amount of short-term locked memory is
          returned.

pBLockRam (PULONG) - output
          Address of the ULONG where the amount of memory which is locked both
          long-term and short-term is returned.


ΓòÉΓòÉΓòÉ <hidden> Example - T2FreeMemory ΓòÉΓòÉΓòÉ

This example will cause T2FreeMemory to calculate the free, idle, and locked
memory.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG freeRam,
      idleRam,
      dirtyRam,
      LLockRam,
      SLockRam,
      BLockRam;

T2FreeMemory(  t2handle0,
              &freeRam,
              &idleRam,
              &dirtyRam,
              &LLockRam,
              &SLockRam,
              &BLockRam);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o Contents of the Free, Idle, and Locked Memory Display


ΓòÉΓòÉΓòÉ 12.2.2.2. T2AnalyzeSwapper ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2AnalyzeSwapper ΓòÉΓòÉΓòÉ

T2AnalyzeSwapper is used to cause THESEUS0 to calculate the amount of free and
used space in the SWAPPER.DAT file.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
PULONG SwapUsed,
       SwapFree;

T2AnalyzeSwapper( t2handle0, SwapUsed, SwapFree);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2AnalyzeSwapper ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          An instance handle previously allocated by T2GetHandle0.

SwapUsed (PULONG) - output
          The address of a ULONG where the number of used disk frames is
          returned.

SwapFree (PULONG) - output
          The address of a ULONG where the number of free disk frames is
          returned.

Each disk frame is 4K bytes.


ΓòÉΓòÉΓòÉ <hidden> Example - T2AnalyzeSwapper ΓòÉΓòÉΓòÉ

This example will cause T2AnalyzeSwapper to calculate the free and used space
in the SWAPPER.DAT file.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG SwapUsed,
      SwapFree;

T2AnalyzeSwapper( t2handle0, &SwapUsed, &SwapFree);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o Contents of the Swapper Display


ΓòÉΓòÉΓòÉ 12.2.2.3. T2FindProcesses ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2FindProcesses ΓòÉΓòÉΓòÉ

T2FindProcesses is used to cause THESEUS0 to count the number of processes in
the system. It also returns an array which contains some information about each
process.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG     ulProcessCount;
T2PROCESS_TABLE *pProcessTable;

ulProcessCount = T2FindProcesses( t2handle0,
                                  pProcessTable);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2FindProcesses ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          An instance handle previously allocated by T2GetHandle0.

pProcessTable (T2PROCESS_TABLE *) - output
          Address of a pointer which will point to the Process Table which is
          returned.

          The array contains an entry for each process currently running:

   ptdaPID          The PID of this process.
   pidParent        The pid of this process's parent process.
   cThreads         The number of threads in this process.
   processName      The name of this process.

          Note:  It is the users responsibility to issue a DosFreeMem on this
          array when it is no longer needed.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2FindProcesses ΓòÉΓòÉΓòÉ

ulProcessCount (ULONG)
          The number of processes currently running in the system. This will
          also be the number of entries in pProcessTable.


ΓòÉΓòÉΓòÉ <hidden> Example - T2FindProcesses ΓòÉΓòÉΓòÉ

This example will cause T2FindProcesses to return an array with process names
and PIDs.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG     cProcess;
T2PROCESS_TABLE *tProcessTable;

cProcess = T2FindProcesses( t2handle0,
                            &tProcessTable);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o Contents of the Process List Display


ΓòÉΓòÉΓòÉ 12.2.2.4. T2RamUseByProcess ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2RamUseByProcess ΓòÉΓòÉΓòÉ

T2RamUseByProcess is used to cause THESEUS0 to determine the RAM used by each
process in the system. It returns an array which contains the usage of each
process.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG     ulProcessCount;
T2RAM_TABLE *pRamTable;
PULONG    ulFreeRam;

ulProcessCount = T2RamUseByProcess( t2handle0,
                                    pProcessTable,
                                    ulFreeRam);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2RamUseByProcess ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          An instance handle previously allocated by T2GetHandle0.

pRamTable (T2RAM_TABLE *) - output
          Address of a pointer which will point to the RAM Table which is
          returned.

          The array contains an entry for each process currently running:

   ptdaPID          The PID of this process. The entry with PID = 0000 contains
                    the memory used by the "system".
   ulPrivate        The amount of memory in the private arena of this process.
                    If multiple processes have the same page in their private
                    arenas, the process with the lowest PID value is charged
                    with the memory.
   ulShared         The amount of memory from the shared arena that is owned by
                    this process.

          Note:  It is the users responsibility to issue a DosFreeMem on this
          array when it is no longer needed.

ulFreeRam (ULONG) - output
          The address of a ULONG where the amount of free memory is returned.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2RamUseByProcess ΓòÉΓòÉΓòÉ

ulProcessCount (ULONG)
          The number of processes currently running in the system. This will
          also be the number of entries in pRamTable.


ΓòÉΓòÉΓòÉ <hidden> Example - T2RamUseByProcess ΓòÉΓòÉΓòÉ

This example will cause T2RamUseByProcess to return an array with PIDs and RAM
usage for each process.

#include "THESEUS0.h"
T2HANDLE0 t2handle0;
ULONG     cProcess;
T2RAM_TABLE *tRamTable;
ULONG     ulFreeRam;

cProcess = T2RamUseByProcess( t2handle0,
                              &tRamTable,
                              &ulFreeRam);


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o Contents of the RAM Usage by Process Display


ΓòÉΓòÉΓòÉ 12.2.3. Working Set Functions ΓòÉΓòÉΓòÉ

These functions are used to acquire working set information.

Working Set functions:

T2WSStart            Sets up to do working set analysis for a particular
                     process or the entire system.
T2WSSystemTick       Collects data when doing working set for the entire
                     system.
T2WSProcessTick      Collects data when doing working set for a particular
                     process.
T2WSStop             Stops the collection of working set data and returns
                     summary information.
T2WSCheck            See if it is valid to collect working set data for a
                     particular process or the entire system.

The general way that these functions are used is:

T2WSStart.
do {
  Wait for the desired interval to elapse.
  T2WSSystemTick or T2WSProcessTick.
} while (data is desired).
T2WSStop.


ΓòÉΓòÉΓòÉ 12.2.3.1. T2WSStart ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

System Example

Process Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2WSStart ΓòÉΓòÉΓòÉ

T2WSStart is used to cause THESEUS0 to set up for working set data collection
for a particular process or the entire system.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
WS_HANDLE0 ws_handle0;
ULONG      pid;

ulrc = T2WSStart( t2handle0, ws_handle0, pid);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2WSStart ΓòÉΓòÉΓòÉ

t2handle0 (T2HANDLE0) - input
          An instance handle previously allocated by T2GetHandle0.

ws_handle0 (WS_HANDLE0) - output
          The address of a WS_HANDLE0 where the working set handle is returned.
          This handle must be used in the T2WSSystemTick/T2WSProcessTick and
          T2WSStop calls.

pid (ULONG) - input
          The pid of the process that you want to measure. If 0 is specified,
          then the working set of the entire system is measured. The process
          with pid of 0001 is not valid for measurement.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2WSStart ΓòÉΓòÉΓòÉ

ulrc (ULONG)
          return code

   T2WS_OK
             The T2WSStart call completed properly. The ws_handle0 value is
             returned.

   T2WS_InUse
             The process requested is already having working set data collected
             for it. A process can have working set data collected for it from
             only one place.

   T2WS_SystemBeingDone
             Working set collection is being done for the system. If system is
             being done, no process can have data collected for it.

   T2WS_PidNotFound
             The requested process was not found as an active process.

   T2WS_BadArena
             An error occurred during initialization. Working set data cannot
             be collected.


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSStart System Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG      ulNow, ulWS, ulAccessed, ulFree, ulIdle,
           ulProcessesUsed, ulProcessCount, ulResident, ulTotalRam;
ULONG      iIntervals, ulMinimum, ulRecommended;

rc = T2WSStart( t2handle0, &ws_handle0, 0);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSSystemTick( ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                         &ulFree, &ulIdle,
                         &ulProcessesUsed, &ulProcessCount,
                         &ulResident, &ulTotalRam);
    printf( "\n  tick (rc=%i), %i %i %i %i %i %i %i %i %i\n",
            rc, ulNow, ulWS, ulAccessed, ulFree, ulIdle,
            ulProcessesUsed, ulProcessCount,
            ulResident, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSStart Process Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG     ulNow, ulWS, ulAccessed;
ULONG     iIntervals, ulMinimum, ulRecommended, ulTotalRam;

rc = T2WSStart( t2handle0, &ws_handle0, 2);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSProcessTick(  ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                          &ulTotalRam);
    printf( "  tick (rc=%i) pid=%i, %i %i %i %i\n",
            rc, i, ulNow, ulWS, ulAccessed, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o T2WSSystemTick

o T2WSProcessTick

o T2WSStop

o Working Set of the Entire System?

o Working Set of a Single Process?


ΓòÉΓòÉΓòÉ 12.2.3.2. T2WSSystemTick ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Notes

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2WSSystemTick ΓòÉΓòÉΓòÉ

T2WSSystemTick is used to cause THESEUS0 to determine the amount of memory
accessed since the last T2WSSystemTick call or from the T2WSStart call.

#include "THESEUS0.h"

ULONG      rc;
WS_HANDLE0 ws_handle0;
ULONG      ulIntervals;
PULONG     ulNow, ulWS, ulAccessed, ulFree, ulIdle,
           ulProcessesUsed, ulProcessCount, ulResident, ulTotalRam;

rc = T2WSSystemTick( ws_handle0, ulIntervals,
                     ulNow, ulWS, ulAccessed,
                     ulFree, ulIdle,
                     ulProcessesUsed, ulProcessCount,
                     ulResident, ulTotalRam);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2WSSystemTick ΓòÉΓòÉΓòÉ

ws_handle0 (WS_HANDLE0) - input
          An instance handle previously allocated by T2WSStart.

ulIntervals (ULONG) - input
          The number of intervals that constitute the working set. This value
          must be less than 254 for the computations to work properly.

ulNow (PULONG) - output
          The address of a ULONG where the number of pages of memory that was
          accessed during the last interval is returned.

ulWS (PULONG) - output
          The address of a ULONG where the number of pages of memory in the
          working set is returned.

ulAccessed (PULONG) - output
          The address of a ULONG where the number of pages of memory accessed
          since the T2WSStart was issued is returned.

ulFree (PULONG) - output
          The address of a ULONG where the number of pages of free memory is
          returned.

ulIdle (PULONG) - output
          The address of a ULONG where the number of pages of idle memory is
          returned.

ulProcessesUsed (PULONG) - output
          The address of a ULONG where the number of processes that had memory
          accessed during the interval is returned. This value indicates the
          number of processes which are both running and touching non-system
          memory.

ulProcessCount (PULONG) - output
          The address of a ULONG where the total number of processes found
          during the interval is returned. This number changes as processes are
          created or destroyed.

ulResident (PULONG) - output
          The address of a ULONG where the number of pages of resident memory
          is returned.

ulTotalRam (PULONG) - output
          The address of a ULONG where the total number of pages of RAM being
          used by OS/2* is returned.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2WSSystemTick ΓòÉΓòÉΓòÉ

ulrc (ULONG)
          return code

   T2WS_OK
             The T2WSSystemTick call completed properly.

   T2WS_InvalidHandle
             The ws_handle0 passed was not valid.


ΓòÉΓòÉΓòÉ <hidden> Notes - T2WSSystemTick ΓòÉΓòÉΓòÉ

The interval between calls to T2WSSystemTick should be chosen carefully. If the
interval is too short, the processing could cause the rest of the system to
have problems. However, if the interval is too long, dynamic memory allocated
and freed will be missed. The overhead is dependent on the number of processes,
more so than the amount of RAM in the machine. The interval should never be
less than 1 second nor longer than 1 minute.


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSSystemTick ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG      ulNow, ulWS, ulAccessed, ulFree, ulIdle,
           ulProcessesUsed, ulProcessCount, ulResident, ulTotalRam;
ULONG      iIntervals, ulMinimum, ulRecommended;

rc = T2WSStart( t2handle0, &ws_handle0, 0);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSSystemTick( ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                         &ulFree, &ulIdle,
                         &ulProcessesUsed, &ulProcessCount,
                         &ulResident, &ulTotalRam);
    printf( "\n  tick (rc=%i), %i %i %i %i %i %i %i %i %i\n",
            rc, ulNow, ulWS, ulAccessed, ulFree, ulIdle,
            ulProcessesUsed, ulProcessCount,
            ulResident, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2WSStart

o T2WSStop

o Working Set of the Entire System?

o System Working Set


ΓòÉΓòÉΓòÉ 12.2.3.3. T2WSProcessTick ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Notes

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2WSProcessTick ΓòÉΓòÉΓòÉ

T2WSProcessTick is used to cause THESEUS0 to determine the amount of memory
accessed since the last T2WSProcessTick call or from the T2WSStart call.

#include "THESEUS0.h"

ULONG      rc;
WS_HANDLE0 ws_handle0;
ULONG      ulIntervals;
PULONG     ulNow, ulWS, ulAccessed, ulTotalRam;

rc = T2WSProcessTick( ws_handle0, ulIntervals,
                     ulNow, ulWS, ulAccessed, ulTotalRam);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2WSProcessTick ΓòÉΓòÉΓòÉ

ws_handle0 (WS_HANDLE0) - input
          An instance handle previously allocated by T2WSStart.

ulIntervals (ULONG) - input
          The number of intervals that constitute the working set. This value
          must be less than 254 for the computations to work properly.

ulNow (PULONG) - output
          The address of a ULONG where the number of pages of memory that was
          accessed during the last interval is returned.

ulWS (PULONG) - output
          The address of a ULONG where the number of pages of memory in the
          working set is returned.

ulAccessed (PULONG) - output
          The address of a ULONG where the number of pages of memory accessed
          since the T2WSStart was issued is returned.

ulTotalRam (PULONG) - output
          The address of a ULONG where the total number of pages of RAM being
          used by OS/2* is returned.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2WSProcessTick ΓòÉΓòÉΓòÉ

ulrc (ULONG)
          return code

   T2WS_OK
             The T2WSProcessTick call completed properly.

   T2WS_InvalidHandle
             The ws_handle0 passed was not valid.

   T2WS_PidNotFound
             The requested process was not found as an active process. It was
             found when the T2WSStart was done, but has since terminated.


ΓòÉΓòÉΓòÉ <hidden> Notes - T2WSProcessTick ΓòÉΓòÉΓòÉ

The interval between calls to T2WSProcessTick should be chosen carefully. If
the interval is too short, the processing could cause the rest of the system to
have problems. However, if the interval is too long, dynamic memory allocated
and freed will be missed. The overhead is dependent on the number of processes
being monitored, more so than the amount of RAM in the machine. The interval
should never be less than 1 second nor longer than 1 minute.


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSProcessTick ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG     ulNow, ulWS, ulAccessed;
ULONG     iIntervals, ulMinimum, ulRecommended, ulTotalRam;

rc = T2WSStart( t2handle0, &ws_handle0, 2);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSProcessTick(  ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                          &ulTotalRam);
    printf( "  tick (rc=%i) pid=%i, %i %i %i %i\n",
            rc, i, ulNow, ulWS, ulAccessed, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2WSStart

o T2WSStop

o Working Set of a Single Process?

o Process Working Set


ΓòÉΓòÉΓòÉ 12.2.3.4. T2WSStop ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

System Example

Process Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2WSStop ΓòÉΓòÉΓòÉ

T2WSStop is used to cause THESEUS0 to count the number of

#include "THESEUS0.h"

WS_HANDLE0 ws_handle0;
BOOL       fCollectOne;
PULONG     iIntervals, ulMinimum, ulRecommended, ulAccessed;

rc = T2WSStop( ws_handle0, fCollectOne, iIntervals,
               ulMinimum, ulRecommended, ulAccessed);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2WSStop ΓòÉΓòÉΓòÉ

ws_handle0 (WS_HANDLE0) - input
          An instance handle previously allocated by T2WSStart.

fCollectOne (BOOL) - input
          Indicate if at least one collection cycle must be accomplished.

   TRUE    Perform a collection cycle (tick), if one has not already been done.
   FALSE   Do not force a collection cycle.

iIntervals (PULONG) - output
          Address of a ULONG where the number of data collections cycles
          completed is returned.

ulMinimum (PULONG) - output
          The address of a ULONG where the maximum value from the now column is
          returned. This is the amount of memory absolutely required to run the
          application without "thrashing" memory.

ulRecommended (PULONG) - output
          The address of a ULONG where the maximum value from the ws column is
          returned. This is the recommended amount of memory for the
          application to run with minimum impact on paging.

ulAccessed (PULONG) - output
          The address of a ULONG where the maximum value from the accessed
          column is returned. This is the amount of memory required to run the
          application with no paging activity.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2WSStop ΓòÉΓòÉΓòÉ

ulrc (ULONG)
          return code

   T2WS_OK
             The T2WSStop call completed properly.

   T2WS_InvalidHandle
             The ws_handle0 passed was not valid.


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSStop System Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG      ulNow, ulWS, ulAccessed, ulFree, ulIdle,
           ulProcessesUsed, ulProcessCount, ulResident, ulTotalRam;
ULONG      iIntervals, ulMinimum, ulRecommended;

rc = T2WSStart( t2handle0, &ws_handle0, 0);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSSystemTick( ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                         &ulFree, &ulIdle,
                         &ulProcessesUsed, &ulProcessCount,
                         &ulResident, &ulTotalRam);
    printf( "\n  tick (rc=%i), %i %i %i %i %i %i %i %i %i\n",
            rc, ulNow, ulWS, ulAccessed, ulFree, ulIdle,
            ulProcessesUsed, ulProcessCount,
            ulResident, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSStop Process Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

#include "THESEUS0.h"

T2HANDLE0  t2handle0;
ULONG      rc;
int        i;
WS_HANDLE0 ws_handle0;
ULONG     ulNow, ulWS, ulAccessed;
ULONG     iIntervals, ulMinimum, ulRecommended, ulTotalRam;

rc = T2WSStart( t2handle0, &ws_handle0, 2);
if (rc == T2WS_OK)
{
  for (i=0; i<5; i++)
  {
    printf( " waiting 2 seconds.");
    DosSleep( 2000);
    rc = T2WSProcessTick(  ws_handle0, 3, &ulNow, &ulWS, &ulAccessed,
                          &ulTotalRam);
    printf( "  tick (rc=%i) pid=%i, %i %i %i %i\n",
            rc, i, ulNow, ulWS, ulAccessed, ulTotalRam);
  }
  rc = T2WSStop( &ws_handle0, TRUE, &iIntervals,
                 &ulMinimum, &ulRecommended, &ulAccessed);
  printf( " count = %i, minimum = %i, recommended = %i, accessed = %i\n",
          iIntervals, ulMinimum, ulRecommended, ulAccessed);
}


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2GetHandle0

o T2WSStart


ΓòÉΓòÉΓòÉ 12.2.3.5. T2WSCheck ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - T2WSCheck ΓòÉΓòÉΓòÉ

T2WSCheck is used to cause THESEUS0 to determine if a particular process or the
entire system can have working set data collected.

#include "THESEUS0.h"

ULONG ulPidToCheck;
BOOL  fStatus;

fStatus = T2WSCheck( ulPidToCheck);


ΓòÉΓòÉΓòÉ <hidden> Parameters - T2WSCheck ΓòÉΓòÉΓòÉ

ulPidToCheck (ULONG) - input
          The pid of the process to be queried. If ulPidToCheck is 0, then
          check for the system as a whole.


ΓòÉΓòÉΓòÉ <hidden> Return Values - T2WSCheck ΓòÉΓòÉΓòÉ

fStatus (BOOL)
          requestable status

   TRUE    A T2WSStart request for this process would probably succeed.
   FALSE   A T2WSStart request for this process will fail. See return values of
           T2WS_InUse and T2WS_SystemBemingDone in T2WSStart Return Values.


ΓòÉΓòÉΓòÉ <hidden> Example - T2WSCheck ΓòÉΓòÉΓòÉ

To determine if it is possible to collect system working set data:

if (T2WSCheck( 0))
  /* I can collect system working set data */
else
  /* not valid, someone else is already doing it or someone is
     collecting process data */

To determine if it is possible to collect working set data for the process with
pid 0002:

if (T2WSCheck( 2))
  /* I can collect process working set data */
else
  /* not valid, someone else is already doing it or someone is
     collecting system data */


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o T2WSStart


ΓòÉΓòÉΓòÉ 12.3. REXX Application Programming Interface ΓòÉΓòÉΓòÉ

The functions provided by THESEUS0.DLL are divided into the following
categories:

Initialization
          Function to cause THESEUS0.DLL to initialize for use by REXX.
Free Memory, Swapper, and Process Functions
          Functions to determine information about the system as a whole.
Working Set Functions
          Functions to perform working set analysis.

Errors are output to the stderr device.


ΓòÉΓòÉΓòÉ 12.3.1. RT2LoadFuncs ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2LoadFuncs ΓòÉΓòÉΓòÉ

RT2LoadFuncs is used to cause THESEUS0 to initialize all its internal
information that is required for later use and make the other functions
available to REXX.

rc = RT2LoadFuncs()


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2LoadFuncs ΓòÉΓòÉΓòÉ

rc (number) return code

   0  Initialization completed successfully.

   1  There is no THESEUS2.SYS installed in CONFIG.SYS. The program cannot
      continue.

   2  The version of THESEUS2.SYS installed in CONFIG.SYS is not the version
      expected.  ulDDVersion contains the versions found and required. The
      program cannot continue.

   3  The initialization code could not determine the size of the PTDA. The
      program cannot continue.

   4  The initialization code could not determine the format for the resident
      portion of the MTE. The program cannot continue.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2LoadFuncs ΓòÉΓòÉΓòÉ

This example will cause RT2LoadFuncs to perform the initialization of the
internal functions.

call RxFuncAdd "RT2LoadFuncs", "THESEUS0", "RT2LoadFuncs"
rc = RT2LoadFuncs()
if rc \= 0 then
  do
    say "THESEUS0 did not initialize properly.  It's return code = "rc
    exit
  end


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

Although the following routines are not directly related, the discussion of
errors is applicable.

o error handler

o T2Initialize


ΓòÉΓòÉΓòÉ 12.3.2. Free Memory, Swapper, and Process Functions ΓòÉΓòÉΓòÉ

These functions are used to acquire specific information about the system as a
whole.

Free memory function:

RT2FreeMemory            Determine the amount of free, idle, and locked memory.

SWAPPER.DAT analysis function:

RT2AnalyzeSwapper        Determine the amount of free and used space in the
                         SWAPPER.DAT file.

Process functions:

RT2FindProcesses         Returns an array with the current processes.
RT2RamUseByProcess       Returns an array with the current RAM usage by each
                         process.


ΓòÉΓòÉΓòÉ 12.3.2.1. RT2FreeMemory ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2FreeMemory ΓòÉΓòÉΓòÉ

RT2FreeMemory is used to cause THESEUS0 to calculate the amount of free, idle,
and locked memory.

FreeReturn = RT2FreeMemory()

FreeReturn contains:

FreeRam IdleRam DirtyRam LLockRam SLockRam BLockRam


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2FreeMemory ΓòÉΓòÉΓòÉ

FreeRam (number)
          The number of bytes of free memory.

IdleRam (number)
          The number of bytes of idle memory.

DirtyRam (number)
          The number of bytes of dirty memory. This memory is included in the
          idle memory.

LLockRam (number)
          The number of bytes of long-term locked memory.

SLockRam (number)
          The number of bytes of short-term locked memory.

BLockRam (number)
          The number of bytes of memory which is locked both long-term and
          short-term.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2FreeMemory ΓòÉΓòÉΓòÉ

This example will cause RT2FreeMemory to calculate the free, idle, and locked
memory.

parse value RT2FreeMemory() with freeRam idleRam dirtyRam LLockRam SLockRam BLockRam
say "freeRam  = "freeRam
say "idleRam  = "idleRam
say "dirtyRam = "dirtyRam
say "LLockRam = "LLockRam
say "SLockRam = "SLockRam
say "BLockRam = "BLockRam
say "cleanRam = "idleRam-dirtyRam" (computed value = idleRam - dirtyRam)"


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o Contents of the Free, Idle, and Locked Memory Display


ΓòÉΓòÉΓòÉ 12.3.2.2. RT2AnalyzeSwapper ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2AnalyzeSwapper ΓòÉΓòÉΓòÉ

RT2AnalyzeSwapper is used to cause THESEUS0 to calculate the amount of free and
used space in the SWAPPER.DAT file.

SwapReturn = RT2AnalyzeSwapper()

SwapReturn contains:

SwapUsed SwapFree


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2AnalyzeSwapper ΓòÉΓòÉΓòÉ

SwapUsed (number)
          The number of used disk frames.

SwapFree (number)
          The number of free disk frames.

Each disk frame is 4K bytes.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2AnalyzeSwapper ΓòÉΓòÉΓòÉ

This example will cause RT2AnalyzeSwapper to calculate the free and used space
in the SWAPPER.DAT file.

parse value RT2AnalyzeSwapper() with SwapUsed SwapFree
say "SwapUsed = "SwapUsed
say "SwapFree = "SwapFree


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o Contents of the Swapper Display


ΓòÉΓòÉΓòÉ 12.3.2.3. RT2FindProcesses ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2FindProcesses ΓòÉΓòÉΓòÉ

RT2FindProcesses is used to cause THESEUS0 to count the number of processes in
the system. It also returns an array which contains some information about each
process.

RT2FindProcesses "stem"


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2FindProcesses ΓòÉΓòÉΓòÉ

stem (string)
          The name of the stem variable used to contain the return list of
          processes.


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2FindProcesses ΓòÉΓòÉΓòÉ

stem.0 contains the number of processes found.

The list contains an entry for each process currently running. Each entry
contains:

ptdaPID pidParent cThreads processName
where:

ptdaPID          The PID of this process.
pidParent        The pid of this process's parent process.
cThreads         The number of threads in this process.
processName      The name of this process.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2FindProcesses ΓòÉΓòÉΓòÉ

This example will cause RT2FindProcesses to return an array with process names
and PIDs.

call RT2FindProcesses "pTable"
say "pTable count = "pTable.0
do i = 1 to pTable.0
  say i": '"pTable.i"'"
end
parse value pTable.1 with Pid Parent Threads Name
say "pid = "Pid", parent = "Parent", threads = "Threads", name = '"Name"'"


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o Contents of the Process List Display


ΓòÉΓòÉΓòÉ 12.3.2.4. RT2RamUseByProcess ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2RamUseByProcess ΓòÉΓòÉΓòÉ

RT2RamUseByProcess is used to cause THESEUS0 to determine the RAM used by each
process in the system. It returns an array which contains the usage of each
process.

T2RamUseByProcess "stem"


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2RamUseByProcess ΓòÉΓòÉΓòÉ

stem (string)
          The name of the stem variable used to contain the return list of
          processes.


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2RamUseByProcess ΓòÉΓòÉΓòÉ

stem.0 contains the number of processes found.

The list contains an entry for each process currently running. Each entry
contains:

ptdaPID Private Shared
where:

ptdaPID          The PID of this process. The entry with PID = 0000 contains
                 the memory used by the "system".
Private          The number of bytes of memory in the private arena of this
                 process. If multiple processes have the same page in their
                 private arenas, the process with the lowest PID value is
                 charged with the memory.
Shared           The number of bytes of memory from the shared arena that is
                 owned by this process.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2RamUseByProcess ΓòÉΓòÉΓòÉ

This example will cause RT2RamUseByProcess to return an array with PIDs and RAM
usage for each process.

call RT2RamUseByProcess "rTable"
say "rTable count = "rTable.0
do i = 1 to rTable.0
  say i": '"rTable.i"'"
end
parse value rTable.1 with Pid Private Shared
say "pid = "Pid", private = "Private", shared = "Shared


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o Contents of the RAM Usage by Process Display


ΓòÉΓòÉΓòÉ 12.3.3. Working Set Functions ΓòÉΓòÉΓòÉ

These functions are used to acquire working set information.

Working Set functions:

RT2WSStart            Sets up to do working set analysis for a particular
                      process or the entire system.
RT2WSSystemTick       Collects data when doing working set for the entire
                      system.
RT2WSProcessTick      Collects data when doing working set for a particular
                      process.
RT2WSStop             Stops the collection of working set data and returns
                      summary information.

The general way that these functions are used is:

RT2WSStart.
do while data is desired
  Wait for the desired interval to elapse.
  RT2WSSystemTick or RT2WSProcessTick.
end
RT2WSStop.


ΓòÉΓòÉΓòÉ 12.3.3.1. RT2WSStart ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

System Example

Process Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2WSStart ΓòÉΓòÉΓòÉ

RT2WSStart is used to cause THESEUS0 to set up for working set data collection
for a particular process or the entire system.

rc = RT2WSStart("ws_handle"ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇ)
                            ΓööΓöÇ,pidΓöÇΓöÿ


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2WSStart ΓòÉΓòÉΓòÉ

ws_handle0 (string)
          The name of a variable that will be the working set handle. This
          handle must be used in the RT2WSSystemTick/RT2WSProcessTick and
          RT2WSStop calls.

          Note:  The value returned in this variable must not be changed.

pid (number)
          The pid of the process that you want to measure. If none is
          specified, then the working set of the entire system is measured. The
          process with pid of 1 is not valid for measurement.


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2WSStart ΓòÉΓòÉΓòÉ

rc (number) return code

   0  The RT2WSStart call completed properly. The ws_handle0 value is returned.

   1  The process requested is already having working set data collected for
      it. A process can have working set data collected for it from only one
      place.

   2  Working set collection is being done for the system. If system is being
      done, no process can have data collected for it.

   4  An error occurred during initialization. Working set data cannot be
      collected.

   5  The requested process was not found as an active process.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSStart System Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle")
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSSystemTick("ws_handle",3) with Rc,
                  Now WS Accessed Free Idle ProcUsed,
                  ProcCount Resident TotalRam
      say Rc Now WS Accessed Free Idle,
          ProcUsed ProcCount Resident TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSStart Process Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle",2)
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSProcessTick("ws_handle",3) with Rc,
                  Now WS Accessed TotalRam
      say Rc Now WS Accessed TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o RT2WSSystemTick

o RT2WSProcessTick

o RT2WSStop

o Working Set of the Entire System?

o Working Set of a Single Process?


ΓòÉΓòÉΓòÉ 12.3.3.2. RT2WSSystemTick ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Notes

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2WSSystemTick ΓòÉΓòÉΓòÉ

RT2WSSystemTick is used to cause THESEUS0 to determine the amount of memory
accessed since the last RT2WSSystemTick call or from the RT2WSStart call.

TickReturn = RT2WSSystemTick("ws_handle", Intervals)

TickReturn contains:

rc Now WS Accessed Free Idle ProcUsed ProcCount Resident TotalRam


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2WSSystemTick ΓòÉΓòÉΓòÉ

ws_handle0 (string)
          The name of the variable that was used in the RT2WSStart.

Intervals (number)
          The number of intervals that constitute the working set. This value
          must be less than 254 for the computations to work properly.


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2WSSystemTick ΓòÉΓòÉΓòÉ

rc (number)
          return code

   0  The RT2WSSystemTick call completed properly.

   3  The ws_handle0 passed was not valid.

Now (number)
          The number of pages of memory that was accessed during the last
          interval.

WS (number)
          The number of pages of memory in the working set.

Accessed (number)
          The number of pages of memory accessed since the RT2WSStart was
          issued.

Free (number)
          The number of pages of free memory.

Idle (number)
          The number of pages of idle memory.

ProcUsed (number)
          The number of processes that had memory accessed during the interval.
          This value indicates the number of processes which are both running
          and touching non-system memory.

ProcCount (number)
          The total number of processes found during the interval. This number
          changes as processes are created or destroyed.

Resident (number)
          The number of pages of resident memory.

TotalRam (number)
          The total number of pages of RAM being used by OS/2*.


ΓòÉΓòÉΓòÉ <hidden> Notes - RT2WSSystemTick ΓòÉΓòÉΓòÉ

The interval between calls to RT2WSSystemTick should be chosen carefully. If
the interval is too short, the processing could cause the rest of the system to
have problems. However, if the interval is too long, dynamic memory allocated
and freed will be missed. The overhead is dependent on the number of processes,
more so than the amount of RAM in the machine. The interval should never be
less than 1 second nor longer than 1 minute.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSSystemTick ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle")
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSSystemTick("ws_handle",3) with Rc,
                  Now WS Accessed Free Idle ProcUsed,
                  ProcCount Resident TotalRam
      say Rc Now WS Accessed Free Idle,
          ProcUsed ProcCount Resident TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o RT2WSStart

o RT2WSStop

o Working Set of the Entire System?

o System Working Set


ΓòÉΓòÉΓòÉ 12.3.3.3. RT2WSProcessTick ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

Notes

Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2WSProcessTick ΓòÉΓòÉΓòÉ

RT2WSProcessTick is used to cause THESEUS0 to determine the amount of memory
accessed since the last RT2WSProcessTick call or from the RT2WSStart call.

TickReturn = RT2WSProcessTick("ws_handle", Intervals)

TickReturn contains:

rc Now WS Accessed TotalRam


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2WSProcessTick ΓòÉΓòÉΓòÉ

ws_handle0 (string)
          The name of the variable that was used in the RT2WSStart.

Intervals (number)
          The number of intervals that constitute the working set. This value
          must be less than 254 for the computations to work properly.


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2WSProcessTick ΓòÉΓòÉΓòÉ

rc (number)
          return code

   0  The T2WSProcessTick call completed properly.

   3  The ws_handle0 passed was not valid.

   5  The requested process was not found as an active process. It was found
      when the RT2WSStart was done, but has since terminated.

Now (number)
          The number of pages of memory that was accessed during the last
          interval.

WS (number)
          The number of pages of memory in the working set.

Accessed (number)
          The number of pages of memory accessed since the RT2WSStart was
          issued.

TotalRam (number)
          The total number of pages of RAM being used by OS/2*.


ΓòÉΓòÉΓòÉ <hidden> Notes - RT2WSProcessTick ΓòÉΓòÉΓòÉ

The interval between calls to RT2WSProcessTick should be chosen carefully. If
the interval is too short, the processing could cause the rest of the system to
have problems. However, if the interval is too long, dynamic memory allocated
and freed will be missed. The overhead is dependent on the number of processes
being monitored, more so than the amount of RAM in the machine. The interval
should never be less than 1 second nor longer than 1 minute.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSProcessTick ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle",2)
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSProcessTick("ws_handle",3) with Rc,
                  Now WS Accessed TotalRam
      say Rc Now WS Accessed TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o RT2WSStart

o RT2WSStop

o Working Set of a Single Process?

o Process Working Set


ΓòÉΓòÉΓòÉ 12.3.3.4. RT2WSStop ΓòÉΓòÉΓòÉ

Select an item:

Function Syntax

Parameters

Return Values

System Example

Process Example

Related Functions


ΓòÉΓòÉΓòÉ <hidden> Syntax - RT2WSStop ΓòÉΓòÉΓòÉ

RT2WSStop is used to cause THESEUS0 to count the number of

StopReturn = RT2WSStop("ws_handle")

StopReturn contains:

rc Intervals Minimum Recommended Accessed


ΓòÉΓòÉΓòÉ <hidden> Parameters - RT2WSStop ΓòÉΓòÉΓòÉ

ws_handle0 (string)
          The name of the variable that was used in the RT2WSStart.

          Note:  The value of this variable is destroyed. (A DROP is done on
          the variable by RT2WSStop.)


ΓòÉΓòÉΓòÉ <hidden> Return Values - RT2WSStop ΓòÉΓòÉΓòÉ

rc (number)
          return code

   0  The T2WSStop call completed properly.

   3  The ws_handle0 passed was not valid.

Intervals (number)
          The number of data collections cycles completed.

Minimum (number)
          The maximum value from the now column. This is the amount of memory
          absolutely required to run the application without "thrashing"
          memory.

Recommended (number)
          The maximum value from the ws column. This is the recommended amount
          of memory for the application to run with minimum impact on paging.

Accessed (number)
          The maximum value from the accessed column. This is the amount of
          memory required to run the application with no paging activity.


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSStop System Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for the entire
system. It will sample every 2 seconds and will take 5 samples. The working set
interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle")
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSSystemTick("ws_handle",3) with Rc,
                  Now WS Accessed Free Idle ProcUsed,
                  ProcCount Resident TotalRam
      say Rc Now WS Accessed Free Idle,
          ProcUsed ProcCount Resident TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Example - RT2WSStop Process Working Set ΓòÉΓòÉΓòÉ

This example will cause THESEUS0 to collect working set data for process with
pid of 2. It will sample every 2 seconds and will take 5 samples. The working
set interval is set as 3 intervals. The results are printed to the window.

rc = RT2WSStart("ws_handle",2)
if rc = 0 then
  do
    do i = 1 to 5
      say "sleep for 2 seconds."
      call SysSleep 2
      parse value RT2WSProcessTick("ws_handle",3) with Rc,
                  Now WS Accessed TotalRam
      say Rc Now WS Accessed TotalRam
    end
    StopReturn = RT2WSStop("ws_handle")
    parse value StopReturn with Rc Intervals Minimum Recommended Accessed
    say Rc Intervals Minimum Recommended Accessed
  end


ΓòÉΓòÉΓòÉ <hidden> Related Topics ΓòÉΓòÉΓòÉ

o RT2LoadFuncs

o RT2WSStart


ΓòÉΓòÉΓòÉ 13. Errors ΓòÉΓòÉΓòÉ

THESEUS2 displays errors in two different ways:

o in popup windows
o imbedded within output.


ΓòÉΓòÉΓòÉ 13.1. Popup Window Errors ΓòÉΓòÉΓòÉ

THESEUS2 generates several popup windows:

o Cannot describe an HCO
o Clipboard error
o Dependent window error
o Error in decimal input
o Error in hex input
o Find text not entered
o Incorrect THESEUS2.SYS version
o Missing THESEUS2.SYS file
o Missing THESEUSR.DLL file
o No monospaced font
o Out of windows error
o Process ended
o PTDA size not determined
o MTE format not recognized
o File name not valid


ΓòÉΓòÉΓòÉ 13.1.1. Cannot describe an HCO ΓòÉΓòÉΓòÉ

Message text:
     An HCO cannot be described.

Explanation:
     The hco is the only one of the address/handle type of hypertext links that
     THESEUS2 is not programmed to describe.

Corrective action:
     Do not request a description of an hco.


ΓòÉΓòÉΓòÉ 13.1.2. Clipboard error ΓòÉΓòÉΓòÉ

Message text:
     Could not allocate memory for Clipboard data.  Copy request cannot be
     done.

Explanation:
     An error was received while trying allocate shared memory. This memory is
     required in order to copy the marked area into the clipboard.

Corrective action:
     Free some memory and try the request again.


ΓòÉΓòÉΓòÉ 13.1.3. Dependent Window Error ΓòÉΓòÉΓòÉ

Message text:
     This window cannot be closed before its dependent window is closed.

Explanation:
     Working Set detail windows are dependent on the Working Set window for
     some of their data.

     As long as the Working Set Detail (by Object) or Working Set Summary by
     Process window is present, the Working Set window cannot be closed.

Corrective action:
     Close the Working Set Detail (by Object) or Working Set Summary by Process
     window, then you can close the Working Set window.


ΓòÉΓòÉΓòÉ 13.1.4. Error in decimal input ΓòÉΓòÉΓòÉ

Message text:
     Enter a valid decimal number in the 's' field.
     s can be `Interval' or `Intervals per Working Set'.

Explanation:
     An error was made when typing the desired decimal value into the dialog
     field.

Corrective action:
     When you press OK, the cursor is placed in the erroneous field in the
     dialog. Type the correct decimal character and press Enter.


ΓòÉΓòÉΓòÉ 13.1.5. Error in hex input ΓòÉΓòÉΓòÉ

Message text:
     Enter a valid hex number in the 's' field.
     s can be `Address', `Length', `Width', `Selector', `or Offset'.

Explanation:
     An error was made when typing the desired hexadecimal value into the
     dialog field.

Corrective action:
     When you press OK, the cursor is placed in the erroneous field in the
     dialog. Type the correct hexadecimal character and press Enter.


ΓòÉΓòÉΓòÉ 13.1.6. Find text not entered ΓòÉΓòÉΓòÉ

Message text:
     Text must be typed in the field.

Explanation:
     You did not type a string to find.

Corrective action:
     When you press OK, the cursor is placed in the erroneous field in the
     dialog. Type the string you want to find and press Enter.


ΓòÉΓòÉΓòÉ 13.1.7. Incorrect THESEUS2.SYS Version ΓòÉΓòÉΓòÉ

Message text:
     THESEUS2.SYS is not version nn.  Please install the current version.

Explanation:
     The version of THESEUS2.SYS which is installed in CONFIG.SYS is not the
     expected version. nn gives the version number that is expected. If the
     correct device driver is not found, THESEUS2 cannot continue to run.

Corrective action:
     Install the correct version of THESEUS2.SYS in your CONFIG.SYS file, then
     restart your computer.


ΓòÉΓòÉΓòÉ 13.1.8. Missing THESEUS2.SYS File ΓòÉΓòÉΓòÉ

Message text:
     THESEUS2.SYS is not installed in your CONFIG.SYS. Please install the
     current version and restart the computer.

Explanation:
     THESEUS2 is made up of several files. The device driver THESEUS2.SYS must
     be installed in the CONFIG.SYS. If this device driver is not found,
     THESEUS2 cannot continue to run.

Corrective action:
     Install THESEUS2.SYS in your CONFIG.SYS file, then restart the computer.


ΓòÉΓòÉΓòÉ 13.1.9. Missing THESEUSR.DLL File ΓòÉΓòÉΓòÉ

Message text:
     THESEUS2 could not locate its resource file THESEUSR.DLL. Please place
     THESEUSR.DLL in a directory pointed to by the LIBPATH statement in
     CONFIG.SYS then restart the computer.

Explanation:
     THESEUS2 is made up of several files. The resources used by the
     Presentation Manager are located in THESEUSR.DLL. If this file is not
     found, THESEUS2 cannot continue to run.

     The LIBPATH statement in your CONFIG.SYS file must contain the directory
     that contains THESEUSR.DLL.

Corrective action:
     Either:

   o Move THESEUSR.DLL into a directory that is in the LIBPATH statement, or
   o Add the directory that contains THESEUSR.DLL to the LIBPATH statement.
     Restart the computer for the changed LIBPATH statement to become
     effective.


ΓòÉΓòÉΓòÉ 13.1.10. No Monospaced Font ΓòÉΓòÉΓòÉ

Message text:
     A monospaced font was not found.  Please install one.

Explanation:
     THESEUS2 uses only monospaced Single Byte Character Set (SBCS) fonts. The
     "System Monospaced - 8x12" font is used, if it is present. If it is not
     present and another monospaced font is present, then the first monospaced
     font found will be used. If a monospaced font is not found, THESEUS2
     cannot continue to run.

Corrective action:
     Install a monospaced font, then try THESEUS2 again.


ΓòÉΓòÉΓòÉ 13.1.11. Out of Windows Error ΓòÉΓòÉΓòÉ

Message text:
     All THESEUS2 windows are in use. You must close one before another can be
     created.

Explanation:
     THESEUS2 can generate only 16 Detail windows.

Corrective action:
     Close one or more of the open THESEUS2 Detail windows. The Windows
     pull-down on the Process Hierarchy window contains a list of the Detail
     windows currently open.


ΓòÉΓòÉΓòÉ 13.1.12. Process Ended ΓòÉΓòÉΓòÉ

Message text:
     The selected process has ended.  The request cannot be performed.

Explanation:
     You had previously selected a process on the Process Hierarchy window. The
     process you had selected has ended and you have requested that a display
     be generated from that process.

Corrective action:
     Only active processes can be used for display generation.


ΓòÉΓòÉΓòÉ 13.1.13. PTDA Size not Determined ΓòÉΓòÉΓòÉ

Message text:
     This version of OS/2 is not supported by THESEUS2. The size of the PTDA
     cannot be determined.

Explanation:
     Different levels of OS/2 2.x have different sizes of PTDAs. THESEUS2 must
     "discover" the size of the PTDA during its initialization. The version of
     OS/2 2.x that you have is so different from those THESEUS2 expects that it
     could not determine the PTDA size.

Corrective action:
     Either:

   o Acquire a version of THESEUS2 that supports the installed version of OS/2
     2.x, or
   o Install a version of OS/2 2.x that THESEUS2 supports.


ΓòÉΓòÉΓòÉ 13.1.14. MTE Format not Recognized ΓòÉΓòÉΓòÉ

Message text:
     This version of OS/2 is not supported by THESEUS2. The Module Table Entry
     (MTE) format is unknown.

Explanation:
     Different levels of OS/2 2.x have different formats of the MTEs. THESEUS2
     must "discover" the format of the MTE during its initialization. The
     version of OS/2 2.x that you have is so different from those THESEUS2
     expects that it could not determine the MTE format.

Corrective action:
     Either:

   o Acquire a version of THESEUS2 that supports the installed version of OS/2
     2.x, or
   o Install a version of OS/2 2.x that THESEUS2 supports.


ΓòÉΓòÉΓòÉ 13.1.15. File Name not Valid ΓòÉΓòÉΓòÉ

Message text:
     The file name is not valid for the file system on the specified disk.

Explanation:
     The file name supplied in the SaveAs dialog was not accepted by the
     operating system. You may have specified:

   o An invalid path, or
   o A long file name for a FAT disk.

Corrective action:
     Specify a correct path and file name.


ΓòÉΓòÉΓòÉ 13.2. Imbedded Errors ΓòÉΓòÉΓòÉ

THESEUS2 generates some errors imbedded within the output:

o Linear address: no Page Table
o Linear address+length: no Page Table
o Linear address: page not present
o Linear address+Length: page not present
o Linear address+Length: > 32 bits
o SystemArenaHeaderLinear was not properly located
o Unknown error to error_handler0

(When the low-level error routine cannot determine what window is generating
data, these messages may appear in a popup window. However, they will normally
appear in the output window text at the point that the error was detected.)


ΓòÉΓòÉΓòÉ 13.2.1. Linear address: no Page Table ΓòÉΓòÉΓòÉ

Message text:
     >>> Linear address: no Page Table, linear=llllllll.

Explanation:
     A "read linear" request was done in the program. The requested linear
     address is not valid because there is no page table defined for that
     linear address.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.2. Linear address+length: no Page Table ΓòÉΓòÉΓòÉ

Message text:
     >>> Linear address+length: no Page Table, linear=llllllll,
     length=hhhhhhhh.

Explanation:
     A "read linear" request was done in the program. The linear address at the
     end of the requested area is not valid because there is no page table
     defined for that linear address.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.3. Linear address: page not present ΓòÉΓòÉΓòÉ

Message text:
     >>> Linear address: page not present, linear=llllllll.

Explanation:
     A "read linear" request was done in the program. The requested linear
     address is not valid because the page at that linear address is not
     present.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.4. Linear address+Length: page not present ΓòÉΓòÉΓòÉ

Message text:
     >>> Linear address+Length: page not present, linear=llllllll,
     length=hhhhhhhh.

Explanation:
     A "read linear" request was done in the program. The linear address at the
     end of the requested area is not valid because the page at that linear
     address is not present.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.5. Linear address+Length: > 32 bits ΓòÉΓòÉΓòÉ

Message text:
     >>> Linear address+Length: > 32 bits, linear=llllllll, length=hhhhhhhh.

Explanation:
     A "read linear" request was done in the program. The requested linear
     address is not valid because the address of the end of the area is greater
     than 32 bits.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.6. SystemArenaHeaderLinear was not properly located ΓòÉΓòÉΓòÉ

Message text:
     >>> SystemArenaHeaderLinear was not properly located at llllllll.

Explanation:
     The "System Arena Header" was not found.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ 13.2.7. Unknown error to error_handler0 ΓòÉΓòÉΓòÉ

Message text:
     >>> Unknown error to error_handler0: error_code=i1, p1=i2, p2=i3.

Explanation:
     An error was sent to the error handler which had an unknown error code.
     The values printed (i1, i2, i3) are the inputs to the routine.

     This is an internal error in the program. It is not caused by user input.
     It is normally caused by the program improperly interpreting a value in
     one of the OS/2 control blocks. It is presented for the program support
     personnel's use.


ΓòÉΓòÉΓòÉ <hidden> Enter Button ΓòÉΓòÉΓòÉ

When you press the Enter button, the action is performed.


ΓòÉΓòÉΓòÉ <hidden> Find Button ΓòÉΓòÉΓòÉ

When you press the Find button, the search begins from the start of the window.


ΓòÉΓòÉΓòÉ <hidden> OK Button ΓòÉΓòÉΓòÉ

When you press the OK button, the dialog is canceled and you are returned to
the window.


ΓòÉΓòÉΓòÉ <hidden> Cancel Button ΓòÉΓòÉΓòÉ

When you press the Cancel button, the dialog is canceled and you are returned
to the window.