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.

Operator Interfaces<br />

The console keyins (UP, DN, RV, FS, <strong>and</strong> SU) that are available for current tape devices<br />

<strong>and</strong> that do not attempt write functions are available for the DVD. Since the DVD is<br />

supported as read-only media, console keyins that attempt to write to the DVD should<br />

not be used. Examples are SV, SB SBDEV, <strong>and</strong> SB IODEV where the device specified is<br />

a DVD. Errors can occur before a write is attempted to the DVD.<br />

DVD Mnemonics<br />

Table 4–6 describes the DVD assign mnemonics. The media type is 79.<br />

4.6.15. Virtual Tapes<br />

4.7. TIP<br />

Table 4–6. DVD Assign Mnemonics<br />

Assign Mnemonic CONV EQUATE Drive Allocated<br />

DVDTP None DVD<br />

Audit trails cannot be configured to use virtual tapes. VTH tapes exist in normal mass<br />

storage files that can be c<strong>and</strong>idates for rollout. If these files get unloaded, the only valid<br />

copy of the data is on a physical tape. However, you cannot access the virtual tape<br />

directly from the physical tape on which it resides. To access the files, you must restore<br />

(in other words, ROLBAK) the virtual tape to mass storage. Be aware that if these virtual<br />

tapes contain backups such as IRU move or dump information, this increases the time it<br />

takes to recover an application group or file. When performance of a recovery or<br />

restoration is critical, the need to restore virtual tapes can cause an undesirable delay.<br />

This subsection describes TIP considerations.<br />

4.7.1. General<br />

• You should install the TIPUTIL level that corresponds with the target Exec level.<br />

Previous levels of TIPUTIL might not be compatible with the target Exec level.<br />

7831 0349–043 4–37<br />

TIP<br />

• TIPUTIL generations require the RLIB$ file which corresponds to the target Exec<br />

level. If you generate your TIPUTIL on the target Exec level, it will include the correct<br />

RLIB$ file. To prebuild your TIPUTIL system on your current system before migration<br />

to the target Exec level, use the RLIB$ SGS to specify the location of the target<br />

Exec’s RLIB$ file. For details on using the RLIB$ SGS, see “TIPUTIL Generation<br />

Control Statements” in the Exec System <strong>Software</strong> Installation <strong>and</strong> Configuration<br />

Guide.

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

Saved successfully!

Ooh no, something went wrong!