HSMS Migrate/recall files with HSMS

HSMS Migrate/recall files with HSMS

ONXHSMS [MIGRATE] [, TO=S1|S2] [, COMP=YES|NO] [, INHIBIT=IGNORE|RESPECT]

ONXHSMS RECALL [, EXP=YES|NO] [, LOC=BEST|SAME|cat-id]

The ONXHSMS Variable Action offers the CFS user the possibility of migrating and recalling files from storage media using HSMS.

MIGRATE The files marked with X (ONX), or all files (ON&) will be migrated to a different storage medium using the HSMS utility program. A CFS procedure will be created containing the following HSMS statement:

//MIGRATE-FILES FROM-STORAGE-LEVEL=*S0-STORAGE-LEVEL(...).

As from OSD V3.0 it must be ensured that files on different SM pubsets are not processed simultaneously in one HSMS run. This restriction is also relevant for files that reside partially on SF and SM pubsets.

TO=S1|S2 The files will be migrated to the specified storage level.

This parameter corresponds to the HSMS statement //MIGRATE-FILES, parameter TO-STORAGE=*S1-STORAGE-LEVEL|*S2-STORAGE-LEVEL

Standard: S2

COMP=YES|NO

Determines whether or not the files should be compressed prior to being written to the storage medium. This parameter corresponds to the HSMS statement //MIGRATE-FILES, parameter COMPRESS-FILES=*YES|*NO

Standard: If this parameter is not specified, the default setting from the archive definition of the pubset will be used.

INHIBIT=IGNORE|RESPECT

This parameter is reserved for the system administrator. It determines whether or not the migration bar set in the file's catalog entry can be ignored or not. this parameter corresponds to the HSMS statement //MIGRATE-FILES, parameter FILE-INHIBIT=*RESPECTED|*IGNORED

Standard: Under TSOS, if this parameter is not specified, the default setting from the archive definition of the pubset will be used.

Under any userid other than TSOS, the RESPECT value is always used.

RECALL The files marked with X (ONX), or all files (ON&) will be recalled from the background storage level (S1/S2 level) to the processing level S0. The advantage of a ONXHSMS RECALL Variable Action compared to an implicit recall by simply opening the file is that each file will not generate its own HSMS job.

The procedure generated by CFS will contain the following HSMS statement:

//RECALL-MIGRATED-FILES.

EXP=YES|NO

This parameter is reserved for the system administrator. It will determine whether or not the job should be started as an Express job.

This parameter corresponds to the HSMS statement //RECALL-MIGRATED-FILES, parameter OPERATION-CONTROL=*PAR(EXPRESS-REQUEST=*YES|*NO)

Standard: NO

LOC=BEST|SAME|cat-id

This parameter is only permitted from OSD V3.0. It will determine to which Volume set the file should be restored, if it had been migrated from an SM pubset.

BEST The file will be restored to the best available Volume set corresponding to it's attribute (e.g. High Performance, High Availability).

SAME The file will be restored to the same Volume set on which it existed prior to it's migration.

cat-id Identification of the Volume set within the SM pubset to which the file should be restored.

This parameter corresponds to the HSMS statement //RECALL-MIGRATED-FILES, parameter ENVIRONMENT=*SYSTEM-MANAGED(NEW-DATA-LOCATION= *BEST-VOLUME-SET|*SAME|cat-id)

Standard: BEST

Notes:

The Variable Action creates a DO procedure with the required HSMS statements. The user can start this DO procedure immediately under control of the Job Report system, and have it monitored by CFS.

The following HSMS parameters will be inserted automatically into the generated job:

FILE-NAMES=*FROM-FILE(LIST-FILE-NAME=listfile)

OPERATION-CONTROL=*PAR(WAIT-FOR-COMPLETION=*YES,REPORT=*FULL, OUTPUT=protfile)

The listfile will be created automatically by CFS, and will contain the names of all files to be processed. This file will be deleted automatically following the successful execution of the HSMS job.

The protfile will be created initially as a temporary file. It will only be copied to a permanent file should the HSMS job terminate with an error.

As from OSD V3.0, the additional parameter ENVIRONMENT=*SYSTEM-MANAGED (PUBSET-ID=cat-id) will be inserted for a //MIGRATE-FILES statement for those files stored on an SM pubset. The PVS-ID of the first file to be migrated will be used as the cat-id. If this first file to be migrated resides on an SF pubset, then the parameter ENVIRONMENT=*SINGLE-FEATURE will be inserted.