Академический Документы
Профессиональный Документы
Культура Документы
Software
Operating System
z/OS family
APARs - OS/390
environment
Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the Operating system(s):
APAR, along with a link to the fix after it becomes available. You can track
this item individually or track all items by product. MVS, OS/390, z/OS
Notify me when this APAR changes.
Software version:
Notify me when an APAR for this component changes.
001
Subscribe
Reference #:
II13354
APAR status
IBM Group:
INTRAN
IBM Server Group
Error description
This informational apar provides step by step procedures Modified
for date:
moving catalogs from one volume to another. This apar further
2010-07-06
expands on the examples provided in the DFSMS manual "Managing
Catalogs" including considerations for shared catalogs.
These are also the same steps that should be used when reorging
a catalog. The only difference between a reorg and a move is the
volume the catalog is on at the end of the process.
.
When moving a catalog there are slightly different processes
depending on whether the catalog is on a single system, or is
shared across systems. This will cover three common system
configurations. The first configuration is a single system, the
second is multiple systems with each system having it's own
master catalog and the third is multiple systems with a single
shared master catalog.
.
Before moving any catalog always:
1. Ensure you have a good backup of a valid catalog. Use of
IDCAMS DIAGNOSE and EXAMINE on the catalog and correcting
any errors before taking the backup will ensure you can
fall back to a valid backup if there are problems. Having
more than one copy is always a good idea in case one copy
becomes damaged or lost. This backup can be a full volume
dump of the volume the catalog is on, a DFDSS backup or
IDCAMS EXPORT. Having all three gives you more options if
you need to back out of the catalog move.
2. Ensure through the use of IDCAMS DIAGNOSE and EXAMINE that
the catalog does not have errors.
3. An IDCAMS LISTCAT ALL of the catalog to be moved is always
a good idea in case there are problems. Since this may
produce a large volume of output you may wish to consider
redirecting the output to a dataset either by pointing the
SYSPRINT DD statement to a dataset, or by use of the OFILE
keyword on the LISTCAT command.
4. If you are moving a catalog that is shared across systems,
a LISTCAT of the master catalog with ALL keyword is needed
to enable a redefine of any aliases that point to the user
catalog that is being moved, unless you already have a job
setup to define the aliases. If you already have a job
verify that it is current by comparing the LISTCAT output
to the job.
Note: EXPORT DISCONNECT is recommended in several of the
examples but it does delete the alias entries in the ucat
connector record making a redefine of them necessary.
Instead, you can use IMPORT CONNECT w/ALIAS on the systems
other than the one you are working with the catalog on.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II13354
Reported component ID
INFOV2LIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2002-07-16
Closed date
Fix information
Applicable component levels
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or other companies. A current list
of IBM trademarks is available on the Web at "Copyright and trademark
information" at www.ibm.com/legal/copytrade.shtml.