Migration of files – particularly to the offline background level S2 – can result in restricted access to this file. This is not always useful or desirable. The BS2000 data management system and HSMS therefore offer several options for exempting files from migration. In particular, files which are needed for starting BS2000 must be exempted from migration, since HSMS has not yet been loaded at this point in time and the files cannot be recalled.
Important system files are supplied with a migration inhibit in their catalog entry (be sure to copy only with COPY-FILE-PROTECTION=*SAME). Customer files can also be protected with a migration inhibit. In respecting the migration inhibit, however, HSMS makes no distinction between different users (see section "Allowing migration").
Files such as the parameter file CMDFILE can be reliably protected against migration by entering these files (or, to be on the safe side, the entire TSOS user ID) in an except file in order to exempt them from migration.
To do this the HSMS administrator lists the files to be exempted from migration in a SAM file, record by record (uppercase characters only). Entire user IDs (such as TSOS) can be exempted from migration by specifying partially-qualified file names. Wildcards can be used to define the files.
The except file is assigned by specifying:
in the SF pubset environment:
//MODIFY-HSMS-PARAMETERS - // MIGRATION-CONTROL=*PARAMETERS(EXCEPT-FILE=<file name>)
in an SM pubset environment:
//MODIFY-SM-PUBSET-PARAMETERS - // SM-PUBSET-ID=<sm-pubset-id>, - // MIGRATION-CONTROL=*PARAMETERS(EXCEPT-FILE=<file name>)