Migration to ROSs/OSS

The EXEC statement in the OSS migration skeleton’s SRVD step contains PARM='OSS'. Change OSS to the logical name of the target media specified in the IOASPRM member in the PARM library.   

It is recommended that you specify a set of platters to which reports (and indexes) must migrate. Use meaningful prefixes to create sets of platters containing reports with similar characteristics (for example, viewed together, viewed with similar frequencies, viewed by the same group of users). If you do not specify a prefix in the migration mission, the report migrates to the first available platter.

The user defines ROSs/OSS platters and the VOLSERs on each platter. The platter prefix in a migration mission resolves to the value specified in parameter PREFIX of the Migration Mission Definition screen. This platter prefix enables the migration process to select the desired platter.

After selecting a platter, the migration process scans the VOLSER list and selects the first completely empty VOLSER in the list. CDAM files migrate sequentially until this VOLSER is filled (to a maximum of 32K blocks on any volume). "Virtual" VOLSERs that are not filled in one migration mission are left partially empty, but no physical platter space is wasted.

When a file is written on a VOLSER on the ROSs/OSS, it is cataloged on that VOLSER with the specific label number. The VOLSER of each migrated report is stored both on the catalog and in the Control‑V Migrated User Report file. When the report is viewed, this catalog entry enables the ROSs/OSS to access the needed platter and read the required VOLSER. When all VOLSERs on a specific platter are no longer needed, the user can destroy the platter.