alias name
ARCHIVE also permits alias names instead of file names. The assignments of file names to alias names are defined in the alias catalog. Internally, ARCHIVE deals with file names only.
ARCHIVE.CHKPT
-> checkpoint file
archive directory
-> directory file
ARCHIVE.LATER
-> queue file
ARCHIVE macro
ARCHIVE can be called from user programs by means of the ARCHIVE macro. In the macro, statements are specified in the same way as in interactive mode. However, the HELP, PARAM and END statements are not permitted.
ARCHIVE sequence number
An ARCHIVE process is created for statements requiring inputs/outputs to a file or to a save volume. This process is assigned a 15-digit ARCHIVE sequence number.
archiving
Swapping out of data no longer required online from disk to magnetic tape or MT cartridges.
backup
-> data saving
backup class
File save level entered in the catalog. Determines how often a file is saved. Possible values: A, B, C, D and E. Files with backup level A are always saved.
cataloged not saved
The file was not saved, either because it had not been updated when an -> incremental save occurred or because it could not be saved due to an error (e.g. OPEN error).
CFID (Coded File ID)
-> internal file name
checkpoint file
Contains an entry for each current save version and, if the ARCHIVE run was effected with the RESTART=YES operand, the checkpoints at which an abnormally terminated ARCHIVE run can be restarted.
CNS
-> cataloged not saved
Coded File ID (CFID)
-> internal file name
command listing
For every ARCHIVE run, ARCHIVE outputs the entered statements in the form of a command listing.
conversion
ARCHIVE offers a conversion option in cases where files have a PAM key but the output volume does not permit the writing of PAM keys.
data
Within ARCHIVE: files, job variables and catalog entries of files stored on magnetic tape, MT cartridge or disk.
data saving
Within ARCHIVE, the periodic creation of copies of the entire data inventory for the purpose of -> reconstruction of -> data in case data is lost due to hardware errors, inadvertent deletion etc. Data saving can also be used to reorganize disk storages.
DIRCONV
The DIRCONV conversion program enables directory files to be converted from CATID=NO mode to CATID=YES mode. Conversion in the opposite direction is not possible.
directory file
Automatically maintained administrative directory of the saved data (files, job variables, -> save files and -> save versions) and of the related -> volumes.
ENTER file
ARCHIVE creates this for a batch process in the -> queue file after the batch process has been started via the PROCESS statement.
export
Writing -> data to tape for -> transfer.
full save
All files or job variables are saved completely, regardless of whether or not they have been updated since the last save run.
HSMS (Hierarchical Storage Management System)
BS2000 software product with migration, -> backup and archival functions; implemented via a storage hierarchy concept and archives. HSMS is based on ARCHIVE functions.
import
Reading exported -> data into the target server for -> transfer.
incremental save
An incremental save includes only those files that have been updated or newly created since the last save run. This save method decreases runtime and reduces storage space requirements.
internal file name
Internal name in addition to the file name in the catalog; serves for unique identification of the file and changes whenever the file is updated. Is passed in the FSTAT macro but not output via /SHOW-FILE-ATTRIBUTES.
job switch
In procedures and ENTER jobs, information on the execution of an ARCHIVE process can be derived from the position of job switches set by ARCHIVE during or after a run.
LATER job
Within ARCHIVE, a job which is running in batch mode due to specification of the NOW=NO operand and which is written to the -> queue file ARCHIVE.LATER. The LATER job can be started or deleted at a later point in time.
MAREN
Software product managing magnetic tapes and MT cartridges in data centers. The ARCHIVE -> volume pools can be included in MAREN management. In this case MAREN assigns the volumes to an ARCHIVE directory file. The MAREN entry of the volume indicates the assignment to the -> directory file.
parallel processing
Files or job variables specified in a single FILES or JOBVAR statement can be simultaneously written to or read from a number of save volumes.
partial save
The user can specify, in the case of large files, that only those pages should be saved that have been updated since the last -> full save.
Performant File Access
Can be defined for directory, checkpoint and print files, i.e. for files continually accessed. This requires specification of the PERFORMANCE attributes for these files.
PFA
-> Performant File Access
pool
-> volume pool
print file
A print file is created for every ARCHIVE run with a -> restart option if a value other than NONE has been specified for the LIST operand. It contains information on the run and an alphabetical list of the files processed in the current run.
queue file
ARCHIVE statements can be processed in a batch process if the operand NOW=NO is specified for the relevant statement. The batch process is entered in the queue file ARCHIVE.LATER and can be started or deleted at a later point in time.
read-after-write check
Such a check can be requested for writing to disk. It is not effected by ARCHIVE but by DMS. After every write operation, the written data is read so that any errors can be pinpointed immediately.
reconstruction
Restoration of data in cases of data loss due to a hardware error or inadvertent deletion. For this purpose, save copies are accessed which were created at an earlier point in time.
report
ARCHIVE issues a report for every ARCHIVE run. The report contains information on the input/output volumes, the processed files and job variables, the save type, the save version number, the user ID and the date of the ARCHIVE run.
restart
ARCHIVE optionally writes checkpoints to the -> checkpoint file. These checkpoints permit ARCHIVE runs interrupted due to a system crash or other errors to be resumed as of a defined status.
save file
Container holding saved files and job variables; comprises one or more -> save versions and consists of a set of -> volumes with the same owner and retention period. A save file can only be released as a whole. It is identified by a -> svid formed from the date and time of day.
save version
Files or job variables saved at a certain point in time are combined into a save version. A save version is identified internally by a -> svid and can be addressed by the user via its creation date or via the name assigned to it during creation.
saving
General term for writing (copying) -> data to a -> save file, regardless of the function involved; also used specifically for -> data saving.
saving, logical
Reading -> data from one or more -> volumes and writing it to one or more volumes as a logical entity.
saving, physical
Writing all the -> data of a -> volume, including the volume labels, block by block to another volume whose contents and structure are identical to the original volume.
serial processing
The various FILES statements are processed one after the other: all the files specified in one FILES statement are transferred before the next FILES statement is processed. The approach for JOBVAR statements is analogous.
subtask
Statements requiring input/output from or to save volumes are normally processed by a subtask created by ARCHIVE, and not by the user job (main task).
svid
Save version identifier designating a -> save file. It has the format: S.yymmdd.hhmmss
transfer
Transfer of files, job variables or catalog entries of files to other BS2000 systems or other user IDs; implemented via -> export to tape and -> import to the target server by means of ARCHIVE.
volumes
Within ARCHIVE: magnetic tapes, MT cartridges and disks.
volume pool
Set of -> volumes managed in the -> directory file. The volumes for the save jobs are requested from the pool of free volumes unless otherwise specified.
work files
ARCHIVE work files can be divided into two categories:
files under the TSOS user ID that exist only once in the system and are created under TSOS during the first run (
->checkpoint file and->queue file)files that are created under the caller's user ID during every ARCHIVE run (e.g. the
->save files).