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.

Integrated Recovery Utility (IRU)<br />

This level of IRU supports both previous <strong>and</strong> current versions of the following IRU<br />

structures:<br />

• Dump tapes<br />

• Move tapes<br />

• FSAH packets (versions 4 <strong>and</strong> 5 - version 3 is no longer supported)<br />

FSAH applications must be able to h<strong>and</strong>le new formats for records they expect to<br />

encounter. FSAH converts packet fields to their appropriate format, but returns audit<br />

records to the caller in whatever format exists on the audit trail being read. Note that<br />

TDATE values in version packets are interpreted as local times on input <strong>and</strong> converted to<br />

local times on output.<br />

These local times use the current system offsets to generate TIMEB internally <strong>and</strong> to<br />

convert TIMEB to TDATE if needed.<br />

Users must initialize or Migrate history files The new IRU level h<strong>and</strong>les only new format<br />

history files. Users who wish to save existing history file information must execute the<br />

migration utility to populate the new history files.<br />

Users who currently have local code to alter the number of MHF entries (tapes) retained<br />

can no longer use that method; they should change the value of MHF-MIN-TAPES<br />

instead.<br />

Time Specification<br />

IRU time management mechanisms now let you choose how times are entered <strong>and</strong><br />

displayed, as either local time or UTC. The new configuration parameter TIMES-ARE-<br />

LOCAL controls the base of displayed <strong>and</strong> entered times; local offsets are based on the<br />

system time at IRU execution.<br />

When you provide a start or end time to read an audit trail, TIMES-ARE-LOCAL must be<br />

set to the appropriate value for the time you enter <strong>and</strong> the current offsets.<br />

Note that times generated by previous IRU levels <strong>and</strong> other Integrated Recovery<br />

products are TDATE based. IRU displays these times without offsets, using the<br />

mnemonic "", without regard to the TIMES-ARE-LOCAL setting. These TDATE$<br />

based times are assumed to be local times. In general, IRU tries to display a timestamp<br />

in the same format <strong>and</strong> offset in which it expects to receive the time input. This means<br />

that some local times for events that took place during a different offset period are<br />

displayed using the current offsets; even when IRU knows the correct offsets for that<br />

historical time.<br />

BUILD <strong>and</strong> REPORT CONFIG changes<br />

Configuration parameter changes in this level alter the IRU BUILD routine, introducing<br />

several new configuration parameters. In addition, DHF-BLK-SIZE parameter was<br />

removed; the DHF block size is no longer configurable.<br />

REPORT CONFIG output is also altered.<br />

7831 0349–043 5–27

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

Saved successfully!

Ooh no, something went wrong!