This statement is used for migrating files to a default system migration archive. The archive can be located in an SF or an SM pubset environment.
The HSMS administrator can also use the statement for reorganizing migration archives on storage level S1 or S2.
A migration archive cannot and need not be specified for migration from S0 (see the note at the end of the operand description for this statement).
The user can select the files to be migrated using the file size and the time that has passed since they were last accessed as selection criteria.
Files which are stored on pubsets which are imported from different computers should not be migrated if the other remote host is unable to access tape devices of the S2 processing level.
Files which reside on Net-Storage and file generation groups cannot be migrated.
The files can be migrated from S0 to either of the storage levels S1 or S2. The HSMS administrator can prohibit all migration by other users or restrict migration to S2.
The option of migrating files from S1 to S2 is restricted to the HSMS administrator.
When a file which has not been modified since the last migration is to be migrated from S0, the old backup on S1 or S2 - if it still exists - is used again for the new migration. This quick and economical form of migration is referred to as “quick migration” or “remigration”.
This statement has different formats for nonprivileged users and HSMS administrators. Privileged operands or operand values are marked with *P).
Format
MIGRATE-FILES | Alias: MGF | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
*P) Privileged operand or operand value
ENVIRONMENT =
Determines the HSMS environment to which the statement applies.
ENVIRONMENT = *STD
Meaning for privileged users: *STD is set to the value *SINGLE-FEATURE.
Meaning for nonprivileged users: *STD is the environment that is associated with the user’s default pubset (the default pubset is defined in the user catalog).
ENVIRONMENT = *SINGLE-FEATURE
The HSMS statement only relates to the SF environment. The request is stored in the central request file.
ENVIRONMENT = *SYSTEM-MANAGED(...)
The HSMS statement only relates to the specified SM pubset environment. The request is stored in the request file of the SM pubset.
CATALOG-ID = <cat-id>
Catalog ID of the SM pubset to which the HSMS statement applies.
MANAGEMENT-CLASS =
This operand is only available to the HSMS administrator.
The objects to be processed are selected according to their assigned management class. Please note the following:
With FROM-STORAGE=*S2-STORAGE-LEVEL the MANAGEMENT-CLASS operand is ignored (corresponds to *ANY).
With FROM-STORAGE=*S0-STORAGE-LEVEL the objects assigned to a management class are the files of an SM pubset.
With FROM-STORAGE=*S1-STORAGE-LEVEL the objects assigned to a management class are the save files on S1 generated with it.
MANAGEMENT-CLASS = *ANY
The HSMS statement is processed irrespective of whether the objects are assigned to a management class or not.
MANAGEMENT-CLASS = *NONE
The HSMS statement is processed with all the specified objects to which no management class is assigned.
MANAGEMENT-CLASS = <alphanum-name 1..8>
The HSMS statement is processed with all the specified objects to which the specified management class is assigned.
FROM-STORAGE =
Serves to specify the storage level from which the files are to be migrated. Nonprivileged users can migrate from S0 only.
FROM-STORAGE = *S0-STORAGE-LEVEL(...)
The files are to be migrated from storage level S0. The files must be specified in more detail.
FILE-NAMES =
Serves to specify the files to be migrated. Specification of this operand is mandatory. The user can further restrict the selection made here by means of the operands EXCEPT-FILE-NAMES, UNUSED-DAYS, MINIMUM-SIZE, MAXIMUM-SIZE, RELEASE-PAGES and DIALOG-FILE-SELECT.
The specified files must be cataloged on an S0 pubset that has been assigned a migration archive.
If files from more than one pubset are to be migrated, then the same default system migration archive must be assigned to all pubsets. Otherwise, the HSMS statement will be rejected. To prevent this you should only specify files from one pubset for each migration request. In addition, migration must be permitted for each of the pubsets affected by the migration request. The HSMS statement will be rejected if this condition is not fulfilled. (This does not apply to the HSMS administrator.)
All nonprivileged users can migrate files belonging to other user IDs if they are co-owners of these files.
Files on Net-Storage and file generation groups cannot be migrated.
Further information on files exempted from migration can be found in the “HSMS Vol. 1” manual [1].
FILE-NAMES = *OWN
All files of the user’s own ID residing on any imported pubset (except for shared SF pubsets for which the home computer is the slave) are to be migrated.
FILE-NAMES = *ALL
All files residing on all imported pubsets (except for shared SF pubsets for which the home computer is the slave) are to be migrated.
FILE-NAMES = *SELECTED
The path names of the files to be migrated are to be taken from a list that was compiled within the same HSMS run by means of the HSMS statement SELECT-FILE-NAMES.
FILE-NAMES = *FROM-FILE(...)
The path names of the files to be migrated are to be taken from a file. The nonprivileged caller must be owner or co-owner of this file. This list file must be a SAM file with variable-length records containing one path name per record. The list file can be created, for instance, by means of the HSMS statement SELECT-FILE-NAMES or the BS2000 command SHOW-FILE-ATTRIBUTES.
LIST-FILE-NAME = <filename 1..54 without-gen-vers>
Path name of the list file.
FILE-NAMES = *FROM-LIBRARY-ELEMENT(...)
The path names of the files which are to be migrated are taken from a PLAM library element (type S). The library element contains one path name per record. Only uppercase letters may be used.
LIBRARY = <filename 1..54 without-gen-vers>
Name of the PLAM library.
ELEMENT = <composed-name 1..64 with-under>
Name of the type-S element. The element of the highest existing version is used.
FILE-NAMES = list-poss(20): <filename 1..80 without-gen-vers-with-wild> /
<partial-filename 2..79 with-wild>
The path names of the files to be migrated are specified directly. A list of up to 20 names may be specified.
The file names may be specified as fully or partially qualified names, with or without a catalog/user ID. If required, the file name is extended by the user ID of the request and with the catalog ID which is either taken from the specified environment or from the default catalog ID of the user ID.
You can also use wildcard syntax to select the files.
When migrating large numbers of files, the recurring output of warnings is not always desired. Such output is therefore suppressed if a privileged user employs wildcards in the user/catalog ID.
The output of warnings is not suppressed, however, if:
wildcards are given in file names
the catalog ID is omitted.
Warnings are never suppressed for nonprivileged users.
In the case of shared pubsets, the replacement of wildcards for catalog IDs does not refer to SF pubsets for which the home computer is the slave.
EXCEPT-FILE-NAMES =
Serves to specify files that are to be excluded from migration.
EXCEPT-FILE-NAMES = *NONE
All files specified with the FILE-NAMES operand are to be migrated.
EXCEPT-FILE-NAMES = *FROM-FILE(...)
The path names of the files to be excluded from migration are to be taken from a file. The nonprivileged caller must be owner or co-owner of this file. This list file must be a SAM file with variable-length records containing one path name per record. The list file can be created, for instance, by means of the BS2000 command SHOW-FILE-ATTRIBUTES.
File names must be in uppercase characters only.
LIST-FILE-NAME = <filename 1..54 without-gen-vers>
Path name of the list file.
EXCEPT-FILE-NAMES = *FROM-LIBRARY-ELEMENT(...)
The path names of the files to be excluded from migration are taken from a PLAM library element (type S). The library element contains one path name per record. Only uppercase letters may be used.
LIBRARY = <filename 1..54 without-gen-vers>
Name of the PLAM library.
ELEMENT = <composed-name 1..64 with-under>
Name of the type-S element. The element of the highest existing version is used.
EXCEPT-FILE-NAMES = list-poss(20): <filename 1..80 without-vers-with-wild> /
<partial-filename 2..79 with-wild>
The path names of the files to be excluded from migration are specified directly. A list of up to 20 names may be specified.
The first character of the file names must not be a hyphen. The file names may be specified as fully or partially qualified names, with or without a catalog or user ID. If required, the file name is extended by the user ID of the request and with the catalog ID which is either taken from the specified environment or from the default catalog ID of the user ID.
You can also use wildcard syntax to select the files.
UNUSED-DAYS =
The files to be migrated can be selected using as the selection criterion the time that has elapsed since they were last accessed.
UNUSED-DAYS = *STD
Meaning for HSMS administrators:
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class.
Meaning for HSMS administrators and nonprivileged users:
If no management class is used, the value *STD is replaced by 0.
UNUSED-DAYS = 0
Meaning for nonprivileged users:
The files are migrated irrespective of the number of days elapsed since they were last accessed.
UNUSED-DAYS = <integer 0..9999 days>
Only files that have not been accessed at least for the specified number of days are migrated.
MINIMUM-SIZE =
Serves to select the files to be migrated using a minimum file size, specified in PAM pages, as the selection criterion.
MINIMUM-SIZE = *STD
Meaning for HSMS administrators:
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class.
Meaning for HSMS administrators and nonprivileged users:
If no management class is used, the value *STD is replaced by 0.
MINIMUM-SIZE = *NONE
Meaning for nonprivileged users:
The files are migrated irrespective of the minimum file size.
MINIMUM-SIZE = <integer 1..2147483647 2Kbyte>
Only files of the minimum specified size are migrated.
MAXIMUM-SIZE =
The files to be migrated can be selected using a maximum file size, specified in PAM pages, as the selection criterion.
MAXIMUM-SIZE = *STD
Meaning for HSMS administrators:
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class.
Meaning for HSMS administrators and nonprivileged users:
If no management class is used, the value *STD is replaced by 0.
MAXIMUM-SIZE = *NONE
Meaning for nonprivileged users:
The files are migrated irrespective of the maximum file size.
MAXIMUM-SIZE = <integer 1..2147483647 2Kbyte>
Only files of the maximum specified size are migrated.
RELEASE-PAGES = *MAXIMUM
The number of files selected for migration by FILE-NAMES and other operands is unrestricted.
RELEASE-PAGES = <integer 1..2147483647 2Kbyte>
Files are only migrated until such time as the specified number of 2 KB blocks has been released as a result of this migration. After this, files are migrated in ascending order according to the LAST ACCESS DATE, or in other words, beginning with the files that have not been accessed for the longest length of time.
FILE-INHIBIT =
This operand is only available to the HSMS administrator.
Defines whether the migration inhibits that are set by the user are to be respected. The user can declare migration inhibits with the BS2000 commands CREATE-FILE and MODIFY-FILE-ATTRIBUTES.
FILE-INHIBIT = *STD
The value is taken from the parameters of the environment to which the statement applies (from the FILE-INHIBIT parameter der HSMS parameters in the SF environment and the associated SM parameters in the SM environment).
FILE-INHIBIT = *RESPECTED
The migration inhibits set by the user are respected. The relevant files are not migrated.
FILE-INHIBIT = *IGNORED
The migration inhibits set by the user are ignored. The relevant files are migrated.
MINIMUM-EXTENTS = *STD / <integer 0..99999>
This operand is only available to the HSMS administrator.
Specifies the minimum number of extents which a file must have in order to be migrated. If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class.
If no management class is used, the value *STD is replaced by 0.
VOLUME-SET-ID = *ANY / <cat-id>
When working in an SM pubset environment, a user who has file allocation permission (see user attributes) can specify the catalog ID of a volume set. All the files of this volume sets are migrated.
VOLUME-SET-ATTRIBUTE = *ANY / *NOT-ON-BEST
When working in an SM pubset environment, only files that are not located on the volume set that best matches their attributes can be selected.
MIGRATION-INFO = *ANY / *REMIGRATION
Determines whether the set of files is to be restricted to files for which quick migration is possible (migration does not require storage on S1 or S2).
MIGRATION-INFO = *ANY
The set of files is not restricted. Files are as far as possible migrated using quick migration, otherwise normal migration takes place with the files being stored on S1 or S2 again.
MIGRATION-INFO = *REMIGRATION
Only those files which have not been modified since their last recall are migrated, i.e. the backup from the last migration can be used. This migration takes place as a quick migration without tape processing. It is executed immediately and not included in a collector request.
COMPRESS-FILES = *STD / *YES / *NO
Determines whether the data is to be compressed before being written to the output volume.
Unless otherwise specified, the default values in the archive definition apply.
TO-STORAGE = *STD
Meaning for HSMS administrators:
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class.
Meaning for HSMS administrators and nonprivileged users:
If no management class is used, the value *STD is replaced by *S2-STORAGE-LEVEL.
TO-STORAGE = *S2-STORAGE-LEVEL
The files are to be migrated to storage level S2.
TO-STORAGE = *S1-STORAGE-LEVEL
The files are to be migrated to storage level S1. An S1 pubset must be assigned beforehand (see the FILE-NAMES operand).
When migrating to storage level S1, at least 10% of the storage space of the S1 pubset must be free. This means for S1-SM-pubets 10% of the total storage space of all its volume sets (excluding control volume set and HSMS-CONTROLLED volume sets) and, if in the SM environment all HSMS-CONTROLLED volume sets are going to be used as S1 level, 10% of the total storage space of all these volume sets.
DIALOG-FILE-SELECT =
Defines whether the user wishes to conduct a dialog in order to select individual files from the set of files selected for migration by means of FILE-NAMES and other operands. Only files which can be migrated from S0 will be available for selection during the dialog.
The operand is evaluated only in interactive mode; for batch tasks it is ignored.
DIALOG-FILE-SELECT = *NO
The specified set of files is not to be further reduced.
DIALOG-FILE-SELECT = *YES
The specified set of files is to be displayed in a screen mask. The user can then mark individual files from the set on display, thus selecting them for or excluding them from migration.
Only files that can be migrated from S0 are output for dialog file selection.
Details on the content of the screen mask are provided in the section "Dialog selectionwhen migrating from processing level S0".
FROM-STORAGE = *S1-STORAGE-LEVEL(...)
This operand is only available to the HSMS administrator.
The files are to be migrated from storage level S1 to S1 or S2. This is done by copying the save files containing only valid files. The original save files are automatically deleted irrespective of their retention period.
S1-PUBSET-ID = <cat-id>
ID of the S1 pubset from which the files are to be migrated. A catalog ID may only be specified in an SF pubset environment.
S1-PUBSET-ID = *FROM-SYSTEM-MANAGED
This specification is only possible in a SM pubset environment.
The appropriate value is taken from the SM pubset parameters. This can be the catalog ID of a single S1 volume set or S1 defined by all HSMS-CONTROLLED volume sets.
MINIMUM-DAYS-ON-S1 =
Serves to select the save files using the minimum number of days they have been residing on S1 as the selection criterion.
MINIMUM-DAYS-ON-S1 = *STD
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class. If no management class is used, the value *STD is replaced by 0.
MINIMUM-DAYS-ON-S1 = <integer 0..9999 days>
The save files that have resided on S1 for at least the specified number of days are selected. The upper limit is determined by the specification in the MAXIMUM-DAYS-ON-S1 operand.
MAXIMUM-DAYS-ON-S1 =
The save files can be selected according to the maximum number of days they have been on S1.
MAXIMUM-DAYS-ON-S1 = *STD
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class. If no management class is used, the value *STD is replaced by 9999.
MAXIMUM-DAYS-ON-S1 = <integer 0..9999 days>
The save files that have resided on S1 for at least the specified number of days are selected. The lower limit is determined by the specification in the MINIMUM-DAYS-ON-S1 operand.
MINIMUM-SIZE = *STD / *NONE / <integer 1..2147483647 2Kbyte>
The save files can be selected according to their minimum PAM page size.
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class. If no management class is used, the value *STD is replaced by *NONE.
UNUSED-SPACE = *ANY / <integer 1..100>
The save files can be selected according to the percentage of invalid files they contain.Unless otherwise specified, the save files are selected irrespective of the percentage of invalid files.
RELEASE-PAGES = *MAXIMUM
All save files on S1 are migrated (reorganized).
RELEASE-PAGES = <integer 1..2147483647 2Kbyte>
The save files on S1 are migrated until the specified number of 2 KB blocks have been released as a result of this migration.
The save files are migrated in descending order according to the length of time they have been on S1, starting with the save files which have been on S1 the longest.
TO-STORAGE = *STD
If the statement is used with a management class, *STD means that the operand value is taken from the corresponding attribute of the management class. If no management class is used, the value *STD is replaced by *S2-STORAGE-LEVEL.
TO-STORAGE = *S2-STORAGE-LEVEL
The files are migrated to storage level S2.
TO-STORAGE = *S1-STORAGE-LEVEL
The files are migrated to storage level S1.
ARCHIVE-NAME = *SYSMIGRATE / <filename 1..22 without-cat-gen-vers>
Name of the archive within which the save files are to be moved. Explicit specification of an archive is required only if there is no default system archive unequivocally assigned to the S1 pubset.
The specified archive must already exist and be available for use as a migration archive.
If the archive directory is protected by a password, this password must be entered by means of the ADD-PASSWORD command prior to statement entry.
ARCHIVE-NAME = *SYSMIGRATE
The save files are to be moved within the default system migration archive (SYSMIGRATE).
FROM-STORAGE = *S2-STORAGE-LEVEL(...)
This specification is only available to the HSMS administrator:
The files are to be migrated from storage level S2 to S2 and are reorganized at the same time. This is done by copying the save files containing only the files which are still migrated. The original save files are automatically deleted irrespective of their retention period. For all specifications it must be borne in mind that the current standard save file will certainly not be reorganized.
SAVE-FILE-ID =
Determines the save files that are to be copied (reorganized).
SAVE-FILE-ID = *ALL
All save files of storage level S2 are copied (reorganized).
SAVE-FILE-ID = *BY-ATTRIBUTES(...)
Only those save files of storage level S2 are copied (reorganized) which were created within a certain period. If nothing further is specified, all save versions are selected.
CREATED-BEFORE = *LATEST-DATE / <date with-compl>(...) / <integer -99999..0 days>(...)
Only those save versions are transferred which were created before the specified date.
The default is *LATEST-DATE, in other words the time period with no upper limit.If a date is specified explicitly (absolutely or relatively), an additional time specification can define the period limit more precisely.
CREATED-BEFORE = <date with-compl>(...)
Date as absolute specification.
TIME = 23:59:59 / <time>
Time in the format hh:mm:ss.
CREATED-BEFORE = <integer -99999..0 days>(...)
Date as relative specification in days to the current date.
TIME = 23:59:59 / <time>
Time in the format hh:mm:ss.
SAVE-FILE-ID = <composed-name 15..15>
The specified save file is copied (reorganized).
You must specify the save file ID as follows: S.yymmdd.hhmmss
UNUSED-SPACE = *ANY / <integer 1..100>
The save files can be selected according to the percentage of invalid files they contain.Unless otherwise specified, the save files are selected irrespective of the percentage of invalid files.
ARCHIVE-NAME = *SYSMIGRATE / <filename 1.22 without-cat-gen-vers>
Name of the archive within which the save files are to be moved.
Explicit specification of an archive is required only if there is no default system archive unequivocally assigned to an SF pubset.
The specified archive must already exist and be available for use as a migration archive.
If the archive directory is protected by a password, this password must be entered by means of the ADD-PASSWORD command prior to statement entry.
ARCHIVE-NAME = *SYSMIGRATE
The save files are to be moved within the default system migration archive (SYSMIGRATE).
OPERATION-CONTROL =
Enables the user to define a number of parameters which are relevant for the execution of the migration run.
OPERATION-CONTROL = *STD
The default (“standard”) values of the parameters described below apply.
OPERATION-CONTROL = *PARAMETERS(...)
The parameters controlling the migration run can be modified as follows:
REQUEST-NAME = *STD / <name 1..8>
Request name that can be used in the HSMS request management statements (DELETE-REQUESTS, RESTART-REQUESTS and SHOW-REQUESTS) to refer to this request. The name is extended internally by a prefix derived from the user ID (or SYSHSMS for the HSMS administrator) and a suffix in the form of a time stamp.Unless otherwise specified, the request name is formed by the short code “MGF#” and the TSN of the calling user task yyyy as follows: MGF#yyyy.
REQUEST-DESCRIPTOR = *NONE / <text 1..60>
It is possible to enter any text that describes the request in more detail.
This text is displayed at the operator console when the request is started. The text can be output using the HSMS statement SHOW-REQUESTS.
EXPRESS-REQUEST = *NO / *YES
This operand is only available to the HSMS administrator.
Determines whether tape access is to take place during the sessions defined for express requests.
CONTROL-JV = *NONE / <filename 1..54 without-gen-vers>
Specifies the name of a job variable that HSMS supplies with various values corresponding to important actions performed by HSMS/ARCHIVE.
The nonprivileged caller must be owner or co-owner of this job variable.The user issuing the request can query the job variable to obtain an overview of the current processing status. How to use the job variable is described in detail in the “HSMS Vol. 1” manual [1] in the section “Job variable for request monitoring”.
WAIT-FOR-COMPLETION = *NO / *YES
Specifies whether the user wishes to wait until processing of his or her request has been completed (synchronous processing) or whether control is to be returned to the user after the validity of the HSMS statement has been checked (asynchronous processing). The maximum wait times for batch tasks and interactive tasks are different and are determined by preset global HSMS parameters.
Interactive tasks are permitted to carry out synchronous HSMS statement processing during tape sessions only.
PERFORMANCE-ANALYSIS =
Specifies whether a statistics file is to be produced for each ARCHIVE subtask.
PERFORMANCE-ANALYSIS = *NO
No statistics file is to be produced.
PERFORMANCE-ANALYSIS = *YES(...)
A statistics file is to be produced for each ARCHIVE subtask.
SEPARATOR = ; / <c-string 1..1>
Character that is inserted between the different fields in the statistics files. This enables programs such as EXCEL or LOTUS to differentiate the different fields.The default value is “ ; ”. This corresponds to the EXCEL default setting.
REPORT =
Serves to define whether a report is to be output for this migration request and to determine the scope of this report.
REPORT = *SUMMARY
A summary of the results of the migration request, including any error messages, is to be output.
REPORT = *FULL
A full report is to be output, including a list of all migrated files.
REPORT = *NONE
No report is to be output.
OUTPUT =
Specifies where the report is to be output.
OUTPUT = *STD
The output destination of the report is determined by the default value that is defined by the global HSMS parameter OUTPUT.
OUTPUT = *PRINTER
The report for this migration request is to be printed.
OUTPUT = *NONE
No report is output. Nevertheless the report is available as a pdf file via the SE manager application Backup Monitoring, if the monitoring is activated in the global HSMS parameters.
OUTPUT = *MAIL
The report for this migration request is sent as an email attachment to the address which is entered in the caller’s user entry. If it is not possible to send the report by email, it is printed out.
OUTPUT = *LIBRARY-ELEMENT(...)
The report for this migration request is edited and output to the specified PLAM library element (type P). If this is not possible, the report is printed out.
LIBRARY = <filename 1..54 without-gen-vers>
Name of the PLAM library.
ELEMENT = <composed-name 1..64 with-under>
Name of the element. A type P element is created with a version which contains the user ID plus the date and time.
OUTPUT = <filename 1..54 without-gen-vers>
The report for this migration request is to be edited and written to the specified file.If the file already exists, the following applies:
if it is a non-empty SAM file, it is continued
if not, the report is printed.
For nonprivileged callers the report files must be under the user’s own user ID. If not, co-ownership is a prerequisite.
Note on migration and the Concurrent Copy function
An attempt made during a Concurrent Copy session to migrate a file that is currently being modified may fail since an action which is uncompleted at migration time may be rejected.
Notes on the migration archive
A migration archive cannot be specified for migration from S0, since migration is possible only to a default archive assigned by the HSMS administrator.
If the archive directory is protected by a password, this password must be entered by means of the ADD-PASSWORD command prior to statement entry. This also applies to HSMS administrators.
If migration is requested by a nonprivileged user, the migration archive must permit write access (USER-ACCESS=*ALL-USERS and ACCESS=*WRITE).
Note on logging in the case of migration from S1 or S2 (reorganization)
When migration takes place from S1 or S2 (reorganization), multiple copy and delete requests are executed internally. Here logging is performed as specified in the REPORT operand. Only delete requests also create a full log (*FULL) when REPORT=*SUMMARY is specified to ensure that in all cases the report contains the volumes which have become free.
Note on migration from S2 to S2 (reorganization)
From HSMS version V12.0C, migration from S2 to S2 level removes duplicates of valid files, leaving only one unique valid file version in the reorganized save file.
Notes on migration from S0 to the extended S1 level
In the case of migration from S0 to S1, HSMS checks whether the saturation level permitted for the S1 level has been reached.
In an SM environment, when an extended storage level S1 is defined using S1-VOLUME-SET=*ALL-HSMS-CONTROLLED, the check takes place for all the volume sets of the SM pubset which are under HSMS control. If the saturation level has been reached, the statement is rejected with one of the following messages:
HSM050B if the S1 level was defined by a single volume set or
HSM050C if the S1 level was defined by all HSMS-CONTROLLED volume sets.
In an SF environment, when S1 level is defined by S1-SM-pubset, the check takes place for all the volume sets of the S1-SM-pubset which are not under HSMS control and excluding the control volume set.
Notes on migration from the extended S1 level to S1 or S2
When an extended storage level S1 is defined using S1-VOLUME-SET=*ALL-HSMS-CONTROLLED, files can be migrated from the S1 level to S1 only under the following circumstances:
SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE is set.
BS2000 OSD/BC V11.0 or higher is used on the system. In the case of a shared pubset network, all pubset sharers of the SM pubset must satisfy this requirement.
Dialog selection when migrating from processing level S0
//MIGRATE-FILES FROM-STORAGE=*S0-STORAGE(...,DIALOG-FILE-SELECT=*YES) s
MIGRATE-FILES : DIALOG-FILE-SELECT #FILES = @@@@@@@@@@ ENVIRONMENT = @@@@@@@@ MINIMUM-SIZE = @@@@@@@@@@ UNUSED-DAYS = @@@@ MAXIMUM-SIZE = @@@@@@@@@@ -------------------------------------------------------------------------------- M FILE-NAME UNUSED #PAGES ST BC _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ _ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@ @@ @ -------------------------------------------------------------------------------- NEXT-PAGE : ____________ (+,-,++,--, E, 'STRING') MARK : __ (A: ALL, N: NONE) @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Key:
Column | Values | Meaning |
M | Mark column (mark character = file is selected, blank = file is not selected) | |
FILE-NAME | Path name of the file | |
UNUSED | Number of days since the file was last accessed | |
#PAGES | File size in PAM pages (last-page pointer) | |
ST | Storage level on which the file is resident | |
S0/S1 |
| |
BC | Backup class of the file | |
A/B/C/D/E |
|
The procedure for selecting files is described in the “HSMS Vol. 1” manual [1].
Examples
A nonprivileged user migrates files of a project which is currently not being worked on using default values; the TSN is 3456
//MIGRATE-FILES FILE-NAMES=proj.
All files of the user’s own ID which have the default catalog ID and whose names start with PROJ. are migrated to the default system archive.
The files are migrated to a standard save file of the archive stored on S2 volumes from the volume pool of the archive; this implies that the retention period is as defined in the archive definition.
The request is given the name MGF#3456.
The request is processed asynchronously.
Depending on the global HSMS parameter OUTPUT a summary report is printed or sent as an email attachment.
The HSMS administrator migrates inactive files of pubset A to S1
//MIGRATE-FILES FROM-STOR=*S0-STOR(FILE-NAMES=:A:, - // UNUSED-DAYS=31,MINIMUM-SIZE=300,TO-STOR=*S1-STOR), - // OPERATION-CONTROL=*PAR(REQUEST-NAME=migpuba, - // EXPRESS-REQUEST=*YES)
All files of pubset A which have not been accessed for 31 days and whose size is at least 300 pages are migrated to the default system archive at storage level S1. (As a prerequisite, pubset A must have been assigned a system migration archive.)
The request is given the name MIGPUBA.
The request is processed asynchronously as an express request.
Depending on the global HSMS parameter OUTPUT a summary report is printed or sent as an email attachment.