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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

With this release, you must also use Mode B to obtain IRU FSAH level 19R1 or any<br />

earlier FSAH levels. The IRU Move history file (MHF) format changed with IRU 20R1. If<br />

you used an IRU 19R1or earlier level to move the COD or system log audit trail files to<br />

tape, then you will need to use IRU Mode B with the appropriate IRU FSAH installed to<br />

access the tapes via the IRU MHF.<br />

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

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

Migration<br />

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

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

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

is the st<strong>and</strong>ard configuration released with the Exec.<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 />

With this release, you must also use Mode B to obtain the new IRU level 20R1 released<br />

in CP 13.0.<br />

For CP 13.0 <strong>and</strong> IRU 20R1, the IRU Move history file (MHF) format is changed. IRU’s<br />

FSAH for CP 13.0 is not compatible with the IRU MHF produced by the IRU 19R1 (CP<br />

12.1) <strong>and</strong> vice versa.<br />

Therefore, for URU 5.0, the FSAH subsystem included in the mode A release is the<br />

subsystem from IRU 19R1. This allows compatibility with any IRU MHFs produced using<br />

IRU 19R1.<br />

To use the IRU 20R1, you must install URU as mode B <strong>and</strong> have the IRU installed on<br />

your system using MODE FSAH.<br />

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

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

Migration<br />

This release will continue to run on previously supported Windows platforms. When<br />

migrating to URU 4.0, the URU Windows components must be updated before the URU<br />

Background Run on metered <strong>OS</strong><strong>2200</strong> partitions. As with previous releases, the URU 4.0<br />

Windows Service will be able to connect to previous levels of the URU Background Run.<br />

However, previous levels of the URU Windows Service should not be used to collect<br />

utilization data from a URU 4.0 Background Run.<br />

Since previous levels of URU cannot execute on a Windows Vista platform, specific<br />

steps are required in order to transfer <strong>and</strong> upgrade existing URU utilization data from an<br />

existing platform.<br />

5–58 7831 0349–043

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

Saved successfully!

Ooh no, something went wrong!