z/VM: CP Commands and Utilities Reference - z/VM - IBM

SPXTAPE LOAD
1498 z/VM: CP Commands and Utilities Reference
anywhere in the pattern as long as the total number of characters,
including the asterisks, does not exceed eight. For example, a pattern
of d* means any string that begins with the character “D”. However, a
pattern of *d* means any string that contains a “D”, whether it is at the
beginning, in the middle, or at the end. A pattern containing a single
asterisk and no other characters means all strings regardless of length
or character content (including the string that contains only blanks).
% is a placeholding character that represents a single character. You can
use as many percents as necessary anywhere in the pattern as long
as the total number of characters, including the percents, does not
exceed eight. For example, a pattern of %%% means any string that is
three characters in length. A pattern of %%%s means any string that is
four characters in length and ends with the character “S”.
Wild cards can also be combined. For example, a pattern of vm%%* means any
string four characters in length or longer that begins with the characters “VM”.
3. When using the APPEND operand, if there is no SPXTAPE LOAD command
currently active on the addressed tape devices, the devices are placed in the
append waiting state (response 10 is issued).
Actual loading from the tape devices does not commence until you enter an
SPXTAPE LOAD command with a disposition of RUN, LEAVE, or REWIND (or
no disposition, which results in a default of RUN).
A sequence of appended SPXTAPE LOAD commands are processed as one
logical SPXTAPE LOAD command. This allows you (or an exec) to specify
different sets of selection criteria for individual files or groups of files to be
loaded from the same set of tapes in a single SPXTAPE LOAD processing run,
as shown in the following sequence:
spxtape load 300-399 selection_criteria_1 append
spxtape
.
load 300-399 selection_criteria_2 append
.
spxtape load 300-399 selection_criteria_n run
4. When using the NODUP operand, the definition of “duplicate” depends on the
type of file.
For standard spool files and system trace files, “duplicate” means that all the
file attributes of the file on the tape are identical to a file on the queue. This
includes the time stamp for when the file was opened. An identical time stamp
indicates that they are identical files. (If some files on the system have been
imported from other systems, it is possible that files could have been created
on both systems at exactly the same microsecond with all the same file
attributes, but contain different data. However, this is not very probable.)
For system data files other than system trace files, “duplicate” means that the
file name, file type, and class of the file on the tape are identical to the file on
the queue. In addition, for named saved system and saved segment files,
class A (active) and class R (restricted) files of the same file name and file
type are considered duplicate because they cannot exist on the system at the
same time.
A file that is found to be a duplicate is identified in the resulting volume log
with DUP_FILE in the SEG_STAT field. The FILE field of this entry in the log
contains the file ID of the file already on the system. If the file on the system is
moved to a different queue or user ID, or its file attributes are changed (for
example, its spool class), the file is no longer identified as a duplicate.
The NODUP operand helps you recover if a system failure occurs while you
are loading files from tape. If you add the NODUP operand to your selection
criteria and reprocess all the tapes that have already been processed, all the