action statement
Statement issued to HSMS which, in order to be processed, requires I/Os to and from user files. The following are action statements:
ARCHIVE-FILES, ARCHIVE-NODE-FILES , BACKUP-FILES, BACKUP-FILE-VERSIONS, BACKUP-NODE-FILES, COPY-EXPORT-SAVE-FILE, COPY-NODE-SAVE-FILE, COPY-SAVE-FILE, EXPORT-FILES, IMPORT-FILES, LIST-VOLUMES, MIGRATE-FILES, MOVE-SAVE-FILES, RECALL-MIGRATED-FILES, REORGANIZE-VERSION-BACKUP, REPAIR-CATALOG-BY-RESTORE, REPLACE-SAVE-FILE-BY-RESTORE, RESTORE-FILES, RESTORE-NODE-FILES, SELECT-FILE-NAMES, SELECT-JV-NAMES, SELECT-NODE-FILES, UPDATE-EXPORT-SAVE-FILE
archival
Long-term saving of selected files, e.g. for product liability or revision security reasons. The files are deleted from the processing level once they have been saved.
ARCHIVE
BS2000 software product which saves files and job variables logically.
ARCHIVE has an internal interface with HSMS and implements the -> HSMS action statements.
archive
Management unit for files under HSMS management, consisting of the archive definition and the associated archive directory (directory file). Archives are addressed via their -> owner ID and the archive name.
HSMS makes a distinction between various archive types:
For DMS files: archives for -> data backup (backup archives), -> files version backup (version backup archives), -> archival (long-term archives) -> migration (migration archives) and -> shadow archives.
For node files: archives for node backup (node backup archives) and node archival (node long-term archives).
An archive can be private, i.e. only available to the -> archive owner, or public, i.e. available to all users.
archive directory
File used for managing the objects saved in an archive, i.e. files, job variables,-> save files, -> save versions and the -> volume pool, and implemented as an ARCHIVE directory file (-> ARCHIVE).
archive owner
Users have the right to create archives by means of the CREATE-ARCHIVE statement. The creator of an archive is the archive owner. Only the HSMS administrator may enter any user ID in the archive name, using the CREATE-ARCHIVE statement. In doing this, the corresponding user becomes the archive owner.
archive type
Determines the basic HSMS function for which an archive is to be used.
backup
The regular creation of copies of the data inventory for the restoration of data lost due to hardware or software errors or inadvertent deletion, etc. This facility can also be used to reorganize disk storage.
backup archive
HSMS archive used for backup.
backup class
Save level assigned to a file and entered in the catalog; this level is used to determine the frequency with which the file is backed up. Possible values are *A, *B, *C, *D and *E. Files of backup class *A are backed up with each backup run. Files with backup class *E are saved only if MAXIMUM-BACKUP-CLASS=*E was specified explicitly.
backup monitor
-> BS2000 Backup Monitor
backup server
Backup server for workstations which are connected to the local BS2000-UFS (POSIX) via NFS.
BS2000 Backup Monitor
The BS2000 backup monitor is an SE management application which is integrated into the Applications main menu of the SE Manager. The BS2000 backup monitor provides information on the status of the backup requests which were assigned in the SE server's BS2000 systems with the software products HSMS and FDDRL.
BS2000 file
Specifies a file which is created and processed exclusively by BS2000. BS2000 files have been processed on Net-Storage (FILE-TYPE=BS2000) since BS2000/OSD-BC V9.0. They reside directly on a Net-Storage volume. Open systems may only access them in read mode.
BS2000 net storage file
-> net storage file
BS2000-UFS
UNIX file system residing on a BS2000 server.
Cataloged-Not-Saved (CNS)
Indicates that a file was not saved either because an incremental backup was performed and the file had not been changed since the previous backup, or because an error (e.g. open error) prevented it from being saved.
CFID
Coded File ID -> internal file name
client
Computer that accesses the services of another computer ( -> server) via the network. Any one computer can simultaneously function as a client requesting services from other computers and as a server offering services to other computers.
see also -> HSMS client
client/server architecture
System architecture in which computing capacities and applications are distributed over -> clients and -> servers.
Client functions are typically performed by PCs, workstations and -> UNIX systems.
Server functions are primarily performed by mainframes and UNIX systems subject to certain constraints.
Client and server systems can be combined as required; in principle, any client has access to any server.
clone unit
A clone unit is the copy of an (original) unit at a particular time (Point-in-Time Copy) which, depending on the clone type, is created by the component QuickOPC or EquivalentCopy. Following activation, the unit and the clone unit are separated from each other, and applications can access both.
CNS
-> Cataloged-Not-Saved
coded file ID
-> internal file name
collector request
Request for migration to S2 or requests for archival in the -> standard save file of a system archive can be combined in a collector request unless they were issued by the HSMS administrator. The requests are then executed together (thus reducing the number of tape access and positioning operations) but HSMS still outputs separate request-specific reports. An aborted collector request must be restarted by the HSMS administrator.
Concurrent Copy
Option of the HSMS statements BACKUP-FILES and BACKUP-FILE-VERSIONS which permits BS2000 files to be modified during a backup.
computer network
Organization of several computers interconnected via a physical line with the purpose of permitting peer-to-peer data exchange between these computers. A distinction is made between local computer networks (-> LAN) and non-local computer networks (-> WAN).
continuation period
Period of time during which the standard save file of an archive is continued. The continuation period may have any length between a day and a month.
control file
File under user ID SYSHSMS that contains the HSMS control parameters and the archive definitions.
On system managed storage, the control file is located under the SYSHSMS user ID of an SM pubset; it contains the control parameters for this SM pubset.
co-ownership
Nonprivileged users can also work with files and job variables of which they are co-owners.
data
Within the context of HSMS, files, job variables and catalog entries of files (on magnetic tape cartridge or private disk).
data transfer
The transfer of files, job variables or catalog entries from files to other BS2000 systems or other user IDs, implemented by exporting data to magnetic tape cartridge, public disk or -> Net-Storage and then importing it to the destination.
default system archive
-> Archive assigned globally to the entire system or to specific SF/SM pubsets and accessed unless another archive is specifically specified. There is a separate default system archive for each of the basic HSMS functions -> migration ( -> SYSMIGRATE), -> version backup ( -> SYSVERSION (only specific to SF/SM pubsets)), -> backup ( -> SYSBACKUP), -> archival ( -> SYSARCHIVE), node backup ( -> SYSNODEBACKUP) and node archival ( -> SYSNODEARCHIVE).
directory
Part of a UNIX file system that serves to group and organize files and directories.
directory file
A term used synonymously for -> archive directory; for more detailed information about the structure of a directory file, see “Directory file“, in the “ARCHIVE“ manual [2].
disk storage system
External disk system. Mirroring functions (e.g. backing up Snapsets) can be used in BS2000/OSD for disk storage systems which the BS2000 host component SHC-OSD manages.
ETERNUS disk system
-> disk storage system of the company Fujitsu Technology Solutions.
Ethernet
Standardized method of computer interconnection used to build -> local area networks (LAN).
except file
File maintained by the system administrator, containing the (fully or partially qualified) names of the files which are to be exempted from migration. The names are stored in the except file.
export
Writing date to magnetic tape cartridge, public disk or -> Net-Storage for the purpose of -> data transfer.
express request
Category of requests restricted to the HSMS administrator for which special -> tape sessions can be defined.
file expiration date
-> retention period for the save version in a long-term archive.
file system
Hierarchical collection of -> directories and files forming a tree structure. The origin of this tree structure is referred to as the -> root directory (/). All other directories are branches of this tree. Each file of a file system is accessible via exactly one path of this file system.
HSMS
Hierarchical Storage Management System: BS2000 software product offering such functions as -> migration, -> backup, -> archival, and -> data transfer, implemented in a -> storage hierarchy and in -> archives.
HSMS administrator
User enjoying the HSMS administrator privilege. This privilege is granted to any user working under the user ID SYSHSMS and under TSOS.
The HSMS administrator can use all HSMS functions without restrictions. The following are typical HSMS administrator tasks: managing the storage hierarchy, creating the default system archives, system backup and control of tape processing.
HSMS client
-> passive HSMS client
HSMS functions
-> HSMS
HSMS run
Period of time between starting the HSMS program and terminating it with END.
HSMS session
Period of time between loading subsystem HSMS (with /START-SUBSYSTEM or //START-HSMS) and unloading it (with /STOP-SUBSYSTEM or //STOP-HSMS); see also -> SM pubset session.
implicit recall
Automatic recall of migrated files as a result of attempts, on the part of DMS, to access these files, as opposed to -> recall requested via an HSMS statement.
import
The loading of exported data to the destination during -> data transfer.
inactive date
Date on which a file was last accessed.
inactive files
Files with a high -> inactive date, i.e. files which have not been referenced for a long time, are obvious candidates for -> migration.
internal file name
Internal name (CFID) listed in the catalog along with the file name; this name uniquely identifies the file and is modified each time the file is altered. It is transferred in the FSTAT macro but not output with SHOW-FILE-ATTRIBUTES.
invalid file
-> Migrated file which is still contained in the -> save file of the -> migration archive, but which was already recalled, overwritten or deleted on processing level S0.
LAN (Local Area Network)
Hardware configuration of a local -> network consisting of data display terminals and other devices installed in proximity to one another, e.g. in the same building.
The proximity permits the use of simple transmission technology and thus transmission at higher speed and lower cost.
Depending on national legislation, the boundaries of the user’s premises may constitute the boundaries of the LAN. A LAN may be connected to other -> computer networks as a private subnetwork and thus become part of a larger network such as a WAN.
Synonyms: local computer network, local network.
level
-> storage hierarchy
locally available
-> pubset
local computer
The computer at which the user is working. All other computers in a -> computer network are -> remote computers for that user. Once a user has connected up with a remote computer, that computer becomes that user’s local computer.
long-term archive
HSMS archive used for archival.
master computer
Computer on which all the DMS management functions of a -> shared pubset are executed.
MDS
-> Modified-during-save
migrated file
A migrated file is a file whose data has been deleted from the processing level but whose catalog entry remains on this level. The catalog entry indicates the background level to which the data was migrated.
migration
Moving -> inactive files from the processing level to a background level without deleting the catalog entry.
migration archive
HSMS archive used for migration.
mirror disk
Disk set consisting of at least two disks having identical contents.
Modified-during-save
Indicates that a -> node file was opened by another user while being saved.
monitoring
If HSMS is linked to the application SM2, SM2 users can better monitor migration or recall activities. The resulting information can result in the migration parameters having to be reset.
MPVS
Multiple public volume set: public volumes distributed over several -> pubsets.
It is possible to assign specific pubsets to specific users.
multiplexing operation
Multiplexing operation is only available for HSMS backup server functions, i.e. for backing up and restoring files at remote workstations. In this operating mode, multiple ARCHIVE subtasks can simultaneously share the same MTC devices and magnetic tape cartridges in parallel. This ensures enhanced performance and the optimum utilization of MTC devices and guarantees that magnetic tape cartridges are optimally filled.
network
A complex structure of lines and control units that provides data communication services.
Net-Storage
The storage space provided by a Net-Server in the computer network and released for use by external servers. Net-Storage can be a file system or also only a node in the Net-Server’s file system.
Net-Storage file
Specifies a file which is created on a Net-Storage volume. On Net-Storage a distinction is made between two file types: BS2000 file and node file.
NFS (Network File System)
BS2000 software product that permits distributed data storage in a heterogeneous -> computer network. It enables users to access remote files as if they were residing on their -> local computer.
NFS is thus used for connecting systems. Furthermore, the automatic and reliable BS2000 data saving functions can be made available for the files of such systems via NFS.
node
Computer (workstation or PC) connected to a computer network.
node backup archive
HSMS archive used to -> back up node files.
node file
Meaning in Net-storage context:
Specifies a Net-Storage file (FILE-TYPE=NODE-FILE) which can be created and processed both by BS2000 and open systems. Node files are supported in BS2000 OSD/BC V10.0 and higher. They reside on a Net-Storage volume in a user-specific directory (name of the user ID), and the file names comply with the BS2000 naming conventions.
Meaning for UNIX workstations:
Node files are files or -> directories in a UNIX file system (UFS) of a UNIX workstation. When implementing -> NFS, node files are understood to be the files or -> directories of a workstation which can be accessed via -> BS2000-UFS. Node files are case-sensitive.
If directories or file systems have been mounted via BS2000-UFS (POSIX), the files contained therein can be saved or archived with HSMS BACKUP-NODE- FILES oder ARCHIVE-NODE-FILES, however, they cannot be processed by BS2000 DMS directly.
node long-term archive
HSMS archive for the -> archival of node files.
node S0
Designates a remote -> file system mounted on the “HSMS“ node of a -> local BS2000-UFS by the system administrator.
The local BS2000-UFS is also considered as a node S0.
number of backup versions
Number in the range of from 0 to 32 which denotes maximum value of file versions guaranteed to be kept within version backup archives. It is a file attribute which is stored in its catalog entry and can be specified within create-file or modified during modify-file-attributes. In SM-environment, it also can be given within management classes. The value is (re)written into directory of a version backup archive during version backups (//BACKUP-FILE-VERSION) and also is updated to the actual during //CHECK-CATALOG-FILES.
owner ID
Upon creation of an archive, the user ID of the -> archive owner is stored as the owner ID in the HSMS control file.
The owner ID SYSHSMS is assumed if the HSMS administrator creates an archive without specifying an owner ID.
passive HSMS client
For UNIX workstations:
The software product -> NFS is required in addition.
A passive HSMS client is mounted using -> NFS in BS2000’s POSIX files system. -> Backup/archiving takes place using HSMS with the BACKUP-NODE-FILES or ARCHIVE-NODE-FILES statement. No additional software is required on the node.
path name
Under -> UNIX, each file and each -> directory is identified by a unique path name. The path name designates the position of the file or the directory within the -> file system as well as indicating how the file/directory can be accessed. The path name is formed by the names of a file’s or directory’s parent directories, starting with the -> root directory, and its own name. The names of the individual directories are separated by a slash.
(Example: c:dir1/dir2/protocol)
UNIX distinguishes between absolute and relative path names.
pool
-> volume pool
protection attributes
Security-relevant attributes of an object (file, job variable, etc.) which determine the type and scope of access to this object.
Examples of file protection attributes are: ACCESS, USER-ACCESS, AUDIT READ-PASSWORD, WRITE-PASSWORD, EXEC-PASSWORD, RETENTION-PERIOD, BASIC-ACL and GUARD.
pubset
Public volume set: set of public disks which belong together and may, for instance, have a common catalog. A pubset is considered to be locally available once its catalog and data have been imported (IMPORT-PUBLIC).
A pubset is identified by a one- to four-character ID.
recall
To move migrated files back from a background level to the processing level -> S0. The recall can be started explicitly using the RECALL-MIGRATED-FILES statement or implicitly by opening the file.
remote computer
A -> network comprises remote and -> local computers. All computers in a network other than the one at which the user is working are remote computers for that user. Users can communicate with all remote computers in the network. Once a user has connected up with a remote computer, that computer becomes that user’s local computer.
reorganization
HSMS function used primarily to reorganize the migration archive, i.e. to reshuffle save files without transferring -> invalid files.
When long-term archives are reorganized, only save versions whose-> file expiration date has not yet been reached are copied.
However, HSMS can also reorganize -> pubsets and private disks (-> backup).
repository
-> archive directory for node files
request
Generated for the processing of -> action statements and in connection with -> implicit recall. All requests are entered in the -> request file.
request file
File under the SYSHSMS user ID containing the requests. It is from this file that the tasks which process the -> action statements are started.
restore
To move data from an HSMS archive back to the processing level -> S0.
retention period
Period of time during which data modification or deletion is prohibited. The (physical) retention period prevents save files and save volumes from being overwritten during this time, while the (logical) retention period defined by the file expiration date prevents files from being modified or deleted.
root directory
Main directory of a tree-structured -> file system which constitutes the origin of all other -> directories. The root directory must be present in any file system.
S0
Online processing level, implemented by disk storages with short access times.
Its management units are the pubsets.
S1
Online background level, implemented by disk storages (possibly with more capacity and longer access times than -> S0); its management units are the pubsets.
S1-SM-pubset
An SM pubset which is used as S1 storage level of SF pubsets. This ensures that the storage space available for backup and migration at storage level S1 is no longer limited to the size of an SF pubset of 4TB, but can almost be 1000TB in size.
S2
Offline background level implemented by archives on magnetic tape cartridges.
save
Generally speaking the copying of data to a -> save file, irrespective of the basic function used. Also used as a synonym for -> backup.
save, logical
To read data from one or more volumes and write it contiguously to one or more volumes.
save, physical
Block-by-block copying of the entire data of a volume, including the volume labels, to another volume, so that the contents and structure of the second are identical to those of the original volume.
save file
“Receptacle“ for saved files and job variables. The save file contains one or more -> save versions and consists of a set of volumes which all have the same owner and -> retention period. The distinction between save file and save versions is introduced with HSMS, where it is possible to manage several save versions in a single save file in conjunction with archival, migration and node backup. Only entire save files can be released. Each save file is identified by a save file ID ( -> SFID) formed by the date and time of its creation.
save version
Result of a backup or archival request. The save version is internally identified by an SVID (save version ID). The user can refer to it via its creation date or the name assigned to it at creation.
server
Computer providing services to other computers ( -> clients) in a network.
SFID
Identifies a -> save file; the save file ID has the following format:
S.yymmdd.hhmmss
SF pubset
Abbreviation for “single-feature pubset”.
An SF pubset consists of a set of public disk storages with a shared catalog. It is defined by its catalog ID.
An SF pubset is not the same as an -> SM pubset.
SF pubset environment
Set of HSMS parameters which are specific to all -> SF pubsets. The SF pubset environment includes the parameters of the global control file and the global request file.
shadow archive
Archive that is linked to a -> backup or -> long-term archive. A shadow archive holds the automatically created copies of data which is stored in a backup or long-term archive.
shared pubset
Pubset that can be accessed simultaneously by more than one computer.
sharers
Computers that have simultaneously imported a particular pubset ( -> shared pubset).
single-feature pubset
-> SF pubset
SM pubset
Abbreviation for system-managed pubset.
The DMS object SM pubset consists of a set of -> volume sets. An SM pubset is not the same as an -> SF pubset.
The term SM pubset is also used in this manual to denote -> “SM pubset under HSMS control”.
SM pubset not under HSMS control
SM pubset that was not declared for HSMS and can therefore also not be managed by HSMS.
SM pubset under HSMS control
Closed container that holds both the data and the metadata.
In this manual also often simply referred to as -> SM pubset.
SM pubset session
For HSMS, the time from the start of the HSMS subsystem (or the import of the SM pubset if this is done later) to the time the HSMS subsystem is stopped (or the SM pubset is exported if this is done later).
SM pubset environment
Set of HSMS parameters that are specific to an -> SM pubset. The SM pubset environment includes the parameters of the SM pubset control file and the SM pubset request file.
Snapset
Copy of a -> pubset on additional -> mirror disks (Snap disks) which as of BS2000/OSD V7.0 can be created as a pubset backup in a -> disk storage system with SHC-OSD. Files and job variables can be restored from a Snapset using a DMS command or saved with HSMS.
standard save file
Save file to which -> backups for an -> archive are written unless otherwise specified.
storage hierarchy
Assignment of storage units to different storage levels, depending on their availability, access time and storage costs (-> S0,-> S1,-> S2).
storage level
-> storage hierarchy
SYSARCHIVE
-> default system archive for -> archival.
SYSBACKUP
-> default system archive for -> backup.
SYSMIGRATE
-> default system archive for -> migration.
SYSNODEARCHIVE
-> default system archive for -> archival of -> node files.
SYSNODEBACKUP
-> default system archive for -> backup of -> node files.
system archive
-> default system archive
system-managed pubset
-> SM pubset
system startup
Loading of the BS2000 operating system software. The following variants exist:
AUTOMATIC-STARTUP, DIALOG-STARTUP and FAST-STARTUP.
The variants are differentiated by their automation. Synonym: system initialization
SYSVERSION
-> default pubset-specific system archive for -> version backup of -> files.
TAPE
Volumes of the class “TAPE“ are assigned to storage level -> S2, these are magnetic tapes with a recording density of 1600 bpi (T1600) and 6250 bpi (T6250) as well as magnetic tape cartridges (TAPE-C2, TAPE-C3, etc.).
tape session
Period of time during which the I/Os to and from -> S2 are processed.
UFS (UNIX File System)
Component of -> NFS providing access to local file systems.
UNIX
Interactive operating system developed by Bell Laboratories in 1969 for use in small computers but meanwhile used in all computer classes. Since only the central UNIX kernel is hardware-dependent, UNIX can be installed on a wide range of systems of different manufacturers.
valid file
-> Migrated file which, up to now, has not been recalled or deleted or overwritten on the processing level. It is marked as a migrated file in the catalog (# before its name).
version backup archive
A new type of archive specially introduced for version backups. In contrast to a backup archive, a version backup archive contains a user-defined number of file versions per file. In the directory file additional information about a files deletion date and if a file should be removed from the archive is stored.
volume pool
Set of volumes managed by an archive and registered in the directory. Volumes required for save requests are normally fetched from the free volume pool of the archive.
volume set
Set of disks that can be addressed by their volume set ID. Several volume sets make up an -> SM pubset.
WAN (Wide Area Network)
-> Computer network not restricted to a limited area. A WAN may include several -> LANs.