               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.



         OS/2 RESOURCE MONITOR FACILITY VERSION 0.1

Files included in this archive set contains the following:

     OSRM201.DOC    =>   This file
     OSRM2.INI      =>   Sample Initialization File
     OSRM201.EXE    =>   Real Time Monitor Only.
     OSRM2D01.DLL   =>   Dynamic Support Dynalibs
     OSRM2S01.DLL   =>   Static Support Dynalibs

This application is shareware, software that is free to use
for a trial period, that being fairly defined by C.O.L.
Consulting LTD. as 1 months time ( 30 days ).

If at the end of the evaluation period, as defined above,
you do not wish to register OSRM201.EXE, you are obligated
to discontinue its use.

This shareware archive package which includes those files as
listed above must be distributed in their entirety, C.O.L.
Consulting LTD, has no responsibility for packages that are
missing documentation, executable files or supportive files.

As mentioned previously, OSRM2 is shareware and thus
supported by the user community. Any questions, comments,
suggestions and criticisms are welcome. Please see the
registration and service section at the end of this
document.

C.O.L. Consulting developers have not inserted any nagware
signs, timers or flags that pester you with the fact that
you have an unregistered copy. As a group they voted
unanimously that they hate this ( feature? ) and more often
then not will discontinue the use of the product for that
very reason.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


            GENERAL INFORMATION AND REGISTRATION

C.O.L. Consulting LTD., incorporated January of 1989, is a
registered subchapter 'S' corporation in the State Of New
York. The corporation provides DP consulting, software
development ( MVS, VM, MS-DOS, UNIX, OS/2 ) as well as
maintenance services.

C.O.L. Consulting LTD., reserves the right to limit
functionality of future versions in unregistered copies, but
will continue to support Version 0.1 in it's entirety.

The software included in this archive package is a fully
functional evaluation copy of OSRM2 Version 0.1. There are
no hidden commands, initialization files or system
parameters that will be found.

Upgrade costs will be based on the amount of functionality
that is added to the application. For instance, C.O.L.
Consulting LTD. will be porting this over to run under the
Presentation Manager of OS/2 as a full PM application, OSRM2
Version 1.1.

If you care to register your copy of OSRM2 Version 0.1,
please refer to the upgrading information section and
registration sheet at the end of this document. Both single
user and corporate discounts are available.

If you register OSRM2 Version 0.1 before the release of
Version 1.0 you will save $30.00 ( Your price would be
$40.00 )  off the list price of OSRM2 Version 1.0. With
receipt of your registration fee, you will receive an OSRM2
Version 1.0 upgrade by mail. The upgrade will include
printed documentation along with the upgraded system,
specify floppy format when registering, and a registration
number to be used for customer support.

If you register Version 0.1 before the release of Version
1.0, you will also be able to upgrade to Version 1.1 at 20%
off the list price.

If you do not register OSRM2 Version 0.1 and Version 1.0 is
released, you will be required to register Version 1.0 at
the full price ( $70.00 ).

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


            GENERAL INFORMATION AND REGISTRATION



An agreement with HH-InfoNEt BBS, New Hartford CT, enables
you to pre-register your copy and expedite the registration
process. Upon completion of the online registration script,
see the registration section at the end of this document,
all you need do is send in your registration payment.

Through HH-InfoNEt you will also be able to communicate
directly with the OSRM2 developers for all versions of the
system. OSRM2 registered users will receive priority
response and will receive update information by mail.

Thank you for your support,

                    Frank V. Castellucci
                         President
                    C.O.L. Consulting, LTD.



               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                     TABLE OF CONTENTS

     

     Introduction....................................1

     Hardware Requirements...........................6

     Installation....................................7

     Initialization Parameter File (INI).............8

     Starting OSRM2.................................22

     The OSRM2 Display..............................23

     Ending OSRM2...................................24

     Upgrade Procedures And Support.................25

     Registration Cost Schedules....................27

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                        INTRODUCTION



OSRM2 was created to provide OS/2 users with minimum of two
things:

1)   The ability to observe system resource contention and
     consumption in a real-time environment.

2)   More importantly, to provide the OS/2 user, or
     administrator, a data collector in which system
     resource usage trends can be stored and analyzed when
     considering upgrades ( CPU, memory, peripherals,
     software ).

The real-time monitor can provide the performance tuner with
indicators as to cpu or memory consumption as well as IO
contention  under varying workloads.

The capacity planner data collector, available with Version
1.0, will provide trend information to observe exactly what
resources are being impacted the most and thus guide them to
configuring for cost effectiveness, one wouldn't buy a
faster CPU if memory contention is causing swapping
overhead.

As with other multitasking operating systems ( MVS, OS/2 )
resources are shared in an OS/2 environment thus allowing
concurrent workloads to exist at the same time in one
system.

Because resources are generally limited, a careful eye must
be kept to insure that it is not exhausted. Once this occurs
processes may wait for a very long time thereby negating the
productivity and throughput originally meant to be provided.

Having solid information as to what the CPU average percent
busy was or the average memory usage percent, will provide a
much better guide to problem resolution or job scheduling
then an eyeball approach. Of course capacity planning
entails much more then mentioned here, but it is this base
that all capacity plans are built.

OSRM2 will provide this information to you in a varying
degree of formats and granularity. Considering the cost of
this application versus blindly going out to buy more
hardware, OSRM2 has the potential to save you dollars.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 INTRODUCTION ( CONTINUED )



Each of the components that make up the OSRM2 system will be
discussed in the following order:

          Real-time Monitor ( Version 0.1 )

          Collector ( Version 1.0 and 1.1 )

          Analyzer And Reporter ( Version 1.0 and 1.1 )

          User Exit Support   ( Version 1.0 and 1.1 )


     Real-time Monitor

The real-time monitor is a visual display that provides the
user with a constantly updated information screen. The
information provided shows the average CPU utilization, the
amount of physical memory consumed, as well as the average
attainable IO disk operations per second.

For CPU utilization, the system assumes that each thread
will process an average time slice ( 32 ms ) and then the
scheduler will dispatch the next thread in the priority
chain. The real-time monitor calculates the CPU utilization
by dividing the amount of millisecond since its last update
by the assumed constant, and then dividing the result by 1
second to discern the amount of utilization per CPU second.
This constant will be able to be adjusted in Version 1.0.

For the physical memory consumption, the amount of storage
physically installed in the system as well as memory
consuming configuration options are considered in
determining the approximate amount of physical storage
remaining for user applications. The monitor continuously
queries for the largest physical block of memory available
and then divides this by the physical memory total.

The disk access service time indicator is based on the
average time it takes to perform and IO to each of the
partitions configured in the system. The user can configure
various partitions to be tested in any order.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 INTRODUCTION ( CONTINUED )


     Real-time Monitor ( continued )



The constant information is kept in an initialization file
which may be updated and re-initialized from the real-time
monitor option panel ( Version 1.0 ).


     Collector ( with OSRM2 Version 1.0 )

The collector samples the average CPU, memory, and IO
variables kept by the real time monitor. The granularity at
which this information is gathered is set by the
administrator of the system. The collector then summarizes
these samples and records the record. For example you can
set the collector to sample every 5 minutes and to report on
the hour interval. This will give you the average indicator
per hour of resource usage collected every 5 minutes.

The data is written to the collector file every increment of
reporting, in the case of the above example, this would be
every hour. Time stamps and date stamps will allow for a
large amount of analysis and cross reference.

The collector will then clear out all of its buffers and
then start collecting again. In the example above the
collector will reset all real-time averages for the
following hours interval.

Each month the collector will create a new file which can
then allow the user to archive back dated history files and
not consume hard disk space. It is recommended to keep a
good amount of history data for analysis as the trends will
be more accurate as the historic data grows.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 INTRODUCTION ( CONTINUED )


     Analyzer And Reporter ( with OSRM2 Version 1.0 )



The analyzer and reporter ( OSRM2RPT.EXE ) are a separate
executable application that uses the information stored by
the collector to report on the amount of resource per time
interval that a particular system is consuming.

Variations as to the report interval are allowed as well as
range definitions, for example one might require a report on
the average amount of CPU utilization between the hours of
10:00 AM and 12:00 noon, for weeks 2 and 4 of the June 1989.

Various data manipulating will be implemented over time, as
well as the ability to create a flat file which can be read
into various statistical packages or spread sheets for a
more detailed analysis. Of course it is the intent of C.O.L.
Consulting, LTD. to provide the user with a one stop
application and the features that will be implemented will
have the objective of obtaining this goal.

The user or administrator will have the ability to report on
utilization growth in the key areas of the system: CPU,
Memory and Disk IO. Regression analysis and queueing delays
will be available for review as well as generated
suggestions for enhancing performance. With this knowledge,
upgrading the system will be an exact decision, and will
vary from user to user. This way selective spending will be
possible.

Currently only CPU, Memory and IO / Sec are collected, there
is no way to attribute these to any application without
creating an intrusive monitor. Because of the protected mode
character of OS/2 this will be avoided until more is known
about the various locations of control blocks and tables
that will allow a monitor to view the system workload as
OS/2 does.

As this 'inside information' is obtained, other versions of
OSRM2 will be made available. The registered user will then
have a choice of upgrading or staying with a release that
best suits their needs.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 INTRODUCTION ( CONTINUED )


     User Exit Support ( With OSRM2 Version 1.0 )



For this feature alone we must respect the capabilities that
OS/2 has offered to use.

User Exit Support ( UES ) is a feature that allows the user
to develop various routines in a Dynamic Link Library  (DLL)
format and hook these routines into various areas of the
OSRM2 Collector and OSRM2 Analyzer And Reporter.

The OSRM2 Collector saves to disk files what in essence is a
series of data structures ( objects ! ) which contains
variables of system activity and performance. With UES a
routine can be called from the OSRM2 Collector and have this
structure passed to it for manipulation.

The OSRM2 Analyzer And Reporter calls its own data reduction
and summary routines via DLL calls. In the same vein, UES
will support the calling of routines both pre and post
analysis. This can allow for more advanced data analysis
routines and report writers to be added.

Through UES, there is the potential for a vast interchange
of data manipulation and reporting routines that may be
freely distributed.

Just as spreadsheet macros are communicated across bulletin
boards as well as incorporated into libraries, the potential
exposure is great and the benefit to the end user even
greater as this would reduce the time required to create
their own routines. At the same time productivity increases
and development time decreases.

The major difference of UES versus macros is that the power
of a programming language, and its flexibility, can be used
in place of the sometimes limited macro capabilities.

C.O.L. Consulting LTD. will not be responsible for
maintaining third party UES libraries but will provide
support through license and maintenance agreements with the
UES developers.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 INSTALLATION REQUIREMENTS


     OSRM2 Versions 0.1 and 1.0



The above versions of OSRM2 require at least OS/2 Version
1.0 operating system. The executable programs included
within this archive package were assembled as a Window
Compatible application which will permit it to run in a text
window under version 1.1 of OS/2 ( Presentation Manager ).
The application will detect if it is running full screen or
as a window and adjust it's color scheme accordingly.

It is recommended to install this application on a hard disk
system, as the IO timing will not allow floppy disk drives
to be tested due to the delay to processing during IO. For
the same reason, Version 1.0 will have the Collector active
and will write collected data structures to the hard drive.


     OSRM2 Version 1.1

Because OSRM2 Version 1.1 will be a Presentation Manager
Application, OS/2 Version 1.1 running the Presentation
Manager are required as the operating system.


     Development Environment

OSRM2 was developed with the following:

SOFTWARE

OS/2 Version 1.1
Microsoft MASM 5.1
Microsoft C 5.1
Microsoft Editor Protected Mode ( MEP )

HARDWARE

Intel based 80386
7 Megabytes Real Memory
80 Megabytes Hard Disk Space with 5 Partitions
VGA Adapter with a Paradise VGA Controller

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                        INSTALLATION



To install the OSRM2 system for various operating system
environments follow these global instructions:

Place the files OSRM201.EXE and OSRM2.INI in a directory
together. The system will not search through the environment
looking for sub-directories paths. The OSRM2.INI file
included in this archive package is a working sample and can
be edited for your specific configuration.

Place the files OSRM2D01.DLL and OSRM2S01.DLL in the
directory specified in your CONFIG.SYS in the LIBPATH=
statement. You can optionally place the DLL files in the
same directory as the executable files but be sure to change
your LIBPATH statement to include the directory and reboot
your machine.

Add the program and path specification to the Program
Selector in Version 1.0 of OS/2 or the Start Program Manager
of Version 1.1 of OS/2.

If added to run under Presentation Manager of OS/2 Version
1.1, specify to run under a text window to display within
the Presentation Manager Screen Space. This is optional as
the OSRM2 system will run full screen as well.

Follow the initialization instructions on how the options
available for the OSRM2.INI file.


     OSRM2 Version 1.0

Create a directory where you will be storing the history
data files as well as the generated report and analysis
files. Make sure to indicate the full designator and path
created in the OSRM2.INI file before starting the system.


     OSRM2 Version 1.1

Follow the instructions for version 1.0 as well as
specifying that the application is a Presentation Manager
Application in the Start Program Manager. Actually OS/2 will
determine that it is a PM App and set the display options
accordingly.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE



OSRM2, all versions, include an required initialization
file, OSRM2.INI, which defines various options to be used
during the processing of each run.

The INI file can be changed to suit a changing environment,
be aware that altering this file after a period of use will
cause statistics to vary in the historic database.

In general each parameter, with the exception of the REAL
parameter, is optional. You may omit to include the optional
parameters and OSRM2 will default to the values noted as
DEFAULT under each description.

Following is the current list of acceptable parameters:

          [REAL=?]  Real memory indicator.

          [NUMDRIVES=?] Number of drive partitions to test.

          [DESIGNATOR=? ? ?] Drive designator list.

          [TIMEDRIVES=?] Disk drive test visit interval.

          [OPTIONIO=?] Drive Testing Options.

          [COLLECTORINTV=?] Collector sample interval.

          [SUMMARY=?] Summary and file interval.

          [UES=?] User Exit Support requests for collector.

          [MODNAME=?] Name of UES dynamic link library.

          [PROCNAME=?] Name of UES procedure for collector.

          [FILESPATH=?] Path to store data files.

          [END] Indicated end of INI file parameter list.

In time additional parameters may be added, or current
parameters may be dropped based on applicability, user
request and functionality.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules



All parameters must be entered in UPPER CASE ONLY and have
both the parameter name and assigned value enclosed in
brackets: [PARAMETER=assigned value].

There should be no spaces between the '=' sign and the
assigned value, note the examples and supplied OSRM2.INI
file.

Comments are allowed and should be preceded by a semi-colon
character ';', for example:
[PARAMETER=assigned value]    ; Comment
; Or comment here as well.

Note the ranges currently acceptable for the parameters,
when an out of range is detected OSRM2 will use default
values for that parameter. Out of range events will be
detected when summary reports are created, those parameters
out of range will be flagged.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [REAL=# of megabytes]

THIS IS A REQUIRED PARAMETER!

DESCRIPT. :    The REAL option allows the user to specify
               the amount of real physical memory installed
               in the system. This value entered will be
               used in determining the amount of free
               physical memory during each real time monitor
               update. The value specified in this option
               must be rounded to the nearest megabyte
               boundary.

VERSIONS  :    0.1 / 1.0 / 1.1

RANGES    :    2 - 16

DEFAULT   :    None, value must be specified

EXAMPLE   :    [REAL=7]
               Specifies that there is 7 megabytes of real
               memory installed in the system.

NOTES     :    This value may be varied upwards to test the
               effect of increasing real memory to reduce
               swapping and decrease response time.

CAUTION   :    Not using this variable, or specifying an
               illegal value may result in undesirable
               errors during real-time processing, data
               recording and reporting. For example, if
               value specified is lower then available
               memory during processing.

RECOMM.   :    At least the amount of actual memory.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [NUMDRIVES=Number Of Disk Partitions To Test]

DESCRIPT. :    The number of hard disk partitions to track
               IO performance for.

VERSION   :    0.1 / 1.0 / 1.1

RANGES    :    1 - 5

DEFAULT   :    1

EXAMPLE   :    [NUMDRIVES=3]
               This would indicate that there are three
               partitions to be tested during the monitor
               session.

NOTES     :    Although specifying 1 will test a drive, the
               user will not be able to appreciate the
               variations to other partitions performance as
               it does differ with respect to data set
               activity, location and read/write head
               movement.

CAUTION   :    Attempting to specify more drives then are
               installed will cause the default to be used.
               See DESIGNATOR cautions as they are included.

RECOMM.   :    At least the number of partitions installed
               or the maximum ( 5 ) if the number of
               partitions exceeds the range.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [DESIGNATOR=Partition List]

DESCRIPT. :    The list of disk drive partition designators
               that will be IO tested.

VERSION   :    0.1 / 1.0 / 1.1

RANGES    :    Combinations of C - Z

DEFAULT   :    C

EXAMPLE   :    [DESIGNATOR=C D F]
               Would indicate that drives C, D and F would
               be tested at the TIMEDRIVES interval.

NOTES     :    The reason for excluding the floppy drives is
               due to the inherent delay associated with
               removable media. See NUMDRIVES notes if more
               then 1 partition in system.

CAUTION   :    Specifying an invalid designator will cause
               the default to be used. See NUMDRIVES caution
               as they are included.

RECOMM.   :    Valid drive for number specified in NUMDRIVES
               parameter.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [TIMEDRIVES=IO Test Time In Seconds]

DESCRIPT. :    The time in seconds that spaces the IO
               testing period. This value must be rounded to
               the nearest second.

VERSIONS  :    0.1 / 1.0 / 1.1

RANGES    :    1 - 15

EXAMPLE   :    [TIMEDRIVES=5]
               This would cause the real time monitor to
               test the disk drive IO rate approximate every
               five seconds. If using the designator options
               in the DESIGNATOR example drive C would be
               tested first then 5 seconds later drive D
               would be tested, etc..

NOTES     :    A small enough value will insure that an
               accurate picture of disk drive performance is
               being captured.

CAUTION   :    To small a value will degradate the
               performance of other applications IO
               activity.

RECOMM.   :    4 - 6 Seconds depending on the number of
               drives being tested. Version 1.0 users please
               reference the OPTIONIO parameter notes.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [OPTIONIO=Options for TIMEDRIVES testing]

DESCRIPT. :    This option allows the user to specify that
               the disk drives selected with the DESIGNATOR
               will be test each during a TIMEDRIVES
               interval ( VALUE = 1 ) or that all drives
               will be tested at once during the TIMEDRIVES
               interval.

VERSIONS  :    1.0 / 1.1

RANGES    :    1 - 2

DEFAULT   :    1

EXAMPLE   :    [OPTIONIO=2]
               Using all the above disk drive IO testing
               options, this would cause drives C, D and F
               to be tested at one time every five seconds.
               Whereas using a value of 1 would cause the
               drive testing to rotate and only one drive at
               a time tested every five seconds.

NOTES     :    Keep in mind that if a low TIMEDRIVES value
               is used in combination with a large NUMDRIVES
               value and using a value of 2 for the OPTIONIO
               parameter may cause degradation to system
               performance.

CAUTION   :    None other then performance issues.

RECOMM.   :    1 with many drives and small TIMEDRIVES value
               or 2 with less then 3 drives and a minimum 5
               second TIMEDRIVES value.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [COLLECTORINTV=Collector Sampling Interval]

DESCRIPT. :    This option allows the user to specify a
               sampling interval, in minutes, for collecting
               performance statistics from the real-time
               monitor.

VERSIONS  :    1.0 / 1.1

RANGES    :    1 - 15 minutes.

DEFAULTS  :    1 minutes

EXAMPLE   :    [COLLECTORINTV=5]
               This would cause the collector to collect the
               real-time monitor variables approximate once
               every five ( 5 ) minutes.

NOTES     :    To large a value will cause peaks of
               performance indicators to be averaged out,
               this would give misleadingly low percentages
               of resource consumption. The real-time
               monitor averages out during each of it's
               monitor passes that while being accurate will
               eventually smooth out over times of
               inactivity.

CAUTION   :    None

RECOMM.   :    If activity is in bursts set this value low,
               if the system sustains constant activity this
               value may be increased but should not exceed
               5 to 10 minutes.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [SUMMARY=Time to gather collector records to file]

DESCRIPT. :    The summary value is used collect and
               summarize the COLLECTORINTV record and write
               the record to disk. A time and date stamp are
               appended to each record before being written
               to disk.

VERSIONS  :    1.0 / 1.1

RANGES    :    15 to 60 minutes

DEFAULT   :    15 minutes.

EXAMPLE   :    [SUMMARY=15]
               This would cause a summary record to be
               recorded to disk every fifteen minutes during
               the session.

NOTES     :    The more numerous the summary records the
               more accurate the analysis.

CAUTION   :    None

RECOMM.   :    Same considerations as COLLECTINTV.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [UES=Flag indicating user exit requested]

DESCRIPT. :    This flag is for indicating that a User Exit
               Support DLL is requesting to be called after
               the summary record is written.

VERSIONS  :    1.0 / 1.1

RANGES    :    Y or N

DEFAULT   :    N

EXAMPLE   :    [UES=Y]
               Indicates that the user is requesting to load
               a UES routine.

NOTES     :    Documentation with Version 1.0 will include
               extensive notes on UES as well as data
               structures passed to the UES.

CAUTION   :    None

RECOMM.   :    Highly!

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [MODNAME=Name of UES DLL file]

DESCRIPT. :    This parameter designates the 1 to 8
               character DLL file name.

VERSIONS  :    1.0 / 1.1

RANGES    :    Only 1 UES module allowable

DEFAULT   :    No UES module loaded

EXAMPLE   :    [MODNAME=MYUES001]
               This would indicate that the User Exit
               Support procedures are in a DLL called
               MYUES001.DLL.

NOTES     :    See UES parameter notes.

CAUTION   :    None.

RECOMM.   :    See UES parameter recommendations.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [PROCNAME=Name of UES procedure to call]

DESCRIPT. :    This parameter designates the UES procedure
               to call from the MODNAME DLL file.

VERSIONS  :    1.0 / 1.1

RANGES    :    Only 1 procname allowable

DEFAULT   :    No procedure called

EXAMPLE   :    [PROCNAME=ExtractDiskTiming]
               This would cause OSRM2 to call the
               ExtractDiskTiming procedure from the
               specified MODNAME module.

NOTES     :    The procedure called has unlimited
               possibilities and may call other routines
               that are imported from other libraries. This
               basically serves as a gateway for object
               passing. See UES parameter notes.

CAUTION   :    The called procedure should not exact a large
               overhead as its resource consumption will
               become a part of the statistics.

RECOMM.   :    See UES parameter recommendations.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [FILESPATH=Path to data file storage]

DESCRIPT. :    This option specifies the drive:\path (up to
               64 characters) specification for storing data
               summary records.

VERSIONS  :    1.0 / 1.1

RANGES    :    See description.

DEFAULT   :    Current directory

EXAMPLE   :    [FILESPATH=C:\OSRM2\HISTRECS]

NOTES     :    For organizational purposes this should
               remain separate from other application data
               and program files.

CAUTION   :    Specify a valid path or will default to
               current directory.

RECOMM.   :    See notes.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               INITIALIZATION PARAMETER FILE


     INI Parameter Rules ( continued )

          [END]

DESCRIPT. :    This indicates that there are no more
               parameters to be read from the INI file.

VERSIONS  :    0.1 / 1.0 / 1.1

RANGES    :    N/A

DEFAULT   :    N/A

EXAMPLE   :    [FILESPATH=C:\OSRM2\HISTRECS]
               [END]
               [UES=Y]
               This indicates that there the end statement
               will cause the remainder of the INI file to
               be disregarded.

NOTES     :    N/A

CAUTION   :    Make sure at least the REAL parameter is
               placed before the END statement.

RECOMM.   :    Have one to reduce INI parsing overhead.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                       STARTING OSRM2



Before starting the OSRM2 real time monitor, please insure
that you have:

          Installed the system files in their proper places,
          refer to Installation on Page 7.

          Prepared your OSRM2.INI file with the proper
          parameter settings for your monitor session, refer
          to Initialization Parameter File section starting
          on Page 8.

you are ready to begin.

Before starting OSRM2, it is recommended to insure that it
is the first applications started after a boot up of OS/2.

To start OSRM2 from:


     OS/2 Version 1.0

From the program selector choose the program name you have
assigned to OSRM2 and press enter. If you have not installed
OSRM2 into the program selector, start a OS/2 session and
switch to the directory where you have installed OSRM2 and
at the command prompt enter:

[C:\OSRM2]osrm2 [ then press the enter key ]


     OS/2 Version 1.1

From the Start Program dialog box, open the group where you
have installed the OSRM2 program entry and double click on
the application name you have assigned OSRM2. If you have
not installed OSRM2 into the Start Program dialog box, start
a windowed OS/2 screen session and switch to the directory
where you have installed OSRM2 and at the command prompt
enter:

[C:\OSRM2]osrm2 [ then press the enter key ]

You will immediately see the real-time monitor screen jump
to life as it begins measuring system activity.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                     THE OSRM2 DISPLAY



When OSRM2 is started, the initialization file is read and
processed and then the system activity display ( SAD ) is
created.

There are 3 system indicators displayed; the CPU utilization
percent, the Real Memory percent allocated, and the number
of Disk IO's attainable per second.

Following are the abbreviations for the resource indicators
in the SAD:

CPU  - Cpu Percent Utilization

MEM  - Percent Memory Allocated

IOs  - Attainable IO Per Second.

As you watch the display, you will see the bars that
indicate resource utilization, or work, change as the number
of applications and the work they are performing consume
these resources.

If OSRM2 is the only application started then you can see
the effect of all three indicators change by opening an OS/2
command prompt window and listing a long file with the type
command.

First the memory utilization will increase as storage is
allocated to open the command environment.

The CPU will flash across the utilization range as windows
are activated and the window is used to process work.

The attainable disk IO will change if you create work that
requires a disk access.

If you make the OSRM2 window the active window, note that
the activity of the CPU will decrease, this is because the
window has input focus, which prioritizes itself, and OSRM2
does not consume much overhead in it's timing or calculation
threads.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


              THE OSRM2 DISPLAY  ( CONTINUED )



Along with the SAD are two ( 2 ) control functions as
described below:

F1) TOGGLE OSRM2 DISPLAY UPDATES: Pressing the F1 key will
    toggle the updating of the SAD. This will increase IO
    testing as the overhead for constantly updating the
    screen display is used in the IO timing visit loop. If
    you find that you often turn off screen updating you may
    wish to lengthen the delay in the TIMEDRIVES parameter.

F5) EXIT OSRM2: Pressing the F5 key will exit the real-time
    monitor in all versions, and in Versions 1.0 and above
    this will also shutdown the data collector and summary
    execution threads and processes respectfully.


                        ENDING OSRM2

As mentioned in the OSRM2 Display section, pressing the F5
key will exit OSRM2 from the system and shutdown all
associated processes.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               UPGRADE PROCEDURES AND SUPPORT


     Current OSRM2 Version 0.1 Users ( Unregistered )

EITHER:
Send in the included registration form, making sure to
include all information as well as payment by check or money
order for your registration payment.

OR:
Dial in to HH-InfoNEt BBS (203) 738-0306 or (203) 738-1046
and fill out the registration script online.

If payment is post marked before midnight September 30th,
1989, the cost to register is $40.00 USD, you will receive a
free update to OSRM2 Version 1.0 as well as a 20 % discount
towards your upgrade to OSRM2 Version 1.1

If you register after the introductory special the cost to
register a single copy is $70.00, you will still receive
OSRM2 Version 1.0, but you will not be eligible for the
discounted OSRM2 Version 1.1.

PLEASE SEE THE REGISTRATION FORM CONCERNING THE COST
SCHEDULES AND SITE LICENSE PLANS.


     SUPPORT

C.O.L. Consulting, LTD. can be reached online from:


Compuserve:    COMPUSERVE ID [72261,2700]

HH-InfoNEt:  (203) 738-0306 / (203) 738-1046 send messages  
          to Frank Castellucci.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               REGISTRATION ORDER PRICE LIST


     Single User Registrations

When you register Version 0.1, you automatically receive
Version 1.0.

Discounts to upgrade to Version 1.1 ( PM ) are applicable
based on time of registration.

Below are the single user registration schedules to follow
when registering a copy of OSRM2:

If registering Version 0.1 BEFORE September 30, 1989:

Single User         $40.00

Upgrade To 1.1      $80.00



If registering Version 0.1 AFTER September 30, 1989:

Single User         $70.00

Upgrade to 1.1      $100.00

When registering include a work or daytime phone number as
well as the OS/2 version currently in use and the size
floppy diskette ( 5 1/4 or 3 1/2 ).

See registration form for details.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


               REGISTRATION ORDER PRICE LIST


     Corporate Discounts Version 0.1 / 1.0 / 1.1

When you register Version 0.1, you automatically receive
Version 1.0.

Discounts for upgrades to Version 1.1 ( PM ) are based on
time of registration.

Below are the corporate discount registration schedules to
follow when registering copies of OSRM2:

IF REGISTERING VERSION 0.1 BEFORE SEPTEMBER 30, 1989:

1 - 20 Users        $40.00 per user.
Upgrade To 1.1      $80.00 per user.

21 - 50 Users       $34.00 per user.
Upgrade To 1.1      $68.00 per user.

If number of users is greater then 50 you qualify for a site
license:

Site License        $1300.00 flat rate.
Upgrade to 1.1      $2700.00 flat rate.

********************************************************

IF REGISTERING VERSION 0.1 AFTER SEPTEMBER 30, 1989:

1 - 20 Users        $70.00 per user
Upgrade to 1.1      $100.00 per user

21 - 50             $59.50 per user
Upgrade to 1.1      $85.00 per user

If number of users is greater then 50 you qualify for a site
license:

Site License        $2400.00 flat rate.
Upgrade to 1.1      $3300.00 flat rate.

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 REGISTRATION FORM TEMPLATE

Single user registration:               Date __ / __ / __



Copys to Register             @ $40.00 each  _____

                              @ $70.00 each  _____



Total Enclosed                       $ _____.__



USER INFORMATION

Name:     _________________________________

Address:  _________________________________

          _________________________________

City:     _________________________________

State:    __

Zip:      __________

Phone:    ( ___ ) ___ - ____

OS/2 Version   1.__

Floppy Size    ____

Media on 5 1/4 is 360kb density

Media on 3 1/2 is 720kb density

Please make all registration payments by check or money
orders in United States Dollars to:

          C.O.L. Consulting, LTD.
          RR1 265 Overlook Way
          Purdys NY, 10578

               OS/2 Resource Monitor Facility
                 Version 0.1 August 1, 1989
         (C) Copyright 1989, C.O.L. Consulting LTD.


                 REGISTRATION FORM TEMPLATE

Corporate registration:                 Date __ / __ / __



Number of Users to Register        _____

Applied Discount From Scedule      ___%

Total Enclosed                   $ _____.__



COMPANY INFORMATION

Contact:  _________________________________

Company
Name:     _________________________________

Address:  _________________________________

          _________________________________

City:     _________________________________

State:    __

Zip:      __________

Phone:    ( ___ ) ___ - ____

OS/2 Version   1.__

Floppy Size    ____ @ 5 1/4   ____ @ 3 1/2

Media on 5 1/4 is 360kb density

Media on 3 1/2 is 720kb density

Please make all registration payments by check or money
orders in United States Dollars to:

          C.O.L. Consulting, LTD.
          RR1 265 Overlook Way
          Purdys NY, 10578
