Memorex LOCK - VERSION 2-24 Especificaciones Pagina 367

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 489
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 366
Mounting Tapes Initializing Tapes (TSIDINIT)
Chapter 12. Managing Tape Volumes 12-9
Initializing Tapes (TSIDINIT)
TSIDINIT initializes tapes with BIM-EPIC VOL1 labels and enters them in the DSN Catalog
under the dataset name ‘***.VOLUME.DSN.**’. The tapes are then ready for use as
controlled scratch tapes.
Up to ten tape drives can be used in the initialization process.
TSIDINIT can be executed from JCL or from the operator console. If it is executed from the
console, the operator is queried for all processing information.
To execute from the console, enter:
EXEC TSIDINIT
after any VSE ‘// PAUSE’ statement.
[// UPSI xxxx]
// EXEC TSIDINIT [,PARM='CONSOLE']
or
// EXEC TSIDINIT [,PARM='ACL=aclname[,COUNT=nnnnn]']
cuu statement
volser statements
/*
To specify... Use UPSI setting...
Sequential initialization
1xxx
Random initialization
0xxx
Forced initialization
x1xx
Scratch tape reinitialization
xxx1
Inclusion of the CUU statement
xx1x
Use an ACL for Initialization
xx101
When more than one tape is to be initialized, you can specify each tape's volume serial number
in individual control statements, and the statements can be placed in any order. This is
referred to as random initialization. You can also specify the starting volume serial number,
and TSIDINIT will initialize successive tapes in ascending volume serial number sequence.
This is referred to as sequential initialization. In sequential initialization, TSIDINIT
continues to initialize tapes until the operator replies STOP to the mount message.
Description
JCL Requirements
UPSI Values
Types of
Initialization
Vista de pagina 366
1 2 ... 362 363 364 365 366 367 368 369 370 371 372 ... 488 489

Comentarios a estos manuales

Sin comentarios