IBM Series/1 User manual

- --
- --
GC34-0070-0
-- ---
- --
- ---
--- ---
- ---
- -.,-

- - -GC34-0070-0
~
---
C -
----
-
--
-
---
---
-~-
-
---
::)
--y-
(!)
~
Series/1
~
Stand-Alone Utilities
~
User's Guide
Program Nu mber 5719-SC2
~
C
~
~
~
~
~
~
a
-...J
~
~
c
~
CI)

... -
ii GC34-0070
First Edition (October 1976)
Changes are periodically made to the information herein; any such changes will be reported in
subsequent revisions or Technical Newsletters.
Text for this manual has been prepared with the IBM Magnetic Tape Selectric® Composer.
Requests for copies
of IBM publications should be made to your IBM representative or the IBM
branch office serving your locality.
A form for readers' comments is provided
at the back of this publication. If the form has been
removed, send your comments to
IBM Corporation, Systems Publications, Department 27T, P.O. Box
1328, Boca
Raton, Florida 33432. Comments become the property of IBM.
© Copyright International Business Machines Corporation 1976 (
'-

c
Preface v
Chapter 1.
Introduction 1-1
Hardware Overview 1-2
Using the Utility Programs 1-3
Making Corrections
at the Opera tor Station 1-4
Chapter 2. System Build and Verification
2-1
Automatic System Build 2-1
What This Program Does 2-1
How To Use It 2-1
The Output You Receive 2-2
How
To Handle Errors 2-2
Example 2-2
System Verification (SF) 2-3
What This Program Does 2-3
How
To Use It 2-3
The Output You Receive 2-3
How
To Handle Errors 2-3
Example 2-4
Chapter 3. Initial Program Load Programs 3-1
Diskette IPL Bootstrap (JP) 3-1
What This Utility Does 3-1
How To Create A Diskette 3-1
How To Use It 3-1
How To Handle Errors 3-2
Example 3-2
Disk
IPL Bootstrap/Loader (Lt, L2) 3-2
What This Utility Does 3-2
How
To Use It 3-2
The
Output You Receive 3-4
How
To Handle Errors 3-4
Chapter 4. Initialization Programs
4-1
Diskette Initialization (RI) 4-1
What This Utility Does 4-1
How To Use It 4-3
The Output You Receive 4-4
How
To Handle Errors 4-4
Example 4-4
Disk Initialization
(FI) 4-5
What This Utility Does 4-5
How
To Use It 4-5
The Output You Receive 4-6
How To Handle Errors 4-7
Examples 4-7
Chapter 5. Create and Delete Programs 5-1
Create Diskette HDRl (CH) 5-1
What This Utility Does 5-1
How To Use It 5-1
The Output You Receive 5-2
How To Handle Errors 5-4
Example 5-4
Delete
Diskette HDRl (DH) 5-5
What This Utility Does 5-5
How To
Use It 5-5
The Output You Receive 5-5
How
To Handle Errors 5-6
Example 5-6
Chapter 6.
Copy, Dump and Patch Programs 6-1
Diskette To Disk Copy (RF) 6-1
What This Utility Does 6-1
How To Use It 6-1
The Output You Receive 6-2
How To Handle Errors 6-2
Example 6-3
Disk
To Diskette Copy (FR) 6-4
What This Utility Does 6-4
How To
Use It 6-4
The
Output You Receive 6-5
How To Handle Errors 6-5
Example 6-6
Diskette
To Printer Dump (RD) 6-7
What This Utility Does 6-7
How To
Use It 6-7
The Output You Receive 6-7
How To Handle Errors 6-8
Example 6-8
Disk
To Printer Dump (FD) 6-9
What This Utility Does 6-9
How To
Use It 6-9
The
Output Yo u Receive 6-9
How to Handle Errors 6-10
Example 6-10
Diskette Patch (TR)
What This Utility Does
How To
Use It 6-11
6-11
6-11
The Output You Receive 6-12
How To Handle Errors 6-12
Example
6-1 3
Disk Patch
(TF) 6-14
What This Utility Does 6-14
HowToUseIt 6-14
The Output You Receive 6-15
How To Handle Errors 6-15
Example 6-16
Stand-Alone Storage
To Diskette Dump (Sl) 6-17
What This Utility Does 6-17
How To Create
The Diskette 6-17
How To
Use It 6-17
The Output You Receive 6-17
How To Handle Errors 6-18
Example 6-18
Storage To
Printer Dump (P 1) 6-19
What This Utility Does 6-19
How To Create
The Diskette 6-19
How To
Use It 6-19
The
Output You Receive 6-20
How To Handle Errors 6-21
Example 6-21
Contents
Contents iii

Appendix M. Messages M-I
Common Messages M-2
Unrecoverable I/O and System Messages M-4
CH-Create Diskette HDRI Messages M-9
DH-Delete Diskette HDRI Messages M-ll
FD-Disk to Printer Dump Messages M-12
FI-Disk Initialization Messages M-13
FR-Disk to Diskette Copy Messages M-16
IP-Bootstrap/Loader Disk Messages M-17
IP-Bootstrap/Loader Disk Wait Codes M-17
PI-Storage to Printer Dump Wait Codes M-18
RD-Diskette to Printer Dump Messages M-19
RF-Diskette to Disk Copy Messages M-20
RI-Diskette Initialization Messages M-21
SB-Automatic System Build M-23
SF-System Verification Messages M-24
SI-Storage to Diskette Dump Wait Codes M-25
TF-Disk Patch Messages M-26
TR-Diskette Patch Messages M-28
Index X-I
iv GC34-0070
, '\

c
Preface
The IBM Series/1 Stand-Alone Utilities Guide describes each of the utility programs.
It tells you:
• What the utility does
• How to use it
• The output you receive
• How to handle errors
This publication
is organized into six chapters, each containing groups of related utility
programs. Appendix M covers messages generated
by each program and the appropriate
action to be taken.
To effectively use the stand-alone utility programs,
you should be familiar with:
• Basic data processing concepts
• Assembler language coding
• Modular programming concepts
Prerequisite Publications
none
v Utilities

This page intentionally left blank.
vi GC34-0070
{ \
'-
f
,

c
c
Chapter 1. Introduction
This manual explains how to use each of the utilities in detail.
For each utility there
is an example of a typical session of using the utility. This
example shows your interaction with the
utility-the prompts it issues and the responses
you supply.
It also covers errors that may occur during the interaction and how you
handle them. The IBM-supplied names (module ID's) for these programs are shown
in
parentheses after the program name.
The Utilities are:
• Automatic System Build copies a portion of the complete system from a diskette to
the system disk.
• System Verification (SF) checks to find if all components of the system were copied
to the system disk and also prints the location
of the components on disk.
• Diskette IPL Bootstrap (IP) loads a program I cylinder in length (from location:
cylinder 1, head 0, sector 1) into the high end
of storage.
• Disk IPL Bootstrap/Loader (Ll, L2) loads programs from the disk into main storage.
• Diskette Initialization (RI) initializes the diskette, writing ID records and checking for
defective cylinders, and assigns alternate cylinders.
• Disk Initialization (FI) initializes the disk, verifying sector IDs and checking for
defective sectors, and assigns alternate sectors.
• Create Diskette HDRI (CH) creates a HDRI record for a diskette, using information
that you specify.
• Delete Diskette HDRI (DH) deletes the HDRI record for a specified diskette data file.
• Diskette to Disk Copy (RF) copies data from a specified diskette data file to a
specified disk data
fIle.
• Disk to Diskette Copy (FR) copies data from a specified disk data file to a specified
diskette data
fIle.
• Diskette to Printer Dump (RD) dumps the contents of a specified area on the diskette
to the printer.
• Disk to Pn·nter Dump (FD) dumps the contents of a specified area on the disk to the
printer.
• Diskette Patch (TR) applies a patch (which you enter at the operator station) to a
specified location on the diskette.
• Disk Patch (TF) applies a patch (which you enter at the operator station) to a
specified location on the disk.
• Storage to Diskette Dump (SI, S2) dumps the contents of main storage to the
diskette.
• Storage to Printer Dump (PI, P2) dumps the contents of main storage to the printer.
Introduction 1-1

HARDWARE OVERVIEW
1-2 GC34-0070
The following is a list of hardware products referred to in this manual. The list includes ( ~
the product name and the term used within this manual when referring to the product. ,
Product Name
IBM 4955 or 4953 Processor
IBM 4962 Disk Module
IBM 4964 Diskette Module
IBM 4974 Printer
Any device that can be used as
an operator station and is attached
to the system through the
ASCII teletypewriter adapter
Term Used Hereafter
processor
disk
diskette
printer
operator station
The minimum hardware configuration required
to run a Series/l program is:
• 1 processor with 32KB of storage
• 1 diskette unit
• 1 disk
• 1 printer
• 1 operator station
(

c
c
c
USING THE UTILITY PROGRAMS
All programs (except the Automatic System Build, Storage to Diskette Dump, and
Storage to Printer Dump) are IPLed from the disk.
All programs are on disk in a
storage-image format, preceded
by a header record designating the load point, entry
point, size
of the program, and maintenance information.
To invoke a program, set the IPL switch to primary (disk) and press the LOAD key on
the system console. Once the loader
is in main storage, it prints a message at the operator
station requesting the name or starting sector address
of the program to be loaded:
IPI00A EXEC=
You can enter either the 2-character name for the IBM-supplied programs (for example,
RI for diskette initialization) or the program's starting sector address. For any other
programs, you must enter the program's starting sector address. Sector addresses must be
specified in this format:
ccchss
where:
ccc the cylinder number
h the head number
ss the sector number
After the program
is loaded, it issues prompts at the operator station requesting you to
enter certain information needed by the program before it can begin processing. This
information
is covered in the chapters describing the individual utilities.
The utility prints an error message at the operator station and reissues the prompt
if (1)
the information you enter is syntactically incorrect or (2) if the utility encounters a
recoverable error. Each time a prompt or message
is printed at the operator station, it
ends with a carriage return. You must also end your entries with a carriage return.
If you are typing a line that is longer than 72 characters, there is an automatic carriage
return after you type the 72nd character.
In the Series/l programs, a contiguous, logically related collection
of data on a
single disk or diskette
is called a data fIle. Through the operator station, you can refer to
a data
fIle by specifying its device address, starting sector address, and ending sector
address. Enter the information in this format:
ddd,ccchss,ccchss
where:
ddd = the device address
ccchss,ccchss = the starting and ending sector addresses
of the data fIle
The device address are fixed as follows:
Device Address Device Type
000
001
002
003
operator station
printer
diskette
disk
The ranges
of the ccc, h, and ss values are:
cylinder (ccc)
Diskette-double-sided 0-74
Disk
Disk
-single-sided
0-74
0-302
head (h)
0-1
o
0-1
sector (ss)
1-26
1-26
0-59
Note. Cylinder 0 of the disk is reserved for the Bootstrap and Loader; cylinder 1 is
reserved for alternate sector assignments; cylinder 302 is reserved for customer engineer
use. On the diskette, track 0
is reserved for system use; tracks 75 and 76 are reserved as
al ternate tracks to replace tracks that become defective.
Introduction 1-3

Both the disk and diskette are supported in a cylinder mode. For example, the disk
sector that follows sector address 005059
is 005100, and the disk sector that follows
sector address 005159
is 006000. ( ~
For more detailed information on the disk and diskette, refer to the IBM 4962 Disk \. ;
Storage Unit Description, GA34-0024, and the IBM 4964 Diskette Input/Output Unit
Description, GA34-0023.
If a program creates or moves data files, it prints a message at the operator station
indicating the last sector written:
id099I LAST SECTOR WRITTEN =ccchss
Messages are a/ways printed on one device line. Some of the messages in this manual are
shown on two lines because
of the message length.
Making Corrections at the Operator Station
1-4 GC34-0070
If you should make typing errors while entering data at the operator station, you can
correct these errors in the following manner.
To correct one or more characters:
You meant to type
CO 10,50,100
Bu t you typed co 10,60
Now type ~ ~- 50,100
Type one left arrow (~) for each character you typed after the last co"ect character. Retype the
characters correctly and continue typing.
To correct an entire line:
You meant to type
CT 10,20,'ABC','DEF'
But you
typed
CT 10,200,'ABC','DEF'
Now type
t
Retype the line. An up arrow (t) causes a carriage return and you can correctly reenter your line.
Note. Ifyou want to interrupt the printing process at the operator station, hold down the
CTRL key, then press the A key.
(

c
c
Chapter 2. System Build and Verification
Automatic System Build (SB)
WHAT THIS PROGRAM DOES
HOW TO USE IT
The Automatic System Build program copies to disk the diskette shipped from IBM. A
copy
of this program resides on the diskette. The layout of the diskette is shown below.
ccchss
000001
000003
001001
DISKETTE
IPL/Bootstrap
Reserved
Auto-System Build
Disk IPL/Bootstrap
Disk Loader
System Verification
Diskette IPL/Bootstrap
Storage to Printer Dump (Phase A)
Storage to Printer Dump (Phase B)
Storage to Diskette Dump (Phase A)
Storage to Diskette Dump (Phase B)
Disk Initialization
Diskette Initialization
Create HDR1
Delete
HDRI
Diskette to Printer Dump
Disk to Printer Dump
Diskette to Disk Copy
Disk to Diskette Copy
Diskette Patch
Disk Patch
The loader loads the contents of the diskette to a predefined area of the disk. When the
diskette has been copied, the system
is built on disk.
(1) mount the diskette, as shipped from IBM,
(2) set the console IPL switch to alternate, and
(3) press the LOAD Key.
The hardware loads the bootstrap, which in turn loads the Automatic System Build
program. No further input
is necessary.
The program issues this message:
SBOOOI AUTOMATIC SYSTEM BUILD STARTED
System Build and Verification 2-1

Once the diskette is mounted, the program prints, from the VaLl label, the volume
identifier field in the following message:
SBIOOI DISKETTE VOLID=nnnnnn
where nnnnnn is the volume identifier for the diskette. It then copies, to a predefined
location on the disk, the contents
of the diskette. There is no operator input required to
build the system. Upon completion the program issues this message:
SBOOII AUTOMATIC SYSTEM BUILD UTILITY COMPLETED
THE OUTPUT YOU RECEIVE
HOW TO HANDLE ERRORS
EXAMPLE
2-2 GC34-0070
Output consists of a complete diskette copied onto the disk and the three preceding
messages.
If any errors occur while copying the diskette to disk, an appropriate I/O error
message
is printed at the operator station.
If an I/O error occurs, the program terminates after issuing an error message to the
operator station.
See Appendix Mfor a complete discussion of possible error codes.
The following
is an example of the automatic system build program. In this example, the
diskette mounted has VOLID=PID002.
1. Mount the IBM diskette.
2. Set console IPL switch to alternate.
3. Press the LOAD Key.
SBOOOI AUTOMATIC SYSTEM BUILD STARTED
SBIOOI DISKETTE VOLID=PID002 COPIED
SBOOlI AUTOMATIC SYSTEM BUILD
UTILITY COMPLETED
After the diskette is copied, your system will be built on disk.
Now use the System Verification program
to insure that the components have been
correctly copied to the system disk.
f ~
\
t
(

c
c
c
System Verification (SF)
WHAT THIS PROGRAM DOES
HOW TO USE IT
Mter you load the program, it ensures that your system is built properly by
cross-checking each module
on your IPLed system disk against a table containing
expected module names.
If any modules are missing, a message is printed indicating which
specific program
is not on the disk system.
Press the LOAD key. After the EXEC= message is printed at the operator station, enter
either SF or the starting sector address (ccchss)
of the program. When it is loaded, no
further input
is required. The program performs the verification, using an internal table of
module names expected to be on the disk.
THE OUTPUT YOU RECEIVE
HOW TO HANDLE ERRORS
If your IPLed system disk is an incomplete system, an error message is printed at the
operator station indicating the name
of the module that was not found. No further
verification processing
is possible.
The system map name contains header record data for all modules encountered before
the error occured.
If your system is correct, a system map containing header record data
for each load module
is printed, and a message verifying that the system was correctly
built
is printed at the operator station.
The system map
is printed in the following format:
Program Name ccchss Entry Point Load Point Module Length
User Data
xx ccchss xxxx
yyyy zzzz aaaaa
•
•
•
where:
the 2-character component
ID xx
ccchss
xxxx
the address of header record on the disk
yyyy
zzzz
aaaaaa
the entry point
of the module in ccchss format
the load point
of the module in ccchss format
the length
of the module in hexadecimal
the description
of the 2-character component ID
If the program encounters any of the following errors, it issues a message at the operator
station:
• Invalid header ID
• Module missing on system disk
• Module name missing in the system table
• Incorrect header chain
If an unrecoverable error occurs, the program abnormally terminates. To reinvoke the
program, you must reIPL. Unrecoverable errors are:
• Operator Station I/O error
• Disk I/O error
System Build and Verification 2-3

EXAMPLE
2-4 GC34-0070
The following is an example of the System Verification program.
Operator Station Printout Explanation
IPI 00A EXEC= The loader issues a request for
the address of the
program
to be loaded.
SF You enter the name of the System Verification
program.
SFOOOI SYSTEM VERIFICATION STARTED The System Verification program has started.
xx ccchss xxxxxx yyyyyy zzzzzz The system map
is printed at the printer.
SF200I SYSTEM CORRECTLY BUILT There has been a successful system verification.
SFOOII SYSTEM VERIFICATION COMPLETE The program
is finished.
(
"

c
c
c
Chapter 3. Initial Program Load Programs
Diskette IPL Bootstrap (IP)
WHAT THIS UTILITY DOES When you press the LOAD key on the console, the hardware loads the bootstrap into
main storage from the diskette. The bootstrap, in
tum, loads the contents of cylinder 1,
head 0, from the IPLed diskette. When the bootstrap is finished, register 7 contains the
device address
of the diskette you IPLed from. The program is loaded into the high end
of storage and then given control.
HOW TO CREATE A DISKETTE
HOW TO USE IT
You must create a special diskette for the diskette IPL bootstrap. See example below.
Locate the ccchss
of the program IP on the system verification listing. Using the disk to
diskette copy program, copy the program IP to the diskette. You must start the copy 1
disk sector beyond the beginning
of the program to remove the header record. IP must be
placed on the diskette at cylinder 0, head 0, sectors 1 and 2.
You invoke this utility by setting the IPL switch to alternate (diskette) and then pressing
the LOAD key.
Note. The bootstrap must be on cylinder 0, head 0, sectors 1 and 2
of the diskette.
Initial Program Load Programs 3-1

HOW TO HANDLE ERRORS
EXAMPLE
3-2 GC34-0070
If a"(jisk~tw: l/fJ ! eittfi-t)todb!firs~\l\lllilluW£it~Yt'n~ fu1iWcoWr~af( itO dR~koih%rtJH8}Pit and
tern:lifl'~le~~' l,() PIluler [ltnnp) arc IPLed from the disk. All programs are on disk in a ('
ni;lt, :1 header record designating the load p:)inL entry \. i
P!(lP':I!I1. ~lIid maintenance information.
SCi the I PL switch to primary (disk) and press the lOAD key on
The following is an example 1J~f~tadlli~it'l1ell~~~flrel1§HotSlifa~tcm~lffiSkgite~agc at the ,npcratlll
. :;r~:d::!g St'C!(lr address uj the program to he l(ladcll
Operator StatiOniPrintout Explanation
IPI DOA, EXEC::: I.' r :()j'hedolaal!ertb!ruH{~teqqt~ ifirl1jlm~r26r( tba:t(is:.a I i pit>.
': I rlt dr tp~be::,-~~~~~ta4mtHlg sel.~(ur address. hH any '1 Iw!
FR' Tfi,.'l tilt plugs; n~'Outh:lltl6l!l1llte~"tlr\trdfdtie(f:}iskSw.:Dlske<1ldle~ llllSI. Iw
FROOll DISK TO DISKETTE COPY
STARTED
FRI00A FROM DATA AREA=
003,002126,002126
FR200A TO DATA AREA;::
002,000001,000002
FR099I LAST SECTOR WRITTEN IS
000002
FRO(}11 DISK TO DISKETTE CQP:Y,
COMPLETED
FRI00A FROM DATA AREA:;:" ;',
utility.
The Disk to Diskette Copy utility has started.
The utility prompts for the source data file infor-
mation.
You enter the device address and the starting
sector address +1 of the program IP. This re-
moves
the header record from the diskette'bOot~
strap.. ~Only ,Qne ,d~sk,secto( i~t ~P~91: l':
The utility ~ssue8' this Illrompt flOr the destination
d~til file informatiqn.,,: ,,,.
Youenoox: the devie¢ address
and,tlte s1Ja~tiElgi "I'
. ~,i~ec~pr!~4A{t!~~,.wp,e~~, ~h~,qpo~~tfjl,~ rn~ti~f1&~4eSl:1 1i ' )
,?~ )c.Y.H~d~r,81 ~eap. R,:.~s~Srms} ;(ln~l~'~~'" 1('( i till.
Tb~ I,l,t~lity prints th.e,~dfffS~,of~~crJ~s~;se~~qf',
written on the diskette .
• ,1, ll'l
: i ~hH.~!i:~il ~ 'q~(.'l:l!nr ~l:l~!{\J!,\(nj (';jl~ i~~·II-f ~
: ;I:t"~, ,\.l~ilitx :RJ;9mpt~ ~Dj( a ~~ ~Q~t::~e :~Ma ,mt(l i If i: ,\' ! i
for the next copy operation. '
,;,
0·)
Intrn(lllcli')11 l·:~

c
c
c
Disk IPL Bootstrap/Loader (Ll, L2)
WHAT THIS UTILITY DOES
HOW TO USE IT
When you press the LOAD key on the console, the hardware loads the bootstrap into
main storage from the disk. The bootstrap then loads and gives control to the loader.
Once the loader is in main storage, it issues a prompt through the operator station
requesting
the two character IBM-supplied name or the ccchss location of the program
you want loaded and given control on level
0. The loader brings into storage the program
you request and passes control to it.
Note. When the requested program receives control, these conditions exist:
• On levels 1, 2, and 3 the LSR, IAR, and all general-purpose registers contain zeros.
• On level 0:
Register 3 contains the device addresses of the operator station in the first byte and
the printer in the second byte.
Register 4 contains the size
of storage:
7FFFis32K
BFFF is 48K
FFFF is 64K.
Register 5 contains the device address
of the IPLed device in the low-order byte.
Register 6 contains the value
of the cylinder that contains the header record of the
requested program.
Register 7 contains the values for the head and sector
that contain the header
record
of the requested program.
• In the LSR, the supervisor state bit for level ° is on.
You invoke this utility by pressing the LOAD key.
Note. The bootstrap must be
on cylinder 0, head 0, sector ° of the disk. The loader
resides
on cylinder 0, head 0, sectors 1-13.
Once the loader is in control, you can specify which program you want loaded for
execution. The loader prints this prompt
at the operator station:
IPIOOA EXEC=
All IBM-supplied programs can be loaded by name. All user programs are loaded by disk
address.
If you load a program by name, enter:
program name
where:
program name is a 2-character IBM-supplied name for the program.
If you enter the program's location, it must be in this form:
ccchss
where:
ccc a 3-digit decimal cylinder number in the range
002-301
h the head number, either °or 1
ss a 2-digit decimal sector number in the range 00-59
Initial Program Load Programs 3-3

The loader assumes that the program you requested is on the same device you IPLed
from. There is. a restriction on how big this program can be. The program's maximum size
is the size of storage minus 2K bytes. The last 2K of storage is reserved for the loader, but ( ;
may be used after control is passed to the program.
If the information you enter is syntactically incorrect, an error message is printed at the
operator station and the prompt
is repeated. If the information you enter is syntactically
correct, the loader checks your program's header record to determine:
• If it is a valid header
• The load point of the program
• The entry point of the program
• If the program can fit into the available storage
If an invalid header is found, the prompt is reissued. If the information is correct, your
program is given control.
THE OUTPUT YOU RECEIVE
HOW TO HANDLE ERRORS
3-4 GC34-0070
The only output from this utility is the prompt IPI DDA EXEC= and possibly some error
messages.
If the utility encounters a recoverable error, it prints an error message and reissues the
prompt. Recoverable errors are:
• Invalid sector address-address is out of range for the device, contains non-decimal
digits, or
is the incorrect length
• Invalid header record
• Invalid program name
• Program too large for storage
If the utility encounters an unrecoverable error, it issues a LEX with a code in the
operand
of the instruction. To reinvoke the utility, you must reIPL. Unrecoverable errors
are:
• I/O error to the operator station
• I/O error to disk

c
c
c
Chapter 4. Initialization Programs
Diskette Initialization (RI)
WHAT THIS UTILITY DOES
This utility initializes either a single-side or double-sided diskette in a diskette drive. The
initialization consists
of three steps:
• The utility formats each track into I28-byte sectors.
• The utility analyzes each track. If it finds a defective sector, it considers that entire
cylinder to be defective, and assigns an alternate cylinder.
If more than two cylinders
are defective, the diskette
is flagged as unusable.
• On cylinder 0, head 0, the utility writes the VaLID (volume identification), one
HDRI (header 1) describing cylinders
1-74 as I data set, deletes unused HDR1s, and
the ERRMAP (error map).
See the following pages for the format of the VaLl and
HDRI field. The contents
of ERRMAP varies based on the results of the surface
analysis done on the diskette, and
is therefore not initialized to a standard format.
If you try to initialize a diskette that has been previously initialized, you destroy all
data on the diskette. Reinitialization rewrites the complete diskette surface.
VaLl LABEL FORMAT
Character Initialization
Position Field Name Length Value
000 Label Identifier 3 'VOL'
003 Label Number 1 1
004 Volume Identifier 6 user id
010 Accessibility 1 space
011 Reserved 26 spaces
037 Owner ID 14 spaces
051 Reserved 20 spaces
071 Volume Surface Indicator 1 space
(two-sided disk only)
074 Reserved 3 space
075 Physical Record Length 1 space
076 Physical Record Sequence Code 2 spaces
078 Reserved 1 space
079 Label-Standard Version 1
'w'
Initialization Programs 4-1