page of. GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 Note: The IBCDASDI program can only assign alternate tracks for real 3330/3340 volumes when they are specified by the GETALT statement. Even
with the GETALT statement, the IBCDASDI program cannot assign alternate
tracks for a 3330/3340/3350 minidisk because CP prevents a virtual
machine from writing a home address record on these devices (effectively
treating the write as a No-OP) unless the device is dedicated to that
virtual machine. Defective tracks are flagged and alternate tracks are
assigned when the 3330/3340/3350 storage volumes are initialized at the
factory. An IBCDASDI job that initializes a 3330 performs the Quick
DASDI function, which reads alternate tracks, decrementing by 1 the
total number of alternates whenever an alternate is found defective or
assigned, writes a volume label and VTOC, and writes an IPLTEXT if
requested. No surface analysis is performed and no home address or
record 0 is written on the primary tracks. The BYPASS and FLAGTEST
options of the DADEF statement are ignored.
Disk packs for the 3340 are factory-shipped without flagged tracks
and alternate track assignments. IBCDASDI's "Quick DASDI" detects 3340 customer-generated alternate track assignments.
The IBCDASDI program cannot check to see if the 3330, 3340, or 3350 space to be initiated was previously formatted.
All utility control statements and operands must be preceded and
followed by one or more blanks.
The IBCDASDI proqram requires control statements as input. Data on a
control statement must not extend beyond column 71 except when a
continuation of the statement is required. Then the statement must be
broken off after a comma and a non-blank character must be placed in
column 72. Then the statement can be continued on the next line,
beginning in column 16 (and beginning only in column 16) The
statements must appear in the following sequence: 1. JOB Statement --indicates the beginning of the IBCDASDI job.
2. MSG Statement --defines the output device for operator messages.
3. DADEF Statement --defines the DASD device to be initialized.
4. VLD Statement labels the volume and allocates space for
additional labels.
5. VTOCD Statement controls the location of the
volume-table-of-contents (VTOC). 6. IPLTXT Statement (optional) --separates service program control
statements from IPL text statements.
7. END Statement --ends an IBCDASDI job or IPL text.
8. LASTCABD Statement (optional) --ends series of stacked IBCDASDI
jobs.
Section 4. VM/370 Service Programs 183
April 1; 1981
To initialize a 3350 in native mode after conversion from 3330 or 3340 compatability mode, the device must be attached (dedicated) to a virtual
machine and either IEHDASDP or IBCDASDI must be run. This is necessary
to allow alternate cylinders to be formatted and alternate tracks
assigned.
The JOB statement indicates the beginning of a job. The format of the JOB statement is:
r I( name] I JOB I[user information] L- ___________________________________________________________________________ The KSG statement defines an output device for operator messages. It
follows the JOB statement and precedes any function-defining state.ents
that are associated with the IBCDASDI program. The format of the KSG statement is: I I[ name 1 TODEV=xxxx TOADDR=CUu I KSG I TODEV=xxxx,TOADDR=cuu is the device type of the message output device (1403, 1052,2400,3400,3210, or 3211).
is the channel number (c) and unit number (uu) of the
message output device.
184 VM/370 Operator's Guide
Previous Page Next Page