This statement moves one or more save or node save files of a BS2000-UFS (POSIX) or node S0 which were created on disk or tape with BACKUP-FILES or BACKUP-NODE-FILES (storage level S1 or S2, SF pubset or private disk) to tape only for node save files, or to tape, disk or Net-Storage for BS2000 save files. The save or node save files are moved within a backup or node backup archive.
The functionality of the MOVE-SAVE-FILES statement combines that of several statements:
copying of several save or node save files from one storage level to another (COPY-SAVE-FILE or COPY-NODE-SAVE-FILE)
subsequent deletion of the original save or node save files on disk or S2 storage level
in addition, as required, implicit copying of the save files to a shadow archive as this is not supported for the original save to disk
The MOVE-SAVE-FILES statement (in contrast to manual copying) allows several save or node save files to be selected and moved. The sequence of the save versions (SVID) is retained.
After a save file or node save file has been moved, the same status is achieved as for an original backup directly to tape for node save files, or to tape, disk or Net-Storage for BS2000 save files.
A save file or node save file is always copied in its entirety (a reduction as with explicit copying is not possible). It thus also contains all Cataloged-Not-Saved (CNS) entries of the original save file. A restore from the backup archive provides the same result after the move as before.
With the move option, the following procedure applies for backup:
The files and job variables or node files are initially saved to disk or tape (one or more backups).
These backups can be moved to tape or disk at a later date. Possible criteria for the move time are, for example, the availability of MTC devices or the reaching of a particular disk utilization.
This statement has different formats for nonprivileged users and HSMS administrators. Privileged operands or operand values are marked with *P).
Format
MOVE-SAVE-FILES | Alias: MSF | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
*P) Privileged operand or operand value
ARCHIVE-NAME = <filename 1..22 without-cat-gen-vers>
Name of the archive in which the save or node save files are to be moved (the input archive corresponds to the output archive).
The archive must already exist and be defined as backup archive for the data backup or for the backup of node files.
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.
ENVIRONMENT =
Determines the HSMS environment in which the target archive is defined.
ENVIRONMENT = *STD
Only possible for a backup archive for data backup (ALLOWED-USAGE=*BACKUP).
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 = *NODE-STD
Only possible for a backup archive for backup of node files of a BS2000-UFS (POSIX) or node S0 (ALLOWED-USAGE=*NODEBACKUP).
For a workstation it is the environment in which the HSMS statement MODIFY-NODE-PARAMETERS was executed.
In BS2000-UFS it is the SINGLE-FEATURE environment for a privileged user; for a nonprivileged user *NODE-STD assumes the value of the environment in which the user’s home directory is defined.
ENVIRONMENT = *SINGLE-FEATURE
The HSMS statement is valid in the SF environment.
ENVIRONMENT = *SYSTEM-MANAGED(...)
The HSMS statement is valid in the specified SM pubset environment.
CATALOG-ID = <cat-id>
Catalog ID of the SM pubset for which the HSMS statement is valid.
FROM-STORAGE =
Defines the storage level from which the files are to be moved.
FROM-STORAGE = *DISK(...)
All save or node save files which were created on disk (storage level S1 or SF pubset or private disk) and satisfy the selection criteria specified below as regards retention period on disk and the storage space released (logical AND) are moved to S2-storage-level for node save files, or are moved to S2-storage-level/Public-disk/Net-storage for other save files. Files which meet both criteria are selected according to ascending retention period on disk, in other words the move starts with the oldest save or node save file and ends with the youngest one.
MINIMUM-DAYS-ON-DISK = *STD / <integer 0..9999 days>
The selection criterion is the retention period of the save or node save file on disk. All save or node save files which have been residing on disk for at least the specified number of days or longer are moved.
The default *STD corresponds to a retention period of 0 days, in other words the selection is independent of the retention period on disk.
RELEASE-PAGES = *MAXIMUM / <integer 1..2147483647 2Kbyte> / *MINIMUM
The selection criterion is the size of the storage space which is released by the move. Only as many save or node save files are moved from disk to S2 as are required to release the specified number of 2-Kbyte blocks by the move.
The default is *MAXIMUM, in other words all save and node save files are moved to S2. *MINIMUM (corresponds to RELEASE-PAGES=1) moves only the oldest save or node save file.
FROM-STORAGE = *S2-STORAGE-LEVEL
The files are to be moved from S2.
- For the process from S2-storage level to disk, each save version is moved to a separate save file on disk (the name of the new save file will be the previous save version name with its timestamp plus one second)
- For the process from S2-storage level to S2-storage level, the result depends on the type of the archive.
Several-svid archives: a new save file with a current time stamp as a SFID is created. All save versions from S2-storage-level are moved to it. Each copy of the save versions receives a SVID equal to the original SVID plus one second.
Single-svid archives: each save version is copied to a separate save file. The copy of save version has a SVID equal to the original SVID plus one second. Each new save file has a SFID with current time stamp.
SAVE-DIRECTORY = *NO / *YES
This specification is ignored for node save files.
Determines whether the directory file of the output archive used for this run is also to be written to the output volume as the last file of the run.
In the case of backup archives with SINGLE-SVID structure, moving generates a corresponding number of new save files. The directory file is only written to the output volume for the last save file generated (in other words the last save file moved).
SAVE-FILE =
Defines the save file on the output volume in which the save files to be moved are to be stored.
SAVE-FILE = *NEW(...)
The save files are stored in a save file which must be created on the output volume. In the case of backup archives with SINGLE-SVID structure, a new save file is created for each save file moved.
You can define the following attributes for the new save file:
RETENTION-PERIOD =
(Physical) retention period in days. During this period, neither the save file nor the save volume may be modified or deleted.
RETENTION-PERIOD = *STD
Unless otherwise specified, the preset value from the archive definition applies.
RETENTION-PERIOD = <integer 0..16383 days>
Explicit specification of the retention period in days.
USER-ACCESS =
This specification is ignored for node save files of a BS2000-UFS (POSIX) or node S0.
Defines whether the save file can also be accessed by user IDs other than that of the owner or of the co-owner.
USER-ACCESS = *OWNER-ONLY / *ALL-USERS
Access to the save file is to be restricted to the archive owner. This implicitly protects the save file against access by other users working without HSMS.
USER-ACCESS = *ALL-USERS
Access to the save file is to be granted to other users as well. If the corresponding directory is shareable and resides under TSOS, each user is simultaneously enabled to restore his or her files using ARCHIVE.
SAVE-FILE = *CONTINUE(...)
This specification is not permitted for backup archives with SINGLE-SVID structure.
A save file is to be continued.
The save file cannot be continued if a backup to tape was performed after backup on disk.
If the archive attribute SHADOW-COPY=*ALLOWED is set for the main archive HSMS attempts to extend the save file in the shadow archive which has the same SFID as the original save file in the event of automatic duplication to a shadow archive. If this save file does not exist the save file is not duplicated.
If the archive attribute SHADOW-COPY=*ALLOWED-AND-NEW-SFID is set for the main archive HSMS creates a new save file in the event of duplication to a shadow archive.
SAVE-FILE-ID = *LATEST
The last save file of the archive which was created for S2 is continued.
TO-STORAGE =
Defines the storage level to which the save file is to be moved.
TO-STORAGE = *S2-STORAGE-LEVEL(...)
The save or node save files are to be copied to storage level S2. The volumes to be used can be specified. If more than one volume is specified, all volumes must be of the same device type.
VOLUMES = *FROM-POOL
The volumes are to be taken from the volume pool of the specified archive, i.e. the pool of the directory or the associated MAREN pool.
VOLUMES = *FROM-OPERATOR
The volumes are to be allocated by the operator on request.
VOLUMES = list-poss(10): <vsn 1..6>
List of volume serial numbers, which will be requested in the specified order.
DEVICE-TYPE = *STD / <device>
Device type of the requested volumes. The device type must belong to the class “TAPE”. Only device types known in the system are accepted. In interactive mode, DEVICE-TYPE=? calls up a list of the available device types.
Unless otherwise specified, the preset value from the archive definition applies (S2-DEVICE-TYPE operand).
LOCATION = *STD / *ANY / <alphanum-name 1..8>
Location used for requesting volumes. This location must be known to MAREN. If the location manager is in use, the location should be properly defined in MARENLM. Otherwise MAREN ignores the specified value.
If MAREN is not in use, you must specify for LOCATION the value *ANY, or *STD if *ANY is the default location of the archive.
LOCATION = *STD
The default location of the archive is used.
LOCATION = *ANY
No location is to be used.
TO-STORAGE = *S1-STORAGE-LEVEL
The save file is to be moved to S1-Storage-Level.
The save file is to be moved according to the following rule:
- if the archive is defined in SF-environment, the save file is moved to the global S1 pubset which must have been defined earlier,
- if the archive is defined in an SM-environment, the save file is moved to the S1 level defined for this environment. This may be a dedicated volume set or one of a set of HSMS-CONTROLLED volume sets according to the definition in HSMS by MODIFY-SM-PUBSET-PARAMETERS.
TO-STORAGE = *PUBLIC-DISK(...)
This operand value is only available to the HSMS administrator.
This value is only valid in an SF pubset environment.
The files are moved to a pubset.
PUBSET-ID = <cat-id>
Catalog ID of the pubset.
TO-STORAGE = *NET-STORAGE(...)
This value is only valid in an SF pubset environment.
The files are backed up to Net-Storage.
VOLUMES = list-poss(16): <vsn 1..6>
Specifies the Net-Storage volume to which the files are moved. The specified volume must be accessible.
More than one Net-Storage volume can also be specified in a list (e.g. when there is more than one save task).
OPERATION-CONTROL =
Defines parameters for moving the save or node save files.
OPERATION-CONTROL = *STD
The default values of the operands described below apply.
OPERATION-CONTROL = *PARAMETERS(...)
You can modify the following operands for controlling the moving of save and node save files:
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 “MSF#” and the TSN of the calling user task yyyy as follows: MSF#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 during a complex processing operation, for example the processing of shadow archives.
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”.
SHADOW-COPY =
Specifies whether the save version is to be automatically duplicated to a shadow archive which may have been assigned.
SHADOW-COPY = *ALLOWED
If the files and job variables on storage level S2 are backed up and the relevant backup archive has been assigned a shadow archive, the save version is automatically duplicated to this shadow archive after the backup run.
SHADOW-COPY = *INHIBITED
The save version is not automatically duplicated to a shadow archive which may have been assigned.
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 statement processing during tape sessions only.
TAPE-CONTROL = *STD / *PARAMETERS(...)
Defines the parameters which are relevant for backup to tape.
TAPE-CONTROL = *STD
The preset values from the definition of the archive from which the elements are to be restored apply.
TAPE-CONTROL = *PARAMETERS(...)
The operands relevant for backup to tape can be modified as follows:
BLOCKING-FACTOR = *STD / <integer 15..15 2Kbyte> / *MAX
Blocking factor to be used for writing the save file to tape, specified as the number of 2-Kbyte blocks (PAM pages) written to tape in a single input/output operation. As the higher blocking factor means that the occupancy level of the volume and the tape processing performance improve, values below 15 should not be selected.
The default value *STD selects the blocking factor from the archive definition. If this also contains the default value, the default values of the ARCHIVE parameters apply (BLOCK-SIZE-TAPE for tapes, BLOCK-SIZE-T-C for magnetic tape cartridges).
*MAX selects the maximum blocking factor possible in the current BS2000 version. Currently this is the value 128.
UNLOAD-TAPE = *STD / *YES / *NO
Specifies whether or not tapes are to be unloaded after processing. This applies both for input and output tapes.
The preset value from the archive definition applies unless otherwise specified.
It is possible that HSMS will ignore the value of this operand in order to avoid irrational tape processing, for example to avoid unloading a tape several times while rewinding it.
DISK-CONTROL =
Defines the parameters which are relevant for move save file to disk.
DISK-CONTROL = *STD
The preset values from the definition of the archive to be used for save file to disk apply.
DISK-CONTROL = *PARAMETERS(...)
The parameters relevant for save file to disk can be modified as follows:
PRIMARY-ALLOCATION = *STD / <integer 36..50331645 2Kbyte>
Size in PAM pages of the primary allocation for save file creation on disk (see the description of the CREATE-FILE command in the “Commands” manual [5]). Unless otherwise specified, the preset value from the archive definition applies.
SECONDARY-ALLOCATION = *STD / <integer 0..32767 2Kbyte>
Size in PAM pages of the secondary allocation for save file extension on disk (see the description of the CREATE-FILE command in the “Commands” manual [5]).
Unless otherwise specified (*STD), the preset value from the archive definition applies.
Values from 1 through 35 are not permitted.
WRITE-CHECK = *STD / *NO / *YES
Specifies whether a read-after-write check is to be performed after each write operation for error detection purposes. Note that read-after-write checking will result in longer execution times.
Unless otherwise specified, the preset value from the archive definition applies.
DESTROY-BY-DELETE = *STD / *NO / *YES
Specifies whether the storage space released by save file deletion is to be erased by overwriting it with binary zeros for data privacy reasons. Note that erasure by overwriting will result in longer execution times for save file deletion.
Unless otherwise specified, the preset value from the archive definition applies.
PERFORMANCE-ANALYSIS =
Specifies whether a statistics file is to be produced for each ARCHIVE subtask. ARCHIVE writes a new line to this statistics file:
when it opens a save file ARCHIVE.SAVE.FILE.
when it closes this save file.
whenever it begins saving or restoring a new file.
every 2 seconds while it is saving/restoring.
This gives a detailed overview of the ARCHIVE activities taking place during the save and restore operations.
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 for the move request is to be output for this archival request and to determine the scope of this report.
REPORT = *SUMMARY
A summary of the results of the move request, including any error messages, is to be output.
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 on this move 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 move 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 move 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 move 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.