Category : OS/2 Files
Archive   : 20MENU.ZIP
Filename : OS20MMHO.P43

 
Output of file : OS20MMHO.P43 contained in archive : 20MENU.ZIP

H&@ƒºK$k$ª"¿"OS20MMHO.P43 OS20MEMU *** Help *** Version 1.0 1-7-93
Authors: Glenn Brew & Ross Cook (c) Copyright IBM Corp. 1987-1993
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ


Application Details "Help"

This panel provides details on several application variables for
the selected process.

PID: - this is the PID you selected on the main panel.

Name: - the name of the program for this PID.

After these entries appears information on the total storage
available for use by this process. This is provided as a summary
followed by details on the memory objects available to this
program.


The summary items provided are:

System Storage - the total amount of system storage used
for this process.

This item includes the processor defined LDT; operating
system control blocks for managing the process as well as
each thread the process has defined; memory required to
manage the private memory objects the process creates; and
other items of system storage OS/2 may require.

Private - the size of all memory objects for this process.

This item will include memory objects in the process' main
.EXE file plus any non-shared objects allocated by the
program or by any dynamic link modules (DLLs) in use by the
process.

Shared - the size of the resident and swapped memory for the
shared objects in use by this process.

This item will include dynamic data memory objects allocated
with sharing indicated plus DLL objects which may be shared
with other processes. This is further broken down into the
shared memory objects created by the application code itself
and those created by the operating system DLLs on behalf of
this application (see the 'object details' section below.)

In Storage - the total number of bytes of private memory which
is actually present in storage.

Swapped to Disk - the total number of bytes for the memory
objects which have been swapped to disk.

Discardable - the amount of this process' storage which is
discardable and that will be loaded from the .EXE / .DLL file
when needed.

Allocated but Not Used - the amount of memory which has been
allocated but not used by this program.

Note that the details of this type memory appears above this
entry (under the 'Not Accessed' heading) and also appears
in the object detail listing which follows under the same
heading.


Following this summary information are details on each individual
memory object: their type, size, an indicator of their presence in
storage, and the name of the module containing / defining them.
This detailed memory object listing is divided into three sections:

1. Objects which are private to this process.

This would generally be data objects and may be either from
the program's EXE file or objects created private to this
process by that program or by a DLL routine.

2. "Application Shared Objects:" - Objects which may be shared
with other processes. This does not include operating system
objects.

The code (instructions) of a program is one type of shared
object but this could also include data that a DLL routine
uses to coordinate activities it performs on behalf of several
concurrently executing applications.

3. "System Shared Objects:" - OS/2 provides many of its own
functions as DLLs - these are the type objects which appear
in this section.

These items may be shared among many, or all, processes.
These objects can be either code or data.


This detailed section is provided in a scrollable table with these
column headings:

Linear Address - the Linear Address where the object is found.

Shared/Private - an indication if the object is shared or
private.

Maximum Size - the amount of virtual space reserved for this
object.

Note that this size is simply the largest size this object
can ever attain and may have little relation to the storage
actually used by this object. For a 16-bit segment, this
size will always be 64 Kb. For a 32-bit object, the size
will be the maximum size this object may be increased to or
64 Kb as a minimum. Only by summing "In Memory" and
"Swapped/Disc" (below) can you find the memory actually in
use for an object.

In Memory (Kb) - the amount of storage in use by this object
which is actually present in memory.

Swapped/Disc (Kb) - (Swapped / Discarded) the amount of storage
for this object which is not in memory; i.e., has been
paged to disk or discarded to be reloaded from the
executable file when needed.

Not Accessed - the amount of memory which has been committed to
this object but which has never be actually used by any
program in the system.

Created By - the name of the file or system component which
created this memory object.


*******************************************************************
* *
* Please note that the storage size information presented here *
* must be analyzed and studied with care and that these values *
* may not portray the storage in use by a particular program *
* with a high degree of accuracy. *
* *
* Although care has been taken in the preparation of this *
* program, and the data presented here is felt to be useful and *
* representative of the storage actually in use by the selected *
* program, there are certain items which may have been created *
* on behalf of this program that are not reported here *
* resulting in a lower than actual storage usage being reported. *
* *
* Examples are the system control blocks needed to track various *
* resources the program may be using such as files, system *
* semaphores, pipes, queues, etc. While it is certainly *
* possible to account for all such storage items, the *
* performance cost to do so is not small and is usually felt to *
* be prohibitive. *
* *
* On the other hand, note also that the values found here may in *
* fact be higher than the storage actually in use by this *
* process. Probably the most common reason for this "over *
* reporting" is because certain shared memory objects which are *
* addressable by this process may not ever be actually used by *
* this instance of this programs execution. *
* *
* Another reason for the storage used to be larger than one *
* might expect has to do with the physical characteristics of *
* virtual memory and paging. With paging enabled, the minimum *
* amount of physical memory which may be allocated by the *
* operating system is 4 Kb. This results in a (theoretical) *
* average waste of 2 Kb for each memory object. This inaccuracy *
* is particularly noticeable with 16-bit applications that *
* allocate many very small segments - each of which occupies *
* 4 Kb in a paging environment. *
* *
*******************************************************************


Also available is an option to save the contents of the current
panel display in a disk file in the current directory. This makes
analysis of a particular application's storage usage much easier.

To use this option, first select the process of interest on the
main screen, then:

Function key F9 is used to cause the contents of this option's
panel to be placed in the file OS20MEMO.DAP. If this file
already exists, the data is appended to the current contents.

Function key F11 (Alt-F1) is used to delete the application
detail file OS20MEMO.DAP.

Enter Esc=Cancel à"
¹¹ÿÿÿ
¹
¹ÿÿÿ#¦#ÿÿÿÿÿÿÿÿ#¦#ÿÿÿÿÿÿÿÿ

  3 Responses to “Category : OS/2 Files
Archive   : 20MENU.ZIP
Filename : OS20MMHO.P43

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/