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
Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 I/O DEFINITION STATEMENTS The I/O definition statements describe the tape, DASD, and printer
devices used while executing the DASD Dump Restore program.
An INPUT or OUTPUT statement describes each tape and DASD unit used.
The format of the INPUT/OUTPUT statement is: r----- , I INput I OUTput I I I I I I I cuu .r ,
type Ivolserl ( (options ••• ) ] I altapel L .J Qption§: r ,
r ,
r
, ISKip nn I I MOde 6250 I I REWind I ,SKip Q I I!Ode 1600 , IUNloadf L .J IlIOde 800 I ILEave I L .J L .J L---- ____________________________________________________________________ INPUT OUTPUT cuu
type
volser
indicates that the device described is an input device.
indicates that the device described is an output device. If the output device is a DASD device and DDR is running
under ClIS, the device is released using the C!S RELEASE command function and DDR processing continues.
is the unit address of the device.
is the device type (2314, 2319, 3330, 3330-11, 3340-35, 3340-70, 3350, 23-05-1, 2305-2, 2400, 2420, or 3420) (no
7-track support for any tape devices). Specify a 3410 as a 3420. Specify a 3340-10F as a 3340-10, and a 3333 as a 3330. specify a 3350 that is in 3330-1 or 3330-11 compatibility mode
as a 3330 or 3330-11. Specify a 3344 as a 3340-10, and
specify 3350 for a 3350 operating in native mode (as opposed
to compatibility mode).
Note: The DASD Dump Restore (DDR) program, executing in a vIrtual machine, uses I/O DIAGNOSE 20 to perform I/O operations on tape and DASD devices. DDR under ClIS requires
that the device type entered agree with the device type of the
real device as recognized by VlI/370. If there is a conflict
with device types, the following message is issued: DMKDDR708E INVALID OPTION However, if DDR executes standalone in a virtual machine, DDR
uses DIAGNOSE 20 to perform the I/O operation if the device
types agree. If the device types do not agree, error message D!KDDR708E is Issued. is the volume serial number of a DASD device. If the keyword "SCRATCH" is specified instead of the volume serial number, no
label verification is performed. 160 VM/370 Operator's Guide
Previous Page Next Page