IBM 3480 User Reference
-_
----
::
=-=
--
.:.
~
-.--'-
.. -
==
---
.:
':'
:.
IBM
User's
GC35-0099-3
3480
Reference
Magnetic
Tape
Subsystem
Storage
Subsystem
Library
Fourth
This
is a
Edition
revision
(November
of
and
makes
1987)
obsolete GC35-0099-2.
Changes
or
additions
by a vertical
References
services do
all
countries
licensed
imply
program
that
in
not
only
functionally
Publications
Requests
for
representative
A form for
reader's
publication.
addressed
Department
distribute
appropriate
©
Copyright
to
61C, Tucson, Arizona, U.S.A. 85744. IBM
whatever
without
1986, 1987
to
line
to
the
left
this
publication
imply
that
in
which
IBM's
equivalent
are
IBM
or
IBM operates.
in
this
licensed
program
not
stocked
publications
to
the
IBM
comments is provided
If
the
form
IBM
Corporation,
information
incurring
International
the
text
or
of
the
to
IBM products, programs,
IBM
intends
publication
program
may
at
the
should
branch
has
been
General
you
any
Business
illustrations
will
change.
to
make
these
Any
reference
is
not
be
intended
may
used
be used.
instead.
to
address given below.
be
made
to
your
office
serving
at
the
your
back
removed, comments
Products
supply
obligation
Machines
Division,
in
any
way
to
you.
Corporation
be
indicated
or
available
to
an
IBM
state
Any
IBM
locality.
of
this
may
be
may
it
believes
or
use
1984,
in
or
Preface
Organization
This
manual
Magnetic
commands,
Publications."
This
•
•
•
•
Tape
or
manual
"Chapter
Tape
Subsystem
"Chapter
standard
"Chapter
that
are
needed
changes,
"Chapter
NOTE, POINT,
macro
gives
programmers
Subsystem.
functions,
contains
1.
2.
data
3.
and
4.
the
Introduction,"
and
Tape
Characteristics,"
set
label
Modifying
to
modifications
Controlling
and
For
consult
following:
the
software
Existing
use
the
3480
the
DEVTYPE
information
complete
the
other
gives
an
requirements
Code," describes
including
to
JFCB
I/O Device," describes
macros,
about
information
manuals
overview
describes
DCB
as
well as
using
ofthe
the
parameters,
about
listed
for
the
format
the
the
the
the
IBM
3480
specific macros,
in
"Related
IBM
3480
Magnetic
3480
of
an
IBM
changes
changes
new
to
JCL
SYNCDEV
code
to
the
•
"Chapter
that
•
"Chapter
changes
•
"Chapter
to
use
information
•
"Chapter
restrictions
• "Appendix
control
• "Appendix B.
completion
taking a checkpoint.
5.
allows messages
6.
for
7.
the
3480 for
8.
A.
block
codes for
Displaying
Managing
DFHSM
Recording
Restrictions
to
DFSORT
Data
fields
Checkpoint/Restart
Messages," describes
to
be
displayed
and
when
using
Error
the
IMS/VS log
to
when
Control
the
IBM
to
the
Controlling
the
or
Statistical
Using
using
Block Symbolic
3480
Data
3480
tape
and
Sorting
the
3480
Codes,"
Magnetic
the
new
MSGDISP
operator
Sets,"
Information,"
error
Applications,"
Field
shows
Tape
describes
and
statistical
Names,"
the
return
Subsystem
macro
the
describes
describes
describes
and
when
Preface 111
how
the
the
Prerequisite
Knowledge
To
use
this
book
management
procedures.
effectively,
you
should
already
understand
data
Related
IBM 3480
Publications
You
below.
Magnetic
Tape
•
IBM
•
IBM
GC35-0098
•
IBM
Status
•
IBM
• Care
•
IBM
for System/360, System/370,
GC22-7064
may
want
to
reference
information
Subsystem
3480
Magnetic Tape Subsystem Introduction, GA32-0041
3480
Magnetic Tape Subsystem Planning
3480
Magnetic Tape Subsystem Reference: Channel Commands,
and
Sense Bytes,
3480
Magnetic Tape Subsystem Operator's Guide, GA32-0066
and
Handling
Input/Output Equipment: Installation
of
the
and
Error Recovery Procedures, GA32-0042
IBM
Magnetic Tape Cartridge, GA32-0047
and
4300
presented
Manual-Physical
Processors,
in
the
publications
and
Migration Guide,
TNL
GN22-2317
listed
Planning
to
MVS/Extended
• Tape and Cartridge Requirements for the
GA32-0048.
Architecture
•
MVS/Extended
•
MVS/Extended
•
MVS/Extended
•
MVS/Extended
Reference,
•
MVS/Extended
Administration,
•
MVS/Extended
Volumes 1
•
MVS/Extended
Architecture Checkpoint/Restart User's Guide, GC26-4139
Architecture System-Data Administration, GC26-4149
Architecture Data Administration Guide, GC26-4140
Architecture Data Administration: Macro Instruction
GC26-4141
Architecture Magnetic Tape Labels
GC26-4145
Architecture Message Library: System Messages,
and
2,
GC28-1376
Architecture Message Library: System Codes, GC28-1157
and
IBM
GC28-1377
3480
Tape Drives,
and
File Structure
IV
IBM 3480
Magnetic
Tape Subsystem
User's
Reference
•
MVS/Extended
MVS/System
Routing
•
MVS/Extended
•
MVS/Extended
and
Information,
•
MVS/Extended
JES2,
5665-291, GC28-1143
•
MVS/Extended
LIC
MVS/System
Architecture,
Product-JES2
Descriptor Codes, GC28-1194
Architecture Installation: System Generation, GC26-4148
Architecture Data Facility Product: General
GC26-4142
Architecture Conversion Notebook:
PROG 5740-XC6;
Architecture,
Product-JES2
Job Control Language, GC28-1148
•
MVS/Extended
Architecture
5740-XC6, Initialization
•
MVS/Extended
MVS/System
Supervisor
Architecture,
Product Version
Services and Macro Instructions, GC28-1154
MVS/System
Version 2,
MVS/System
MVS/System
Version
MVS/System
and
Tuning, GC28-1149
MVS/System
2-JES2,
Product-JES3
LIC
PROG 5665-291, 5740-XC6,
MVS/System
Product
JES3,
Product-JES3
2,
LIC
PROG 5665-291, 5740-XC6,
Product Version 2 5665-291
Product Version
LIC
PROG 5665-291, 5740-XC6,
Version
LIC
PROG
Version
2-JES3
2,
Product
2,
•
MVS/Extended
MVS/System
System
GC28-1151
•
MVS/Extended
Macros and Facilities,
Architecture
Product-JES2
Architecture,
Modifications, GC28-1152
•
MVS/Extended
MVS/System
Architecture,
Product-JES2
Management Facility, GC28-1153
•
MVS/Extended
5740-XC6 Operations:
•
MVS/Extended
PROG
•
MVS/Extended
LIC
•
MVS/Extended
5740-XC6, Initialization
PROG
Version 2,
Architecture,
JES2
Architecture,
Architecture,
5665-291, Operations:
Architecture System,
LIC
PROG 5665-291, Initialization
MVS/System
Version 2,
Volumes 1 and
LIC
PROG
MVS/System
Version
MVS/System
Product-JES3
LIC
PROG 5665-291, 5740-XC6,
2,
GC28-1150
5665-291, 5740-XC6, System
Product-JES3
2,
5665-291, 5740-XC6, System
Product-JES2
Commands, SC23-0064
MVS/System
and
Tuning, SC23-0065
MVS/System
JES3
Product
Product-JES3
Commands, SC23-0063
MVS/System
and
JES2
Version
and
Version
Version
Version 2,
Version
2,
2,
2,
2,
Product-JES3
Tuning, SC23-0059
LIC
•
MVS/Extended
Version 2,
Architecture Debugging,
MVS/System
Product-JES2
MVS/System
Product-JES3
Version 2,5665-291, 5740-XC6,
Preface
V
MVS/370
Handbook,
LC28-1l67
•
MVS/370
•
MVS/370
GC26-4063
•
MVS/370
Instructions,
Volumes 1 through
and
LC28-1l68.
5, LC28-1l64,1 LC28-1l65, LC28-1l66,
Data Facility Product, 5665-295, Checkpoint/Restart, GC26-4054
Data Facility Product, 5665-295, System Generation Reference,
Data Facility Product, 5665-295, Data Management Macro
GC26-4057
• MVS/370 Data Management Services, Data Facility Product
GC26-4058
•
MVS/370
•
MVS/370
•
MVS/370
GC28-1374
•
OS/VS
•
OS/VS
Data Facility Product, 5665-295, Data Management, GC26-4056
Magnetic Tape Labels
Message Library: System Messages,
and
GC28-1375
and
File Structure, 5665-295, GC26-4064
Volumes
1
and
Message Library: System Codes, GC38-1008
Message Library:
VS2
Routing
and
Descriptor Codes, GC38·1102
• MVS/370 Installation: System Generation, GC26-4166
•
MVS
JCL
MVS/System
Product-JES3
•
MVS/370
•
OS/VS2
MVS/System
3, GC28-1047, GC28-1048,
Data Facility Product: General Information, GC26-4160
System Programming Library: Debugging Handbook,
Products,
Release 3.1,
Product-JES2
LIC
PROG 5740-XYS,
LIC
PROG
and
5740-XYN,
GC28-1049
Release 3.3,
-XYN,
-XYS,
MVS/System
GC28-1300
Volumes 1 through
5665-295,
2,
VI
IBM 3480
Magnetic
• OS/
• OS/
VS2
VS2
Guide, GC28-0681
•
OS/VS2
•
OS/VS2
Facilities,
All five volumes
Tape
Subsystem
MVS
Supervisor Services
MVS
System Programming Library: Initialization
MVS
System Programming Library: Supervisor, GC28-0628
MVS
System Programming Library: System Management
GC28-1030.
may
be
ordered
User's
Reference
and
under
Macro Instructions, GC28-0683
one
order
number,
LBOF-I015.
and
Tuning
VMjSP
and
VMjHPO
VSEjSP
Other
Related
• Virtual Machine/System Product Planning Guide
SC19-6201
• Virtual Machine/System Product High Performance Option Planning
Guide
•
IBM
Support Extensions, Version
and
Reference, SC19-6223.
Virtual Storage Extended/System Package Hardware
2 Release
1,
SC33-6184.
and
Reference,
Publications
•
OS/VS
SC33-4035
• Data Facility Hierarchical Storage Manager: Version 2 Release 3.0
Installation
• Data Facility Hierarchical Storage Manager: Version 2 Release 3.0
System
• Data Facility Hierarchical Storage Manager: Version 2 Release 3.0
System
Sort/Merge Programmer's Guide Program Product 5740-SM1,
and
Customization Guide, SH35-0084
Programmer's Guide, SH35-0085
Programmer's Reference Guide, SH35-0083
and
Software
•
OS/VS2
Program,
GC28-1027
• Environmental Recording Editing and Printing (EREP) Program,
GC28-1178
• Data Facility/Data Set Services,
Reference, SC26-3949
•
IBM
for
•
IBM
MVS
and
Stand-Alone Versions: Input/Output Configuration
LIC
PROG 5740-XYN,
Input/Output Equipment: Installation
System/360, System/370, and
System/370 Installation Manual: Physical Planning, GC22-7004.
-XYS,
LIC
4300
User's Guide and Reference,
PROG 5740-UT3, User's Guide
Manual-Physical
Processors, GC22-7064
Planning
and
Preface
Vll
Contents
Chapter
IBM
Conventions
Chapter
Changed
Chapter
Selecting
DCB
Coding
Constructing a Data
Specifying
Modifying
Setting
Example
MVS Block
User
EXCP
User
Performance
IEBGENER
Chapter
Controlling
How
Retrieving
Performing
Comparing
Examples
NOTE-Provide
Completion Codes from NOTE
POINT
Completion Codes from
Controlling
Example
SYNCDEV-Synchronize
SYNCDEV-List
SYNCDEV-Execute
Completion Codes from SYNCDEV
Obtaining
1.
3480
2.
Format
3.
Parameters
Search
Exits
Routines
Programs
4.
the
-Moving
BSAM)
The
IBM
3480
Magnetic
Magnetic
Used
Tape
Modifying
Data
the
JCL
the
the
................................................
of
Count
Options for
Controlling
High-Speed
Physical
the
of
...............................................
Data
of
I/O Device
Tape
Subsystem
...........................................
Characteristics
of
IBM
Standard
Existing
Set
Options
..........................................
Block Size
Options
Job
File
Header
How
..............................................
Storage
the
Conventional
How
How
Label
to
Checking
..........................................
..........................................
Block
BLOCKID
High-Speed
to
Relative
Tape
Synchronization
to
Form
Characteristics
....................................
and
Logical Record
Control
......................................
Control
Block
Code
OPEN(J)
..................................
IEBGENER
Requirements
the
110
Search
Identifier
..................................
Search
Search
Code NOTE
Position
to
a Relative Block
POINT
Code SYNCDEV
Device
....................................
Form
Tape
Subsystem
Operating
..........................
Data
Set
Code
in
Block
Block (JFCB)
(NOTE/POINT)
.................................
...........................
ID
in
the
...........................
...........................
...........................
Device
Works
...........................
and
High-Speed
and
POINT
(BPAM
..............................
..............................
(SYNCDEV)
.............................
...........................
(DEVTYPE)
Mode
Label
2 (HDR2/EOV2/EOF2) 5
MVS
Systems
Length
.....................
JFCB
..................•..
.........................
for High·Speed
...................
......................
...................
and
BSAM)
Position
...................
.................
...........
...............
Operands
Search
............
(BP
AM
..........
........
..........
and
1
2
3
5
7
7
7
8
8
9
9
10
11
12
13
13
14
15
15
17
17
17
17
18
19
20
22
23
23
25
25
27
28
29
30
31
32
Contents
IX
Chapter
Displaying a Message from
Example
MSGDISP-Displaying a Ready Message
,MSGDISP-Displaying a Ready Message
5.
Displaying
of
How
Messages
any
to
Code MSGDISP RDY
(MSGDISP)
User
Program
List
•••.•...••.•••.•
(MSGDISP RDY)
......................
......................
Form
MSGDISP-Displaying a Ready Message Execute Form
Displaying a Message from Authorized Programs
MSGDISP-Displaying a Mount
MSGDISP-Displaying
MSGDISP-Displaying
MSGDISP-Resetting
MSGDISP-Providing
Return
Codes from MSGDISP
Modifying MSGDISP for
a Verify Message
a Demount Message
the
Message Display
the
Other
Message
Full
Range
of
Display Options
...............................
Languages
.......................
..................
......................
......................
....................
.....................
...........
...........
..........
......
l...
33
33
34
35
36
37
38
39
42
46
50
53
57
58
Chapter
Specifying Esoteric
Recycling Tapes
Establishing
(SETSYS)
Specifying
Specifying
Specifying Esoteric Tape
6.
Managing
or
Changing
...............................................
the
(DENSITY)
the
(UNITNAME)
and
Controlling
Unit
Names
...............................
...........................................
the
Values of DFHSM Control
Tape Density When Allocating
............................................
Type
of
Unit
for
Mounting a Scratch
..........................................
Unit
Name
(USERUNITTABLEI NOUSERUNITTABLE)
Adding
Chapter
Using
Using
Using IMS/VS Logging
Chapter
SORTWKnn
SORTOUT
or
Changing
Specifying
Specifying
7.
EREP
Error
8.
DD
the
Volumes Managed by DFHSM (ADDVOL)
the
Type
of
Device (UNIT)
the
Tape Density (DENSITY)
Recording
Reports
Error
or
Statistical
........................................
Recovery Procedures (ERP)
......................................
Restrictions
DD
statement
Statement
to
Using
Sorting
...................................
....................................
Data
Sets
Scratch
to
DFHSM
..................
........................
......................
Information
........................
Applications
.•....••.•••.
Parameters
Tapes
Tape
.......•.
(DFSORT)
61
61
61
62
62
62
63
64
64
65
67
67
67
67
69
69
69
x IBM 3480
Magnetic
Appendix
Magnetic Tape Interface
Appendix
Return
A.
Data
B.
Programming
Code from
Control
.....................................
the
CHKPT Macro
Block
ABEND Completion Codes Issued by
ABEND
Glossary
Index
Tape Subsystem
Return
Codes
......................................
.•..•.••.•.•••....•.........•..............•
...............................................
User's
Reference
Symbolic
Messages
Instruction
Checkpoint/Restart
and
Field
Codes
for
Names
•.•..••.•..••
the
3480
for
........
........
the
3480
..
71
72
73
73
73
73
75
79
Figures
1.
JFCB
Layout
2.
Sample Message Display
3.
Description
of
.........................................
Language
CSECT IGXMSGOI
Modification
.........................
..............
11
58
59
Figures
Xl
Summary
of
Amendments
IBM
Release
Release
Release
3480
Magnetic
GC35-0099-3,
GC35-0099-2,
GC35-0099-1,
Tape
July
This
edition.
January
This
Model
There
previous
July
This
information
1987
edition
edition
Bll
are
edition.
1986
edition
Subsystem
includes
1987
adds
information
Tape
Drive.
also
miscellaneous
incorporates
on
the
changes
Technical
Automatic
to
correct
on
the
changes
Newsletter
Cartridge
User's
errors
3480 Model
to
correct
Loader
Reference
or
omissions
All
Control
errors
number
Feature.
or
omissions
GN35-0319
in
Unit
the
previous
and
in
the
and
adds
Summary
of
Amendments
XUl
Chapter
1.
The
IBM
The
IBM 3480
Model
tape
unit
Communications
allow
Cartridge
premounted
cartridges,
channel
channels.
The
subsystem
second.
linear
The
control
between
delays
start
data
to
is
ready
while
reading,
as
to
3480
All
or
contains
mutual
Loader
can
attachment
This
data
recording
the
in
the
and
stop
be
written
to
accept
the
data
data
be
available
Magnetic
Magnetic
A22,
and
two
Coupler
control
feature,
tape
cartridges
be
added
features,
can
read
high
data
unit
contains
tape
drive
operations
actions
are
them.
transfers
is
transferred
when
Tape
Subsystem
up
to
four
magnetic
feature, two
of
eight
tape
which
and
to
any
each
and
write
rate
is achieved by
density
of
transferred
of
a buffer
and
the
of
the
individual
The
channel
from
the
from
the
controlling
Tape
3480
Tape
tape
drives.
control
units
allows
the
or
about
controlling
processor
the
manual
all
of
control
data
38000
that
drives.
to
the
is
control
tape
both
at
stores
processor
Subsystem
consists
(16
the
unit
rates
recording
processor.
that
Because
control
then
unit
drive
of
Units,
With a Dual
units
drives).
the
automatic
loading
tape
units.
can
up
to
bytes
per
the
data
are
normally
unit
released
to
the
to
the
requests
a 3480
Model
can
be
The
Automatic
of
single
With
connect
three
18
data
inch.
being
The
of
the
before
to
do
tape
control
Control
Bll
or
B22.
Control
connected
loading
tape
additional
with
megabytes
tracks
transferred
buffer
caused
buffer,
the
tape
other
drive.
During
unit
it.
Unit,
Each
Unit
to
of
up
to
four
per
at
a
reduces
by
the
blocks
drive
work
buffer
of
so
Because
soon
provides a tape-write-immediate mode
Tape-write-immediate mode forces
tape
mode
reduces
The
search,
disconnected
reading
the
Each
messages
tape
messages
the
as
the
before
should
subsystem
3480
subsystem
you
and
channel
tape
on
drive.
to
3480 subsystem
write
data
it
indicates
be
used
only
performance.
provides a high-speed
can
search
from
the
writing.
to
signal
drive
this
In
an
the
When
that
has
a message display
display
MVS system,
drive
message display.
indicates
has
been
transferred
the
that
the
action
when
the
data
for specific blocks
channel)
can
Chapter
at
much
the
block is found,
it
is
ready
keep
the
the
1.
program
The
that
the
writing
to
the
of
writing
subsystem
is complete. Tape-write-immediate
is
critical
search
on
the
higher
for
the
on
operator
IBM 3480
next
its
operator's
can
speed
the
informed
action
buffer,
data
to
to
write
because
function.
tape
(with
than
subsystem
command.
panel.
write
any
Magnetic
is
the
subsystem
tape.
the
data
this
With
the
is
used
reconnects
of
the
necessary
Tape
complete
on
mode
high-speed
subsystem
for
The
status
Subsystem
the
of
as
also
to
the
1
The
tape
drives
This assignment
assignment for
assignment, see
earlier
Migration Guide.
can
be assigned
ability
IBM
3480
to
specific
replaces
tape
drives.
the
mechanical
For
more
Magnetic Tape Subsystem
channels
switching
information
by
program action.
used for
on
channel
Planning
and
channel
IBM 3480
Magnetic
In
MVS systems,
mode,
controls
function
generated
a
3480
any
other
and
the
catalog. This allows you
full function
catalog
that
system. VM
provided
When
• Tape write-immediate mode (OPT
•
• Buffered
the
features
Full
Tape
or
it
can
the
mode
at
in
full function mode, you
3480s
3420C
entry
in
3480
are
error
Subsystem
the
3480 subsystem
operate
mode
and
the
on
are
3480
appropriate
MVS compatibility mode. i
is
supported:
recovery (ERP)
read
in
in
which
the
3480
same
time
the
system. However,
synonymous,
to
without
and
VSE/SP
operating
and
write mode
Operating
can
operate
3420
compatibility mode. System
the
3480 operates.
in
3420
compatibility
on
the
same
cannot
and
both
share
catalogs among systems
changing
to
the
in
catalog
3480
device type
support
compatibility mode,
support
for
CD = W)
Both
system.
generate
catalog
entries
entries.
the
3480
Mode
as a 3480
compatibility mode for
entries
can
that
is
the
in
full function
generation
the
3480
in
mode
exist
Each
cannot
If
you
are
for
both
in
the
or
migrate
system uses
was
generated
comparable
following
full
both
generating
the
same
on
to
that
3480
3480
to
a
the
be
2 IBM
3480
Magnetic
• Hardware-initiated message display.
When
• High-speed
• Program-initiated message display (MSGDISP macro)
• Processor assignment
Tape Subsystem
the
3480
is
operating
features
• Dynamic device
• User-requested
• Automatic
For
compatibility mode, see
and
are
more
IBM
not
supported:
search
reconfiguration
synchronization
cartridge
information
3480
Magnetic Tape Subsystem Planning
User's
on
Reference
in
compatibility mode,
(block locate)
loader
IBM
the
functions
3480
in
System mode.
Magnetic Tape Subsystem Introduction
(DDR)
of
the
3480
the
following
in
full function
and
Migration Guide.
3480
or
Conventions
Used
The
following
used for
macro
list
the
3480,
statement.
of
symbols
but
you
are
should
used
never
to
type
define
the
the
format
symbols
in
of
the
the
actual
macros
• Braces
items appears
•
Brackets
• Items
otherwise stated,
selected.
• An ellipsis ( ... ) indicates
preceding
• Other
must be
•
Boldface
must be
({
})
indicate a required
within
([
])
indicate
separated
punctuation
entered
entered
by a
no
the
ellipsis
as
type indicates
exactly
field
or
parameter.
braces, you
an
optional field
vertical
more
than
that
are
allowed.
(parentheses, commas, slashes, spaces,
shown.
the
as
bar
one
multiple
exact
shown.
must
choose
or
(I)
represent
of
the
entries
characters
one
parameter.
alternative
alternative
of
to
• Italic type indicates fields to be supplied by you.
• Underscored type indicates a default option.
omitted,
the
default is assumed.
If
When
of
the
be entered.
the
a group
the
items.
items. Unless
items
type immediately
and
parameter
can
be
so forth)
Such
is
of
items
Chapter
1. The IBM 3480
Magnetic
Tape Subsystem 3
Chapter
2.
Tape Characteristics
The 3480 subsystem uses compact cartridges containing i/2-inch (l2.65-mm)
chromium dioxide tape. The cartridge
(731-meter) reel
Only a single density
reading and writing.
of
magnetic tape, but it stores up to 20% more data than the reel.
is
about 25% the size
is
available for tape cartridges and
of
is
used by the system for
Changed Format for the IBM Standard Data-Set Label 2
(HDR2/EOF2/EOV2)
a standard 2400-foot
The following fields contain changed
Field
6,
Tape Density
• Contents: A code indicates the recording density
equivalent to the
Use code = 0 for the 3480.
Processing: The field
•
creates labels, the information for this field
Field 13, Reserved
• Contents:
reserved for possible future use.
reserved, byte
the last four digits
subsystem, bytes
four digits
device address (for
The serial numbers in the header and trailer labels may
data set
data set
• Processing: A unique number identifying the recording unit
tape during open processing, converted into hexadecimal, and inserted into the
UCBCTD field in the
is
is
(1
byte)
DEN
parameter value on the
is
neither used
(8
bytes)
For
2400 and 3410 tape drives (for MVSj370 only), the entire field
43
contains the model number, and bytes 44 through
of
the serial number
40
through
of
the serial number
MVSj370)
opened for update
being created.
UCB tape extension.
data
for the IBM standard
of
the tape. The code
data
definition (DD) statement.
nor
verified. When
is
obtained from the JFCB.
For
3420 drives, bytes 40 through
of
the creating tape unit.
42
are reserved, bytes
of
the control unit, and byte
or
the device number (for MVSjXA).
or
if
DDR
is
used to swap tape units while the
43
through
not
file
data
management
46
47
be
the same
is
read from the
label
42
47
For
contain the last
contains the
2:
is
are
contain
the 3480
if
the
is
Chapter
2.
Tape Characteristics
2-1
~
?
Recording Mode for the IBM Standard Data Set Label 2
(HDR2/EOF2/EOV2)
If
the Improved
on the subsystem, the existing two-byte field, which
technique (previously used for seven-track tapes), indicates the data-set attribute for
the IBM standard label
IECDSECT macro:
Data
Recording Capability feature
file
2.
This field is
is
installed, enabled,
is defined as the tape recording
FL2TRTCH
and defined in the
and
invoked
'P , (P
,
(two
followed
bl
anks)
by
a blank)
The
The
file
file
is
written
is
not
in
written
compacted
in
compacted
mode.
mode.
h 2-2 IBM 3480 User's Reference
I
Chapter
3.
Modifying
Existing
Code
in
MVS
Systems
Selecting
DeB
Parameters
Data
Introducing
modifications
JCL,
and
Set
For
each
and
DD
information
supply
requests,
documentation.
statement
DD
of
field
the
data
After
you
can
change
of
the
access
appropriate
the
JFCBs
Options
data
statement.
can
data
set
and
related
the
DCB macro,
set.
have
them
DCB discussed below
techniques.
data
3480 subsystem
to
your
existing
should
set
be
identification, device
You
by specifying
specified
only by
management/administration
be
you
want
The
characteristics
supplied
information
establish
or
the
(For
more
changing
into
code.
examined
to
process,
by
either
as
the
logical
the
name
by
completing
data
set
are
common
information
your
Such
for needed changes.
characteristics,
specified
characteristics
the
operations
areas
as
there
must
of
the
data
source. Also,
in
the
connection
of
the
DD
statement
the
field
DCB
during
to
most
data
about
the
macro
can
require
DCBs, DD
be a
corresponding
set
and
device-dependent
the
DD
statement
space
allocation
appropriate
between
in
the
yourself
in
processing.
DCB fields, see
instruction
before
the
DCB macro,
organizations
some
statements,
DCB
must
JES
a DCB
and
DDNAME
opening
you
The
fields
and
reference.)
a
Density
Option
(DEN)
Note: When using the
OPTeD = Wand
The
tape
density
bits-per-inch-per-track.
capable
by
Note: The
parameter
the
unit
is used.
3480
does not need the
option is ignored.
specify only
DEN
IBM
3480,
you need
the
DEN
options.
(DEN) specifies
When
DEN
DEN
In
compatibility mode,
=
4.
Chapter
3.
Modifying
is
not
option.
to
consider the effect
the
recording
specified,
Existing
the
If
UNIT = 3480,
if
DEN
Code
of
the
density
highest
in
density
the
DEN
is specified, you can
in
MVS Systems 7
Write-Validity-Check
Option
You
parameter
3480
For
interrupt
validity
buffering.
blocks
The
buffering
each
before
(The read-back
written).
(OPTCD=W)
can
specify
of
to
operate
buffered
until
check
per
second.
OPTCD = W
in
block
the
control
the
the
DD
in
tape-write-immediate mode.
tape
devices,
the
data
option, you do
This
causes
parameter
the
control
of
data
is
unit
check
write-validity-check
statement
is
the
unit
physically
gives
is
done by
or
the
DCB macro. OPTCD = W
write
validity
physically
not
maximum I/O
of
the
be bypassed
write·
on
benefit
DCB
written
completion
the
hardware
option
check
tape.
from
rate
can
when
on
the
in
delays
When
the
to
be
be
used
writing
tape
indication
while
either
performance
the
the
device-end
you
use
reduced
to
request
data.
and
read-back
to
the
data
DCB
the
to
It
the
is being
causes
write
advantage
about
10
that
data
ensures
checked,
processor.
the
of
that
Coding
the
Block
Size
Constructing a Data
Macro
Instructions
Available
Generally, you
write
operations
control
and
unit
EXCP.
and
The
3480 provides good performance for all block sizes,
provide optimal performance for
kilobytes.
Control
The
access
the
for
used
3480. QSAM, BSAM,
is buffered
by
MACRO
INSTRUCTION
DCB X X X
DCBD X X X
MSGDISP
NOTE X
POINT
SYNCDEV X X X
use
the
write-validity-check
go
directly
buffer. OPTCD = W is
Logical
Record
Block
method
Access
support
data
Method
EXCP
that
transfer
X
to
the
Length
block
exists
and
EXCP
for
both
BSAM
X
X
tape
instead
generally
Operands
sizes
for
data
are
read
QSAM
X
option
in
supported.
and
of
storing
only
meaningful
the
sets
write.
to
make
range
on
magnetic
the
the
but
is designed
of 8 to
The
default
application's
data
in
the
with
BSAM
to
32
tape
is used
mode
8
IBM
3480
Magnetic
Tape
Subsystem
User's
Reference
Specifying
JCL
Options
The W option
the
3480.
"Write-Validity-Check Option (OPTCD = W)"
Use
the
•
The
•
The
•
The
•
That
uses
•
That
until
If
you
request
or
the
proper
function
For
further
MVS/Extended
MVS/System
Control Language
MVS/System
for OPTCD
For a discussion
UNIT
specific device you
types
number
parameter
of
devices you
of
the
system is
(unit
affinity)
the
system is
the
data
set
the
3480 subsystem
esoteric
mode, code
information
devices you
requests a validity
to
to
assign
not
is opened (deferred volume mounting).
name.
UNIT
on
Architecture,
Product-JES2
or
MVS
Product-JES3
of
the
OPTCD = W option, see
specify:
want
the
want
the
want
data
to
request
in
If
you
= 3480
the
or
use
of
MVS/System
Version 2,
JCL
MVS/System
Release 3.1,
system
system
the
system
sets
to
the
operator
compatibility
request
the
proper
the
UNIT
Product-JES3
LIC
LIC
check
to
the
the
for
on
page
assign
to
assign
to
assign
same
to
mode, code
3480
esoteric
parameter,
write
operations
8.
to a data
to a data
to a data
unit
another
mount
subsystem
the
name.
see
Version
set
set
volume
UNIT
in
full
2,
on
set
data
set
= 3400-9
PROG 5665-291, 5740-XC6, Job
Product-JES2
PROG 5740-XYS,
Release 3.3,
-XYN.
Modifying
the
Job
The
supplied
the
In
before
to
to
further
File
OPEN
system
certain
issuing
specify
permit
information
Control
macro
in a data
in a job
applications, you
the
a high-speed
instruction
definition
file
an
OPEN
physical
about
search
control
macro
block
Library: Data Management
Administration.
Block
requires
(DD)
statement.
block
might
the
or
have
instruction.
identifier
of
a specific
JFCB,
MVS/Extended
(JFCB)
access
(JFCB).
in
see MVS/370 System Programming
to
modify
the
data
to
information
This
information
the
For
example, you
JFCB
(explicitly
block
contents
on a tape
that
you
is
stored
of a JFCB
might
or
by
volume.
Architecture System-Data
have
want
default)
by
For
Chapter
3.
Modifying Existing Code in
MVS
Systems 9
Setting
the
Header
Label
Block
ID
in
the
JFCB
for
High-Speed
Search
To use
label
certain
The
software support.
The
high-speed search:
1.
2.
3.
4.
If
the
If
OPEN
header
the
high-speed
tape
data
set, you
fields
in
ability
following
Use
Set
provided.
Move
field JFCRBIDO. (The block ID
example, from
Use
the
high-speed
the
to
use
procedure
the
RDJFCB
the
JFCPOSID
the
block ID
the
OPEN
JFCPOSID
search
fast
positioning
moves
record
the
into
search
must
the
JFCB
the
high-speed
macro
bit
of
the
ID
macro
bit
is
set
function
bit
tape
normally
JFCRBIDO.
should
in
the
available
with
is
function
specify
and
using
to
read
field JFCBFLG3
first
TYPE=J
off,
OPEN
is
set
on
of
the
OPEN
search
be used
the
standard
must
at
close time.)
moves
not
active.
but
no
and
inserts
the
3480
subsystem
block
ID for
TYPE
function
to
modify
JFCB
into
to
header
have
to
open
the
block ID is found
the
= J
is
supported
the
your
indicate
label
been
saved
the
tape
block
the
to
data
normally, as
ID
data
open
JFCB
work
that
of
set.
of
on a standard
by modifying
the
data
only by 3480
for a
area.
a block ID is
the
tape
to
earlier,
in
the
for
though
JFCRBIDO,
first label
set.
the
If
the
JFCPOSID
match
IEC147I
If
block
specified.
previous
During
first label
inserted
device
should
Note
FREE
CLOSE macro),
program.
the
block
indicates
the
block ID specified does
or
file
The
block
CLOSE processing,
header
into
and
save
that
if
= CLOSE
This
bit
is
set
on
but
ID
on
the
tape,
OPEN
that
the
block ID
not
mark
preceding
drive moves
or
file mark.
record
the
JFCRBIDO field. Therefore,
plan
to
use
the
block ID before you close
dynamic
in
the
the
block ID for
is
because
unallocation
the
if
of
the
the
current
DD
statement,
dynamic
the
tape
the
next
the
block ID
processing fails
could
not
exist,
the
control
one
that
the
to a position
JFCPOSID
data
block ID for
is specified (with SVC
or
the
next
unallocation
set
the
with
data
bit
(which
Note: The data set sequence number (as coded
be
specified as
usual
(either explicitly or by
the tape at high-speed.
in
JFCRBIDO does
and
be found
Locate
is on,
if
you
subsequent
data
the
set
frees
in
on
unit
searches
Block command
to
write
the
may
deallocate
set.
FREE
is
option
not
the
available
LABEL
default)
not
error
message
the
tape.
for
the
data
following
block ID for
not
exist) is
the
3480
processing, you
99,
with
in
the
to
your
JFCB.
= (seqno,SL))
when you move
the
the
must
10
IBM
3480
Magnetic
Tape
Subsystem
User's
Reference
Example
of
How
to
Code OPEN(J)
The
example program, following, shows how
existing multifile volume.
the
predecessor file was created),
file
to
be added
The
example program opens
sequence number
and
BLOCKID
Figure
The
beginning
CLOSE,
picked from
stored
The
1.)
subsequent OPEN TYPE = J performs a high-speed
the
back
fields
are
are
of
the
new
BLOCKID
the
JFCB,
into
the
in
the
JFCB
and
stored
the
stored
tape
of
the
control
that
to
add
another
The
last
time
this
program was processed (after
the
file number
in
a small control
the
control
BLOC KID
into
the
file.
The
the
next
file sequence number is increased,
data
set.
are
referred
data
of
the
JFCB
of
new file is
file (the one
to
data
set
file
the
in
the
and
the
BLOCKID
set
on
DASD.
and
retrieves
to
be created.
new
tape
file. (see
search
created
to
and
be
created
example program are:
data
set
to
an
of
the
the
file
File
number
to
the
closed. After
next
time) is
and
both
are
Offset
+56
+108
+163 JFCBFLG3 1 New
Figure
Dec.
1.
Name
JFCRBIDO 4
JFCRBIDC 4
JFCPOSID
JFCB
Layout
Length
-
Comment
Physical
of
processed by
Physical
of
same
of
tape
3480.
Bit
request
identifier processing
OpenjClosejEOV.
block identifier
SL HDR1
final
as
the
volume.
bit
3 (hex 10) indicates
to
be
Open.
block identifier
tape
mark.
the
first SL HDR1
next
data
set
defined for
for physical block
The
on
the
in
the
Chapter
3.
Modifying Existing Code
in
MVS Systems
11
CDSDCB
TAPEDCB
DCB
DCB
DDNAME=CDSDD,DSORG=PS,MACRF=(GM,PM))
DDNAME=TAPEDD,DSORG=PS,MACRF=(PM),EXLST=JFCBP
JFCBP
JFCB
*
CDSBUF
CDSFLSQ
CDSRBID
LPI
EOF
DS
DC
DS
ORG
IEFJFCBN
ORG
DS
DS
DS
ORG
OPEN
GET
CLOSE
RDJFCB
MVC
MVC
01
OPEN
PUT
B
CLOSE
0F
X'87'
CL176
JFCB
0CL80
CL2
CL4
CDSDCB
CDSDCB,CDSBUF
CDSDCB
TAPEDCB
JFCBFLSQ,CDSFLSQ
JFCRBIDO,CDSRBID
JFCBFLG3,JFCPOSID
(TAPEDCB,(OUTPUT)),TYPE=J
TAPEDCB,
LPI
TAPEDCB
,AL3(JFCB)
....
OPEN J INDICATOR
JFCB
CONTROL
SEQUENCE
BLOCKID
OPEN
READ
CLOSE
GET
PUT
PUT
SET
CREATE
DATA
NUMBER
OF
CONTROL
CONTROL
CONTROL
JFCB
OF
FILE
SEQ.
BLOCKID
BLOCKID
OPEN/
POSITION
NEW
AND
SET
RECORD
OF
BEGINNING
DATA
SET
DATA
SET
DATA
TAPE
FILE
NO.
INTO
INTO
JFCB
BIT
ON
FILE
JFCB
NEW
FILE
OF
SET
JFCB
HIGH
ADDR
FILE
SPEED
MVS
RDJFCB
LH
AH
STH
MVC
OPEN
PUT
CLOSE
TAPEDCB
Rl,CDSFLSQ
Rl,=H'l'
Rl,CDSFLSQ
CDSRBID,JFCRBIDC
(CDSDCB,
CDSDCB,CDSBUF
CDSDCB
Block
(OUTPUT))
Count
When
standard
block
described
MVS/Extended
Administration,
For
the
These
block
the
tape
GET
UPDATED
GET
FILE
INCREMENT
STORE
STORE
OPEN
CONTROL
UPDATE
CLOSE
JFCB
SEQUENCE
BY
SEQ.
BLOCKID
CONTROL
1
NO.
OF
DATA
CONTROL
DATA
Checking
using
MVS
to
read
or
ANSI
tape
labels,
count
count
checking
in
MVS/370 Magnetic Tape Labels and File Structure,
that
Architecture Magnetic Tape Labels
DFP
Version
3480, MVS does block
are
when
the
data
error
on
the
is
written,
rather
OF
TAPEDD
NUMBER
OF
NEXT
FILE
NEXT
FILE
SET
DATA
SET
SET
any
type
of
magnetic
certain
is performed for
1,
count
set
is
written
tape,
the
than
block
and
DFP
checking
system will
when
it
tape
count
checking
all
magnetic
and
Version
and
for all label types.
is
later
2.
under
attempt
read.
volume
tape
that
is done.
devices
File Structure
more
circumstances.
to
discover
If
has
and
there
it
IBM
The
is
is a
when
12
IBM
3480
Magnetic Tape Subsystem User's Reference
This
additional
block
identifier
identifier
For
3480, MVS
to
DCBBLKCT
during
the
done
(imbedded
With
processing.
With
trailer
record
For
the
The
label
block
labels.
CLOSE, EOV
DCBBLKCT
for
an
BSAM
standard
labels.
the
tape
devices
correct
block
is performed
count
to
the
MVS
DOS
and
For
labels (IBM
The
block
number
count
checks
block
count
to
each
block
system
compares
when
and
checkpoints)
QSAM,
EXCP
count
other
check
using
the
it
is
being
and
FEOV
block
checkpoint
the
and
installation's
in
the
than
of
blocks.
that
only
on
are
performed
checking
written
the
number
ID
data
data
is specified.
system
EXCPVR, DCBBLKCT
and
trailer
3480,
compares
input
is possible
on
the
Read
Block
of
blocks
maintained.
operations
do
not
set
or
one
maintains
ANSI)
the
NSL
(nonstandard
labels.
output
the
data
sets
for 3480
data
tape
ID
written
The
and
match.
for
DCBBLKCT
block
sets
DCBBLKCT field
with
standard
input
because
and
provides
channel
or
comparison
results
which
count
data
in
This
comparison
OPTCD = H
may
is
label)
cannot
sets
also
the
3480
the
command.
read
in a data
is
done
an
ABEND
during
be
maintained.
recorded
routines
be
checked
to
the
labels.
with
Thus,
standard
appends
block
set
when
is
not
tape
in
the
may
also
for
trailer
two
a
User
EXCP
Exits
Routines
The
additional
codes for ABEND messages
programs.
Return
include
certain
For
the
trailer
both
prevent
can
DCB ABEND
DCBBLKCT is assumed
EXCP
words.
DCBMACRF
that
Codes"
user
user
those
3480-written
label
ABENDs,
the
prevent
DCB
For
the
routine
3480
The
additional
on
exits for
programs.
data
sets
block
to
DCBBLKCT.
you
3480
block
the
DCBBLKCT
exit
that
does
EXCP
must
is
block
count
page
73.
the
additional
that
receive
ID
is
must
handle
count
or
in
the
to
not
have
routines
be
set
to
maintaining
checking
and
may
require
ABEND
Programming
performed before
block
be
this
1.
both
If
both
each
check
to
trailer
count
present
a device
means
Bit 5 of
an
return
block
block
checks
ABEND
ABEND
label
unequal
and
interface
that
MACRF
accurate
provides some
you
to
change
codes
are
explained
changes
count
count
fail
mismatch
valid
any
block
that
check,
checks,
the
check
and
you
independently.
in
the
DCB
ABEND
exit.
in
all
cases
section
of
bits
12,
must
also
count.
additional
some
in
may
be
EXCP
that
routines,
the
check
compares
want
to
You
ABEND
except
of
at
least
13,
or
be 1
return
of
your
"ABEND
required
using
prevent
can
exit
and
in
either
for
three
14
of
to
indicate
and
the
the
an
Chapter
3. Modifying
Existing
Code
in
MVS
Systems
13
For
further
information
concerning
the
use
of
EXCP
and
EXCPVR,
MVS/370 System Programming Library: Data Management,
MVS/Extended
and
DFP
Version
Architecture System-Data Administration,
2.
DFP
and
Version
see
1,
User
Programs
A few
block
are:
•
•
The
• Keep
user
programs
count
checking
Programs
tape
the
Programs
count
calculated
mismatch
block
following
the
CNTRL macro.
IOBINCAM specifies
EXCP.
A positive
forward
that
position
tape
has
that
discrepancies.
from
between
count
are
an
accurate
access
method
If
IOBINCAM is zero,
or
or
backward, respectively,
written
may
not
do
not
cause
when
one
of
non-standard
depend
the
exit
changes
With
negative
on
The
unit
DCBBLKCT
to
be called.
that
block
takes
EXCP,
the
value
for
an
operate
the
the
following is
labels,
the
block
mismatch
causes
you
count
in
care
of
the
number
your
indicates
environment
successfully.
DCBBLKCT field
or
BLP
count
between
an
ABEND
and
the
can
make
DCBBLKCT.
this
except
system
of
blocks
program
the
on
the
where
true:
is used.
exit
to
DCBBLKCT
to
be
tape
label would
to
such
with
will
maintain
read
can
number
tape.
For
or
the
system
Programs
to
reflect
the
tape
handle
issued
some uses
maintain
known
before
programs:
BSAM
DCBBLKCT
written
of
blocks
does less
that
may
the
correct
is unlabeled,
block
and
the
count
the
cause
the
and
QSAM,
of
the
if
with
each
DCBBLKCT.
going
fail
•
Set
all
of
bits
12, 13,
DCBMACRF
because
• Supply a DCB ABEND
handle
•
Supply
Administration
•
Supply
is
least
volumes
to
the
block
the
117,
an
installation
an
EST
desirable
cannot
zero.
count
137,
Guide)
AE
exit
because
easily
and
and
14
of
DCBMACRF
This
may
cause
is
not
checked.
exit
routine
214 ABEND.
DCB ABEND
to
handle
routine
the
be
handled.
the
to
handle
DCB becomes
the
(see
exit
117,
to
zero
program
Data
Administration
routine
137,
and
the
new
unusable
and/or
to
be
less
(see
Data
214
ABENDs.
ABENDs.
and
set
bit 5 of
reliable
Guide)
This
action
subsequent
to
14 IBM
3480
Magnetic
Tape Subsystem
User's
Reference
Performance
Options
for IEBGENER
IEBGENER
Storage
BUFNO
IEBGENER
data
device,
IEBGENER
When
the
number
maximum
IEBGENER
buffers
BSAM specifies a
If
INPUT
used.
is a
supported
provides
blocks
performance
to
and
allows
provides a
one
or
both
of
buffers above
number
uses
if
the
BUFNO
data
be
sets
Requirements
Using
storage
REGION
ABENDs.
multiple
needed
parameter
You
buffers for
to
can
parameter
better
read
and
the
potential
default
of
the
of
IEBGENER
the
of
blocks
the
DCB
parameter
number
are
concatenated,
run
the
for
the
calculate
for
performance
written
for more
value
data
sets
may
default
per
track.
parameter
is
greater
IEBGENER
program.
additional
the
than
region
DeB
with
of
are
on
be
value,
NCP = nn
not
specified.
99,
BUFNO
increases
You
storage
specifications
when
multiple
each
I/O
overlap
5 for
the
DASD
further
may
size
and
improved by
up
to
to
the
value
is
need
to
by
using
for
buffers
operation
of
reading
number
one more
determine
If
ignored
the
avoid 80A
of
has a small
the
parameter
99
is used.
and
amount
to
change
the
IEBGENER.
permit
initiated
with
buffers.
increasing
than
the
the
one
of
virtual
or
system
following formula:
more
to
writing.
block
size,
number
used
buffer
add
a
a
the
of
for
is
50K + ((2+SYSUTl
((2+SYSUT2
Note:
If
BUFNO
formula yields slightly large values for region size
and
different
The
following is
amount
SYSUTl
SYSUTl
SYSUT2
SYSUT2
of
virtual
BLKSIZE=2K
BUFNO=20
BLKSIZE=32K
BUFNO=Not
Virtual region =
REGION=318K
DCBBUFNO)*(SYSUTl
DCBBUFNO)*(SYSUT2
DCBBLKSIZE))
DCBBLKSIZE))
is not specified, use a value
MVS
environments.
an
example
storage
specified, default is
50K + ((2+20)*(2K))
of
how
needed:
to
used
+
use
((2+5)*(32K))
+
of
5 in the calculation.
the
formula
to
This
to
allow for growth
calculate
the
Chapter
3.
Modifying
Existing
Code
in
MVS
Systems
15
Loading...