18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Utilization Report Utility for <strong>OS</strong> <strong>2200</strong> (URU-<strong>OS</strong><strong>2200</strong>)<br />

5.52. Utilization Report Utility for <strong>OS</strong> <strong>2200</strong><br />

(URU-<strong>OS</strong><strong>2200</strong>)<br />

General Considerations<br />

URU-<strong>OS</strong><strong>2200</strong> should be installed soon after <strong>OS</strong> <strong>2200</strong> metered system is ready for use.<br />

This includes installing the Windows components of URU-<strong>OS</strong><strong>2200</strong>—the URU Windows<br />

Interface <strong>and</strong> the URU Windows Service, installing the <strong>OS</strong> <strong>2200</strong> component of<br />

URU-<strong>OS</strong><strong>2200</strong> <strong>and</strong> starting the URU Background Run. The URU Background Run allows<br />

the URU Windows Service running on the workstation to connect using a TCP/IP<br />

connection to the <strong>OS</strong> <strong>2200</strong> metering partition using CPComm.<br />

Before you install Windows components of URU-<strong>OS</strong><strong>2200</strong>, you must determine which<br />

workstation can provide the connectivity <strong>and</strong> availability required. The workstation<br />

selected to execute URU-<strong>OS</strong><strong>2200</strong> for the site must be available to run the URU<br />

Windows Service as necessary to ensure collection of the COD usage data. Capacity on<br />

Dem<strong>and</strong> (COD) data is recorded in the <strong>OS</strong> <strong>2200</strong> COD audit trail <strong>and</strong> the system log file.<br />

The URU Windows Service running on the workstation retrieves or harvests the COD<br />

data from the COD audit trail or system log file periodically. The URU Windows Service<br />

must be running in order for the COD data to be harvested. It is imperative that the COD<br />

log data be harvested from the <strong>OS</strong> <strong>2200</strong> system before the file cycles containing the<br />

data are overwritten or deleted.<br />

Unisys strongly recommends that the URU Windows Service be up <strong>and</strong> running 24 by 7.<br />

If the URU Windows Service is not running continuously, file management must be done<br />

by the <strong>OS</strong> <strong>2200</strong> system administrator to ensure that the COD audit trail <strong>and</strong> system log<br />

file cycles are not deleted or overwritten before the COD log data is retrieved. The<br />

methods available to manage the COD audit trail files are the same as those methods<br />

available for other Exec audit trails: step control, system log <strong>and</strong> TPM. See the IRU<br />

Administration Manual <strong>and</strong> IRU Operations Guide for additional information.<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.1<br />

URU-<strong>OS</strong><strong>2200</strong> Level 5.1<br />

Migration<br />

This release of URU has two modes of installation: Mode A <strong>and</strong> Mode B. Mode A URU<br />

contains a st<strong>and</strong>ard version of IRU’s Free St<strong>and</strong>ing Audit H<strong>and</strong>ler (FSAH) subsystem.<br />

This mode is used when the COD <strong>and</strong> system log audit trails’ configuration is the<br />

st<strong>and</strong>ard configuration released with the Exec.<br />

The IRU FSAH level included in URU 5.1 Mode A is IRU level 20R2 released with<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> 13.1.<br />

Mode B URU does not contain an IRU FSAH subsystem but instead uses the IRU FSAH<br />

subsystem that is installed on the system. Mode B must be used when the COD <strong>and</strong>/or<br />

system log audit trails’ configuration differs from the st<strong>and</strong>ard configuration released<br />

with the Exec. URU requires that IRU be installed with mode FSAH, when you install<br />

using Mode B.<br />

7831 0349–043 5–57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!