Microsoft
Windows Server © 2003 includes a process accounting tracker: the
Windows © System Resource Manager (WSRM). This
Windows component checks the task manager after a configured
period of time, records which processes are running along with
statistics about those processes, and saves these records in a
database. The statistics may then be exported to capture
process accounting information from the Windows © Server
environment.
The KOMAND Server Charging System for Windows © (SCSW) collects
the process accounting data from the Windows © System Resource
Manager (WSRM) and generates chargeback
data to be processed and merged with other KOMAND chargeback
data. SCSW consists of two parts: a Microsoft© Server component
and an IBM/MVS component. KOMAND will eventually offer an
optional Windows processing component to be used instead of the
IBM/MVS component for those users who do not have a mainframe or
wish to keep their Windows© data separate from their mainframe
Enterprise data.
The
Microsoft Server component consists of a shell script and C++
program which harvest the WSRM utilization data and convert it
into a format readable by the MVS component. This file (see
tables below for field descriptions) must then be transferred to
the mainframe MVS component to be processed and merged with
other charging data in the format expected by the other
component. SCSW is designed to function automatically using the
Windows © Task Scheduler and to
provide the maximum amount of flexibility through it's execution
options.
The MVS
component consists of costing modules which interpret user
supplied control statements to charge resource usage back to an
organizational accounting structure. KOMAND Accounting Records
(KARs) containing the resource utilization data and the
respective charges are generated by the MVS component and may
then be passed to the KOMAND Financial Management System (FMS)
or KOMAND Information Manager (KIM) for additional processing
and reporting. FMS is the KOMAND system used to combine all data
center resource usage and charges into a customer database for
invoicing and other financial reporting. KIM allows the
mainframe database to be imported to a SQL PC database for
additional access and reporting.
SCSW Accounting Record Format
The following Record fields are best suited for use as
accounting or control information:
DDT
Field Name |
Field Description |
Field Type |
|
Name of
user who started process |
CL40 |
DOMAIN |
Domain
of user who started process |
CL40 |
POLICYNM |
Resource-Allocation Policy |
CL40 |
PRCESSID |
Identifies process while it is running |
CL8 |
PRCESSNM |
Process
name |
CL40 |
SESSID |
Terminal Service that owns the process |
CL8
|
The following Record
fields are best suited for utilization tracking or charging:
DDT
Field Name |
Field Description |
Field Type |
THREDCT |
Number
of active threads |
CL8 |
TCPUTM |
Total
time of process (milliseconds) |
CL16 |
ELAPSTM |
Elapsed
time of process (milliseconds) |
CL16 |
KERNLTM |
Time in
Kernel Mode (milliseconds) |
CL16 |
USRMDTM |
Time in
User Mode (milliseconds) |
CL16 |
PGFLUSE |
Memory
reserved for paging (kilobytes) |
CL16 |
PKPGUSE |
Max
memory reserved for paging (kilobytes) |
CL16 |
PGFLTCT |
Number
of Page Faults |
CL16 |
VIRTSZE |
Virtual
address space of process (kilobytes) |
CL16 |
PKVTSZE |
Max
Virtual address space (kilobytes) |
CL16 |
WRKSTSZ |
Working
set of process (kilobytes) |
CL16 |
PWRKSTS |
Max
Working Set (kilobytes) |
CL16 |
PVTPGCT |
Pages
allocated to process (kilobytes) |
CL16 |
QPGPUSE |
Page
pool usage for process (kilobytes) |
CL16 |
QPKPGPU |
Peak
Page pool usage (kilobytes) |
CL16 |
QNPGPU |
Non-page pool usage (kilobytes) |
CL16 |
QPKNPGU |
Peak
Non-page usage (kilobytes) |
CL16 |
RDOPRCT |
Number
of read I/O generated by process |
CL16 |
RDTRNCT |
Number
of read I/O operations (kilobytes) |
CL16 |
WTOPRCT |
Number
of write I/O generated by process |
CL16 |
WTTRNCT |
Number
of write I/O operations (kilobytes) |
CL16 |
OTOPRCT |
Number
of other I/O generated by process |
CL16 |
OTTRNCT |
Number
of other I/O operations (kilobytes) |
CL16 |
The following
Record fields are best suited for use as log date/time or other
information:
DDT
Field Name |
Field Description |
Field Type |
STAMPDTE |
Date
data entered database (MMDDYY) |
CL6 |
STAMPTME |
Time
data entered database (HHMMSS) |
CL6 |
POLICYDT |
Date
resource alloc policy set (MMDDYY) |
CL6 |
POLICYTM |
Time
resource alloc policy set (HHMMSS) |
CL6 |
CREATEDTE |
Date
process started (MMDDYY) |
CL6 |
CREATETME |
Time
process started (HHMMSS) |
CL6 |
MATCH |
Processing Matching Criteria |
CL100 |
EXECPATH |
Path to
directory where exec file located |
CL100 |
CMDLINE |
Command
used to start process |
CL100 |
For additional information contact:
PACE Applied Technology, Inc. 4192 Aiken Drive
Warrenton, Virginia
20187
Phone: (703) 369-3200
Fax: (703)
369-4595
Note:
Microsoft, Windows Server 2003, Windows System Resource Manager "Windows System Resource Manager" , and Windows Task
Scheduler "Windows Task Scheduler" are either registered
trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.