z/OS V1R6.0 DFSMS Access Method Services for CatalogsFor
information
on
concatenated
DD
statements,
see
the
FILE
parameter
descriptions
in
Chapter
3,
“Functional
Command
Syntax.”
Examples
using
concatenated
DD
statements
follow
the
description
of
the
REPRO
command
that
begins
on
Chapter
30,
“REPRO,”
on
page
305.
For
additional
information
about
the
various
types
of
concatenated
DD
statements,
see
the
section
on
special
DD
statements
in
z/OS
MVS
JCL
Reference.
JCL
DD
Statement
for
a
Non-VSAM
Data
Set
You
can
allocate
non-VSAM
data
sets
with
the
access
method
services
ALLOCATE
command.
See
the
DD
statements
in
the
examples
that
follow
the
descriptions
of
the
BLDINDEX,
EXPORT,
IMPORT,
REPRO,
and
PRINT
commands
for
additional
methods
of
describing
and
allocating
non-VSAM
data
sets.
JCL
DD
Statement
for
a
Snap
Dump
If
access
method
services
encounters
a
condition
that
requires
it
to
abnormally
end
a
job,
it
takes
a
snap
dump
of
virtual
storage.
You
must
write
an
AMSDUMP
DD
statement
to
get
the
snap
dump;
that
is,
//AMSDUMP
DD
Is
the
graphic
character
set
of
the
print
chains
you
want
to
use.
The
processor
usesPN
unless
the
program
explicitly
directs
it
to
use
another
set
of
graphics.
AN
Arrangement
A,
standard
EBCDIC
character
set,
48
characters
HN
Arrangement
H,
EBCDIC
character
set
for
FORTRAN
and
COBOL,
48
characters
PN
PL/1
alphanumeric
character
set
QN
PL/1
preferred
alphanumeric
character
set
for
scientific
applications
RN
Preferred
character
set
for
commercial
applications
of
FORTRAN
and
COBOL
SN
This
character
set
contains
lower
case
and
is
the
preferred
character
set
for
text
printing
TN
Character
set
for
text
printing,
120
characters
TABLE(mname)
Is
the
name
of
a
table
you
supply.
This
256-byte
table
defines
the
graphics
for
each
of
the
256
possible
bit
patterns.
Any
character
sent
to
the
printeris
translated
to
the
bit
pattern
found
in
the
specified
table
at
the
position
corresponding
to
its
numeric
value
(0-255).
If
the
print
chain
does
not
have
a
graphic
for
a
[BLKSIZE(value)]2
[BUFL(buffer-length)]2
[DEST(destination|destination.userid)]
[DIAGNS(TRACE)]2
[EROPT(ACC|SKP|ABE)]
[UCOUNT(count)|PARALLEL]
Gives
the
magnetic
tape
density
as
follows:
0
200
bpi/7
track
1
556
bpi/7
track
2
800
bpi/7
and
9
track
3
1600
bpi/9
track
4
6250
bpi/9
track
(IBM®
3420
Models
4,
6,
and
8)
DIAGNS(TRACE)
The
Open/Close/EOV
trace
option
that
gives
a
module-by-module
trace
of
the
Open/Close/EOV
work
area
and
your
DCB.
DIR(integer)
Gives
the
number
of
256
byte
records
for
the
directory
of
a
new
partitioned
data
set.
You
must
use
this
parameter
to
allocate
a
new
partitioned
data
set.
The
data
set
organization
as:
DA
Direct
access
DAU
Direct
access
unmovable
PO
Partitioned
organization
POU
Partitioned
organization
unmovable
PS
Physical
sequential
PSU
Physical
sequential
unmovable
ALLOCATE
Chapter
4.
ALLOCATE
37
When
you
allocate
a
new
data
set
and
do
not
use
the
DSORG
parameter,
these
occur:
v
If
you
assign
a
non-zero
to
the
DIR
parameter,
DSORG
defaults
to
the
partitioned
organization
(PO)
option.
v
If
you
do
not
assign
a
value
to
the
DIR
parameter,
DSORG
defaults
to
the
physical
sequential
(PS)
option.
v
The
system
does
not
store
default
DSORG
information
into
the
data
set
until
a
program
opens
and
writes
to
the
data
set.
With
PDSEs,
the
PSU
and
POU
options
are
incompatible
and
result
in
an
error
if
used
with
DSNTYPE(LIBRARY)
while
the
data
set
is
open
for
output.
If
the
data
set
is
open
for
input
or
update,
PSU
and
POU
are
ignored.
To
indicate
the
data
set
organization
for
VSAM
data
sets,
see
RECORG.
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
MASTERPW X X X X X X X X X
X
AUTHORIZATION X X X X X X X X X
X
X
X
X
X
X
X
X
X
X
NULLIFY X X X X X X X X X X X
1
1
1
X
LOGSTREAMID
X X
XX X
X X
OWNER X X X X X X X X X X X
RETENTION X XX X X X X
X
X
ERASE
EXCEPTIONEXIT
CCSID
BUFNI
BWO
BUFFERSPACE
1
3
4
1. LOCK and UNLOCK and ECSHARING and NOECSHARING can only be specified for an integrated catalog facility catalog.
2. Alter commands cannot be run against OAM data sets.
3. The data set must be a generation data set in either deferred rolled-in or rolled-off status.
4. When SHAREOPTIONS is specified or an integrated catalog facility catalog, the data level
share option will be propagated to the index level as well.
2
IN D
E X
D A
T A
S E
[ENTEREJECTDATE(eedate)]
[EXPIRATIONDATE(expdate)]
[LIBRARYNAME(libname)]
MEDIA5|MEDIA6|MEDIA7|MEDIA8}]
Identifies
whether
the
data
on
the
volume
is
compacted.
The
YES
and
IDRC
parameter
variables
are
synonymous.
The
NO
and
NONE
parameter
variables
are
synonymous.
Use
this
parameter
only
for
private
tape
volumes.
If
you
use
it
for
scratch
tape
volumes,
a
default
of
NONE
is
forced.
YES
Specifies
that
data
is
compacted
in
the
manner
appropriate
for
the
type
of
media.
IDRC
Specifies
that
improved
data
recording
capability
(IDRC)
compaction
was
used.
NO
Specifies
that
no
compaction
was
used.
NONE
Specifies
that
no
compaction
was
used.
UNKNOWN
Specifies
that
it
is
unknown
if
compaction
was
used.
Abbreviation:
COMP
ENTEREJECTDATE(eedate)
Identifies
the
date
that
a
tape
volume
was
last
ejected
from
a
tape
library
or
last
entered
into
a
tape
library.
eedate
The
date,
as
YYYY-MM-DD.
See
“Tape
Library
Date
Formats”
on
page
9
for
valid
dates.
The
default
is
blank.
Abbreviation:
EEDATE
EXPIRATIONDATE(expdate)
Identifies
the
date
on
which
the
tape
volume
expires.
If
there
is
more
than
one
data
set
on
the
volume,
the
expiration
date
is
the
latest
expiration
date
among
the
data
sets
on
the
volume.
expdate
Enter
a
date
as
YYYY-MM-DD.
The
expiration
date
is
set
to
blanks
when
the
USEATTRIBUTE
is
SCRATCH.
Abbreviation:
EXDATE
LIBRARYNAME(libname)
Identifies
the
name
of
the
tape
library
in
which
this
tape
volume
resides.
If
ALTER
VOLUMEENTRY
84
z/OS
V1R6.0
DFSMS
Access
Method
Services
for
Catalogs
you
use
this
parameter,
the
parameter
LOCATION
must
equal
LIBRARY.
If
LOCATION
equals
SHELF,
the
library
name
is
set
to
SHELF.
libname
A
1-to-8
character
library
name.
Abbreviation:
LIBNAME
[ENTEREJECTDATE(eedate)]
[EXPIRATIONDATE(expdate)]
[LIBRARYNAME(libname)]
MEDIA5|MEDIA6|MEDIA7|MEDIA8}]
shows
the
type
and
format
of
the
cartridges
used
for
mountable
tape
data
sets
used
with
this
data
class.
It
is
mapped
by
one
of
the
following
attributes:
DDCMENUL
Media
type
is
not
specified
(NULL).
The
constant
value
is
0.
DDCMEDA1
Media
type
is
MEDIA1
(cartridge
system
tape
media).
The
constant
value
is
1.
DDCMEDA2
Media
type
is
MEDIA2
(enhanced
capacity
cartridge
tape
media).
The
constant
value
is
2.
DDCMEDA3
Media
type
is
MEDIA3
(high-performance
cartridge
tape
media).
The
constant
value
is
3.
DDCMEDA4
Media
type
is
MEDIA4
(extended
high-performance
cartridge
tape
media).
The
constant
value
is
4.
DCOLLECT
Chapter
11.
DCOLLECT
115
//
//
//
//
//
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//
//SYSPRINT
DD
//
//SYSPRINT
DD
//
//
//
//
//
//
//
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//
//PORTDS2
DD
//
//PORTDS3
DD
//
//PORTDS4
DD
//
//SYSIN
DD
//SYSPRINT
DD
//SYSIN
DD
specifies
the
fields
to
be
included
for
each
entry
listed.
Appendix
B,
“Interpreting
LISTCAT
Output
Listings,”
on
page
357,
shows
the
listed
information
that
results
when
you
specify
nothing
(which
defaults
to
NAME),
HISTORY,
VOLUME,
ALLOCATION,
or
ALL.
For
SMS-managed
data
sets
and
catalogs,
the
SMS
class
names
and
last
backup
date
are
listed
in
addition
to
the
other
fields
specified.
The
class
definitions
are
not
displayed.
Exception:
For
tape
library
and
tape
volume
entries,
only
the
ALL
parameter
is
functional.
If
the
HISTORY,
VOLUME,
and
ALLOCATION
parameters
are
specified
for
tape
library
and
tape
volume
entries,
these
parameters
are
ignored.
If
ALL
is
not
specified,
only
the
names
of
the
tape
library
or
tape
volume
entries
are
listed.
NAME
specifies
that
the
name
and
entry
type
of
the
entries
are
to
be
listed.
Some
entry
types
are
listed
with
their
associated
entries.
The
entry
type
and
name
of
the
associated
entry
follow
the
listed
[{FILE(ddname)|{VOLUME(volser)+
specifies
whether
a
Subsystem
Counters
report,
a
subsystem
status
report,
a
pinned
track
to
Data
Set
Cross
Reference
report,
or
a
Device
Status
report
is
printed;
or
an
operator
message
with
the
remote
access
code
is
issued.
COUNTS
specifies
that
a
Subsystem
Counters
report
be
printed.
This
parameter
is
the
default.
Abbreviation:
CNT
Note:
COUNTS
can
be
used
with
DEVICE,
SUBSYSTEM,
or
ALL.
STATUS
specifies
that
a
Subsystem
Status
report
be
printed.
Abbreviation:
STAT
Notes:
1.
STATUS
can
be
issued
to
an
offline
device
by
using
the
UNITNUMBER
parameter.
2.
STATUS
can
be
used
with
WTO
parameters
PINNED
//SYSPRINT
DD
//
//SYSPRINT
DD
LISTDATA
Chapter
28.
LISTDATA
291
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//SYSPRINT
DD
//
//
//SYSPRINT
DD
//
//
//SYSPRINT
DD
//
//SYSIN
DD
//SYSPRINT
DD
specifies
whether
the
command
pertains
to
caching
for
a
specific
device
or
subsystem
caching,
nonvolatile
storage,
DASD
fast
write
to
a
specific
device,
or
cache
fast
write
access
for
the
subsystem.
DEVICE
specifies
that
access
to
the
cache
for
a
particular
device
is
allowed
or
prohibited.
Abbreviation:
DEV
Notes:
1.
DEVICE
OFF
is
not
supported
for
the
ESS.
2.
DEVICE
ON
or
OFF
can
be
issued
to
an
offline
device
by
using
the
UNITNUMBER
parameter.
SUBSYSTEM
specifies
that
access
to
cache
for
the
subsystem
is
allowed
or
prohibited.
Abbreviation:
SUBSYS
or
SSYS
Notes:
1.
SUBSYSTEM
OFF
is
not
supported
for
the
ESS.
SETCACHE
328
z/OS
V1R6.0
DFSMS
Access
Method
Services
for
Catalogs
[LISTSUBSYS(subsystem|ALL)]|
[LISTSUBSYSDS(subsystem|ALL)]|
//
//SYSPRINT
DD
specifies
that
the
LISTCAT
output
records
are
variable-length,
blocked
5-to-1,
and
are
preceded
by
an
ANSI
print
control
//
//SYSUT2
DD
IOLIST A
AUX LIST
PAGE NUMBER LIST
PAGE NUMBER LIST: Optional. Provides a way to specify the starting page number for system output.
LENGTH: A halfword that specifies the number of bytes in the PAGE NUMBER field.
PAGE NUMBER: 1- to 4 byte character string that can specify the starting page number of system output listing. This value is reset to the current page number upon completion of the present invocation of the access method services processor.
OPTIONS LIST: Required. Provides a way to specify processing option. If you do not wish to specify any options, you must set the LENGTH field to binary zeros.
LENGTH: Halfword that specifies the number of bytes in the OPTIONS field.
OPTIONS: Character string that contains the processing options of the access method services PARM command. The options may be specified in the PARM field of the EXEC statement or they may be set up by the problem program. The options must comply with the parameter syntax of the access method services PARM command.
DDNAMES LIST: Optional. Provides a way to specify alternative names for the SYSIN and SYSPRINT data sets.
LENGTH: halfword that specifies the number of bytes in the reminder of the list.
DDNAME: Unseparated 8-character ddnames, left- justified, and padded with blanks. To change the name of SYSIN or SYSPRINT, supply an alternate name in the same position. If an alternate name is not supplied, the standard name is assumed. If the name is not supplied with the list, the 8-byte entry must contain binary zeros. Names in any position other than those for SYSIN and SYSPRINT are ignored. Note: No record descriptor word (RDW) will be passed back from IDCAMS for the SYSPRINT data set.
INPUT/OUTPUT LIST: Optional. Provides the means of identifying those data sets for which the invoker wishes to manage all I/O operations.
n: A fullword that specifies the number of groups of three fields that follow. Each group consists of a DDNAME address, an IOROUTINE address, and a USER DATA address.
DDNAME: Address of a character string that identifies a data set that will result in the invocation of the associated IOROUTINE for all I/O operations (including OPEN and CLOSE) against the data set. The character string identifies the data set as either a 10-byte or 46-byte character string as follows:
A 10-byte character string: The first two characters are ‘DD’. The next 8 characters are the DDNAME field value left-justified (padded with blanks as necessary), which can appear in the FILE, INFILE, or OUTFILE parameters of any access method services command. The SYSIN and SYSPRINT ddnames can also appear if the invoker wishes to manage these data sets.
A 46-byte character string: The first two characters are ‘DS’. The next 44 characters are the data set name left-justified (padded with blanks if necessary), which can appear in the INDATASET, OUTDATASET, or DATASET parameters of any access method services command.
Figure
31.
Processor
Invocation
Argument
List
from
Your
Program
(Part
1
of
2)
Invoking
from
Program
Appendix
D.
Invoking
Access
Method
Services
from
Your
Program
425
Processor
Invocation
Figure
31
on
page
425
shows
the
processor
invocation
argument
list
as
it
exists
in
the
Auxiliary List
Auxiliary list: Optional. Provides a way to allow migration/recall products to pass indications through AMS IMPORT to SMS for volume selection.
‘AUXLIST’: 8-character identifier with name of control block.
LENGTH: A halfword that specifies the length of the AUXLIST.
FLAGS: One byte of processing flags used by AMS.
ACERO: Address of the ACERO control block to be passed to SMS.
VOLIST: Address of the space provided for IMPORT to return to a list of volume name and associations used to satisfy the request.
BASEVOL: Address pointing to the volume serial number of the base cluster for an ALTERNATE INDEX.
IOROUTINE: Address of the program that is to be invoked to process I/O operation upon the data set associated with DDNAME. This routine, instead of the processor, is invoked for all operations against the data set. See “USER I/O ROUTINES” in this appendix for linkage and interface conventions between the IOROUTINE and access method services.
USER DATA: Address, supplied by the user, that is passed to the exit routines.
WORKAREA VOLUME LIST: Provides a list large enough to return the information necessary for the object being imported.
‘AUXVOLST’: 8-character identifier with name of control block.
LENGTH: One fullword that specifies the number of bytes in the volume list.
VOLIST CNT: One fullword that specifies the number of VOLSERS returned. For multi-volume import, the volume list can be as large as 118 volume (59 for data component, 59 for index component).
VOLUME INFO: Multiple volume information entries. Each contains two bytes of a six character volume name, return status for the volume, and a character association (D or I).
‘AUXLIST’
‘AUXVOLST’
LENGTH
SET
ACBNOJCL
FLAG
If
the
data
set
that
is
being
opened
is
currently
open
for
RLS
or
DFSMStvs
access,
the
non-RLS
open
fails.
If
the
data
set
has
previously
been
opened
for
RLS
or
DFSMStvs
access,
but
requires
recovery,
a
non-RLS
open
for
input
is
allowed.
However,
open
for
output
fails.
Invoking
from
Program
430
z/OS
V1R6.0
DFSMS
Access
Method
Services
for
Catalogs
Appendix
E.
DCOLLECT
User
Exit
This
appendix
is
intended
to
help
you
understand
the
DCOLLECT
user
exit.
User
Exit
Description
DCOLLECT
enables
you
to
intercept
records
after
they
are
created,
but
before
they
are
written
to
the
output
data
set.
This
ability
is
provided
by
either
IDCDCX1,
the
default
DCOLLECT
user
exit,
or
any
load
module
named
with
the
EXITNAME
parameter.
In
this
chapter,
the
term
DCOLLECT
user
exit
is
used
to
denote
either
the
default
exit
or
a
named
exit.
The
DCOLLECT
user
exit
allows
the
programmer
to
enhance,
modify,
or
delete
records
created
by
DCOLLECT.
If
IDCDCX1
is
modified,
it
must
be
link-edited
into
the
IDCDC01
load
module,
or
applied
to
the
system
by
the
System
Modification
Program
Extended
(SMP/E).
A
separate
user
exit
must
be
loaded
into
an
APF
authorized
load
library
if
the
EXITNAME
parameter
is
used.
All
records
produced
by
DCOLLECT,
including
records
created
for
DFSMShsm
are
passed
to
the
DCOLLECT
user
exit
before
they
are
written
to
the
output
data
set.
Use
the
default
exit,
IDCDCX1,
to
provide
some
standard
customization
to
DCOLLECT.
You
can
use
and
the
EXITNAME
parameter
for
special
situations,
or
testing
a
new
exit
for
DCOLLECT.
The
DCOLLECT
user
exit
should
use
standard
save
area
conventions,
and
it
should
be
reentrant.
The
user
exit
must
return
to
the
caller
in
the
Dissatisfied
Overall
How
satisfied
are
you
that
the
information
in
this
book
is:
Very
Dissatisfied
Easy
to
Easy
to
Well
Applicable
to
your
Please
tell
us
how
we
can
improve
this
book:
Thank
you
for
your
responses.
May
we
contact
you?
h
Yes
h
No
When
you
send
comments
to
IBM,
you
grant
IBM
a
nonexclusive
right
to
use
or
distribute
your
comments
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Name
Address
Company
or
Organization
Phone
No.
Readers’
Comments
Notational conventions
Commands
How to continue commands and parameters
The terminator
Summary of changes for SC26-7394-03 z/OS Version 1 Release 6
New information
Changed information
Chapter 1. Using Access Method Services
Identifying Data Sets and Volumes
Dynamic Allocation
Security Authorization
JCL DD Statements
JCL DD Statement for a Volume
JCL DD Statement for a Non-VSAM Data Set
JCL DD Statement for a Snap Dump
JCL DD Statement for a Target Data Set
JCL DD Statement for an Alternate Target Data Set
JCL JOBCAT and STEPCAT DD Statements
Direct Allocation Using JCL
Invoking Access Method Services
Using a Job or Jobstep to invoke Access Method Services
From a Time Sharing Option Session
Access Method Services Tape Library Support
Summary of Tape Library Support
Access Method Services Commands for Tape Library Support
ALTER LIBRARYENTRY
ALTER VOLUMEENTRY
CREATE LIBRARYENTRY
CREATE VOLUMEENTRY
DEFINE USERCATALOG
Catalog Selection Order for EXPORT DISCONNECT
Catalog Search Order for LISTCAT
Generic Catalog Selection for DELETE and LISTCAT
Specifying Attribute Selection Order
Chapter 2. Modal Commands
Null Command
CANCEL Command
Condition Codes
Chapter 3. Functional Command Syntax
Functional Command Syntax Summary
Allocating Non-SMS Managed Data Sets
Return Codes for the ALLOCATE Command
Syntax for ALLOCATE Parameters
Allocate a Data Set Using SMS Class Specifications: Example 1
Allocate a VSAM Data Set Using SMS Class Specifications: Example 2
Allocate a New Data Set: Example 3
Allocate a non-VSAM Data Set: Example 4
Allocate a Partitioned Data Set Extended: Example 5
Chapter 5. ALTER
ALTER Parameters
Required Parameters
Optional Parameters
ALTER Examples
Roll-In a Generation Data Set: Example 2
Alter the Entry Names of Generically Named Clusters: Example 3
Alter the Attributes of a Generation Data Group: Example 4
Alter a Data Set Expiration Date: Example 6
Migrate a DB2® Cluster to a Linear Data Set Cluster: Example 7
Alter a Cluster Name and the Associated Data and Index Names: Example 8
Chapter 6. ALTER LIBRARYENTRY
Altering a LIBRARY Entry: Example 2
Chapter 7. ALTER VOLUMEENTRY
Chapter 8. BLDINDEX
BLDINDEX Examples
Build an Alternate-Index over a Key-Sequenced Data Set (KSDS): Example 1
Build an Alternate-Index over a Key-Sequenced Data Set (KSDS) Using DFSORT: Example 2
Chapter 9. CREATE LIBRARYENTRY
Creating a LIBRARY Record: Example 2
Chapter 10. CREATE VOLUMEENTRY
Creating a VOLUME Entry: Example 2
Chapter 11. DCOLLECT
Generic Volume Data Collection: Example 1
Storage Group Data Collection: Example 2
Migrated and Backup Data Set Data Collection: Example 3
Combination of Options: Example 4
Collection of SMS Construct Information: Example 5
Chapter 12. DEFINE ALIAS
Define Alias for a non-VSAM non-SMS-Managed Data Set: Example 1
Define an Alias for a User Catalog: Example 2
Chapter 13. DEFINE ALTERNATEINDEX
DEFINE ALTERNATEINDEX Examples
Define an Alternate Index Using SMS Data Class Specification: Example 1
Define an SMS-Managed Alternate Index: Example 2
Define an Alternate Index: Example 3
Define an Alternate Index with RECATALOG: Example 4
Chapter 14. DEFINE CLUSTER
DEFINE CLUSTER Examples
Define an SMS-Managed Key-Sequenced Cluster Specifying Data and Index Parameters: Example 2
Define a Key-Sequenced Cluster Specifying Data and Index Parameters: Example 3
Define a Key-Sequenced Cluster and an Entry-Sequenced Cluster: Example 4
Define a Relative Record Cluster in a Catalog: Example 5
Define a Reusable Entry-Sequenced Cluster in a Catalog: Example 6
Define a Key-Sequenced Cluster in a Catalog: Example 7
Define an Entry-Sequenced Cluster Using a Model: Example 8
Define a VSAM Volume Data Set: Example 9
Define a Relative Record Data Set with Expiration Date: Example 10
Define a Linear Data Set Cluster in a Catalog: Example 11
Chapter 15. DEFINE GENERATIONDATAGROUP
DEFINE GENERATIONDATAGROUP Examples
Define a Generation Data Group and a Generation Data Set within it: Example 1
Use Access Method Services to Define a GDG and JCL to Define a GDS in that GDG: Example 2
Chapter 16. DEFINE NONVSAM
DEFINE NONVSAM Examples
Define a Non-VSAM Data Set with the RECATALOG Parameter: Example 1
Define a Non-VSAM Data Set: Example 2
Chapter 17. DEFINE PAGESPACE
Define a Page Space in another Catalog: Example 3
Chapter 18. DEFINE PATH
Define a Path (Recatalog) in a Catalog: Example 2
Chapter 19. DEFINE USERCATALOG
DEFINE USERCATALOG Examples
Define a User Catalog, Specifying SMS Keywords: Example 1
Define a User Catalog, Taking All Defaults: Example 2
Define a User Catalog, Using SMS Keywords and the VOLUME Parameter: Example 3
Define a User Catalog, Using SMS Keywords and the VOLUME Parameter: Example 4
Define a User Catalog: Example 5
Define a User Catalog Using the MODEL Parameter: Example 6
Define a General Tape Volume Catalog: Example 7
Define a Specific Tape Volume Catalog: Example 8
Chapter 20. DELETE
Delete a User Catalog for Recovery: Example 2
Delete VSAM Volume Records: Example 3
Delete a Non-VSAM Data Set's Entry: Example 4
Delete Entries Associated with a Non-VSAM Object from VVDS and VTOC: Example 5
Delete a Key-Sequenced VSAM Cluster in a Catalog: Example 6
Delete Two Key-Sequenced Clusters in a Catalog: Example 7
Delete a User Catalog: Example 8
Delete an Alias Entry in a Catalog: Example 9
Delete Generically Named Entries in a Catalog: Example 10
List a Generation Data Group's Entries, Then Delete the Group and Its Data Sets in a Catalog: Example 11
Delete a Generation Data Group with Recovery: Example 12
Delete a Member of a Partitioned (Non-VSAM) Data Set in a Catalog: Example 13
Delete a Page Space: Example 14
Delete a VVDS with Recovery: Example 15
Delete an OAM Collection Name Catalog Entry: Example 16
Delete a Tape Library Entry: Example 17
Delete a Tape Volume Entry: Example 18
Chapter 21. DIAGNOSE
Diagnose a VVDS: Compare the BCS and VVDS Example 1
Diagnose Only the BCS: Example 2
Diagnose the BCS: Compare the BCS and Certain VVDSs: Example 3
Diagnose a VVDS: Compare the BCS and VVDS: Example 4
Diagnose a VVDS: Compare the BCS and VVDS: Example 5
Diagnose a VVDS: Compare the BCS and VVDS: Example 6
Diagnose a VVDS: Compare the BCS and VVDS: Example 7
Chapter 22. EXAMINE
Examine the Index Component of a User Catalog: Example 1
Examine Both Components of a Key-Sequenced Data Set: Example 2
Examine the Data Component of a User Catalog: Example 3
Chapter 23. EXPORT
Export a Key-Sequenced Cluster: Example 2
Export an Entry-Sequenced Cluster: Example 3
Export an Entry-Sequenced Cluster Using CIMODE: Example 4
Export Multiple Data Sets Using Multiple INFILE Parameters: Example 5
Chapter 24. EXPORT DISCONNECT
EXPORT DISCONNECT Examples
Export Disconnect of a User Catalog from Another User Catalog: Example 1
Export Disconnect of a User Catalog: Example 2
Chapter 25. IMPORT
Import a Catalog: Example 2
Import a Key-Sequenced Cluster: Example 3
Import an Entry-Sequenced Cluster in a Catalog: Example 4
Import a Cluster to a Volume Other Than One on Which It Was Originally Defined: Example 5
Chapter 26. IMPORT CONNECT
Chapter 27. LISTCAT
List a Key-Sequenced Cluster's Entry in a Catalog: Example 2
Alter a Catalog Entry, Then List the Modified Entry: Example 3
List Catalog Entries: Example 4
List Catalog Entries: Example 5
List a Tape Library Entry: Example 6
List Tape Volume Entries: Example 7
Chapter 28. LISTDATA
Listing Subsystem Counters for a Particular Device: Example 1
Listing Subsystem Counters for All Devices within a Subsystem: Example 2
Listing Subsystem Counters for All Devices on Similar Subsystems: Example 3
Listing Subsystem Status: Example 4
Listing Pinned Data: Example 5
Listing Device Status: Example 6
Generating a Remote Support Access Code: Example 7
Chapter 29. PRINT
CHARACTER example
DUMP example
HEX example
Print a Key-Sequenced Cluster's Data Records: Example 3
Copy Records from a Non-VSAM Data Set into an Entry-Sequenced VSAM Cluster, Then Print the Records: Example 4
Print a Linear Data Set Cluster: Example 5
Print a Data Set that Contains DBCS Data: Example 6
Chapter 30. REPRO
STEP1
STEP2
Merge an Integrated Catalog Facility User Catalog into Another Integrated Catalog Facility User Catalog: Example 3
Merge Selected Entries (Split) from a User Catalog into Another User Catalog: Example 4
Copy a Catalog: Example 5
STEP 1
STEP 2
STEP 3
STEP 4
Encipher Using System Keys: Example 7
Decipher Using System Keys: Example 8
Encipher Using Private Keys: Example 9
Decipher Using Private Keys: Example 10
Chapter 31. SETCACHE
Setting Cache Fast Write On for the Subsystem
Setting Nonvolatile Storage On for the Subsystem
Setting DASD Fast Write On for a Volume
Creating a Duplex Pair from Two Simplex Volumes
Changing 3990 and 9390 Cache and NVS Operating Modes
Setting Cache Off for the Subsystem
Setting Caching Off for a Device
Setting Nonvolatile Storage Off for the Subsystem
Setting DASD Fast Write Off for a Volume
Setting Cache Fast Write Off for the Subsystem
Resetting a Duplex Pair to Two Simplex Volumes
Destaging All Modified Data in Cache and NVS to DASD
Resetting All Cache and NVS Operating States to Defaults
Using Dual Copy to Migrate Volumes
Migrating Simplex Volume
Migrating Duplex Volumes
Chapter 32. SHCDS
SHCDS Parameters
Required Parameters
Optional Parameters
SCHDS Examples
Using PERMITNONRLSUPDATE With a Generic Data Set Name Specification: Example 1
Listing Data Sets With the High-Level Qualifier SYSPLEX: Example 2
Listing data sets with JOBS: Example 3
Listing shunted entries: Example 4
Chapter 33. VERIFY
Appendix A. Security Authorization Levels
Required RACF Authorization Tables
LISTCAT Output Keywords
Alias Entry Keywords
Alternate-Index Entry Keywords
Cluster Entry Keywords
Data Entry Keywords
Index Entry Keywords
Non-VSAM Entry Keywords
NVS: Non-VSAM Entry, Special Field
HIS: History Group
PRT: Protection Group
STA: Statistics Group
VLS: Volumes Group
Job Control Language (JCL) for LISTCAT Jobs
LISTCAT and Access Method Services Output Messages
LISTCAT Output Listing
LISTCAT NAMES Output Listing
LISTCAT VOLUME Output Listing
LISTCAT ALL Output Listing
LISTCAT ALL Output Listing for a Non-VSAM Tailored Compressed Data Set
LISTCAT ALLOCATION Output Listing
LISTCAT HISTORY Output Listing
LISTCAT LEVEL Output Listing
LISTCAT ENTRIES Output Listing
LISTCAT CREATION/EXPIRATION Output Listing
Appendix C. Interpreting SHCDS Output Listings
LISTDS
LISTDS with Data Set in Retained Lock State
LISTDS for Data Set Shared by Multiple Subsystems
LISTDS for Data Set in Non-RLS Permitted State
LISTDS with Data Set in Non-RLS Update and Permit First Time States
LISTDS for Data Set in Lost Lock State
LISTDS with JOBS keyword
LISTSUBSYS for All Subsystems Sharing Data Sets in the Sysplex
LISTSUBSYSDS
LISTSUBSYSDS for Subsystem Sharing Multiple Data Sets
LISTSUBSYSDS for All Subsystems in the Sysplex and the Shared Data Sets
LISTRECOVERY
Appendix D. Invoking Access Method Services from Your Program
Authorized Program Facility (APF)
Processor Invocation
User Exit Description
User Exit Example
DCOLLECT Output Record Structure
Header Record Field
VSAM Association Record Field
Appendix G. Accessibility
Using assistive technologies
z/OS information