z/OS V1R3.0 DFSMS Advanced Copy Services

z/OS V1R3.0 DFSMS Advanced Copy ServicesDATA
SET
SYS1.XCOPY.session_id.JRNLnn
NOT
IN
CATALOG
OR
CATALOG
CANNOT
BE
ACCESSED
44
z/OS
V1R3.0
DFSMS
Advanced
Copy
Services
Note:
The
maximum
total
journal
data
set
size
is
2
GB.
Allocating
more
than
1.5
GB
of
space
for
all
journal
data
sets,
however,
does
not
provide
any
additional
performance
benefit.
Optimal
Performance
Specifications
The
following
steps
are
recommended
to
achieve
optimal
journal
performance:
v
Allocate
the
journal
data
sets
on
high-performance
volumes,
and
place
them
behind
storage
controls
that
use
DASD
fast
write,
cache
functions,
and
have
large
NVSs.
v
Attach
the
journal
data
sets
with
high
bandwidth
ESCON
or
FICON
channels,
preferably
capable
of
very
high
transfer
rates.
v
Allocate
the
same
amount
of
space
for
all
journal
data
sets.
v
Put
the
journal
data
set
volumes
behind
storage
controls
that
do
not
also
process
primary
or
secondary
volumes.
v
Spread
the
striped
journal
data
sets
across
as
many
disk
volumes
as
possible,
preferably
with
each
journal
data
set
on
a
separate
volume.
Processing
performance
is
improved
because
XRC
assigns
a
separate
internal
subtask
for
each
pair
of
allocated
journal
data
sets.
Table
18
lists
journal
data
set
patterns
that
optimize
journal
performance.
Table
18.
Journal
data
set
patterns
for
optimal
performance
Striped
data
sets
Nonstriped
data
sets
For
two
journal
data
sets:
VOL1
VOL2
JRNL01
JRNL01
JRNL02
JRNL02
VOL1
JRNL01
JRNL02
For
four
journal
data
sets:
VOL1
VOL2
VOL3
VOL4
JRNL01
JRNL01
JRNL03
JRNL03
JRNL02
JRNL02
JRNL04
JRNL04
VOL1
VOL2
JRNL01
JRNL03
JRNL02
JRNL04
For
eight
journal
data
sets:
VOL1
VOL2
VOL3
VOL4
JRNL01
JRNL01
JRNL03
JRNL03
JRNL02
JRNL02
JRNL04
JRNL04
VOL5
VOL6
VOL7
VOL8
JRNL05
JRNL05
JRNL07
JRNL07
JRNL06
JRNL06
JRNL08
JRNL08
VOL1
VOL2
JRNL01
JRNL03
JRNL02
JRNL04
VOL3
VOL4
JRNL05
JRNL07
JRNL06
JRNL08
For
16
journal
data
sets:
VOL1
VOL2
VOL3
VOL4
JRNL01
JRNL01
JRNL03
JRNL03
JRNL02
JRNL02
JRNL04
JRNL04
VOL5
VOL6
VOL7
VOL8
JRNL05
JRNL05
JRNL07
JRNL07
JRNL06
JRNL06
JRNL08
JRNL08
VOL9
VOL10
VOL11
VOL12
JRNL09
JRNL09
JRNL11
JRNL11
JRNL10
JRNL10
JRNL12
JRNL12
VOL13
VOL14
VOL15
VOL16
JRNL13
JRNL13
JRNL15
JRNL15
JRNL14
JRNL14
JRNL16
JRNL16
VOL1
VOL2
JRNL01
JRNL03
JRNL02
JRNL04
VOL3
VOL4
JRNL05
JRNL07
JRNL06
JRNL08
VOL5
VOL6
JRNL09
JRNL11
JRNL10
JRNL12
VOL7
VOL8
JRNL13
JRNL15
JRNL14
JRNL16
Chapter
4.
Setting
Up
the
Extended
Remote
Copy
Environment
45
Related
reading:
For
additional
information
about
optimizing
XRC
performance,
see
“Maximizing
Access
to
Journal
Data
Sets”
on
page
52.
Specifying
the
Control
Data
Set
The
recovery
operation
uses
the
control
data
set
to
determine
what
data
XRC
must
still
write
to
the
secondary
volumes.
The
control
data
set
contains
control
records
that
indicate:
v
The
last
set
of
data
that
is
written
to
the
secondary
volumes
v
The
amount
of
unwritten
data
that
exists
in
the
journal
v
The
location
of
this
unwritten
data
XRC
uses
a
control
data
set
name
in
one
of
the
following
forms:
The
XRC
session
ID
can
be
up
to
eight
characters
long
and
must
be
the
same
name
that
you
will
specify
with
the
session_id
parameter
of
the
XSTART
command.
Example:
The
following
is
an
example
of
a
control
data
set
name:
Guidelines:
Use
the
following
guidelines
to
allocate
the
control
data
set:
v
Place
the
control
data
set
on
a
different
volume
from
the
journal
data
sets.
v
Allocate
the
control
data
set
without
defining
secondary
extents.
Specifying
the
State
Data
Set
The
state
data
set
defines
and
contains
the
status
of
the
XRC
session
and
of
associated
volumes
pairs
that
XRC
is
currently
managing.
The
state
data
set
is
updated
whenever
an
XADDPAIR,
XDELPAIR,
XSET,
XSUSPEND,
XRECOVER,
or
XEND
command
is
issued,
or
whenever
a
volume
state
changes.
XRC
uses
a
state
data
set
name
in
one
of
the
following
forms:
Rule:
The
XRC
session
ID
can
be
up
to
eight
characters
long
and
must
be
the
same
name
that
you
will
specify
with
the
session_id
parameter
of
the
XSTART
command.
Example:
The
following
is
an
example
of
a
state
data
set
name:
SYS1.XCOPY.session_id.CONTROL
or
hlq.XCOPY.session_id.CONTROL
SYS1.XCOPY.DALLAS.CONTROL
SYS1.XCOPY.session_id.STATE
or
hlq.XCOPY.session_id.STATE
SYS1.XCOPY.DALLAS.STATE
46
z/OS
V1R3.0
DFSMS
Advanced
Copy
Services
Guidelines:
The
following
are
guidelines
for
the
state
data
set:
v
Allocate
the
state
data
set
on
disk
as
an
SMS-managed
partitioned
data
set
extended
(PDSE)
data
set
with
the
following
attributes:
v
Allocate
ten
tracks
per
storage
control
session.
Try
to
plan
for
expected
future
growth
when
you
initially
allocate
the
state
data
set,
as
it
may
be
inconvenient
to
reallocate
it
later.
v
Allocate
one
track
for
each
volume
pair
in
the
storage
control
session,
again
planning
for
expected
future
growth.
For
volumes
that
have
a
larger
capacity
than
a
3390
Model
3
(3339
cylinders),
allocate
one
additional
track
for
every
3000
additional
cylinders.
Because
XRC
posts
an
error
if
the
state
data
set
runs
out
of
space,
ensure
that
the
allocation
size
is
sufficient
to
prevent
this
situation.
You
cannot
add
additional
storage
control
sessions
or
volume
pairs
if
there
is
insufficient
space
in
the
state
data
set,
nor
will
you
be
able
to
couple
a
session
to
a
master
session.
Perform
the
following
steps
to
allocate
a
new,
larger
data
set:
1.
Issue
XSUSPEND
session_id
TIMEOUT(hh.mm.ss)
2.
Copy
all
members
from
existing
state
data
set
to
the
new,
larger
data
set.
3.
Rename
the
existing
state
data
set
to
an
unused
name.
4.
Rename
the
new,
larger
data
set
to
the
pre-existing
state
data
set
name.
5.
Issue
XSTART
and
resume
XRC
operations.
Note:
Some
environments
can
benefit
from
specifying
a
STORCLAS
parameter
to
ensure
that
SMS
allocates
the
state
data
set
to
the
proper
SMS-managed
volume.
Related
reading:
For
additional
information
about
the
syntax
for
specific
commands,
see
Chapter
5,
“Extended
Remote
Copy
Command
Descriptions,”
on
page
55.
Creating
a
PARMLIB
Data
Set
The
main
purpose
of
creating
a
PARMLIB
data
set
is
to
provide
a
single
method
to
specify
parameters
for
each
system
in
a
multisystem
environment,
without
modifying
the
ANTXIN00
member
of
SYS1.PARMLIB.
XRC
uses
a
PARMLIB
data
set
name
in
one
of
the
following
forms:
hlq.XCOPY.PARMLIB
or
SYS1.XCOPY.PARMLIB
Guideline:
Allocate
hlq.XCOPY.PARMLIB
as
RECFM
fixed,
with
Chapter
4.
Setting
Up
the
Extended
Remote
Copy
Environment
47
Copying
the
Catalog
and
Control
Data
Sets
You
can
ensure
faster
disaster
recovery
if
you
use
remote
copy
functions
to
copy
volumes
that
contain
the
master
catalog,
key
user
catalogs,
and
system
control
data
sets
to
the
recovery
system.
Remote
copy
automatically
copies
all
data
sets
on
the
managed
volumes.
Managed
volumes
can
include
catalog
data
sets
and
control
data
sets.
XRC
can
copy
any
data
set
type,
which
includes
JES
spool,
JES
checkpoint,
system
volumes,
and
paging
volumes.
Specifying
XRC
Utility
Volumes
XRC
utility
volumes
are
specified
according
to
the
configuration
of
the
storage
subsystem.
See
Table
19
when
specifying
XRC
utility
volumes.
For
more
information,
see
“Using
XRC
Utility
Devices”
on
page
129.
Table
19.
Decision
process
for
utility
volume
specification
If
DISP
Specifies
how
XRC
writes
the
XQUERY
output
to
the
data
set,
as
follows:
MOD
Specifies
that
XRC
append
the
output
to
the
data
set.
OLD
Specifies
that
XRC
clear
the
data
set
before
it
receives
output.
SHR
Specifies
that
XRC
clear
the
data
set
before
it
receives
output.
SHR
also
allows
multiple
allocations
of
the
same
data
set.
If
you
specify
DISP,
you
must
also
specify
DATASET.
CONFIGURATION
Specifies
that
XRC
generate
a
configuration
report
to
provide
the
details
of
the
XRC
session
configuration.
CONFIGURATION
is
mutually
exclusive
with
the
SET,
STORAGECONTROL,
ENVIRONMENT,
and
VOLUME
parameters
(VOLUME,
however,
is
a
valid
subparameter
of
CONFIGURATION).
If
you
specify
only
the
CONFIGURATION
parameter,
XRC
generates
a
report
on
the
entire
configuration.
You
can
use
combinations
of
the
ERRORLEVEL,
SCSESSION,
SSID,
and
VOLUME
parameters
on
a
single
configuration
report.
The
report
will
include
the
volumes
that
meet
all
of
the
specified
filters.
ERRORLEVEL
Specifies
that
the
requested
report
displays
only
volumes
that
are
defined
with
the
specified
error
level
(session,
volume,
or
group_name).
If
you
do
not
specify
ERRORLEVEL,
the
requested
report
will
contain
a
list
of
all
volumes
which
meet
the
specified
report
criteria.
SCSESSION
Specifies
that
the
requested
report
displays
volumes
that
are
associated
with
the
storage
control
session
that
is
specified
by
session_name.
This
parameter
is
only
valid
for
the
VOLUME
or
CONFIGURATION
reports.
SSID
Specifies
that
the
requested
report
displays
only
volume
pairs
that
are
associated
with
the
storage
control
that
matches
the
specified
SSID.
If
you
do
not
specify
SSID,
the
requested
report
contains
a
list
of
all
volumes
that
meet
the
specified
report
criteria.
You
can
request
a
report
that
is
based
on
the
primary
or
secondary
SSID.
VOLUME
Specifies
that
the
requested
report
displays
only
volumes
that
meet
the
specified
volume
serial
number
criteria,
as
well
as
any
other
specified
78
z/OS
V1R3.0
DFSMS
Advanced
Copy
Services
report
criteria.
The
VOLUME
parameter
has
the
following
options:
v
VOLUME(volser)
provides
a
report
of
the
primary
or
secondary
volume
or
list
of
volumes
that
meet
the
specified
criteria.
v
VOLUME(volser*)
provides
a
report
of
the
primary
volumes
that
match
a
single
volume
serial
number
prefix.
Specify
the
prefix
with
one
to
five
characters
that
are
followed
by
an
asterisk
(wildcard
character).
v
VOLUME(ALL)
provides
a
report
of
all
volumes
in
the
session
that
meet
the
specified
criteria.
v
VOLUME(*)
provides
a
report
of
all
volumes
in
the
session
that
meet
the
specified
criteria
and
that
also
match
the
character
and
asterisk
(wildcard)
pattern
specified
with
//XSTART
EXEC
Primary System
Primary System
Primary System
Recovery System
Recovery System
Recovery System
Data Mover
Data Mover
Data Mover
Primary System
Primary System
Primary System
Recovery System
Recovery System
Recovery System
Data Mover
Data Mover
Data Mover
Figure
7.
CXRC
configuration
with
system
data
mover
at
primary
site
Chapter
8.
Managing
Coupled
Extended
Remote
Copy
Sessions
173
Locating
the
system
data
mover
on
a
remote,
separate
host
at
the
primary
site
is
an
option
for
configuring
your
CXRC
environment,
as
shown
in
Figure
8.
There
is
a
certain
measure
of
safety
built
into
having
your
SDM
located
on
a
separate
host
from
your
primary
system,
even
if
the
hosts
are
at
the
same
site.
You
run
the
risk,
however,
of
the
same
disasters
impacting
the
remote
recovery
host
that
affect
the
primary
application
host.
This
option
is
valid
for
early
CXRC
configuration
testing
or
for
special
testing
at
any
time.
System
Data
Mover
Boundaries
Ideally,
it
is
best
to
split
volumes
so
that
the
SDMs
receive
an
equal
workload
distribution,
either
by
the
disk
subsystem
or
by
the
subsystem
identifiers
(SSIDs).
In
general,
most
customers
split
mirrored
volumes
among
multiple
SDMs
at
the
disk
subsystem
level
to
simplify
the
allocation
of
volume
pairs
to
an
SDM.
If
you
prefer
a
finer
level
of
granularity,
then
splitting
at
the
SSID
level
is
also
feasible.
Assigning
volumes
to
different
SDMs
on
a
logical
storage
subsystem
(LSS)
boundary
should
give
you
enough
options
to
reasonably
distribute
activity
over
available
SDMs.
Primary System
Primary System
Primary System
Recovery System
Recovery System
Recovery System
Data Mover
Data Mover
Data Mover
176
z/OS
V1R3.0
DFSMS
Advanced
Copy
Services
XRC
uses
the
master
data
set
name
in
one
of
the
following
forms:
v
SYS1.XCOPY.msession_id.MASTER
v
mhlq.XCOPY.msession_id.MASTER
Where:
msession_id
Specifies
the
same
name
that
you
issued
with
the
MSESSION
parameter
of
the
XCOUPLE
ADD
command.
The
name
can
be
up
to
eight
characters
long.
The
name
you
specify
for
the
msession_id
cannot
be
the
same
as
any
session_id.
mhlq
Specifies
the
name
of
the
master
data
set
high-level
qualifier
that
is
specified
on
the
MHLQ
parameter
of
the
XCOUPLE
ADD
command.
The
mhlq
must
be
one
to
eight
characters,
and
can
be
any
name
acceptable
to
TSO.
“SYS1”
is
the
default
value.
You
can
change
the
default
mhlq
to
a
name
that
corresponds
with
the
MHLQ
that
is
issued
on
the
XCOUPLE
command.
When
you
issue
the
XSUSPEND,
XEND,
or
XQUERY
commands
with
the
MASTER
option,
use
the
MHLQ
parameter.
The
following
is
an
example
of
a
master
data
set
name:
SYS1.XCOPY.DALLAS.MASTER
Using
Journal,
State,
and
Control
Data
Sets
There
are
special
considerations
for
journal,
state,
and
control
data
sets
when
you
work
with
master
data
sets
in
CXRC.
In
a
CXRC
environment,
each
SDM
uses
its
own
journal,
state,
and
control
data
sets.
Place
these
data
sets
so
a
performance
bottleneck
is
not
created
due
to
contention
between
the
multiple
SDMs
for
the
same
channel
path,
disk
subsystem,
or
volume
resources.
Example:
Suppose
you
have
four
primary
disk
subsystems,
generating
100
MB
per
second
update
rate
and
two
separate
SDMs,
each
managing
two
disk
subsystems.
By
placing
the
journal
data
sets
for
both
SDMs
on
a
common
disk
subsystem,
that
subsystem
will
experience
a
400®
MB
per
second
update
rate.
The
channel
paths,
disk
subsystem,
and
volumes
must
be
able
to
manage
this
update
rate.
Guidelines:
Consider
the
following
guidelines
when
using
journal,
state,
and
control
data
sets
in
a
coupled
environment:
v
Allocate
the
journal,
control,
and
state
data
sets
for
the
individual
sessions
in
the
same
manner
as
the
existing
support.
v
Add
a
new
member
to
the
state
data
set
to
indicate
that
the
session
is
coupled
and
to
allow
the
XSTART
command
to
process
the
XCOUPLE
ADD
command
automatically
during
restart.
On
a
new
start,
this
member
is
used
to
uncouple
the
session.
Note:
The
size
of
this
new
state
data
set
member
is
small
and
does
not
affect
the
size
requirements
for
the
state
data
set.
v
Define
from
eight
to
16
journal
data
sets
to
improve
the
efficiency
of
XRC
in
a
large
coupled
environment.
v
Allocate
the
control
data
set
using
physical
sequential
allocation.
Note:
The
state
data
set
is
updated
whenever
you
issue
XCOUPLE
ADD,
XCOUPLE
DELETE,
and
XCOUPLE
PURGE
commands.
Chapter
8.
Managing
Coupled
Extended
Remote
Copy
Sessions
177
If
there
is
insufficient
space
in
the
state
data
set,
you
will
not
be
able
to
couple
an
XRC
session
to
a
master
session.
To
allocate
a
new,
larger
state
data
set,
perform
the
following
steps:
1.
Issue
XSUSPEND
msession_id
TIMEOUT(hh.mm.ss).
2.
Copy
all
members
from
the
existing
state
data
set
to
the
new,
larger
data
set.
3.
Rename
the
existing
state
data
set
to
an
unused
name.
4.
Rename
the
new,
larger
data
set
to
the
name
of
the
pre-existing
state
data
set.
5.
Issue
the
XSTART
command
and
resume
XRC
operations.
Managing
Coupled
XRC
Operations
This
section
contains
the
following
information
about
managing
coupled
XRC
operations:
Topic
yy
IEE094D
SPECIFY
OPERAND(S)
FOR
DUMP
COMMAND
R
SDATA=(ALLNUC,PSA,SQA,CSA,LPA,TRT,SUM,LSQA,RGN),END
(’ANTAS*’)),DSPNAME,SDATA),END
FlashCopy Withdraw
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
Summary of Changes
Summary of Changes for SC35-0428-04 z/OS Version 1 Release 3
New Information
Summary of Changes for SC35-0428-03 z/OS Version 1 Release 3
New Information
Changed Information
In this Chapter
Extended Remote Copy (XRC)
Peer-to-Peer Remote Copy (PPRC)
Combining Copy Services Operations
Chapter 2. What is Remote Copy?
In this Chapter
Recovering from a Disaster without Remote Copy
Recovering with Remote Copy
Restrictions for Migrating Data
Deciding which Remote Copy Option to Use
Choosing Extended Remote Copy
Choosing Peer-to-Peer Remote Copy
How Synchronous PPRC Works
How Asynchronous PPRC Works
In this Chapter
Address Spaces for XRC
XRC Session State Descriptions
XRC Data Sets
Defining Storage Requirements
Virtual Storage Requirements
Real Storage Requirements
Paging Space Requirements
Determining the Recovery Site Storage Capacity
Determining Recovery System Access to Resources
Establishing Storage Subsystem Channel Connections
Establishing XRC ESCON Connections
Estimating XRC System Resources for System Data Mover Operations
Allocating XRC Journal Data Sets
Protecting Access to XRC Commands
Chapter 4. Setting Up the Extended Remote Copy Environment
In This Chapter
Controlling ICKDSF Activity to XRC Volumes
Controlling Access to XRC Commands
Placing TSO Commands in an RACF-Protected Library
Defining Resource Profiles in the RACF Facility Class
Including XRC TSO Commands in Automated Procedures
Specifying XRC Journal, Control, and State Data Sets
Specifying the Journal Data Sets
Required Specifications
Recommended Specifications
Copying the Catalog and Control Data Sets
Specifying XRC Utility Volumes
Balancing Storage Control Configurations
Chapter 5. Extended Remote Copy Command Descriptions
In This Chapter
XADDPAIR–Adding Volume Pairs or Utility Volumes
XADDPAIR Command Syntax
XADDPAIR Command Examples
XQUERY–Querying a Session
XRECOVER–Recovering Data On the Recovery System
XRECOVER Command Syntax
XRECOVER Command Example
XSUSPEND Command Syntax
XSUSPEND Command Examples
Chapter 6. Administering Your Extended Remote Copy Environment
In This Chapter
PARMLIB Members
Flag Parameters
Patch Parameters
XQUERY ENVIRONMENT(FLAG) Report
XQUERY ENVIRONMENT(PARM) Report
XQUERY ENVIRONMENT(PATCH) Report
In This Chapter
Workload Balancing
Application Protection
Fixed Utility Devices
Floating Utility Devices
Initializing Volume Pairs
Adding a Volume With the FULLCOPY or QUICKCOPY Option
Use the QUICKCOPY Option With Caution
Adding a Volume With the NOCOPY Option
Use the NOCOPY Option With Caution
Adding a Volume With the SUSPENDED Option
Adding a Volume with the DONOTBLOCK Option
Understanding the XADDPAIR Command
Example: Use a CLIST to Start an XRC Session
Using the ATTIME, DRAIN, and IMMEDIATE Keywords
Deleting an XRC Volume Pair
Using Tertiary XRC Volumes
Using the XSUSPEND Command
Suspending XRC Volume Pairs
Suspending an XRC Session
Managing Cache Resources on Storage Subsystems That Support Hardware Bitmaps
Managing Cache Resources on Storage Subsystems That Do Not Support Hardware Bitmaps
Avoiding Deadlock Conditions
Adding Back Specific Suspended Volume Pairs
Adding Back All Suspended Volume Pairs
Adding a Suspended Utility Volume Back to the Storage Control Session
Using XRC With FlashCopy
Running the ICKDSF Program
Using XRC XQUERY Reports
XQUERY Summary Report
XQUERY Volume Report
XQUERY Summary Report
XQUERY Volume Report
XQUERY Set Report
Accessing Secondary Volumes While XRC is Active
Ending an XRC Session
Applying XRC Operational Scenarios
Example: Changing a Volume Pair's Error Recovery Level
Example: Suspending and Resynchronizing a Volume Pair
Example: Suspending and Resynchronizing a Session
Example: Changing Volume Channel Connection Addresses
Alerting the System Data Mover to a Changed Volume CCA
Examples: Changing TIMEOUT Intervals for Suspended Sessions
Changing XSUSPEND TIMEOUT Intervals
Identifying XRC System Interactions
Chapter 8. Managing Coupled Extended Remote Copy Sessions
In This Chapter
Overview of CXRC
Identifying Sessions in a Coupled Environment
Choosing a Coupled XRC Configuration
System Data Mover Boundaries
Defining Master Data Sets in a Coupled Environment
Allocating the CXRC Master Data Set
Changing the Characteristics of a Master Data Set
Specifying the Master Data Set
Using Journal, State, and Control Data Sets
Managing Coupled XRC Operations
Querying Coupled Status for XRC Sessions
Creating a Backup Copy of Secondary Volumes (XADVANCE)
Using the XADVANCE Command
Restarting an Inactive XRC Coupled Session
Example: Restarting an Inactive XRC Coupled Session After an Error Occurs
What to Do if the Master Session is in Coupled HOLD Status
Determining Coupled HOLD Status
Entering Coupled HOLD Status
Restrictions When the Master Session Is in Coupled HOLD Status
Clearing a Master Session From Coupled HOLD Status
Example: Resuming Operations After a Sympathetic Suspension
Using the XCOUPLE RELEASE Command
XCOUPLE RELEASE Command Considerations
What to Do if a Session is in COUPLE_FAILED Status
Removing the XCOUPLE_FAILED Status for a Session
Removing Coupled Sessions
Generating Dumps of Address Spaces
Steps for Generating Multiple Dumps in a Single LPAR
Generating Dumps Across Multiple LPARs
Applying CXRC Operational Scenarios
Example: Applying Software Maintenance in a Coupled Environment
Chapter 9. Extended Remote Copy Data Recovery Operations
In This Chapter
Overview of Consistency Group Time
Terms Used for Consistency Group Time
Changes to Consistency Group Time
Example: Illustration of Consistency Group time
Understanding the Importance of Timestamped Writes
Recovering Data with XRC—Uncoupled and Coupled Sessions
Recovering Data with XRC
Advancing Consistency Time Using the XADVANCE Command
Chapter 10. Migrating Data With Extended Remote Copy
In This Chapter
Migration Operation Considerations
Chapter 11. Recovering from Error Conditions Using Extended Remote Copy
In This Chapter
Comparing the ERRORLEVEL Options
Steps for Recovering From Environmental Errors
Steps for Recovering From Processor, Address Space, and XRC Data Set Failures
Part 3. Peer-to-Peer Remote Copy
Chapter 12. Planning for Peer-to-Peer Remote Copy
In This Chapter
Determining PPRC Resource Needs
Steps for Evaluating How PPRC Affects the Primary Storage Subsystem
Evaluating How PPRC Affects the Recovery Storage Subsystem
Determining the Recovery Site Storage Capacity
Determining Recovery System Access to Resources
Establishing Storage Subsystem Channel Connections
Establishing PPRC ESCON Connections
Establishing PPRC FCP Connections
Controlling Access to PPRC Commands
Chapter 13. Setting Up the Peer-to-Peer Remote Copy Environment
In This Chapter
Steps for Placing TSO Commands in a RACF-Protected Library
Controlling ICKDSF Activity to PPRC Volumes
Steps to Perform an ICKDSF Repair on a PPRC-Managed Primary Volume:
Steps to Perform an ICKDSF Repair on a PPRC-Managed Secondary Volume:
Identifying Volume Pairs
Configuring Storage Subsystem Resources for PPRC
Configuring IBM Storage Controls
Attaching a Recovery Site Storage Control to a Host System
Using Remote Power Sequence Control Cables
Accessing PPRC Secondary Volumes
In This Chapter
PPRC Command Overview
CDELPAIR – Deleting Pairs
CDELPAIR Command Syntax
CRECOVER Command Syntax
In This Chapter
DEVSERV and IDCAMS
Establishing PPRC Paths
General Overview for Establishing ESCON Paths
Managing Volumes and Paths
Querying PPRC Volumes
CQUERY Formatted Output for a SIMPLEX Device, Level 3, ESCON Format
CQUERY Formatted Output for a Synchronous PPRC Primary Volume
CQUERY Formatted Output for a PPRC Extended Distance Primary Volume
CQUERY Formatted Output for a Synchronous PPRC Secondary Volume
CQUERY Formatted Output for a PPRC Extended Distance Secondary Volume
CQUERY Unformatted Output for a Primary Volume
CQUERY Unformatted Output for a Suspended Secondary Volume
CQUERY Unformatted Output for a Primary Volume on an ESS Enabled for FCP
CQUERY Formatted Output for a Primary Volume on an ESS Enabled for FCP
CQUERY Formatted Output for a Simplex Device with No Paths
CQUERY Formatted Output for a Primary Volume on an ESS Enabled for FCP
Querying PPRC Paths
CQUERY Unformatted Output With the PATHS Option
CQUERY Formatted Output With the PATHS Option
Example: CLIST to Add a PPRC Path, Add a Volume Pair, and Query PPRC
Suspending PPRC Volume Pair Operations
Deleting a PPRC Volume Pair
Deleting PPRC Paths
Setting Up Your Environment to Use PPRC Extended Distance
Ensuring PPRC Paths are Active
Establishing PPRC Volume Pairs
Using PPRC Extended Distance
Long Distance Data Migration
Monitoring PPRC Volume Pairs
Scenarios Using PPRC Extended Distance and Synchronous Mode for Backup Purposes
Using Extended Distance Operation and Converting to Synchronous Operation
Step 1. Establish Consistency at the Volume Level
Step 2. Freeze Updates to the Primary Volume
Step 3. Resume Operations After a Freeze
Step 4. Copy Secondary Volumes
Step 5. Restart Your Applications
Using Synchronous Operation and Then Converting to Extended Distance Operation
Using Extended Distance and Synchronous Modes During peak and Nonpeak Operations
Establish PPRC Volumes in PPRC Extended Distance for Use During Peak Hours
Convert PPRC Volumes to Synchronous Mode During Nonpeak Hours
Convert Back to PPRC Extended Distance Mode During Peak Hours
Chapter 16. Peer-to-Peer Remote Copy Data Recovery Operations
In This Chapter
Resuming Operations at the Recovery Site
Managing Errors During Recovery
Errors Encountered When Writing to PPRC Volumes Established With CRIT(YES)
Errors That Occur in the Absence of Write Activity
Errors That Cause a PPRC Pair to Become Suspended
Chapter 17. Moving and Migrating Data with Peer-to-Peer Remote Copy
In This Chapter
Steps for Migrating Data with PPRC
Steps for Copying the Secondary Volumes with PPRC
Chapter 18. Recovering from Peer-to-Peer Remote Copy Error Conditions
In This Chapter
Putting PPRC Error Recovery Procedures Into Effect
RAMAC Device Sparing With PPRC
Steps to Spare a RAMAC Drawer
Chapter 19. Peer-to-Peer Remote Copy Dynamic Address Switching (P/DAS)
In This Chapter
Steps for Using P/DAS in a Nonsysplex, Shared-Disk Environment
Typical PPRC Configuration After a P/DAS Function has Completed
Steps for Using P/DAS in a Sysplex Environment
Replying to P/DAS-Related Messages
Action A:
Action B:
Action C:
Action D:
In This Chapter
Overview of FlashCopy
How to Determine Fast Replication Eligibility
FlashCopy Requirements
Creating a Backup Copy of Your Data Using FlashCopy
Displaying Information About FlashCopy Volumes
Withdrawing FlashCopy Relationships
FlashCopy V2 Withdraw Options
Using FlashCopy TSO Commands
Controlling Access to FlashCopy Commands
Steps for Placing TSO Commands in a Library Protected by RACF
FlashCopy Establish (FCESTABL) Command
In This Chapter
SnapShot Copy Requirements
Making Cache Available
Using SnapShot Copy
Copying Data With SnapShot Copy
Moving Data Sets With SnapShot Copy
Determining How DFSMSdss Determines Volume Eligibility for Fast Replication Operations
Using SnapShot Copy, PPRC, and RVA Together
SnapShot SMF Information
In This Chapter
Concurrent Copy Requirements
Concurrent Copy With Shared Storage Subsystems
Determining Concurrent Copy Hardware Requirements
Determining Concurrent Copy Resource Needs
Central and Expanded Storage
Storage Subsystem Cache
Restarting System Data Mover Address Spaces (SDM, XRC, CC, SnapShot)
Diagnosing System Data Mover Functions with the MVS MODIFY Command
AUTO_READD Operation (XRC)
Peer-to-Peer Remote Copy Diagnostic Aids
Appendix B. Configuring the System Data Mover and PPRC Options on IBM 3990 and 9390 Storage Controls
Appendix C. SMF Type 42 Records
XRC Information in SMF Type 42 Records
Concurrent Copy Information in SMF Type 42 Records
Concurrent copy SMF type 42 subtype 4 records
Appendix D. Advanced Copy Services Messages
Appendix E. ANTRQST Macro – Call to the System Data Mover API
Environment
Subparameters for REQUEST=LEVEL
Subparameters for REQUEST=FCESTABLISH
Subparameters for REQUEST=FCQUERY
Subparameters for REQUEST=FCWITHDRAW
Subparameters for REQUEST=QFRVOLS
Subparameters for REQUEST=PDELPAIR
Subparameters for REQUEST=PDELPATH
Subparameters for REQUEST=PESTPAIR
Subparameters for REQUEST=PESTPATH
Subparameters for REQUEST=PFREEZE
Subparameters for REQUEST=PQUERY
Subparameters for REQUEST=PRECOVER
Subparameters for REQUEST=PRUN
Subparameters for REQUEST PSUSPEND
Subparameters for REQUEST=SDVCINFO
Subparameters for REQUEST=SQRYDVCS
Subparameters for REQUEST=SQRYSSYS
Subparameters for REQUEST=SRELEASE
Subparameters for REQUEST=SSNAP
Subparameters for REQUEST=XADD
Subparameters for REQUEST=XADVANCE
Subparameters for REQUEST=XCONTIME
Subparameters for REQUEST=XCOUPLE
Subparameters for REQUEST=XDEL
Subparameters for REQUEST=XEND
Subparameters for REQUES=XQUERY
Subparameters for REQUEST=XRECOVER
Subparameters for REQUEST=XSCSTATS
Subparameters for REQUEST=XSET
Subparameters for REQUEST=XSTART
Subparameters for REQUEST=XSUSPEND
ANTQFVRL MACRO
ABEND Codes
Return and Reason Codes
Example: Getting the Current Consistency Time for XRC Session TUCSON in Assembler
Appendix F. Accessibility
Using assistive technologies
Notices

Documents

z/OS V1R3.0 DFSMS Advanced Copy Services