Earlier this year I had several problems with these
theseholds. The most common problem I had was with the
CM data segments. Every session was taking 5 processes
and filling this up. Moving to 6.5 increased this
table 4 fold.We also started to usie the NEWCI command
which brough the processes down to 4 per user.

Because of the problems, I created a job which will
stop users logging on if the tables hit 97%. this will
stop system failures. Below is the JCL that I created
which runs in the SYSSTART.

Regards

Steve


!job thmonit,manager.sys;outclass=lp,2
!thmgr
 em
 mt timers 90 97 yes job_session_control
 mt access_rights 90 97 yes job_session_control
 mt cm_code_segments 90 97 yes job_session_control
 mt cm_data_segments 90 97 yes job_session_control
 mt cm_physical_code_segments 90 97 yes
job_session_control
 mt cm_ports_completion 90 97 yes job_session_control
 mt cm_ports 90 97 yes job_session_control
 mt file_descriptors 90 97 yes job_session_control
 mt file_extents 90 97 yes job_session_control
 mt io_notifications 90 97 yes job_session_control
 mt io_requests 90 97 yes job_session_control
 mt locality_list_entries 90 97 yes
job_session_control
 mt memory_information_blocks 90 97 yes
job_session_control
 mt process_information_blocks 90 97 yes
job_session_control
 mt shared_global_space 90 97 yes job_session_control
 mt sys_vol_set_permanent_space 90 97 yes
job_session_control
 mt sys_vol_set_transient_space 90 97 yes
job_session_control
 mt timer_req_list 90 97 yes job_session_control
 mt virtual_space_cache 90 97 yes job_session_control
 mt virtual_space_objects 90 97 yes
job_session_control
 mt virtual_storage 90 97 yes job_session_control
 exit
!eoj












 --- "Eric H. Sand" <[log in to unmask]> wrote: > Hi Folks,
>     Many of our customer sites are attempting to
> qualify their systems in
> terms of system performance and resources in
> preparation for upgrading and I
> have been researching the "Threshold Manager"
> program that began to be
> included in the MPE/iX 5.0 FOS to address this.
> Other than the section
> "Using Threshold Manager" in the "Performing System
> Management Tasks"
> manual, I have not been able to find any references
> to it in other HP
> manuals. This section in the manual is very thorough
> in outlining how to
> activate and monitor the various "resource names",
> but nothing that outlines
> what the "resource names" themselves represent.
>
>     I contacted the RC and was informed they have
> only one(1) internal
> document that attempts to discuss what each of these
> resource names
> represent. Many of the items in this document appear
> to be at a technical
> level that someone who is familiar with MPE
> internals might understand, but
> there seems to be very little explanation of how
> they "measure" or
> "represent" system performance. Can anyone add any
> insight to these
> "resource names" and perhaps how they interact with
> each other?
>
>     I have included the internal HP document
> below(long).
>
>
>                            Thank you......Eric Sand
>
> [log in to unmask]
>
>
>
> The following is a brief description of the system
> resources currently
> monitored by Threshold Manager
>
> ACCESS RIGHTS
>    This resource is also referred to as the Extent
> B-Tree AR Table.  Disk
> files and virtual memory
>    disk areas are allocated in contiguous pieces
> called "extents". Each node
> in the Extent AR B-
>    Tree can describe up to eight extents. If an
> object contains more than
> eight extents, it will use
>    additional nodes as needed. Every non-resident
> object with variable
> access rights will obtain
>    one or more nodes in this table when it is mapped
> in (opened). NOTE:
> Objects with variable
>    access rights are those for which not all pages
> have identical read
> and/or write access or the
>    same  privilege level. NM program files and NM
> library files are examples
> of objects with
>    variable access rights. Page 0 has write access
> in addition to the
> read/execute access that is
>    given to the other pages of the file. Extent
> information about objects
> with fixed access rights is
>    kept in the Extent B-TreeTable.
>
> CM CODE SEGMENTS
>    Compatibility Mode (CM) Code Segments are part of
> a Segmented Library
> (SL). Entries in the
>    Code Segment Table (CST) are allocated whenever
> an SL segment is  loaded
> for the first
>    time. This occurs when: *A CM program is executed
> via the :RUN command
> with the ;LIB=
>    option *SL segments are :ALLOCATEd *A procedure
> (in a Segmented Library)
> is loaded via
>    the LOADPROC intrinsic CST entries are shared.
> Loading a SL segment after
> the first  time
>    will not result in the allocation of an
> additional CST  entry. When the
> last user of a particular
>    code segment unloads  that segment, the CST entry
> is released.
>
> CM DATA SEGMENTS
>    Compatibility Mode (CM) Data Segments contain
> program data for processes
> during the time
>    they  execute in compatibility mode,  and for
> system data structures that
> have not yet been
>    converted to Native Mode  (NM). Also, some CM
> data structures may have
> been retained
>    because some application and third party code
> depend on accessing them
> directly. Note that
>    even some NM programs may need CM Data Segment
> entries.
>
> CM PHYSICAL CODE SEGMENTS
>    Compatibility Mode (CM) Physical Code Segments
> are allocated by the
> operating system and
>    typically are contained in the system Segmented
> Library (SL.PUB.SYS).
> There are 255 entries
>    in the CST which are reserved for these segments.
>
> CM PORTS COMPLETION
>    CM Ports Completion are used as a fast queuing
> and messaging system
> within the operating
>    system, primarily by datacomm subsystems.
> Processes (including system
> processes) create
>    ports at which they can receive brief messages
> from other processes or
> other parts of the
>    system. Typically, processes will eventually wait
> on some port, to be
> awakened when a
>    message arrives then act on that message.
>
> CM PORTS
>    CM Ports are used as a very fast queuing and
> messaging system within the
> operating system.
>    Processes (including system processes) create
> ports at which they can
> receive brief messages
>    from other processes or other parts of the
> system. Typically, processes
> will eventually wait on
>    some port and then be awakened when a message
> arrives then act on that
> message.
>
> FILE DESCRIPTORS
>    This resource is also referred to as the
> VSOD/GUFD table (Virtual Space
> Object
>    Descriptor/Global Unique File Descriptor  Table).
> Every object in the
> system requires
>    an  entry in either the VSOD or VSOD/GUFD table
> (with the exception  of
> certain resident
>    objects that reside in the Disabled Expandable
> VSOD table). All file
> objects obtain an entry in
>    the VSOD/GUFD table when they are mapped in (or
> opened). When the  file
> is mapped out
>    (closed), the entry is linked onto a list  known
> as the LRU (Least
> Recently Used) list. If the
>    same file is  opened again, the LRU list is
> searched to see if an entry
> already  exists for that
>    file. If so, the entry is re-used which saves
> the overhead of mapping
> the file in again. If the
>    entry is not on  the LRU list, a new entry must
> be obtained. If there are
> no  free entries in the
>    table, an entry is obtained from the LRU  list.
> The object previously
> associated with that LRU
>    entry is now considered to be mapped out.
>
>    Entries are allocated within the Process Local
> File Descriptor  (PLFD)
> table.  Each PLFD entry
>    is paired with a GDPD entry  within the PLFD
> table. However, if a native
> mode file is opened
>    with Multi Access (intra-job) or G-Multi Access
> (inter-job),  then the
> GDPD entry is allocated
>    from the System GDPD table.  Subsequent opens of
> the same Multi Access
> file will share the
>    same GDPD entry. If the file is a CM file (for
> example, Message, RIO, or
>
=== message truncated ===

____________________________________________________________
Nokia Game is on again.
Go to http://uk.yahoo.com/nokiagame/ and join the new
all media adventure before November 3rd.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *