
Initializing Tapes for BIM-EPIC Control
12-12 User Reference
Connectivity Systems, Inc.—Copyright © 2006
Use Pursuant to Company Instructions
In sequential initialization, TSIDINIT continues to initialize tapes until
the operator replies STOP to the mount message.
Sequential initialization requires the last four characters of the volume
serial number be numeric, for example, EP1200 or A67019. Random
initialization places no restrictions on the volume serial number.
TSIDINIT normally checks the actual volume serial number of each tape
before writing to the tape to ensure that an active tape is not initialized by
mistake. This check also protects against the creation of duplicate volume
serial numbers. If one of the specified volume serial numbers already
exists in the DSN Catalog, BIM-EPIC issues an error message and
requests a new volume serial number.
Forced initialization is used if you are initializing new tapes that have not
been previously initialized. Forced initialization directs TSIDINIT to
bypass any attempt to read data from the volume and to immediately
initialize the volume with the requested volume serial number.
!
WARNING:
Forced initialization should be used with caution because it
bypasses tape label checking. This may cause active data to be
lost if the wrong tape is mounted. If the volume serial number
already exists in the DSN Catalog, TSIDINIT issues an error
message. The resulting tape will contain only tape marks.
If it is necessary to reinitialize a tape that is currently in scratch status,
execute TSIDINIT with UPSI xxx1.
If the initialization process is for ACL-resident tapes:
PARM=’CONSOLE’ cannot be used. The cuu and volume serial
information must be submitted via SYSIPT statements.
PARM=’ACL=aclname’ or
PARM=’ACL=aclname,COUNT=nnnnn’ must be present on
the // EXEC statement.
Random initialization, sequential initialization, and forced
initialization are permitted. Forced initialization should be used
with caution. If a volume serial number should accidentally be
specified for an existing volume serial number containing an
active dataset or if the volume serial number is owned by another
operating system or machine, EPIC will initialize the volume
serial number and its existing data will be lost.
If multiple ACLs are present, only one ACL can be used in a
TSIDINIT execution. If concurrent TSIDINIT executions are to
be done, each execution should specify a different ACL name.
Commenti su questo manuale