CBSBATCH COBPARE COPYFILE ERASE FORBAT LISTDS LISTFILE BOYEFILE PRINT PUNCH QUERY READCARD SET STATE TAPE TAPPDS TYPE UPDATE 1 complete description of these and other commands and their usage is
contained in the YB/J70 £!§ and the !Dg Reference. DASD Dump Restore (DDR) Service Program and
How To Use It Use the D1SD Dump Restore (DDR) program to dump, restore, copy, or print YB/370 user minidisks. The DDR program may run as a standalone program, or under CBS via the DDR co.mand. The DDR program has five functions:
1. Dumps part or all of the data from a D1SD device to tape.
2. Transfers data from tapes created by the DDR dump function to a
direct access device. The direct access device must be of the same type as that which originally contained the data.
3. Copies data fro. one device to another of the same type. Data may be reordered, by cylinder, when copied from disk to disk. In order
to copy one tape to another, the original tape must have been
created by the DDR DUftP function.
q. Prints selected parts of DASD and tape records in hexadecimal an')
EBCDIC on the virtual printer.
5. Displays selected parts of DASD and tape records in hexadecimal ana EBCDIC on the terminal. To generate the YB/370 starter system from the distribution tape, th, standalone RESTORE function Jitistbe used. IBYOKIBG DDR UNDER CftS The format of the DDR co •• and is: r ,
DDR [ fn ft I fml ] r ,
fn ft Ifal 1* I L .. I! I L .t is the identification of the file containing the control statements for the DDR program. If no file
identification is provided, the DDR program attempts to
obtain control statements from the console. The filemode defaults to an asterisk (*) if a value is not provided.
158 Yft/370 Operator's Guide
Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 If you use the CMS DDR command, CMS ignore3 the SYSPRINT control
statement and directs the output to the CMS printer OOE. INVOKING DDR AS A STANDALONE PROGRAM To use DDR as a standalone program, the operator should IPL it from a
real or virtual IPL device as he would any other standalone program.
Then indicate where the DDR program is to obtain its control statements
by responding to prompting messages at the console.
1. Be aware that DDR when run as a standalone program has only the
most elementary error recovery support. However, when DDR is
invoked in CMS, in a virtual machine environment, the I/O operation
is performed by CP which has better error recovery facilities.
2. When running standalone, DDR will search for a console at address 009 or 01F. If these consoles are not operational, the program
will enter a wait state, waiting for an interrupt to identify the
console. If any nonconsole-type device is physically connected to
address 009 or 01F, it must be made nonoperational or the results
will be unpredictable. 3. The standalone DDR utility not support cylinder faults for MSS virtual volumes when performing the DUMP or COpy functions.
DDR CONTROL STATEMENTS DDR control statements describe the intended processing and the needed I/O devices. I/O definition statements must be specified first.
All control statements may be entered from either the console or the
card reader. Only columns 1 to 71 are inspected by the program. All
data after the last operand in a statement is ignored. An output tape
must have the DASD cylinder header records in sequences;
therefore, the extents must be entered in sequence by cylinder. Only one type of function --dump, restore, or copy --may be performed in
one execution, but up to 20 statements describing cylinder extents may
be entered. The function statements are delimited by (preceded by) an INPUT and OUTPUT statement. If additional functions are to be performed, the sequence of control cards must be repeated. If you do
not use INPUT or OUTPUT control statements to separate the functions you
specify when the input is read from a card reader or CMS file, an error
message (DMKDDR702E) is displayed. However, the remainder of the input
stream will be checked for proper syntax, but no further DDR operations
will be performed. Only those I/O devices defined by the INPUT statement and the OUTPUT statement must be redefined in subsequent
steps. The SYSPRINT I/O definition remains the same.
To return to eMS, enter a null line (carriage return) in response to
the prompting message (ENTER:). To return directly to CP, key in .CP. The PRINT and TYPE statements work differently from other DDR control
statements in that they operate on only one data extent at a time and it
is not necessary to respecify the INPUT statement ahead of each PRINT or TYPE statement. If the input is from a tape created by the dump
function, the tape must be positioned at the header record for each
step. The PRINT and TYPE statements have an implied output of either
the console (TYPE) or system printer (PRINT), so no OUTPUT statement is
required.
section 4. VM/370 Service Programs 159
Previous Page Next Page