CA CREWS™ Catalog Recovery
User Guide
r4.5
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■
CA CREWS™ Catalog Recovery (CA CREWS)
■
CA Disk™ Backup and Restore (CA Disk)
■
CA Graphical Management Interface (CA GMI)
■
CA Vantage™ Storage Resource Manager (CA Vantage SRM)
■
CA Workload Automation CA 7® Edition (CA 7)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■
Online and telephone contact information for technical assistance and customer
services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you
can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.
Contents
Chapter 1: Introduction
11
Description ................................................................................................................................................................. 11
Working in the Automated Catalog Environment ............................................................................................... 11
Backing Up and Restoring Catalogs ..................................................................................................................... 12
Recovering Catalogs ............................................................................................................................................ 12
Correcting Aliases................................................................................................................................................ 12
Deleting Scratched Data Sets .............................................................................................................................. 13
Recataloging or Deleting Uncataloged Data Sets ................................................................................................ 13
Automated IDCAMS DIAGNOSE .......................................................................................................................... 13
Merging User Catalogs ........................................................................................................................................ 14
Rebuilding User Catalogs .................................................................................................................................... 14
Reorganizing User Catalogs ................................................................................................................................. 14
Synchronizing Master Catalogs ........................................................................................................................... 14
Interfacing with CA Vantage SRM ....................................................................................................................... 15
Record Necessary SMF Record Types ........................................................................................................................ 15
Required Record Types ....................................................................................................................................... 15
Optional Record Types ........................................................................................................................................ 16
JCL Requirements ....................................................................................................................................................... 16
Chapter 2: Using the Catalog Checkup Tool (CREWSCHK)
17
How the Catalog Checkup Tool Works ....................................................................................................................... 17
When to Run the Catalog Checkup Tool ............................................................................................................. 18
Required JCL ............................................................................................................................................................... 19
Control Statements .................................................................................................................................................... 19
EXTENT(n)............................................................................................................................................................ 19
VOLCAP(n) ........................................................................................................................................................... 20
CISPLIT(n) ............................................................................................................................................................ 20
CASPLIT(n) ........................................................................................................................................................... 20
CREWSCHK Example............................................................................................................................................ 20
CREWSCHK Report Description ........................................................................................................................... 21
Chapter 3: Working in the Automated Catalog Environment (ACE)
23
How ACE Works .......................................................................................................................................................... 24
Exception Solutions ............................................................................................................................................. 24
Required JCL ............................................................................................................................................................... 25
Control Statements .................................................................................................................................................... 27
Contents 5
CATALOG(catalogname) ...................................................................................................................................... 27
VOLUME(volser) .................................................................................................................................................. 28
ARCSYS(sysname) ................................................................................................................................................ 28
ARCVOL(volser) ................................................................................................................................................... 28
DELAY(days) ........................................................................................................................................................ 29
NOTAPE ............................................................................................................................................................... 29
BUFFERS(n) .......................................................................................................................................................... 29
BUFSIZE(n) ........................................................................................................................................................... 29
SUMMARY(opt) ................................................................................................................................................... 29
LOG(task)............................................................................................................................................................. 29
TASKS(n) .............................................................................................................................................................. 30
TIMEOUT(n)......................................................................................................................................................... 30
TRACE | TRACEDSN(dsn) ..................................................................................................................................... 30
Batch Operation ......................................................................................................................................................... 30
Exception Analysis ............................................................................................................................................... 30
CREWSABT Jobstream ......................................................................................................................................... 31
Control Statements ............................................................................................................................................. 31
Online Operation ........................................................................................................................................................ 35
Exception and Analysis ........................................................................................................................................ 35
Main Panel .......................................................................................................................................................... 35
Chapter 4: Merging User Catalogs
41
JCL Requirements ....................................................................................................................................................... 41
Control Statements .................................................................................................................................................... 42
MERGE ................................................................................................................................................................ 42
Options ....................................................................................................................................................................... 42
Examples .................................................................................................................................................................... 42
Example 1 ............................................................................................................................................................ 43
Example 2 ............................................................................................................................................................ 43
Example 3 ............................................................................................................................................................ 43
Example 4 ............................................................................................................................................................ 44
More Examples ................................................................................................................................................... 44
Return Codes .............................................................................................................................................................. 45
Chapter 5: Protecting and Fixing Catalogs
47
Protection Functions .................................................................................................................................................. 47
Back Up Catalogs ................................................................................................................................................. 47
Restore Catalogs ................................................................................................................................................. 48
Recover Catalogs ................................................................................................................................................. 49
6 User Guide
Chapter 6: Verifying Protection Functions
53
Verify Catalog Backup ................................................................................................................................................ 53
Backup Summary Report..................................................................................................................................... 53
Backup Summary Report Explained .................................................................................................................... 54
Verify Catalog Backup Procedure ........................................................................................................................ 54
Verify Catalog Restore................................................................................................................................................ 54
Restore Summary Report .................................................................................................................................... 55
Restore Summary Report Explained ................................................................................................................... 55
Verify Catalog Restore Procedure ....................................................................................................................... 55
Verify Catalog Recovery ............................................................................................................................................. 56
SMF Gap Reports................................................................................................................................................. 56
Chapter 7: Backing Up, Restoring, and Recovering Reference
59
Back Up Catalogs Reference....................................................................................................................................... 59
JCL Requirements ................................................................................................................................................ 59
Control Statements ............................................................................................................................................. 60
Specifying Generic Catalog Names...................................................................................................................... 62
Backup Examples................................................................................................................................................. 62
Restore Catalogs Reference ....................................................................................................................................... 64
JCL Requirements ................................................................................................................................................ 64
Control Statements ............................................................................................................................................. 65
Specifying Generic Catalog Names...................................................................................................................... 67
Restore Examples ................................................................................................................................................ 67
Recover Catalogs Reference....................................................................................................................................... 68
JCL Requirements ................................................................................................................................................ 69
Control Statements ............................................................................................................................................. 70
Specifying Generic Catalog Names...................................................................................................................... 72
Recovery IDCAMS Requirements ........................................................................................................................ 73
Recover Examples ............................................................................................................................................... 73
Chapter 8: Checking and Fixing Functions
77
JCL Requirements ....................................................................................................................................................... 77
Using DIAGNOSE ................................................................................................................................................. 78
DIAGNOSE Control Statement............................................................................................................................. 78
VOLUME(volser) .................................................................................................................................................. 78
Specifying Generic Volumes ................................................................................................................................ 79
CATALOG(catalogname) ...................................................................................................................................... 79
Specifying Generic Catalog Names...................................................................................................................... 80
MASTERPW(password) ....................................................................................................................................... 80
Required DIAGNOSE Output JCL ......................................................................................................................... 81
Contents 7
DIAGNOSE Examples ........................................................................................................................................... 82
Chapter 9: Reporting CA 7 Catalog Dependencies
85
How CA 7 Catalog Dependency Analysis Works ......................................................................................................... 85
Types of CA 7 Catalog Dependencies ......................................................................................................................... 86
Required JCL ............................................................................................................................................................... 87
Control Statements .................................................................................................................................................... 88
CA7ID(id) ............................................................................................................................................................. 89
CA7PSWD(password) .......................................................................................................................................... 89
CA7NODE(ccinode).............................................................................................................................................. 89
CA7SSCT(PROD|TEST) ......................................................................................................................................... 89
SYSTEM(applsys) ................................................................................................................................................. 90
Chapter 10: Rebuilding Catalogs
93
How the Catalog Rebuild Utility Works ...................................................................................................................... 93
JCL Example and Steps ............................................................................................................................................... 93
Job 1: Delete and Lock ........................................................................................................................................ 94
Job 2: Backup, Read/Write, List, and Sort ........................................................................................................... 94
Job 3: Delete, Redefine, Load, Define, and Reconnect ....................................................................................... 97
Chapter 11: Using Real Time Reorg (CREWSRTR)
101
Required JCL ............................................................................................................................................................. 103
Syntax Statements.................................................................................................................................................... 106
Overriding USERCATALOG Parms ............................................................................................................................. 108
Examples .................................................................................................................................................................. 109
Parameters ............................................................................................................................................................... 110
Restart Considerations ............................................................................................................................................. 111
Chapter 12: Synchronizing Master Catalogs
113
How the MCAS Works .............................................................................................................................................. 113
Types of Problems Detected .................................................................................................................................... 114
Inputs and Outputs .................................................................................................................................................. 114
Control Statements .................................................................................................................................................. 116
Control Statement Example .............................................................................................................................. 117
JCL Examples and Steps ............................................................................................................................................ 117
Step 1: Delete Previous Output......................................................................................................................... 118
Step 2: Locate, Read, and Check ....................................................................................................................... 118
Step 3: List Control Statements......................................................................................................................... 119
Step 4: Synchronize Master Catalogs ................................................................................................................ 120
8 User Guide
Chapter 13: Interfacing with CA Vantage SRM
121
CREWSCHK Interface ................................................................................................................................................ 121
CREWSCHK Control Statements ........................................................................................................................ 121
Data Options ..................................................................................................................................................... 122
CREWSCA7 Interface ................................................................................................................................................ 122
CREWSCA7 Control Statements ........................................................................................................................ 122
Data Options ..................................................................................................................................................... 123
CREWSACE/CREWSABT Interface ............................................................................................................................. 123
CREWSACE Control Statements ........................................................................................................................ 123
Reporting Objects ............................................................................................................................................. 124
Index
125
Contents 9
Chapter 1: Introduction
CA CREWS (Catalog Recovery Early Warning System) is designed to assist data center
personnel responsible for managing ICF catalogs. This guide describes how to use CA
CREWS and documents the associated functions and options.
This section contains the following topics:
Description (see page 11)
Record Necessary SMF Record Types (see page 15)
JCL Requirements (see page 16)
Description
CA CREWS is a collection of functions that assist in protecting, checking, and fixing ICF
catalogs. Following are the functions of CA CREWS:
■
Automated Catalog Environment (ACE)
■
Back up Catalogs
■
Restore Catalogs
■
Recover Catalogs
■
Check Alias
■
Check Scratch
■
Check Uncatalog
■
Diagnose
■
Merge User Catalogs
■
Rebuild User Catalogs
■
Reorganize User Catalogs
■
Master Catalog Alias Synchronizer (MCAS)
■
Interface to CA Vantage SRM
Working in the Automated Catalog Environment
The Automated Catalog Environment (ACE) feature automatically gathers data and
analyzes your catalog environment. ACE is useful for daily examination of your catalog
environment.
Chapter 1: Introduction 11
Description
More Information:
Working in the Automated Catalog Environment (ACE) (see page 23)
Backing Up and Restoring Catalogs
CA CREWS uses IDCAMS EXPORT for backup and IDCAMS IMPORT for restore. In
addition, CA CREWS backup and restore have the following usability features:
Aggregate Reference to Catalogs
You can back up or restore either all catalogs or generic groups. Because an ICF
catalog environment can quickly change (it is easy to create and merge catalogs),
you should be able to reference catalogs in ways other than lists of names.
Availability of Backups for Restore
Export backups are stacked in the same backup file, separated by header and trailer
records. This method ensures that groups of backups are always available for
restore.
Recovering Catalogs
CA CREWS uses System Management Facilities (SMF) data to find the update, delete,
and define activity that occurred to catalogs during the recovery period. CA CREWS
builds IDCAMS DELETE, DEFINE, and ALTER commands to update a catalog to its
previous level. The CA CREWS forward recovery mechanism is independent of the CA
CREWS backup and restore. If a catalog is restored by any other means, you can use CA
CREWS to recover it. CA CREWS uses any form of SMF data dump (tape or disk), or reads
the VSAM collection files directly. Also, the aggregate reference to catalog names is
available in recovery, permitting multiple catalogs to be recovered simultaneously.
Correcting Aliases
Data sets must be accessible by the normal catalog search order. Important files can be
lost when they cannot be found through the catalog system, and forgotten files can
occupy valuable disk space. Check Alias finds data sets that are in the wrong user
catalog, or that do not have a valid alias name. Both kinds of data sets can be
independently selected, and their catalog entries can be moved to the correct catalog or
deleted.
12 User Guide
Description
Deleting Scratched Data Sets
Scratched data sets have a valid catalog entry, but cannot be found in the VVDS or the
VTOC of the volume their catalog entry indicates. Check Scratch finds scratched data
sets and generates the necessary IDCAMS commands, leaving only valid entries that
point to active data sets and disk volumes.
Recataloging or Deleting Uncataloged Data Sets
Uncataloged data sets or orphan data sets have a VTOC entry, but cannot be found in
any catalog. Check Uncatalog creates the IDCAMS commands to make these data sets
accessible again by recataloging or corrects catalogs by deleting them.
Check Uncatalog handles VSAM components that exist only in the VTOC. CA CREWS
creates an IMASPZAP jobstream to modify the VTOC entry, making the file a non-VSAM
file. Once the file is non-VSAM, a SCRATCH can remove the entry.
Automated IDCAMS DIAGNOSE
CA CREWS analyzes the output of DIAGNOSE and generates the appropriate IDCAMS
commands to correct the problem. When diagnosing a catalog, CA CREWS does the
following:
■
Finds all volumes that the data sets in that catalog reside on
■
Allocates these volumes
■
Generates the appropriate COMPAREDD parameter to check each volume
When diagnosing a VVDS, CA CREWS finds the names of all catalogs with data sets on
the VVDS volume, and generates the appropriate COMPAREDS parameter to check all
relations of the VVDS.
Chapter 1: Introduction 13
Description
Merging User Catalogs
You can merge one or more ICF user catalogs with other ICF user catalogs. The merge
deletes the old alias catalog pointers, and performs the definition of the catalog aliases
to the new catalog. All VVDS records are modified to reflect the new catalog name for
each dataset within the merged ICF user catalogs.
This tool is useful for catalog administrators to do the following:
■
Organize their ICF catalog environment.
■
Combine and consolidate catalogs to create a more logical catalog structure for
reduced maintenance efforts.
■
Maintain a more streamlined catalog structure.
Rebuilding User Catalogs
The Catalog Rebuild utility is designed to rebuild catalogs in which the data or index
components have been corrupted or the pointers are incorrect.
Reorganizing User Catalogs
The Real Time Reorg utility (CREWSRTR) allows user catalogs to be reorganized without
having to schedule stand-alone time. CREWSRTR will reorganize a user catalog in real
time causing jobs requiring the catalog to wait until the reorganization is complete.
Production schedules are not disrupted to the extent that jobs have to be monitored
and rescheduled when the reorganization is finished.
Synchronizing Master Catalogs
The Master Catalog Alias Synchronizer (MCAS) ensures that the systems' master
catalogs are synchronized to provide the same catalog structure across multiple LPARS,
where master catalogs are being shared in a multi-LPAR environment.
14 User Guide
Record Necessary SMF Record Types
Interfacing with CA Vantage SRM
CA Vantage SRM is an automated storage management system that provides
comprehensive reporting, monitoring, and automation capabilities. CA Vantage SRM
reduces storage-related costs, increases productivity, and improves service levels.
CA CREWS interfaces with CA Vantage SRM. With this bridge, CA Vantage SRM users can
access the following CA CREWS functions:
■
CREWSCHK
■
CREWSACE
■
CREWSABT
■
CREWSCA7
■
Catalog backup, restore, and diagnose
Release Requirements
To use the CA Vantage SRM interface, only the non-licensed CA GMI is required. The CA
GMI is available on the CA Support Online website at https://support.ca.com/.
Record Necessary SMF Record Types
Before you use CA CREWS for catalog recovery, record the necessary SMF record types
as specified in the active SMFPRMxx member of SYS1.PARMLIB.
Required Record Types
The following records are the core of the forward recovery mechanism. CA CREWS
recovery requires that the following SMF record types be recorded:
Record type 60 (3C)
VVDS update record
Record type 61 (3D)
Integrated Catalog Facility define activity
Record type 65 (41)
Integrated Catalog Facility delete activity
Record type 66 (42)
Integrated Catalog Facility alter activity
Chapter 1: Introduction 15
JCL Requirements
Optional Record Types
The forward recovery process uses the following optional SMF record types to detect
time gaps:
0
IPL Records
7
Lost Data Records
36
Catalog Export
90
System Status
To verify that all required SMF records are being recorded, run the CREWSCHK tool.
Note: For more information about recording SMF records, see IBM manuals regarding
System Management Facilities (SMF).
More Information:
Using the Catalog Checkup Tool (CREWSCHK) (see page 17)
JCL Requirements
Guidelines to assist you in preparing your JCL are provided in this manual. The sample
code provided in this manual is intended for reference only. You can copy and modify
these samples for your specific requirements.
The libraries listed for searching must include the following in the order shown:
16 User Guide
1.
User libraries you have defined
2.
Product base libraries
3.
CA Common Services for z/OS base libraries
Chapter 2: Using the Catalog Checkup Tool
(CREWSCHK)
Before you begin the backup process or analyze your catalog environment for errors, a
good high-level perspective about the scope of your effort is desirable. The CREWSCHK
Catalog Checkup tool provides a snapshot of your entire system catalog environment. It
displays all catalogs connected to the target system and various catalog settings.
The Catalog Checkup tool analyzes the environment for potentially hazardous situations.
For example, it ensures the SMF records required for catalog recovery are being
recorded. It also notes other conditions, such as a catalog volume that is running out of
free space.
Note: Run this program as the first step to using CA CREWS. CREWSCHK should also be
run periodically as part of your system monitoring activities.
This section contains the following topics:
How the Catalog Checkup Tool Works (see page 17)
Required JCL (see page 19)
Control Statements (see page 19)
How the Catalog Checkup Tool Works
The Catalog Checkup tool accesses the system environment, but requires no APF
authorization. To do this, it performs the following actions:
■
Interrogates the system's master catalog for all connected catalogs and catalog
aliases.
■
Investigates each catalog separately for various conditions.
■
Examines the volume on which it resides for available free space to ensure room for
catalog growth.
■
Compares its findings with threshold values, highlighting potentially hazardous
conditions.
■
Issues a warning message if any threshold value is exceeded.
Note: You can override any of the default threshold values with optional input
control statements.
■
Produces reports.
Chapter 2: Using the Catalog Checkup Tool (CREWSCHK) 17
How the Catalog Checkup Tool Works
When to Run the Catalog Checkup Tool
In most storage environments, the size and number of the catalogs has grown
significantly. While most system data administrators ensure their catalogs are being
backed up, it is easy to overlook several conditions that could negatively impact the
production environment. You should run the Catalog Checkup tool when the following
conditions occur:
■
The volume on which a catalog resides is nearly full and the catalog requires a
secondary allocation. If insufficient space remains, the secondary allocation fails
and the catalog records are not written. This has the potential to stop your
production environment.
■
A very active catalog is becoming increasingly fragmented through CI and CA splits.
Any access to the catalog is being affected by the fragmentation. The space
allocated to the catalog is not being used efficiently and reorganization of the
catalog is necessary.
■
The SMF records required for a catalog recovery are not being completely recorded.
In a recovery situation, it might be possible to restore the catalog, but a forward
recovery cannot be done because the SMF data is incomplete.
■
Two information processing environments have been merged, causing a variety of
undesirable situations in the catalog environment. When this occurs, normally the
first priority is restoring production to full operation, not verifying the catalog
environment. The Catalog Checkup tool provides a quick verification of the many
critical situations.
Because the Catalog Checkup tool dynamically acquires all of the required catalog
environmental data, there is no need to update the control parameters. You should run
the tool periodically as one of the normal preventive maintenance procedures.
18 User Guide
Required JCL
Required JCL
The following JCL is required for CREWSCHK:
//JOBSTATEMENT JOB
//CREWSCHK EXEC PGM=CREWSCHK
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
*
EXTENT(12)
VOLCAP(98)
CISPLIT(120)
CASPLIT(120)
If a particular threshold is not specified in the SYSIN data stream, the default takes
effect.
JCL Description
EXEC PGM=CREWSCHK
Specifies CREWSCHK as the program name.
STEPLIB
Required if CA CREWS is not in the link list.
SYSPRINT
Required. Specifies a data set for the output report.
SYSIN
Required. Specifies a data set for the control statements.
Note: If DD DUMMY is specified, all of threshold limits are assigned their default
values.
Control Statements
The following control statements set the various threshold values. Limits can be set
according to your own tolerances. If any threshold is exceeded, an associated warning
message is issued and a return code of 4 is given. This lets CREWSCHK be included as
part of your regularly scheduled production with the output being reviewed only when a
non zero return code is generated.
EXTENT(n)
Sets the threshold value for the number of extents. When the number of extents in the
catalog meets or exceeds this value, the FC820W warning message is issued. (n) is a
numeric value between 1 and 255. If omitted, the default is 10.
Chapter 2: Using the Catalog Checkup Tool (CREWSCHK) 19
Control Statements
VOLCAP(n)
Sets the threshold value of space utilization for the volume on which the catalog resides.
When the space utilization meets or exceeds the threshold value, the FC826W warning
message is issued. (n) is a numeric value between 1 and 100. If omitted, the default is
90.
CISPLIT(n)
Sets the threshold value for control interval splits. When the number of control interval
splits in the catalog meets or exceeds this value, the FC822W warning message is issued.
(n) is a numeric value between 1 and 9999. If omitted, the default is 15.
CASPLIT(n)
Sets the threshold value for control area splits. When the number of control area splits
in the catalog meets or exceeds this value, the FC823W warning message is issued. (n) is
a numeric value between 1 and 9999. If omitted, the default is 15.
CREWSCHK Example
In the following example, the Catalog Checkup tool is set up to look for catalogs residing
on volumes that are critically near capacity. The storage administrator is not concerned
about CI or CA splits in the various catalogs.
//CREWSCHK JOB (1),JOE,CLASS=A
//*
//*
Print a snapshot report of the catalog environment
//*
//CREWSCHK EXEC PGM=CREWSCHK
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
*
CISPLIT(9999)
CASPLIT(9999)
VOLCAP(99)
If any catalog is found residing on a volume that is 99% full, the FC826W warning
message is displayed and CREWSCHK issues return code 4.
20 User Guide
Control Statements
CREWSCHK Report Description
The report is divided into six sections as follows:
1.
Threshold Values in Effect - Reports the threshold values that will be used to
generate warning messages and set a return code of 4.
2.
System Analyzed - Identifies on which machine this analysis was run. The sysplex
name and operating system level is reported.
3.
Catalog Environment Summary - Provides high-level information about the catalog
environment, such as the name of the master catalog, the total number of user
catalogs connected to this master catalog, and the total number of aliases found in
the master catalog.
The number of catalogs for which no catalog alias exists is reported here. If this
number is non-zero, there are catalogs that cannot receive new catalog entries
through normal catalog activity. Data sets cataloged in these catalogs cannot be
found without JOBCAT/STEPCAT processing. This may represent orphaned catalogs.
The specific catalogs may be found in the Catalog Detail section. Under the column
heading "Number of Alias(s)" look for entries showing zero.
The number of aliases with no associated catalog should always be zero. If not, the
ACE component off CA CREWS must be run to find and correct this problem.
4.
CA 7 Detection - Lists the nodes that can be contacted from this system. CA 7 r3.3
or higher must be installed in the environment. If any nodes are listed, you also can
run the CREWSCA7, the CA 7 Catalog Dependency Analysis tool. See Reporting CA 7
Job Management Catalog Dependencies for details.
Note: CA 7 has been changed to CA Workload Automation SE.
5.
Status of Required Recording of SMF Record Types - Identifies the SMF records
being recorded from each of the z/OS subsystems. "Y" indicates a given record type
is being recorded and "N" indicates that it is not. If a required SMF record type is
not being recorded, a return code of 8 is given. CA CREWS requires that certain SMF
records be recorded to perform a forward recovery after a catalog has been
restored from backup. Other SMF records provide useful information that aids CA
CREWS in the forward recovery process.
6.
Catalog Detail - Lists every catalog connected to the master catalog and reports
certain critical information about each catalog. The first catalog in the list is always
the master catalog. The rest of the catalogs appear in alphabetical order. The report
fields are:
Catalog Name
Name from the user catalog record.
Extents
Number of extents in the user catalog. A warning message and return code of 4
can be triggered if the value in this column meets the threshold value set by
the EXTENT parameter.
Chapter 2: Using the Catalog Checkup Tool (CREWSCHK) 21
Control Statements
Volume Serial
Volume serial number of the disk volume where this catalog resides.
Volume % Full
Indicator of how near capacity this volume is. Volumes that are near capacity
may not have enough room for the catalog to acquire secondary extents. A
warning message and return code of 4 can be triggered if the value in this
column meets the threshold value set by the VOLCAP parameter.
Sharing Opt
Shared catalogs should have share options "3,4" defined.
Sharing ECS
Indicator of whether catalog is enabled for Enhanced Catalog Sharing. If catalog
is enabled, a "Y" appears in the column.
Splits CA
Number of control area splits this catalog has undergone. Excessive splitting
can impact catalog performance. A warning message and return code of 4 can
be triggered if the value in this column meets the threshold value set by the
CASPLIT parameter.
Splits CI
Number of control interval splits this catalog has undergone. Excessive splitting
can impact catalog performance. A warning message and return code of 4 can
be triggered if the value in this column meets the threshold value set by the
CISPLIT parameter.
Number of Alias(s)
Number of catalog alias records found in the master catalog that "point" to this
user catalog. If the number is zero, this catalog may be an orphaned catalog.
Messages
Any processing error message or threshold warning message.
22 User Guide
Chapter 3: Working in the Automated
Catalog Environment (ACE)
The CA CREWS Automated Catalog Environment (ACE) feature automatically gathers
data and analyzes your catalog environment. The environment consists of a master
catalog, user catalogs, VVDSs, and VTOCs.
ACE is useful for daily examination of your catalog environment. Because ACE considers
the entire environment dynamically, there are no command sets to maintain. Due to its
global examination, ACE can be used in other situations. For example, if a volume has
been restored, ACE can resynchronize the volume to all catalogs in the system. Any data
sets ACE reports as scratched were created after the volume backup was taken and
need to be restored from other sources. Uncataloged data sets can be deleted as they
were deleted from the catalog after the backup occurred.
ACE also has the ability to use multiple tasks to extract information. For example, a
given task will read a VTOC, a VVDS, or a catalog. Therefore, multiple volumes and
catalogs can be processed simultaneously. The multiple tasks funnel the information
obtained into the sorting process, reducing the time for the discovery process to
complete.
This section contains the following topics:
How ACE Works (see page 24)
Required JCL (see page 25)
Control Statements (see page 27)
Batch Operation (see page 30)
Online Operation (see page 35)
Chapter 3: Working in the Automated Catalog Environment (ACE) 23
How ACE Works
How ACE Works
The objective of ACE is to validate the path through the catalog environment from top
to bottom. To do this, ACE performs the following actions:
■
Locates data sets by following the path from master catalog (using alias) to user
catalog to VVDS to VTOC. Other variations, depending on data set type and whether
SMS is implemented, are:
–
Master catalog to VVDS to VTOC
–
Master catalog to VTOC
–
Master catalog (by alias) to user catalog to VTOC
■
Reads aliases and data set names from catalogs and data set names from the VVDSs
and VTOCs of volumes in your system.
■
Sorts the aliases and data set names.
■
Produces an ordered list of all data set names in the catalog environment.
■
Processes this list and validates the accessibility of each data set.
■
Writes any data sets with problems to an exception file.
■
Examines the exception file and suggests solutions. ACE may review the exceptions
through ISPF panels where the final disposition of each exception is determined.
Alternately, the batch component of ACE is used to correct the problems in a single
pass, handling classes of problems rather than handling each exception separately.
Exception Solutions
ACE suggests solutions for the following exceptions:
24 User Guide
Exception
Solution
Uncataloged or orphaned data sets have a valid
VVDS (VSAM and SMS-managed non-VSAM) and
VTOC but are not in any catalog.
Data sets can be recataloged or
deleted.
Scratched data sets have a valid catalog entry but
cannot be found in the VVDS and VTOC of the
volume indicated in their catalog record.
Catalog entries can be deleted.
Like scratched data sets, volume not mounted data
sets have a valid catalog record but the volume the
catalog says they're on is not mounted.
Catalog entries can be deleted.
Data sets in the wrong catalog have an alias that
points to a different catalog than the one in which
the data set is currently cataloged.
Data sets can have their catalog
entries moved to the correct
catalog or be deleted.
Required JCL
Exception
Solution
Data sets are cataloged in a user catalog but have no Data sets can be deleted, moved
alias.
to a user chosen catalog, or
have an alias defined.
Unused aliases have no related data sets.
They can be deleted.
Aliases with no user catalog are aliases whose
related user catalog cannot be found.
Aliases can be deleted.
VSAM or SMS-managed non-VSAM data sets have
Data sets can be deleted.
either their VVDS entry or their VTOC entry missing.
Required JCL
The first step in analyzing a catalog environment is to run the CREWSACE program. This
program gathers data set names from all or selected catalogs and volumes, sorts them,
and creates an exception file of missing, unused, and lost components.
Important! The exception file must be empty (for example, deleted and defined) before
CREWSACE is run. Reusable files do not work.
The following JCL is required for CREWSACE:
//CREWSACE JOB
//STEP1
EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN
DD *
DEFINE CLUSTER (NAME(exception.file) INDEXED KEYS(45 6) RECSZ (1024 1024) MEGABYTES(1 1) CISZ(4096)VOL (volser))
//CREWSACE EXEC PGM=CREWSACE
//SORTWK01 DD ...
//SORTWK02 DD ...
//EXCWORK DD DSN=&.&EXCWORK.,DISP=(,DELETE),
//
UNIT=SYSDA,SPACE=(CYL,(50,50))
//EXCFILE DD DSN=exception.file,DISP=OLD
//SYSOUT
DD SYSOUT=A
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
...control statements...
Chapter 3: Working in the Automated Catalog Environment (ACE) 25
Required JCL
JCL Description
EXEC PGM=IDCAMS
Creates the exception record file, a VSAM KSDS. ACE loads this file, so it must be
empty. The only AMS DEFINE parameter of any concern is KEYS (45 6). The records
are fixed length, 1024 bytes. Any CI size can be used. The space required is a
function of the number of exceptions encountered and is difficult to predict. To be
safe, consider using one exception at 1024 bytes for each data set in your largest
catalog and adjusting the value after you run ACE.
DEFINE CLUSTER (NAME(CREWSACE.EXCPTNS.LOAN04) INDEXED VOLUME(LOAN04) KEYS (45 6) RECSZ(1024 1024) CYLINDERS(20))
EXEC PGM=CREWSACE
Specifies CREWSACE as the program name.
SORTWK
Specifies the disk work areas necessary for your system sort program.
EXCWORK
Required. Specifies the exception work file.
EXCFILE
Required. Specifies the exception file, an empty VSAM KSDS with KEYS (45 6)
defined in STEP1.
DEFINE CLUSTER (NAME(CREWSACE.EXCPTNS.LOAN04) INDEXED VOLUME(LOAN04) KEYS (45 6) RECSZ(1024 1024) CYLINDERS(20))
SYSPRINT
Required. SYSPRINT DD specifies a data set for output messages.
SYSIN DD
Required. Specifies a data set for CREWSACE control statements.
26 User Guide
Control Statements
Control Statements
The following control statements select the catalogs and volumes that ACE searches and
the options it uses:
CATALOG (ALL|catalogname [EXCEPT catalogname ... ])
VOLUME (ALL|volser ... [EXCEPT volser ... ])
ARCSYS (HSM|DMS|ABR)
ARCVOL (volser volser...) (MIGRAT)
DELAY=nn
NOTAPE
BUFFERS(n)
BUFSIZE(n)
SUMMARY(opt)
LOG(TASK)
TASKS(n)
TIMEOUT(n)
TRACE | TRACEDSN (data set name)
Important! Both the CATALOG and VOLUME control statements must be specified for
correct analysis. No defaults are assumed, and incorrect results may be generated if
both are not included.
CATALOG(catalogname)
CATALOG selects the catalogs to be checked.
Note: For more information about catalog naming conventions, see Backing Up,
Restoring, and Recovering Reference.
The following options are used with the CATALOG control statement:
ALL
All catalogs are included in the search.
catalogname
The catalogs included in the search.
EXCEPT catalogname
The catalogs excluded from the search.
Chapter 3: Working in the Automated Catalog Environment (ACE) 27
Control Statements
VOLUME(volser)
VOLUME selects the volumes to be checked. The following options are used with the
VOLUME control statement:
ALL
All volumes are included in the search.
volser
The volumes included in the search.
EXCEPT volser
The volumes excluded from the search.
Note: For more information about VOLSER specifications, see VOLUME(volser).
ARCSYS(sysname)
ARCSYS lets you define the type of archival system you are using. The following options
are available:
HSM
Specify HSM if you are using the IBM archival system. HSM is the default.
DMS
Specify DMS if you are using a CA Disk archival system.
ABR
Specify ABR if you are using the FDR archival system.
When using RACF to allow delete/noscratch functions, the CREWS userid must be
defined to the RACF logon group ARCCATGP. This allows the BYPASS RELOAD process in
DFHSM during catalog recovery.
ARCVOL(volser)
ARCVOL specifies the volume that your archival system requires. MIGRAT is the default
for HSM. If your system supports multiple archival systems, ARCVOL lets you specify
multiple volume serial identifiers. Simply specify ARCVOL (volser volser...). A maximum
of two (2) pseudo VOLSER names are permitted.
28 User Guide
Control Statements
DELAY(days)
DELAY stops CA CREWS from considering recently created data sets. Specify nn to
determine the number of days to delay before data sets are considered for CREWSACE.
The DELAY parameter is optional. If it is not specified, data sets created on the same day
are not reported.
NOTAPE
NOTAPE does not include tape data sets from catalogs. The only tests performed on
tape data sets are based on their aliases, wrong catalog, and no alias. Because many
cataloged data sets are tape files, ACE performance can be enhanced by eliminating
them from consideration after they are moved to the correct catalog.
BUFFERS(n)
BUFFERS specifies the number of buffers in the buffer pool to be used by the catalog
reader and volume reader tasks. (n) is a value from 8 to 128. If omitted, the default is
64.
BUFSIZE(n)
BUFSIZE designates the size of each of the buffers in the buffer pool used by the catalog
reader and volume reader tasks. (n) is a value from 195 to 16384. Kilobyte notation is
permitted to express values from 1K to 16K. If omitted, the default is 4K.
SUMMARY(opt)
SUMMARY requests that summary reports be generated for catalog processing, volume
processing or both. The summary reports are generated after all other processing has
been completed. If omitted, no summary reports are generated. (opt) can be CATALOG,
VOLUME, or ALL. During execution, ACE records all activity on the catalogs and volumes
it processes in tables. The summary reports display the contents of these tables.
LOG(task)
LOG requests that detailed task activity be logged in the message data set. Message
entries are logged for each catalog and volume being processed. This parameter can
cause the print data set to increase in size by many pages. If omitted, only errors from
individual tasks appear in the message data set.
Chapter 3: Working in the Automated Catalog Environment (ACE) 29
Batch Operation
TASKS(n)
TASKS controls the maximum number of catalog reader and volume reader tasks. Each
task can process either catalogs or volumes. When processing begins, half of the tasks
are designated for catalogs and half for volumes. When all catalogs have been
processed, then catalog tasks switch to volume processing. Likewise, when all volumes
have been processed, then volume tasks switch to catalog processing. ACE can set the
TASKS value to a smaller number based on the perceived workload. (n) is a value from 1
to 32. If omitted, the default is 16.
TIMEOUT(n)
TIMEOUT specifies the minimum number of minutes of inactivity after which a given
task is considered to be "hung". Each "n" minutes, the main task examines the activity of
each catalog reader and volume reader task. If no change is detected from the previous
examination, that task is considered "hung". Therefore, if TIMEOUT(1) is in effect, a
given task could be hung for up to 2 minutes before it is detected. A hung task is
terminated and restarted. The volume or catalog that was being processed by the hung
task is marked as being in error. (n) is a value from 1 to 30. If omitted, the default is 1.
TRACE | TRACEDSN(dsn)
Note: This is a diagnostic control statement that should be used only under direction
from CA technical support.
TRACE and TRACEDSN are used to produce a set of trace information found in the
catalog, VVDS, and VTOC. You can specify one or the other, but not both.
■
TRACE. Traces everything. The results could be extensive, so use this control
statement with care.
■
TRACEDSN (data set name). Traces only the data set name you specify. If you
specify a partial data set name, it becomes a generic match and finds all matches.
For example, a data set name of PAY finds PAYLESS, PAYDAY, and so forth.
Batch Operation
This section contains information necessary for exception handling and defines the
batch control statements used in this process.
Exception Analysis
The CREWSABT program provides exception handling through batch.
30 User Guide
Batch Operation
CREWSABT Jobstream
//CREWSABT JOB
//CREWSABT EXEC PGM=CREWSABT
//SYSPRINT DD SYSOUT=A
//EXCFILE DD DSN=exception.file,DISP=OLD
//JOBSTRM DD DSN=action.job.file,DISP=(,NEW,CATLG),
//
SPACE=(CYL,(5,5)),
//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=4000)
//JOBCARD DD DSN=jobcard.file,DISP=OLD
//SYSIN
DD *
...control statements...
JCL Description
EXCFILE
Specifies the exception file created by CREWSACE.
JOBSTRM
Specifies the jobstream created to correct the exceptions. This is a sequential file of
80-byte records.
JOBCARD
Specifies a file containing a job statement to be used in the job written to the
jobstream file.
SYSPRINT
Specifies the output class for message and report printing.
SYSIN
Specifies the data set for ACE control statements.
Control Statements
The batch control statements follow:
UNCATALOGED=INFO|DELETE|RECATALOG
SCRATCHED=INFO|DELETE
NOTMOUNTED=INFO|DELETE
WRONGCAT=INFO|DELETE|MOVE
NOALIAS=INFO|DELETE|MOVE|DEFALIAS
UNUSEDALIAS=INFO|DELETE
NOUSERCAT=INFO|DELETE
VVDSVTOC=INFO|DELETE
Chapter 3: Working in the Automated Catalog Environment (ACE) 31
Batch Operation
UNCATALOGED
The UNCATALOGED control statement specifies how to handle uncataloged data sets.
UNCATALOG accepts the following parameters:
INFO
Prints a report about all uncataloged data sets.
DELETE
Adds IDCAMS DELETE NVR or DELETE VVR JCL and commands to the jobstream file.
RECATALOG
Adds IDCAMS DEFINE RECATALOG (VSAM and SMS-managed non-VSAM) or DEFINE
NONVSAM to the jobstream.
SCRATCHED
The SCRATCHED control statement specifies how to handle scratched data sets.
SCRATCHED accepts the following parameters:
INFO
Prints a report about all scratched data sets.
DELETE
Adds IDCAMS DELETE CLUSTER NOSCRATCH and DELETE NVSAM NOSCRATCH JCL
and commands to the jobstream.
NOTMOUNTED=opt
The NOTMOUNTED control statement specifies how to handle cataloged data sets
whose volume is not mounted. NOTMOUNTED accepts the following parameters:
INFO
Prints a report about all data sets not mounted on a volume.
DELETE
Adds IDCAMS DELETE CLUSTER NOSCRATCH and DELETE NVSAM NOSCRATCH JCL
and commands to the jobstream.
32 User Guide
Batch Operation
WRONGCAT=opt
The WRONGCAT control statement specifies how to handle data sets in the wrong
catalog. WRONGCAT accepts the following parameters:
INFO
Prints a report about all data sets in the wrong catalog.
DELETE
Adds IDCAMS DELETE CLUSTER and DELETE NVSAM JCL and commands to the
jobstream.
MOVE
Adds IDCAMS REPRO MERGECAT JCL and commands to the jobstream to move the
catalog entries to the correct catalog.
NOALIAS=opt
The NOALIAS control statement specifies how to handle data sets defined in user
catalogs but without an alias. NOALIAS accepts the following parameters:
INFO
Prints a report about all data sets with no alias.
DELETE
Adds IDCAMS DELETE CLUSTER and DELETE NVSAM JCL and commands to the
jobstream.
MOVE
Adds IDCAMS REPRO MERGECAT JCL and commands to the jobstream to move the
catalog entries to a catalog named NEW.CATALOG. You must edit the jobstream
created in the JOBSTRM file to specify the appropriate catalog before submitting
the generated jobstream.
DEFALIAS
Adds IDCAMS DEFINE ALIAS JCL and commands to the jobstream. The alias is for the
first qualifier of the data set name. All data sets with the same first qualifier are
listed in comments following the DEFINE command. This list can be edited to let
multilevel aliases be defined.
Chapter 3: Working in the Automated Catalog Environment (ACE) 33
Batch Operation
UNUSEDALIAS=opt
The UNUSEDALIAS control statement specifies how to handle aliases that have no
associated data sets. USEDALIAS accepts the following parameters:
INFO
Prints a report about all unused aliases.
DELETE
Adds IDCAMS DELETE ALIAS JCL and commands to the jobstream.
NOUSERCAT=opt
The NOUSERCAT control statement specifies how to handle aliases that have no related
user catalog. NOUSERCAT accepts the following parameters:
INFO
Prints a report about all aliases without user catalogs.
DELETE
Adds IDCAMS DELETE ALIAS JCL and commands to the jobstream.
VVDSVTOC=opt
The VVDSVTOC control statement specifies how to handle data sets with missing VVDS
entries or missing VTOC DSCBs. VVDSVTOC accepts the following parameters:
INFO
Prints a report about all data sets with missing VVDS or VTOC parts.
DELETE
Adds IDCAMS DELETE ALIAS JCL and commands to the jobstream. The supplied
commands remove the following objects:
DELETE VVR or NVR
Uncataloged data sets with missing DSCBs.
DELETE CLUSTER or NVSAM
Cataloged data sets missing a VVDS entry or DSCB.
IEHPROGM SCRATCH
Uncataloged non-VSAM data sets missing a VVDS entry.
SUPERZAP
VSAM indicators from the VTOC, followed by an IEHPROGM SCRATCH for VAM
components that are missing a VVDS entry.
34 User Guide
Online Operation
Online Operation
This section contains the panels used for online operation.
Exception and Analysis
The first panel displayed by ACE identifies the exception file created by the CREWSACE
job and permits selection by exception type. The exception file data set name is a
required parameter.
Main Panel
-------------------- CREWSACE Release 04.03.01 -- Main Menu ----------Option ===>
Specify exception file:
Data set name ===> CREWSACE.EXCPTNS.XE76
Line command S selects exceptions:
All
- Display all exception records.
Uncataloged
- Data sets not found in any catalog.
Scratched
- Data sets not found on any volume.
Not mounted
- Data sets whose volume is not mounted.
Wrong catalog
- Data sets in wrong user catalog.
No alias
- Data sets in user catalogs but have no alias.
Unused alias
- Aliases with no associated data sets.
No user cat
- Aliases with no related user catalog.
VVDS/VTOC missing - Data sets that are missing a VTOC or VVDS entry.
To display exceptions, type S next to each type desired.
Selecting All displays all records in the exception file.
To exit the Main panel and return to ISPF, press F3.
Chapter 3: Working in the Automated Catalog Environment (ACE) 35
Online Operation
Exceptions Panel
On the Exceptions panel, the exceptions are read from the file specified on the main
panel, filtered by type and displayed by data set name in alphabetic order.
-------------------------------- Exceptions -------------------- ROW 1 OF 9
Command ===>
Scroll ===> PAGE
COMMAND
DATA-SET-NAME
ACTION
REASON
------ ----------------------------------------- ------ ---------------------ADA.AOFE.SAMPLES
Uncat volser
ADA.AOFE.TEXT
Scratch volser
ADA.ASM
Not mnt volser
ADA.CNTL
Wrong cat
ADA.LIST
No alias
ADA.LOG.MISC
No VVDS volser
ADA.O.ASM
No VTOC volser
ADB
Unused alias
ADC
No user cat
To exit the Exceptions panel, press F3. If any corrective actions were
taken, the Jobstream Generation panel appears. If only information
actions were specified, the Main panel is displayed.
Commands
You can enter the following commands on the command line of the Exceptions panel:
■
LOCATE data set: Scrolls directly to the specified data set name. data set can be a
1-to-44 character string. Scrolling stops at the name closest to data set.
Abbreviation: LOC or L.
■
ISPF table display commands.
Actions
In the COMMAND column on the Exceptions panel, you can enter any of the following
actions next to a data set name:
36 User Guide
COMMAND
Function
DEFAL
Defines an alias. Can be used only for no alias exceptions.
Abbreviation: A.
DELETE
Deletes or scratches data sets. Can be used for all exceptions.
Abbreviation: D.
INFO
Displays an information panel detailing the contents of the exception
record. Can be used for all exceptions. Abbreviation: I.
Online Operation
COMMAND
Function
MOVE
Moves data sets in the wrong catalog to the correct catalog with
REPRO MERGECAT. Data sets with no alias are moved with REPRO
MERGECAT to a catalog named NEW.CATALOG. The generated
jobstream must be edited and NEW.CATALOG renamed. Can be used
only for wrong catalog and no alias exceptions. Abbreviation: M.
RECAT
Recatalogs uncataloged data sets. Can be used only for uncataloged
exceptions. Abbreviation: R.
RESET
Removes the action taken from a data set and permits another action
to be specified. No abbreviation.
Action Rules
The following usage rules apply to the actions entered on the Exceptions panel:
■
All actions except INFO cause the appropriate IDCAMS or IEHPROGM JCL and
commands to be created. The ACTION column contains the action (other than INFO)
that was specified. Once ACTION indicates a command has been issued for a data
set, no other corrective actions can be used.
■
RESET clears ACTION and permits another corrective action to be specified. All line
commands create utility JCL and commands; RESET does not eliminate any JCL or
commands. You must revise the jobstream to eliminate duplicate or contradictory
actions. If any corrective actions have been specified (even if they have been
RESET), exiting the Exceptions panel takes you to the Jobstream Generation panel.
If INFO is the only command specified, the Main panel appears.
■
The entry in the ACTION column is retained (unless RESET is issued against it) in the
exception record. If the same exception file is displayed again, previous actions are
indicated.
Chapter 3: Working in the Automated Catalog Environment (ACE) 37
Online Operation
Jobstream Generation Panel
When corrective actions are specified on the Exceptions panel the Jobstream
Generation panel is displayed. The disposition of the generated jobstream is specified
on this panel.
-------------------------- Job Stream Generation ------------------------------Option ===>
Specify the file for the exception correction job stream:
Data set name ===> jobstream.file
Replace current file or add to end:
===>
(MOD or OLD)
Job card for job-streams created:
===> //JOBCARD JOB
===> //*
===> //*
===> //*
Review job-stream:
===>
(EDIT, BROWSE, blank)
ENTER to write output, END to leave without writing
Required Field
The jobstream.file data set is required for CA CREWS ACE online. The jobstream data set
is a previously defined sequential data set where the jobstream is written. The
characteristics of the data set should be RECFM=FB, LRECL=80, BLKSIZE. BLKSIZE can be
set to any permitted value. The default is 4000.
Optional Fields
The following fields accept information optional for ACE online:
■
38 User Guide
Replace current file or add to end: Specifies the status of the data set.
–
OLD: Allocate the jobstream data set with DISP=OLD and write over anything
that is already there. This is the default.
–
MOD: Allocate the jobstream data set with DISP=MOD and append new
jobstreams to the end.
■
Job card for jobstreams created: The Job statement and up to three other
statements placed at the beginning of the jobstream.
■
Review jobstream: Allows the jobstream to be examined or changed. If nothing is
specified, you are returned to the Main panel.
–
BROWSE: Invokes the PDF BROWSE function for the jobstream file.
–
EDIT: Invokes PDF EDIT for the jobstream file. The correction JCL and
commands can be examined, altered, and submitted.
Online Operation
Exiting the Jobstream Panel
To exit the Jobstream Generation panel, perform either of the following actions:
■
Press Enter. This writes the jobstream to the jobstream file and returns to the Main
panel if reset was not specified. If reset was specified, the selected PDF function is
invoked before returning to the Main panel.
■
END command or press PF3. This does not write the jobstream to the file, ignores
any review specified, and returns to the Main panel.
Note: Exiting in this manner drops undesired JCL and commands that are still present
when RESET was specified as an action on the Exception panel.
Submit the jobstream for execution from the Review EDIT function by entering EDIT or
by exiting the ACE application.
Chapter 3: Working in the Automated Catalog Environment (ACE) 39
Chapter 4: Merging User Catalogs
This section provides information on merging user catalogs.
This section contains the following topics:
JCL Requirements (see page 41)
Control Statements (see page 42)
Options (see page 42)
Examples (see page 42)
Return Codes (see page 45)
JCL Requirements
The following JCL statements are required to execute a merge function:
//XCATMERG JOB (00000000),PGMRNAME,
// MSGCLASS=X,MSGLEVEL=(1,1)
//*
//MERGE
EXEC PGM=XCATMERG
//SYSPRINT DD SYSOUT=*
//AMSPRINT DD SYSOUT=*
//SYSIN
DD *
MERGE FROM=source.catdsn TO=destination.catdsn [TEST|NOTEST]
//*
DD Statements:
SYSPRINT
Defines the print output for the merge report and related messages. The file
characteristics are LRECL=133 and RECFM=FBA. If BLKSIZE is coded in the JCL, it is
used. Otherwise, system determined BLKSIZE is used.
AMSPRINT
Defines the print output for any of the messages resulting from the XCATMERG
program invoking IDCAMS to perform various catalog functions The file
characteristics are LRECL=133 and RECFM=FBA. If BLKSIZE is coded in the JCL, it is
used. Otherwise, system determined BLKSIZE is used. If AMSPRINT is not present,
IDCAMS output is directed to SYSPRINT.
SYSIN
Defines the control statement input. This is used to specify the source and
destination catalogs to be merged. Multiple control statements can be present,
each specifying the source and destination catalogs to be merged.
Chapter 4: Merging User Catalogs 41
Control Statements
Control Statements
Control statements can start at any position on the line and can continue over multiple
lines. A keyword and its operand, for example FROM=dsn, must be together on one line.
MERGE
MERGE
Specifies a MERGE control statement. Any number of merge control statements can
be specified. Each MERGE command must contain a FROM= and a TO= keyword
with the appropriate operands.
FROM=
The FROM= keyword operand is the input catalog name.
TO=
The TO= keyword operand is the destination catalog name.
[TEST|NOTEST]
Specifies that that a TEST merge is performed. A TEST merge does not merge the
catalogs. It only lists any duplicate entries that may exist in the destination catalog.
Default is NOTEST.
Options
The source catalog DSN can be coded using wild card notation (* or **) in place of a DSN
qualifier.
A single asterisk (*) by itself indicates that either a full qualifier or one or more
characters within a qualifier can occupy that position. An asterisk can precede or follow
a set of characters.
A double asterisk (**) indicates that zero or more qualifiers can occupy that position. A
double asterisk cannot precede or follow any characters. It must be preceded or
followed by either a period or a blank.
An asterisk (*) in column 1 indicates that it is a comment.
Examples
This section provides examples of the MERGE statement.
42 User Guide
Examples
Example 1
In the following example the first line would be ignored. The MERGE statement requests
the catalog records from catalog dataset MY.PERSONAL.USERCAT to be merged into
catalog dataset MY.NEW.USERCAT.
//SYSIN DD
* This is a comment line
MERGE FROM=MY.PERSONAL.USERCAT
TO=MY.NEW.USERCAT
Example 2
In the following example, the first line would be ignored. The MERGE statement
requests the catalog records from all catalogs, matching the high level node of MY. to be
merged into catalog dataset MY.NEW.USERCAT.
//SYSIN DD
* This is a comment line
MERGE FROM=MY.**
TO=MY.NEW.USERCAT
Example 3
In the following example, the first line would be ignored. The MERGE statement
requests the catalog records from all catalogs matching the high level node of MY.,
matching any second node, and matching a third node of USERCAT, to be merged into
catalog dataset MY.NEW.USERCAT.
//SYSIN DD
* This is a comment line
MERGE FROM=MY.*.USERCAT
TO=MY.NEW.USERCAT
Chapter 4: Merging User Catalogs 43
Examples
Example 4
In the following example, the first line would be ignored. The MERGE statement
requests the catalog records from all catalogs matching the high level node of MY., and
matching the first three positions of the second node, and matching a third node of
USERCAT, into catalog dataset MY.NEW.USERCAT.
//SYSIN DD
* This is a comment line
MERGE FROM=MY.PER*.USERCAT
TO=MY.NEW.USERCAT
More Examples
The following table lists the entry names, which will be returned, and which will not be
returned for a given statement.
44 User Guide
Statement
Returns
Does Not Return
CATALOG.DATA.SET%
CATALOG.DATA.SET1
CATALOG.DATA.SET2
CATALOG.DATA.SET30
CATALOG.DATA.SET%% CATALOG.DATA.SET30
CATALOG.DATA.SET31
CATALOG.DATA.SET1
CATALOG.DATA.SET2
CATALOG.*.SET
CATALOG.DATA1.SET
CATALOG.DATA2.SET
CATALOG.DATA.SET.KSDS
CATALOG.*A
CATALOG.A
CATALOG.BA
CATALOG.BBA
CATALOG.B
CATALOG.AB
CATALOG.DATA.*
CATALOG.DATA.SET1
CATALOG.DATA.SET2
CATALOG.DATA.SET.KSDS
CATALOG.DATA*
CATALOG.DATA1
CATALOG.DATA23
CATALOG.DATA.SET
CATALOG.**
CATALOG
CATALOG.DATA.SET1
CATALOG.DATA.SET2
CATALOG.DATA.SET.KSDS
CATALOG1.DATA.SET
CATALOG.DATA.SET
CATALOG.DATA.SET
**.DATA
CATALOG.DATA
NONVSAM.WORK.DATA
Return Codes
Statement
Returns
Does Not Return
**
Returns every entry
name in the catalog.
For a GDG base named DATASET.GDG containing the following GDS entries
DATASET.GDG.G0001V00
DATASET.GDG.G0002V00
DATASET.GDG.G0003V00
and for the non-VSAM data set named DATASET.GDG.G0001V00.XYZ, the following
statements will return the following results:
Statement
Returns
DATASET.GDG.**
DATASET.GDG.G0001V00
DATASET.GDG.G0002V00
DATASET.GDG.G0003V00
DATASET.GDG.G0001V00.XYZ
DATASET.GDG.G0001V00
DATASET.GDG.G0001V00
DATASET.GDG.G0001V00.**
DATASET.GDG.G0001V00.XYZ
DATASET.GDG.G000%V00
DATASET.GDG.G0001V00
DATASET.GDG.G0002V00
DATASET.GDG.G0003V00
DATASET.GDG.G000%V00.**
DATASET.GDG.G0001V00
DATASET.GDG.G0002V00
DATASET.GDG.G0003V00
DATASET.GDG.G0001V00.XYZ
Note: The entries returned by the data set name are not necessarily returned in
ascending order.
Return Codes
The following is a list of return codes:
0
All MERGE operations successful.
4
One or more MERGE commands had errors. Command was skipped.
Chapter 4: Merging User Catalogs 45
Return Codes
8
One or more MERGE operations failed, but back-out was successful.
12
One or more MERGE operations failed, and back-out also failed. Check listing
carefully.
16
Program initialization failed. No MERGE operations attempted.
The following is a list of abend codes:
1001
SYSPRINT did not open
1002
LMP error (other than license related)
46 User Guide
Chapter 5: Protecting and Fixing Catalogs
CA CREWS is an automated catalog protection, checking, and fixing program. The
protection functions protect catalogs and recover from catalog losses. The checking and
fixing functions identify catalog trouble and prescribe fixes for them.
This chapter provides an overview of the following functions:
■
■
Protection Functions
–
Back Up Catalogs
–
Restore Catalogs
–
Recover Catalogs
Checking and Fixing Functions
–
Check Scratch
–
Check Alias
–
Check Uncatalog
–
Diagnose
Protection Functions
This section provides the functions, processes, and procedures used by the Back Up,
Restore, and Recovery catalogs.
Back Up Catalogs
This section gives an overview of the following:
■
CA CREWS Backup process
■
Your actions as part of that process
Backup Function
CA CREWS backs up the master catalog and any selected user catalog defined in the
master Catalog.
Note: It is strongly recommended that a backup master catalog be available on disk at
all times. In the event that the master catalog becomes unusable, a backup copy must
be on disk to enable the IPL of a z/OS system and the execution of the catalog restore
program.
Chapter 5: Protecting and Fixing Catalogs 47
Protection Functions
Backup Process
Flexible Catalog Backup: CA CREWS enables you to select the catalogs to back up by
specifying a particular or generic catalog name. You can also choose to back up all user
catalogs. The flexibility to specify which catalogs to back up means user catalogs are
backed up without the trouble of maintaining a list of catalog names.
IDCAMS DIAGNOSE and EXPORT: CA CREWS creates IDCAMS DIAGNOSE and EXPORT
commands for each catalog selected for backup. The DIAGNOSE reports any current
problems with the catalog. The EXPORT creates a portable copy of the catalog. The
portable copy of the catalog is preceded by a header record and followed by a trailer
record. The header and trailer records let the backups of multiple catalogs be written to
the same file and be found at restore time.
Backup Reporting: The backup process reports on its activities. All IDCAMS output is
printed. On the last page of the printout is the Backup Summary Report which
summarizes the results of all DIAGNOSE and EXPORT executions and gives the page
number of the IDCAMS output.
Backup Procedure
Use the following procedure to back up catalogs with CA CREWS. For specific
information to help you complete each step, see the page number listed.
Step
Action
Statement
For More Information
1
Specify necessary JCL for backup.
OC
See JCL Requirements
2
Specify the BACKUP control statement.
BACKUP
See Control Statements
3
Specify which catalogs to back up with the
CATALOG statement.
CATALOG
See CATALOG(catalogname)
4
Inspect Backup Summary Report to verify
successful catalog backup.
OC
See Backup Summary Report
Restore Catalogs
This section gives an overview of the following:
■
CA CREWS Restore process
■
Your actions as part of that process
Restore Function
CA CREWS restores any selected user catalog name from the CA CREWS backup file.
48 User Guide
Protection Functions
Restore Process
Flexible Catalog Restore: CA CREWS lets you select which catalogs to restore by
specifying a particular or generic catalog name. You also can choose to restore all user
catalogs.
IDCAMS EXPORT and IMPORT : The restore process finds header records that precede
IDCAMS EXPORT output and compares them for catalog names to restore. IDCAMS
IMPORT is used to restore the catalog. Restore continues until a trailer record is
encountered.
Restore Reporting: The restore process reports on its activities. All IDCAMS output is
printed. On the last page of the output is the Restore Summary Report which
summarizes the results of all IMPORT executions and gives the page number of the
IDCAMS output.
Restore Procedure
Use the following procedure to restore catalogs with CA CREWS. For specific
information to help you complete each step, see the page number listed.
Step
Action
Statement
For More Information
1
Specify necessary JCL for restore.
OC
See JCL Requirements
2
Specify the RESTORE control statement. RESTORE
See Control Statements
3
Specify which catalogs to restore with
the CATALOG statement.
CATALOG
See CATALOG(catalogname)
4
Specify IMPORT values.
ALIAS
INTOEMPTY
LOCK
See IMPORT
5
Check Restore Summary Reports to
verify successful catalog restore.
OC
See Restore Summary Report
Recover Catalogs
This section provides an overview of the following:
■
Recovery function
■
Recovery process
■
Independent recovery
■
Recovery procedure
Chapter 5: Protecting and Fixing Catalogs 49
Protection Functions
Recovery Function
Whenever a catalog is restored, its status reverts to the date and time it was backed up.
CA CREWS recovery updates all catalog activity that occurred between the backup time
and current time.
Recovery Process
Flexible Catalog Recovery: CA CREWS lets you select which catalogs to recover by
specifying a specific or generic catalog name. You also can choose to recover all user
catalogs.
SMF Records and IDCAMS Commands : SMF logs all define, delete, and alter activity for
all record types stored in ICF catalogs. CA CREWS reads SMF files and finds the catalog
activity records within the recovery period for the catalogs needing recovery. These SMF
records are turned into IDCAMS DEFINE, DELETE, and ALTER commands, which in turn
become input to IDCAMS for the catalog recovery. The recovery includes all activity
during the recovery period, which is defined by the FROM and TO date and time
parameters.
Independent Recovery
CA CREWS recovery operates independently of CA CREWS backup and restore. Recovery
is used after a CA CREWS restore, but it can also be used after a volume restore or after
any action that back-levels a catalog.
Recovery Procedure
Use the following procedure to recover catalogs with CA CREWS. For specific
information to help you complete each step, see the page number listed.
Step Action
50 User Guide
Statement
For More Information
1
Specify necessary JCL for
recovery
See JCL Requirements
2
Specify the RECOVER control
statement.
RECOVER
See Control Statements
3
Specify which catalogs to
recover with the CATALOG
statement.
CATALOG
See
CATALOG(catalogname)
4
Specify the recovery time
period.
FROM...TO
See FROM(date time)
TO(date time)
5
Specify the time difference
between CPUs.
TIMEDIFFERENCE
See
TIMEDIFFERENCE=seconds
Protection Functions
Step Action
Statement
For More Information
6
Specify relevant SMF files.
See SMF Gap Reports
7
Inspect Recovery Summary
Report to check for missing
SMF data and to verify
successful catalog recovery.
See FC322I SMF Record
Read Report
8
Review IDCAMS generated
by recovery, and execute.
See Recovery IDCAMS
Requirements
Chapter 5: Protecting and Fixing Catalogs 51
Chapter 6: Verifying Protection Functions
Each CA CREWS protection function generates a performance report. This chapter
explains how to verify the success of CA CREWS functions by interpreting the
information in the performance reports.
This chapter provides details about the following CA CREWS protection functions:
■
Back Up Catalogs
■
Restore Catalogs
■
Recover Catalogs
To verify the CA CREWS check alias, check scratch, check uncatalog, and diagnose
functions, examine the results of the IDCAMS job that each function creates.
This section contains the following topics:
Verify Catalog Backup (see page 53)
Verify Catalog Restore (see page 54)
Verify Catalog Recovery (see page 56)
Verify Catalog Backup
This section explains how to verify the CA CREWS catalog backup function.
Backup Summary Report
The results of each catalog backup are summarized in the Backup Summary Report. An
example of this report follows:
FC111I BACKUP SUMMARY REPORT
CATALOGS DEFINED IN MASTER CATALOG
---------------------------------CATALOG.DB2ICF.VS33802
CATALOG.MVSICF.VS33801
CATALOG.MVSICF1.VMVS001
CATALOG.MVSICF1.VSYSC06
CATALOG.MVS005
BACKUP
-----YES
YES
NO
NO
YES
DIAGNOSE CC
----------0
0
12
EXPORT CC
---------0
0
12
PAGE
----1
1
2
Chapter 6: Verifying Protection Functions 53
Verify Catalog Restore
Backup Summary Report Explained
The Backup Summary Report contains the following column headings:
CATALOGS DEFINED IN MASTER CATALOG
Lists every user catalog found in the master catalog
BACKUP
Indicates with a YES or NO whether the CATALOG statement selected that catalog
for backup
DIAGNOSE CC
Shows the condition code results of IDCAMS DIAGNOSE for catalogs selected for
backup
EXPORT CC
Shows the condition code results of IDCAMS EXPORT for catalogs selected for
backup
PAGE
Shows the page in the listing where the IDCAMS activity for this catalog is printed
Verify Catalog Backup Procedure
The following procedure explains how to verify a catalog backup:
Step
Look For
What To Do
1
Step condition codes
If any condition code other than 0 is reported, an
error has occurred. Review all error messages in the
listing to determine the problem.
2
Backup Summary Report Verify that all catalogs requested were included in
the backup by reviewing the catalog names listed. If
a condition code other than 0 is reported in the
DIAGNOSE CC or EXPORT CC column, check the
IDCAMS report listed on the page specified in the
PAGE column.
3
Any other error
message
Review the listing for an explanation of other
errors.
Verify Catalog Restore
This section explains how to verify the CA CREWS catalog restore function.
54 User Guide
Verify Catalog Restore
Restore Summary Report
The results of each catalog restore are summarized in the Restore Summary Report. An
example of this report follows:
FC211I BACKUP SUMMARY REPORT
ALL USER CATALOGS ON BACKUP FILE
-------------------------------CATALOG.DB2ICF.VS33802
CATALOG.MVSICF.VS33801
CATALOG.MVSICF1.VMVS001
CATALOG.MVSICF1.VSYSC06
CATALOG.MVS005
RESTORE
------NO
NO
YES
NO
NO
IMPORT CC
---------
0
PAGE
----
1
Restore Summary Report Explained
The Restore Summary Report contains the following column headings:
ALL USER CATALOGS ON BACKUP FILE
Lists every user catalog found on the backup file
RESTORE
Indicates with a YES or NO whether the CATALOG statement selected that catalog
for restore
IMPORT CC
Shows the condition code results of the IDCAMS IMPORT for catalogs selected for
restore
PAGE
Shows the page in the listing where the IDCAMS activity for this catalog is printed
Verify Catalog Restore Procedure
The following procedure explains how to verify a catalog restore:
Step
Look For
What To Do
1
Step condition codes If a condition code other than 0 is reported, an error has
occurred. Review all error messages in the listing to
determine the problem.
Chapter 6: Verifying Protection Functions 55
Verify Catalog Recovery
Step
Look For
What To Do
2
Restore Summary
Report
Verify that all catalogs requested were included in the
restore by reviewing the catalog names listed. If a
condition code other than 0 is reported in the IMPORT
CC column, check the IDCAMS report listed on the page
specified in the PAGE column.
3
Any other error
message
Review the listing for an explanation of other errors.
Verify Catalog Recovery
This section explains how to verify the CA CREWS catalog recovery function.
Recovery is dependent on the completeness of SMF records. Recovery reports on the
gaps it finds between records as an indicator of missing records. Each SMF record,
regardless of type, that fits between the FROM/TO date and time has its date and time
compared to the date and time of the last record read. When the record just read has a
greater date and time than the last record read, the difference between the two is a
forward gap. When the record just read has a lower date and time than the last record
read, the difference between the two is a backward gap. The ten largest backward and
forward gaps are saved and reported.
The size of the gaps can indicate missing SMF records or files. Forward gaps can mean
periods when the system is down or inactive, or that SMF files are not in date-time
order. Typically, a backward gap indicates that multiple SMF files were used as input but
not placed in date-time order. There is no requirement that SMF files be in date-time
order.
SMF Gap Reports
The following reports explain gaps between SMF records:
56 User Guide
■
FC322I: SMF Record Read Report
■
FC350I: Record Closest 'FROM' DATE/TIME Report
■
FC351I: Record Closest 'TO' DATE/TIME Report
■
FC355I: 10 Largest Backward Time Gaps Between Records Report
■
FC356I: 10 Largest Forward Time Gaps Between Records Report
Verify Catalog Recovery
FC322I SMF Record Read Report
Certain SMF records can provide explanations for gaps or missing data. Report FC322I
contains pertinent information about the following SMF record types:
Type
Code
Explanation
IPL
0
Date, time, and ID of the system IPL
Lost data
7
Date and time of the start of the data lost, and the
number of records lost
SMF status switch SMF
90
Date and time a switch SMF occurred
Export catalog
36
Date, time, and portable data set name when a
selected catalog was s exported
FC350I Record Closest 'FROM' DATE/TIME Report
Report FC350I is an informational message that shows how close SMF records are to the
FROM date and time. An example of this report follows:
FC350I RECORD CLOSEST TO 'FROM' DATE/TIME
FROM DATE/TIME : 20-FEB-2002.051 12:00:00.00
CLOSEST RECORD : 20-FEB-2002.051 12:39:18.44
DIFFERENCE
:
00:39:18.00
FC351I Record Closest 'TO' DATE/TIME Report
Report FC351I is an informational message that shows how close SMF records are to the
TO date and time. An example of this report follows:
FC351I RECORD CLOSEST TO 'TO' DATE/TIME
CLOSEST RECORD : 20-FEB-2002.051 14:33:35.94
TO DATE/TIME
: 20-APR-2002.110 15:00:00.00
DIFFERENCE
:
00:26:25.00
Chapter 6: Verifying Protection Functions 57
Verify Catalog Recovery
FC355I 10 Largest Backward Time Gaps Between Records Report
Report FC355I is an informational message that identifies a report about the backward
gaps found between records read. An example of this report follows:
FC355I 10 LARGEST BACKWARD TIME GAPS BETWEEN RECORDS
GAP (HH:MM:SS)
RECORD
RECORD
---------------------------------------- --------------------------02:48:18
01-MAR-2002.060 12:49:34.64
01-MAR-2002.060 10:01:16.71
FC356I 10 Largest Forward Time Gaps Between Records Report
Report FC356I is an informational message that identifies a report about the forward
gaps found between records read. An example of this report follows:
FC356I 10 LARGEST FORWARD TIME GAPS BETWEEN RECORDS
GAP (HH:MM:SS)
RECORD
RECORD
---------------------------------------- --------------------------00:01:10
20-FEB-2002.051 14:08:42.85 20-FEB-2002.051 14:09:52.68
00:01:04
20-FEB-2002.051 12:00:21.75 20-FEB-2002.051 12:01:25.86
00:01:04
20-FEB-2002.051 13:00:22.60 20-FEB-2002.051 13:01:26.52
00:00:53
20-FEB-2002.051 13:03:52.39 20-FEB-2002.051 13:04:45.18
00:00:53
20-FEB-2002.051 13:18:52.48 20-FEB-2002.051 13:19:45.27
00:00:52
20-FEB-2002.051 13:39:52.68 20-FEB-2002.051 13:40:44.26
00:00:48
20-FEB-2002.051 13:54:52.64 20-FEB-2002.051 13:55:40.80
00:00:35
20-FEB-2002.051 14:08:07.57 20-FEB-2002.051 14:08:42.85
00:00:33
20-FEB-2002.051 14:16:00.35 20-FEB-2002.051 14:16:33.28
00:00:33
20-FEB-2002.051 14:30:49.46 20-FEB-2002.051 14:31:22.61
58 User Guide
Chapter 7: Backing Up, Restoring, and
Recovering Reference
This chapter explains the following functions associated with the verification used in the
CA CREWS catalog backup:
■
Back up catalogs reference
■
Restore catalogs reference
■
Recover catalogs reference
JCL requirements and examples are provided to assist you in understanding this
procedure.
Back Up Catalogs Reference
This section describes the JCL requirements and control statements associated with
catalog backup.
JCL Requirements
To execute a catalog backup, the following JCL statements are required:
//jobname
JOB
//BACKUP EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=class
//BACKUP
DD DSN= user-outfile
//SYSIN
DD *
[DCB= blksize ]
The following table explains the statements in the required backup JCL:
Statement
Explanation
jobname JOB
jobname is a user-specified job name.
BACKUP EXEC PGM=CREWS
Initiates a backup and specifies CA
CREWS as the program name.
SYSPRINT DD SYSOUT=class
Specifies output message data
Chapter 7: Backing Up, Restoring, and Recovering Reference 59
Back Up Catalogs Reference
Statement
Explanation
BACKUP DD DSN= user-outfile [DCB= blksize] Specifies the backup output file as
user-outfile and, optionally, specifies
the blocksize. The default blocksize is
32760.
SYSIN DD
Specifies the data set containing the
CA CREWS control statements. The file
is either a sequential file with a fixed
logical record length of 80, or a PDS
member with a fixed logical record
length of 80.
Control Statements
The BACKUP control statement initiates a backup.
BACKUP
CATALOG ( catalogname ...[EXCEPT catalogname...]) EXAMINE |
NOEXAMINE MASTERPW= (password) DIAGNOSE | NODIAGNOSE
CATALOG(catalogname)
CATALOG provides comprehensive catalog selection methods. The following table
explains the options for CATALOG:
60 User Guide
Option
What You Specify
Explanation
catalogname
ALL
Specifies for backup all user
catalog names currently defined
in the master catalog.
speccatname
Specifies for backup a particular
catalog name.
gencatname
Specifies for backup (with a
generic name) multiple catalog
names. For more information,
see Specifying Generic Catalog
Names.
Back Up Catalogs Reference
Option
...
What You Specify
Explanation
EXCEPT
Excludes from backup all catalog
names that match a fully
qualified or generic name. You
can exclude a specific catalog or
generic groups of catalogs by
specifying speccatname or
gencatname. EXCEPT and its
parameters are optional.
...
Indicates an indefinite number of
additional specifications of
catalog names.
Note: Acceptable variations of CATALOG are CAT and CATS.
EXAMINE
EXAMINE is issued against a catalog prior to backup. It performs an integrity check on
data and index structure in the file. The default is NOEXAMINE.
NODIAGNOSE
The default is to DIAGNOSE a catalog to make sure it is structurally sound before a
backup.
MASTERPW=password
MASTERPW specifies the master password of the master catalog. CA CREWS uses VSAM
macros to read the master catalog in order to find user catalog names. If the master
catalog at your installation is password protected, the password needs to be specified to
avoid open errors or operator prompting.
Chapter 7: Backing Up, Restoring, and Recovering Reference 61
Back Up Catalogs Reference
Specifying Generic Catalog Names
Generic catalog names can contain skip characters. Skip characters are represented by a
plus-sign (+) or an asterisk (*). The plus-sign (+) skips only one character. The asterisk (*)
skips one or more characters.
Examples Of Specifying Generic Catalog Names
The following are the examples of the generic catalog selection:
CATALOG.*
Selects all catalog names with a high-level qualifier of CATALOG
*DB2*
Selects all catalog names that contain the character string DB2
CATALOG.V3390++
Selects all catalog names that begin with CATALOG.V3390 and end in any two
characters
ICFCAT*CICS++
Selects all catalog names consisting of ICFCAT, followed by any number of
characters, then CICS followed by any two characters
Backup Examples
This section provides examples of backup jobstreams.
Back Up All User Catalogs
The following is an example of a backup for all user catalogs:
//BACKCAT
//BACKUP
//SYSPRINT
//BACKUP
//SYSIN
BACKUP
CAT (ALL)
62 User Guide
JOB
EXEC PGM=CREWS
DD SYSOUT=A
DD DSN=BACKUP.CATALOGS(+1),DCB=MODEL,DISP=(,CATLG)
DD *
Back Up Catalogs Reference
Back Up One User Catalog to a Disk Data Set
The following is an example of a backup for one user catalog to a disk data set:
//BACKCAT JOB
//BACKUP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//BACKUP
DD
DSN=BACKUP.ICFCAT.LAX.TEST,UNIT=SYSDA,SPACE=(CYL,(1,1)),
//
DCB=BLKSIZE=27998,DISP=(,CATLG)
//SYSIN
DD *
BACKUP
CAT (ICFCAT.LAX.TEST)
Back Up User Catalogs with a High-Level Qualifier
The following is an example of a backup for all catalogs with a high-level qualifier of
CATALOG:
//BACKCAT JOB
//BACKUP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//BACKUP
DD DSN=BACKUP.CATALOGS(+1),DCB=MODEL,DISP=(,CATLG)
//SYSIN
DD *
BACKUP
CAT (CATALOG.*)
Backup Using EXCEPT
The following is an example of a backup for all user catalogs except those having the
character string TEST anywhere in their names:
//BACKCAT JOB
//BACKUP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//BACKUP
DD DSN=BACKUP.PROD.CATALOGS,UNIT=TAPE,DISP=(,CATLG)
//SYSIN
DD *
BACKUP
CAT (ALL EXCEPT *TEST*)
Chapter 7: Backing Up, Restoring, and Recovering Reference 63
Restore Catalogs Reference
Back Up Specific Catalogs
The following is an example of a backup for all user catalogs with the character string
DB2 anywhere in their names, except two specific catalogs:
//BACKCAT JOB
//BACKUP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//BACKUP
DD
DSN=BACKUP.DB2.PROD.CATALOGS,UNIT=TAPE,DISP=(,CATLG)
//SYSIN
DD *
BACKUP
CATS (*DB2* EXCEPT CATALOG.DB2TEST CATALOG.DB2.IMSCNV)
Back Up Two User Catalogs
The following is an example of a backup for two user catalogs:
//BACKCAT JOB
//BACKUP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//BACKUP
DD DSN=BACKUP.CATS(+1),DCB=MODEL,DISP=(,CATLG)
//SYSIN
DD *
BACKUP
CATALOG (ICFCAT.USERCAT CATALOG.TESTCAT)
Restore Catalogs Reference
This section explains the required JCL associated with catalog restore.
JCL Requirements
To restore a catalog, the following JCL statements are required:
//jobname JOB
//RESTORE EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=class
//RESTORE DD DSN=user-outfile
//SYSIN
DD*
64 User Guide
Restore Catalogs Reference
The following are the statements in the required restore JCL:
jobname JOB
jobname is a user-specified job name.
RESTORE EXEC PGM=CREWS
Initiates a restore and specifies CA CREWS as the program name.
SYSPRINT DD SYSOUT=class
Specifies output message data.
RESTORE DD DSN= user-outfile
Specifies the restore output file as user-outfile.
SYSIN DD
Specifies the data set containing the CA CREWS control statements. The file is either
a sequential file with a fixed logical record length of 80, or a PDS member with a
fixed logical record length of 80.
Executing a Restore
When a RESTORE is performed, CA CREWS prompts you to confirm the restore of the
catalog. Enter YES to confirm the restore request, and NO to bypass the restore request.
Control Statements
The RESTORE control statement initiates a restore. The following shows the syntax for
RESTORE.
RESTORE
CATALOG (catalogname...[EXCEPT catalogname...])
OBJECTS ((catalogname...))
ALIAS| NOALIAS
INTOEMPTY
LOCK
CATALOG(catalogname)
CATALOG provides comprehensive catalog selection methods. The following table
explains the options for CATALOG:
Option
What You
Specify
Explanation
catalogname
ALL
Specifies for restore all user catalog names
currently defined in the master catalog.
Chapter 7: Backing Up, Restoring, and Recovering Reference 65
Restore Catalogs Reference
Option
EXCEPT
What You
Specify
Explanation
speccatname
Specifies for restore a particular catalog name.
gencatname
Specifies for restore (with a generic name) multiple
catalog names. For more information, see
Specifying Generic Catalog Names.
EXCEPT
Excludes from restore all catalog names that match
a fully qualified or generic name. You can exclude a
specific catalog or generic groups of catalogs by
specifying speccatname or gencatname. EXCEPT
and its parameters are optional.
...
...
Indicates an indefinite number of additional
specifications of catalog names.
Note: Acceptable variations of CATALOG are CAT and CATS.
IMPORT
Since the backup uses IDCAMS EXPORT, the restore uses IDCAMS IMPORT. The RESTORE
IMPORT parameters have the following values:
OBJECTS
Allows the IDCAMS IMPORT parameter OBJECTS to be specified when restoring a
catalog. The syntax is the same as when IDCAMS is used. CA CREWS does not edit
the OBJECTS parameter; it only passes it to IDCAMS.
ALIAS|NOALIAS
Specifies whether any aliases are defined for the imported catalog. Export includes
all aliases along with the backup of the catalog. If ALIAS is not specified, the default
is NOALIAS; no aliases are imported.
INTOEMPTY
Indicates the target catalog is empty. If the catalog being restored was redefined
prior to the restore, this is a necessary parameter.
LOCK
Indicates whether the catalog should be locked from access while it is being
imported.
Note: For complete information on IMPORT parameters, see IBM manuals regarding
DFSMS Access Method Services for Catalogs.
66 User Guide
Restore Catalogs Reference
Specifying Generic Catalog Names
Generic catalog names can contain skip characters. Skip characters are represented by
a plus-sign (+) or an asterisk (*). The plus-sign (+) skips only one character. The asterisk
(*) skips one or more characters.
Examples of Specifying Generic Catalog Names
The following are the examples of the generic catalog selection:
CATALOG.*
Selects all catalog names with a high-level qualifier of CATALOG
*DB2*
Selects all catalog names that contain the character string DB2
CATALOG.V3390++
Selects all catalog names that begin with CATALOG.V3390 and end in any two
characters
ICFCAT*CICS++
Selects all catalog names consisting of ICFCAT, followed by any number of
characters, then CICS followed by any two characters
Restore Examples
This section provides examples of restore jobstreams.
Restore One Catalog and Its Aliases
The following is an example of a restore for one catalog and its aliases:
//RESTORE JOB
//STEP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//RESTORE DD DSN=BACKUP.CATALOGS(-1),DISP=OLD
//SYSIN
DD *
RESTORE
ALIAS
CAT(CATALOG.MVSICF1.VSYSC06)
Chapter 7: Backing Up, Restoring, and Recovering Reference 67
Recover Catalogs Reference
Restore Two User Catalogs Into Previously Defined User Catalogs
The following is an example of a restore for two user catalogs into empty previously
defined user catalogs. Also, this jobstream restores the aliases for the catalog to the
master catalog:
//RESTCAT JOB
//RESTORE EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//RESTORE DD DSN=BACKUP.CATS(-1),DISP=OLD
//SYSIN
DD *
RESTORE
ALIAS
INTOEMPTY
CATALOG (ICFCAT.USERCAT CATALOG.TESTCAT)
Restore One Catalog and Its Aliases
The following is an example of a restore for one user catalog and its aliases to the
master catalog. Use the LOCK parameter to exclude all activity to this catalog during the
restore:
//RESTCAT JOB
//RESTORE EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//RESTORE DD DSN=BACKUP.CATALOGS(-1),DISP=OLD
//SYSIN
DD *
RESTORE
ALIAS
LOCK
CAT (CATALOG.CMH.USERCAT)
Recover Catalogs Reference
This section explains the required JCL associated with catalog recovery.
68 User Guide
Recover Catalogs Reference
JCL Requirements
To recover a catalog, the following JCL statements are required:
// jobname
JOB
//RECOVER EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=class
//SMF1
DD......
//SMFnnnnn DD...
//AMS1
DD DSN=ams1.[DCB=
//AMS2
DD DSN=ams2.[DCB=
//AMS3
DD DSN=ams3.[DCB=
//SYSOUT
DD SYSOUT=class
//SORTWKnn DD...
//SYSIN
DD *
blksize ]
blksize ]
blksize ]
The following are the statements in the required recovery JCL:
jobname JOB
jobname is a user-specified job name.
RECOVER EXEC PGM=CREWS
Initiates a restore and specifies CA CREWS as the program name.
SYSPRINT DD
Specifies output message data.
SMFnnnnn DD
SMF files can be QSAM or VSAM, on tape or disk, and can be any number of files in
any order. Interpreting the results of the recovery is easier if the files are in
chronological order. A maximum of 128 DD statements can be used. You should
code an SMF DD statement for each SMF file that covers some part of the recovery
period. nnnnn is anything that is valid for a DD name and makes each SMF DD
statement unique.
AMS1 DD DSN=ams1[DCB= blksize ]
AMS2 DD DSN=ams2[DCB= blksize ]
AMS3 DD DSN=ams3]DCB= blksize ]
Required statements that specify the output data sets for the AMS commands.
These three data sets contain fixed length 80-byte records. Block size can be
specified in blksize. The default block size is 4,000.
SYSOUT DD
Specifies the output message data set for sort messages.
SORTWKnn DD
Specifies sort work areas if required by the available system sort package.
SYSIN DD
Chapter 7: Backing Up, Restoring, and Recovering Reference 69
Recover Catalogs Reference
Specifies the data set containing the CA CREWS control statements. The file is either
a sequential file with a fixed logical record length of 80, or a PDS member with a
fixed logical record length of 80.
Control Statements
Syntax Statement
RECOVER initiates the recovery process. The following shows the syntax for RECOVER:
RECOVER
CATALOG (catalogname...[EXCEPT catalogname...])
FROM ([ ccyy.ddd ] [ hh:mm:ss ])
TO ([ ccyy.ddd ] [ hh:mm:ss ])
TIMEDIFFERENCE(sss)
ARCSYS (HSM|DMS|ABR)
ARCVOL (MIGRAT)
MASTERPW( password )
SMFDUMP
CATALOG(catalogname)
CATALOG provides comprehensive catalog selection methods. The following table
explains the options for CATALOG:
Option
What You
Specify
Explanation
catalogname
ALL
Specifies for recovery all user catalog names
currently defined in the master catalog.
speccatname
Specifies for recovery a particular catalog name.
gencatname
Specifies for recovery (with a generic name) multiple
catalog names. For more information, see Specifying
Generic Catalog Names.
EXCEPT
Excludes from recovery all catalog names that match
a fully qualified or generic name. You can exclude a
specific catalog or generic groups of catalogs by
specifying speccatname or gencatname. EXCEPT
and its parameters are optional.
EXCEPT
...
...
Indicates an indefinite number of additional
specifications of catalog names.
Note: Acceptable variations of CATALOG are CAT and CATS.
70 User Guide
Recover Catalogs Reference
ARCSYS(sysname)
ARCSYS lets you define the type of archival system you are using. The following options
are available:
HSM
Specify HSM if you are using the IBM archival system. HSM is the default.
DMS
Specify DMS if you are using the CA archival system.
ABR
Specify ABR if you are using the FDR archival system.
When using RACF to allow delete/noscratch functions, the CREWS userid must be
defined to the RACF logon group ARCCATGP. This allows the BYPASS RELOAD process in
DFHSM during catalog recovery.
ARCVOL(volser)
ARCVOL lets you specify the volume serial identifier used by your archival system.
Specify the volume that your archival system requires. MIGRAT is the default for HSM. If
your system supports multiple archival systems, ARCVOL lets you specify multiple
volume serial identifiers by specifying: ARCVOL (volser volser...)
MASTERPW(pw)
MASTERPW lets you specify the IDCAMS password so the operator does not have to
respond to it for each command. This parameter is added to IDCAMS commands.
SMFDUMP(opt)
SMFDUMP produces a dump of SMF records being processed for diagnostic purposes. It
reads and sorts SMF records. SMFDUMP is optional. If you specify SMFDUMP, one of the
following parameters must also be specified:
IN
Produces a dump in the same order that the records came in.
OUT
Produces the dump in sorted order.
BOTH
Produces a dump of the records in the order they came in, and another in sorted
order.
Chapter 7: Backing Up, Restoring, and Recovering Reference 71
Recover Catalogs Reference
FROM(date time) TO(date time)
FROM and TO define the beginning and end of the recovery time period. FROM and TO
must be specified.
ccyy.ddd
The date cc is an optional two-digit century, yy is a two-digit year, and ddd is a
three-digit day of the year in the range 001 to 366. If cc is not specified, the default
is 19.
hh:mm:ss
The time hh is a two-digit hour, mm is a two-digit minute, and ss is a two-digit
second.
TIMEDIFFERENCE=seconds
TIMEDIFFERENCE is the time difference, in seconds, between the time-of-day clocks in a
multiple-CPU environment. Specifying TIMEDIFFERENCE is optional.
sss
The time difference, in seconds, between the time-of-day clocks in a multiple-CPU
environment. The range is 1-999.
Specifying Generic Catalog Names
Generic catalog names can contain skip characters. Skip characters are represented by
a plus-sign (+) or an asterisk (*). The plus-sign (+) skips only one character. The asterisk
(*) skips one or more characters.
Examples of Specifying Generic Catalog Names
The following are the examples of generic catalog selection:
CATALOG.*
Selects all catalog names with a high-level qualifier of CATALOG
*DB2*
Selects all catalog names that contain the character string DB2
CATALOG.V3390++
Selects all catalog names that begin with CATALOG.V3390 and end in any two
characters
ICFCAT*CICS++
Selects all catalog names consisting of ICFCAT, followed by any number of
characters, then CICS followed by any two characters
72 User Guide
Recover Catalogs Reference
Recovery IDCAMS Requirements
To implement the IDCAMS commands created by recovery, the following JCL is required:
//RECOVER
JOB
//IDCAMS
EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=class
//SYSIN
DD DSN=ams1 ...
//
DD DSN=ams2 ...
//
DD DSN=ams3 ...
Recover Examples
This section provides examples of recover jobstreams.
Recover One User Catalog
The following is an example of a recover for one catalog on day number 169 from 4:30
pm to 7 pm:
//RECOVER JOB
//STEP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//SMF1
DD DSN=SYS1.MAN1,AMP='BUFND=30',DISP=SHR
//SMF2
DD DSN=SYS1.MAN2,AMP='BUFND=30',DISP=SHR
//SMF3
DD DSN=SYS1.MAN3,AMP='BUFND=30',DISP=SHR
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//AMS1
DD DSN=RECOVER.AMSOUT1,UNIT=SYSDA,SPACE=(TRK,(1,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS2
DD DSN=RECOVER.AMSOUT2,UNIT=SYSDA,SPACE=(TRK,(1,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS3
DD DSN=RECOVER.AMSOUT3,UNIT=SYSDA,SPACE=(TRK,(1,1)),
//
DISP=(NEW,CATLG,DELETE)
//SYSIN
DD *
RECOVER
FROM (2003.169 16:30:00) TO (2003.169 19:00:00)
CAT(CATALOG.MVSICF1.VSYSC06)
Chapter 7: Backing Up, Restoring, and Recovering Reference 73
Recover Catalogs Reference
The following is an example of a recover for one user catalog for the time period 6:00 to
8:15 on day 93 of 2001:
//RECVCAT JOB
//RECOVER EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//SMF1
DD DSN=SYS1.MAN1,AMP='BUFND=30',DISP=SHR
//SMF2
DD DSN=SYS1.MAN2,AMP='BUFND=30',DISP=SHR
//SMF3
DD DSN=SYS1.MAN3,AMP='BUFND=30',DISP=SHR
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(100,10))
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(100,10))
//AMS1
DD DSN=RECOVER.AMSOUT1,UNIT=SYSDA,SPACE=(TRK,(3,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS2
DD DSN=RECOVER.AMSOUT2,UNIT=SYSDA,SPACE=(TRK,(3,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS3
DD DSN=RECOVER.AMSOUT3,UNIT=SYSDA,SPACE=(TRK,(3,1)),
//
DISP=(NEW,CATLG,DELETE)
//SYSIN
DD *
RECOVER
FROM (01.093 06:00:00) TO (01.093 08:15:00)
CAT (CATALOG.CMH.USERCAT)
/*
//*
//*
Execute IDCAMS to update the catalog with the activity
//*
during the recovery period.
//*
//AMS
EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN
DD DSN=RECOVER.AMSOUT1,DISP=OLD
//
DD DSN=RECOVER.AMSOUT2,DISP=OLD
//
DD DSN=RECOVER.AMSOUT3,DISP=OLD
74 User Guide
Recover Catalogs Reference
Recover Two User Catalogs
The following is an example of a recover for two user catalogs during the time period
4:30 pm to 7:00 pm on day 169 of 2003. Use one SMF unloaded tape file and two active
SMF log files.
//RECVCAT JOB
//RECOVER EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//SMF1
DD DSN=MAN1.BACKUP(-1),DCB=BUFNO=20,DISP=OLD
//SMF2
DD DSN=SYS1.MAN1,AMP='BUFND=30',DISP=SHR
//SMF3
DD DSN=SYS1.MAN2,AMP='BUFND=30',DISP=SHR
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(100,10))
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(100,10))
//AMS1
DD DSN=RECOVER.AMSOUT1,UNIT=SYSDA,SPACE=(TRK,(10,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS2
DD DSN=RECOVER.AMSOUT2,UNIT=SYSDA,SPACE=(TRK,(10,1)),
//
DISP=(NEW,CATLG,DELETE)
//AMS3
DD DSN=RECOVER.AMSOUT3,UNIT=SYSDA,SPACE=(TRK,(10,1)),
//
DISP=(NEW,CATLG,DELETE)
//SYSIN
DD *
RECOVER
FROM (2003.169 16:30:00) TO (2003.169 19:00:00)
CATALOG (ICFCAT.USERCAT CATALOG.TESTCAT)
/*
//*
//*
Execute IDCAMS to update the catalog with the activity
//*
during the recovery period.
//*
//AMS
EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN
DD DSN=RECOVER.AMSOUT1,DISP=OLD
//
DD DSN=RECOVER.AMSOUT2,DISP=OLD
//
DD DSN=RECOVER.AMSOUT3,DISP=OLD
Chapter 7: Backing Up, Restoring, and Recovering Reference 75
Chapter 8: Checking and Fixing Functions
This chapter explains the required JCL associated with DIAGNOSE catalog backup and
provides the following:
■
JCL Requirements
■
Syntax statements
■
Control statements
■
Options
■
Examples
JCL Requirements
To diagnose catalogs or volumes, the following JCL statements are required:
// jobname
JOB
//DIAGNOSE EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=class
//SYSIN
DD *
The following are the statements in the required DIAGNOSE JCL:
jobname JOB
jobname is a user-specified job name.
DIAGNOSE EXEC PGM=CREWS
Specifies CA CREWS as the program name.
SYSPRINT DD SYSOUT=class
Specifies the output message data set.
SYSIN DD
Specifies the data set containing the control statements for CA CREWS. It can be DD
*, a sequential file with a fixed logical record length of 80, or a PDS member with a
fixed logical record length of 80.
Note: In the case of a catastrophic CATALOG/BCS/VVDS error, no AMS statements are
generated for the entries selected. IDCAMS diagnostic messages are provided to aid in
further recovery.
Chapter 8: Checking and Fixing Functions 77
JCL Requirements
Using DIAGNOSE
The following table explains the syntax statement for DIAGNOSE.
DIAGNOSE
VOLUME (volser...[EXCEPT volser...])
CATALOG (catname...[EXCEPT catname...])
MASTERPW=(password)
DIAGNOSE Control Statement
DIAGNOSE indicates that an IDCAMS DIAGNOSE is to be performed. The type of
diagnose to be performed is determined by choosing either CATALOG or VOLUME. A
DIAGNOSE VVDS is executed when you specify VOLUME. A DIAGNOSE ICFCAT is
executed when you specify CATALOG. You must specify one.
VOLUME(volser)
VOLUME provides comprehensive volume selection methods. The following table
explains the options for VOLUME:
Option
What You Specify
volser
78 User Guide
Explanation
Specifies for DIAGNOSE all
volumes currently defined in
the master catalog.
specvolser
Specifies for DIAGNOSE a
particular volume.
genvolser
Specifies for DIAGNOSE
(with a generic name)
multiple volumes.
EXCEPT
EXCEPT
Excludes from DIAGNOSE all
volumes that match a fully
qualified or generic name.
You can exclude a specific
volume or generic groups of
volumes by specifying
specvolser or genvolser.
EXCEPT and its parameters
are optional.
...
...
Indicates an indefinite
number of additional
specifications of volumes.
JCL Requirements
Note: Acceptable variations of VOLUME are VOL and VOLS.
Specifying Generic Volumes
Generic volumes can contain skip characters. Skip characters are represented by a
plus-sign (+) or an asterisk (*). The plus-sign (+) skips only one character. The asterisk
(*) skips one or more characters.
Examples Of Specifying Generic Volumes
The following are the examples of generic volume selection:
MVS*
Selects all volumes where the VOLSER begins with MVS.
*DB2*
Selects all volumes that contain the character string DB2 in their VOLSERs.
PROD++
Selects all volumes that begin with PROD and end in any two characters.
CATALOG(catalogname)
CATALOG provides comprehensive catalog selection methods. The following table
explains the options for CATALOG:
Option
What You
Specify
Explanation
catalogname
ALL
Specifies for recovery all user catalog names
currently defined in the master catalog.
speccatname
Specifies for recovery a particular catalog name.
gencatname
Specifies for recovery (with a generic name) multiple
catalog names. For more information, see Specifying
Generic Catalog Names.
EXCEPT
Excludes from recovery all catalog names that match
a fully qualified or generic name. You can exclude a
specific catalog or generic groups of catalogs by
specifying speccatname or gencatname. EXCEPT
and its parameters are optional.
EXCEPT
Chapter 8: Checking and Fixing Functions 79
JCL Requirements
Option
What You
Specify
...
...
Explanation
Indicates an indefinite number of additional
specifications of catalog names.
Note: Acceptable variations of CATALOG are CAT and CATS.
Specifying Generic Catalog Names
Generic catalog names can contain skip characters. Skip characters are represented by
a plus-sign (+) or an asterisk (*). The plus-sign (+) skips only one character. The asterisk
(*) skips one or more characters.
Examples of Specifying Generic Catalog Names
The following are the examples of generic catalog selection:
CATALOG.*
Selects all catalog names with a high-level qualifier of CATALOG
*DB2*
Selects all catalog names that contain the character string DB2
CATALOG.V3390++
Selects all catalog names that begin with CATALOG.V3390 and end in any two
characters
ICFCAT*CICS++
Selects all catalog names consisting of ICFCAT, followed by any number of
characters, then CICS followed by any two characters
MASTERPW(password)
MASTERPW specifies the master password of the master catalog. CA CREWS uses VSAM
macros to read the master catalog in order to find user catalog names. If the master
catalog at your installation is password protected, the password needs to be specified to
avoid open errors or operator prompting.
80 User Guide
JCL Requirements
Required DIAGNOSE Output JCL
This section shows the required JCL generated by DIAGNOSE.
DIAGNOSE VVDS JCL Requirements
Specifying DIAGNOSE VVDS causes the following JCL to be written to the AMS1 file for
any VVDS entries with errors:
//CREWS
JOB
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD SYSPRINT DD SYSOUT=*
//DD1
DD UNIT=unit,VOL=SER=volser1,DISP=SHR
//SYSIN
DD *
DELETE (name) CATALOG (catname)
DELETE (name) VVR FILE (DD1) CATALOG (catname)
DIAGNOSE ICFCAT JCL Requirements
For any catalog entries with errors, the following is written to the AMS1 file:
DELETE (name) NOSCRATCH CATALOG (catname)
IDCAMS JCL Requirements
To implement the IDCAMS commands created by DIAGNOSE, the following JCL is
required:
//JOB
//IDCAMS
//SYSPRINT
//SYSIN
JOB
EXEC PGM=IDCAMS
DD SYSOUT=A
DD DSN=ams1 ...
Chapter 8: Checking and Fixing Functions 81
JCL Requirements
DIAGNOSE Examples
Sample DIAGNOSE of All Catalogs
The following JCL performs a DIAGNOSE on all catalogs with complete checks for all
VVDSs. The delete jobstream is saved for you to examine and submit.
//DIAGNOSE
//DIAG
//SYSPRINT
//SYSIN
DIAGNOSE
CAT (ALL)
JOB
EXEC PGM=CREWS
DD SYSOUT=A
DD *
Sample DIAGNOSE VVDS Jobstream For Specific VOLSERs
The following JCL performs a DIAGNOSE VVDS on all volumes with a VOLSER beginning
with MVS:
//DIAG
//STEP
//SYSPRINT
//SYSIN
DIAGNOSE
VOL(MVS*)
JOB
EXEC PGM=CREWS
DD SYSOUT=A
DD *
Sample DIAGNOSE VVDS on Specific Volsers
The following JCL performs a DIAGNOSE VVDS on all volumes with a VOLSER beginning
with DB2 . The delete jobstream is saved for you to examine and submit.
//DIAG
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//SYSIN
DD *
DIAGNOSE
VOL (DB2*)
82 User Guide
JCL Requirements
Sample DIAGNOSE ICFCAT Jobstream
The following JCL performs a DIAGNOSE ICFCAT on all catalogs having the character
string DB2 anywhere in their name:
//DIAG
JOB
//STEP
EXEC PGM=CREWS
//SYSPRINT DD SYSOUT=A
//SYSIN
DD *
DIAGNOSE
CATALOG (*DB2*)
Chapter 8: Checking and Fixing Functions 83
Chapter 9: Reporting CA 7 Catalog
Dependencies
If a given job or application system is considered critical, then any catalog containing
pertinent catalog records is equally critical. You should take special care to ensure that
these catalogs are backed up more frequently and recovery data is more accessible. The
CREWSCA7 catalog dependency analysis tool assists you in determining these
dependencies.
CREWSCA7 extracts catalog environment information from the system catalog where it
runs. It then extracts job-related information from CA 7, correlates catalog
dependencies of those jobs, and summarizes its analysis in three sets of reports.
This information helps you classify your system catalogs as critical production,
production, or as any other classification that makes sense in your environment. Once
you have classified your catalogs, you can assign relative priorities to keep the most
critical catalogs free of errors and ensure they are adequately backed up.
Note: To use this feature, you must have CA 7 r3.3 or higher. CREWSCA7 accesses CA 7
through the CCI interface provided in r3.3.
This section contains the following topics:
How CA 7 Catalog Dependency Analysis Works (see page 85)
Types of CA 7 Catalog Dependencies (see page 86)
Required JCL (see page 87)
Control Statements (see page 88)
How CA 7 Catalog Dependency Analysis Works
To determine catalog dependencies, CREWSCA7 performs the following actions:
■
CREWSCA7 queries CAICCI for all occurrences of CA 7 within the current
environment. These are listed for your convenience.
Note: To produce correct results, CREWSCA7 needs to be run in the production
environment with the local node. Although both local and remote nodes can be
accessed, only the local system's master catalog will be used as the reference point.
However, if the remote node shares the same catalog environment as the local
node, correct results are still achieved even if that remote node is accessed.
■
CREWSCA7 extracts job-related information from CA 7 at the application system
level. You can include or exclude entire application systems by name, either
explicitly, or generically using pattern masking.
Chapter 9: Reporting CA 7 Catalog Dependencies 85
Types of CA 7 Catalog Dependencies
■
CREWSCA7 determines which catalog is required for each data set from every job
involved.
■
CREWSCA7 generates the following three sets of summary and detail reports, six in
all, plus the processing log containing control statements processed and any other
messages.
–
CA 7 Catalog Dependency By Application System (Summary and Detail)
For each application system, CREWSCA7 displays the system catalogs required.
The detail report identifies the specific data sets whose records are contained
in the catalog, along with job name, step name and, DD name.
–
CA 7 Catalog Dependency By Catalog (Summary and Detail)
For each system catalog, CREWSCA7 displays the CA 7 application systems and
jobs that depend on that catalog. The detail report identifies the specific data
sets whose records are contained in the catalog, along with system name, job
name, step name, and DD name.
–
CA 7 Catalog Dependency By Job (Summary and Detail)
For each CA 7 job, CREWSCA7 displays the system catalogs required. The detail
report identifies the specific data sets whose records are contained in the
catalog, along with job name, system name, step name, and DD name.
Types of CA 7 Catalog Dependencies
System catalogs often are either taken for granted or are not considered as part of the
application system. The reports generated by CREWSCA7 reveal the important
relationship between your production environment and the system catalogs. The
following types of dependencies may become evident in the reports:
86 User Guide
■
Single application systems or even single jobs that require multiple catalogs in order
to run. This represents multiple points of failure, any one of which would prevent
that system or job from running.
■
All of your production jobs depend on a single catalog. In this extreme, a single
catalog failure could stop your entire production environment. It would be prudent
to back this catalog up multiple times each day since it would tend to be highly
volatile. You might consider using a catalog for each application system or group of
application systems.
■
Non-production catalogs in use. Your disaster recovery plans might not take that
catalog into account. In this case, consider changing the catalog alias to designate
an appropriate production catalog.
■
The system's master catalog appears in the list. In this case, you need to create a
catalog alias for those data sets. The master catalog should be protected so that
only the system administrators can update it. Catalog records in the master catalog
may be accessible only to one system, creating a "data set not found" condition if
the affected jobs are run in another shared system.
Required JCL
Required JCL
The following JCL is required for running CREWSCA7:
//CREWSCA7 JOB
//ANALYZE EXEC PGM=CREWSCA7,REGION=0M
//STEPLIB DD DISP=SHR,DSN=crews.linklib
//
DD DISP=SHR,DSN=ca-7.loadlib
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,100)
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,100)
//SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,100)
//SYSPRINT DD SYSOUT=* Processing log
//APPLSUM DD SYSOUT=* Application system summary
//APPLDTL DD SYSOUT=* Application system detail
//CATSUM
DD SYSOUT=* Catalog summary
//CATDTL
DD SYSOUT=* Catalog detail
//JOBSUM
DD SYSOUT=* Job summary
//JOBDTL
DD SYSOUT=* Job detail
//SYSOUT
DD SYSOUT=* Sort's messages
//SYSIN
DD *
SYSTEM(ALL)
JCL Description
EXEC PGM=CREWSCA7
Specifies CREWSCA7 as the program name.
STEPLIB
Required if either CA CREWS or CA 7 is not in the linklist.
SORTWKnn
Required. Specifies disk work areas necessary for your system sort program.
SYSOUT
Required. Specifies a data set for SORT's messages.
SYSPRINT
Required. Specifies a data set for output messages.
Chapter 9: Reporting CA 7 Catalog Dependencies 87
Control Statements
APPLSUM
Required. Specifies a data set for "CA 7 Catalog Dependency By Application System Summary" report.
APPLDTL
Required. Specifies a data set for "CA 7 Catalog Dependency By Application System Detail" report.
CATSUM
Required. Specifies a data set for "CA 7 Catalog Dependency By Application System Summary" report.
CATDTL
Required. Specifies a data set for "CA 7 Catalog Dependency By Application System Detail" report.
JOBSUM
Required. Specifies a data set for "CA 7 Catalog Dependency By Job - Summary"
report.
JOBDTL
Required. Specifies a data set for "CA 7 Catalog Dependency By Job - Detail" report.
SYSIN
Specifies a data set for CREWSCA7 control statements.
If DD DUMMY is specified, the following rules apply:
■
CREWSCA7 will access the production CA 7 system on the local CCI node.
■
The user ID associated with the job is used to authenticate access to CA 7.
■
CREWSCA7 analyzes all CA 7 jobs.
Control Statements
The following control statements identify which CA 7 system to be accessed and which
application systems are to be analyzed.
CA7ID(id)
CA7PSWD(password)
CA7NODE(ccinode)
CA7SSCT(PROD|TEST)
SYSTEM(ALL|ca-7_system ca-7_sys* ...
[ EXCEPT ca-7_system])
Note: If no control statements are encountered, or if DD DUMMY is specified for SYSIN,
all the default settings will be applied.
88 User Guide
Control Statements
CA7ID(id)
Specifies the CA 7 logon ID normally used to log onto a CA 7 terminal. If omitted, the
security profile associated with the job is used to access CA 7us security options offered
by CA 7, it is possible that taking this default will be inadequate. If you have problems
connecting with CA 7 local CA 7 system administrator for a proper ID and password.
CA7PSWD(password)
Specifies the password associated with the CA 7 logon ID mentioned above. If CA7PSWD
is omitted, but CA7ID is specified, no password is given to CA 7. If CA7PSWD is specified,
but CA7ID is omitted, the password is ignored and the security profile associated with
the job is used to access CA 7.
CA7NODE(ccinode)
Specifies the CCI node where CREWSCA7 is to find a CA 7 system. If omitted, the local
node is assumed.
CA7SSCT(PROD|TEST)
Specifies which CA 7 system on the target CCI node is to be accessed. The valid options
are "PROD" for the production system and "TEST" for the test system. If omitted,
CA7SSCT(PROD) is assumed.
Chapter 9: Reporting CA 7 Catalog Dependencies 89
Control Statements
SYSTEM(applsys)
Specifies the CA 7 application system or systems to be analyzed. Every CA 7 job has an
associated system name. The following options are used with the SYSTEM control
statement:
ALL
All CA 7 application systems are included in the analysis.
applsys
The specific or generic application system names to be included in the analysis.
EXCEPT applsys
The specific or generic application systems that are to be excluded from the search.
Note: CA 7 permits the system name to be blank. To refer to the all-blank system name,
you must use the special keyword *BLANKS* in the system parameter. For example, if
you want to include only the named systems in your analysis, you would specify:
SYSTEM(ALL EXCEPT *BLANKS*)
Specifying Generic System Names
Generic system names can contain skip characters. Skip characters are represented by a
plus-sign(+) or an asterisk (*). The plus sign (+) skips only one character. The asterisk
skips one or more characters.
Examples of Specifying Generic System Names:: The following are the examples of
generic system name selection:
PAY*
Selects all CA 7 application systems beginning with PAY.
*WKLY*
Selects all CA 7 application systems containing WKLY anywhere in their name.
++MAINT
Selects all CA 7 application systems containing MAINT starting in the third letter of
the name.
Using combinations of generic system names with ALL and EXCEPT, you can select any
combination of application systems to be analyzed. For example, you specify:
SYSTEM(ADMIN PAY* MFG* MKT* EXCEPT PAYYR* MFGYR* MKTYR* MKTMAINT)
This would include the ADMIN system, all systems beginning with PAY, MFG, MKT unless
they begin with PAYYR, MFGYR, MKTYR. Also, the MKTMAINT system would be
excluded.
90 User Guide
Control Statements
CREWSCA7 Examples
Catalog Dependency Analysis of All Systems
The following JCL performs a catalog dependency analysis on every system defined to
CA-7. Since this job is being run by the CA-7 system administrator, there is no need to
specify an ID or password. Also, since every system is to be analyzed, which is the
default, there is no need to specify the SYSTEM parameter. Therefore, there is no need
for any control input, so the SYSIN DD statement is dummied out. In this case, all the
jobs in all CA-7 application systems are analyzed.
//CREWSCA7
//RPT
//STEPLIB
//
//SORTWK01
//SORTWK02
//SORTWK03
//SYSPRINT
//APPLSUM
//APPLDTL
//CATSUM
//CATDTL
//SYSOUT
//SYSUDUMP
//SYSIN
JOB
EXEC
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
DD
(1),'CA-7 Admin',CLASS=A
PGM=CREWSCA7,REGION=0M
DISP=SHR,DSN=CAI.ISM.CAILIB
DISP=SHR,DSN=CAI.CA7.CAILIB
UNIT=SYSDA,SPACE=(CYL,200)
UNIT=SYSDA,SPACE=(CYL,200)
UNIT=SYSDA,SPACE=(CYL,200)
SYSOUT=* PROCESSING LOG
SYSOUT=* APPLICATION SYSTEM SUMMARY
SYSOUT=* APPLICATION SYSTEM DETAIL
SYSOUT=* CATALOG SUMMARY
SYSOUT=* CATALOG DETAIL
SYSOUT=* SORT'S MESSAGES
SYSOUT=*
DUMMY
Chapter 9: Reporting CA 7 Catalog Dependencies 91
Control Statements
Catalog Dependency Analysis of the Payroll System
The following JCL performs a catalog dependency analysis on the payroll system. This
system is considered by the Payroll Department to be crucial to continued operations in
a disaster recovery scenario. They want to ensure the related system catalogs are
identified for the payroll system backup. Since the storage administrator does not have
a CA-7 ID, the CA-7 system administrator sets up a special ID "JOHN" with the password,
"TESTING". This ID and password is given to CA-7 through the CA7ID and CA7PSWD
parameters. Since the application system to be analyzed is the payroll system, that
name is given through the SYSTEM parameter. In this case, all the jobs comprising the
CA-7 system "PAYROLL" are analyzed.
//CREWSCA7 JOB (1),'Storage Admin',CLASS=A
//RPT
EXEC PGM=CREWSCA7,REGION=0M
//STEPLIB
DD
DISP=SHR,DSN=CAI.ISM.CAILIB
//
DD
DISP=SHR,DSN=CAI.CA7.CAILIB
//SORTWK01 DD
UNIT=SYSDA,SPACE=(CYL,200)
//SORTWK02 DD
UNIT=SYSDA,SPACE=(CYL,200)
//SORTWK03 DD
UNIT=SYSDA,SPACE=(CYL,200)
//SYSPRINT DD
SYSOUT=* PROCESSING LOG
//APPLSUM
DD
SYSOUT=* APPLICATION SYSTEM SUMMARY
//APPLDTL
DD
SYSOUT=* APPLICATION SYSTEM DETAIL
//CATSUM
DD
SYSOUT=* CATALOG SUMMARY
//CATDTL
DD
SYSOUT=* CATALOG DETAIL
//JOBSUM
DD
SYSOUT=* JOB SUMMARY
//JOBDTL
DD
SYSOUT=* JOB DETAIL
//SYSOUT
DD
SYSOUT=* SORT'S MESSAGES
//SYSUDUMP DD
SYSOUT=*
//SYSIN
DD
*
CA7ID(JOHN)
CA7PSWD(TESTING)
SYSTEM(PAYROLL)
92 User Guide
Chapter 10: Rebuilding Catalogs
The Catalog Rebuild utility lets catalog administrators rebuild broken catalogs without
the typical restore from a previous backup and subsequent forward recovery process.
This section contains the following topics:
How the Catalog Rebuild Utility Works (see page 93)
JCL Example and Steps (see page 93)
How the Catalog Rebuild Utility Works
The Catalog Rebuild utility rebuilds VSAM catalogs where the data, index components,
or both have been corrupted, or where the pointers are incorrect. This process requires
three jobs, each containing a series of job steps. When the jobs are executed, the
Catalog Rebuild utility performs the following functions:
■
Deletes output from the previous job submission
■
Locks and reads the catalog to be repaired
■
Generates the IDCAMS control statements to define the catalog aliases
■
Sorts the catalog data into logical statements
■
Deletes the catalog, but not the records contained within
■
Redefines and loads the repaired catalog
■
Redefines the catalog aliases
■
Unlocks the catalog
Note: The Catalog Rebuild utility is designed to resolve only the type of catalog problem
in which the VSAM catalog data, index components, or both are broken. This utility will
not correct other catalog type problems.
JCL Example and Steps
The jobs, steps, and associated programs in the Catalog Rebuild utility are described
here. An example of the JCL for each job is shown.
Chapter 10: Rebuilding Catalogs 93
JCL Example and Steps
Job 1: Delete and Lock
In this job, the IDCAMS program deletes the output from any previous runs and locks
the catalog being rebuilt for the duration of the job.
JOB1 JCL:
//JOBNAME JOB (acct number),'pgmr name',CLASS=x,
// MSGCLASS=x,MSGLEVEL=(1,1),NOTIFY=&SYSUID.
//*
//*****************************************************************
//* DELETE OUTPUT DATASETS FROM PREVIOUS EXECUTIONS
//* AND LOCK CATALOG IN ERROR
//*****************************************************************
//*
//LOCKCAT EXEC PGM=IDCAMS
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
*
DELETE HLVLNOD.UNLOADED.CAT
PURGE
DELETE HLVLNOD.DEF.ALIAS
PURGE
DELETE HLVLNOD.UNLOADED.SORTED.CAT PURGE
VERIFY DATASET(HLVLNOD.USER.CATALOG)
SET MAXCC=0
ALTER HLVLNOD.USER.CATALOG LOCK
IF LASTCC NE = 0
THEN CANCEL
//*
Job 2: Backup, Read/Write, List, and Sort
This job does the following:
■
Step 1:
–
Backs up the input catalog
–
Reads the catalog records
–
Writes the catalog records to a sequential dataset
■
Step 2: Lists the catalog alias records
■
Step 3: Sorts the sequential dataset into logical sequence
Note: Before you run this job, verify that the previous job performed a lock on the
catalog with a zero return code.
94 User Guide
JCL Example and Steps
Step 1: Backup, Read, and Write
In this step, the XCATDUMP program does the following:
■
Reads the catalog in error physically to end of extent
■
Writes all data read to a temporary file
■
Generates the define Alias control statements required at the end of the job
■
Reads control statements from the SYSIN DD
The control statements from the SYSIN DD identify the function to be performed.
Currently, the only valid function is COPY. This control statement requires no additional
parameters. The following table provides an example and explains the COPY statement:
Example
Explanation
//SYSIN DD * COPY
Required. Identifies the function to be performed, copy catalog
designated in sysut1 dd statement in the JCL. This control
statement must begin in column 1.
Chapter 10: Rebuilding Catalogs 95
JCL Example and Steps
Note: This program must execute from an APF authorized library.
JOB2 JCL:
//JOBNAME JOB (acct number),'pgmr name',CLASS=x,
// MSGCLASS=x,MSGLEVEL=(1,1),NOTIFY=&SYSUID.
//*
//JOBLIB DD DSN= HLVLNOD.CREWS.LINKLIB,DISP=SHR
//*
//*****************************************************************
//*
BEFORE RUNNING THIS JOB
//* YOU MUST VERIFY THE PREVIOUS JOB PERFORMED A LOCK ON
//* THE CATALOG WITH A ZERO RETURN CODE
//*****************************************************************
//*
//******************************************************************
//* BACKUP INPUT CATALOG
//******************************************************************
//BACKUP EXEC PGM=CREWS
//*
//BACKUP
DD DSN= HLVLNOD.CREWS.BACKUP,
//
UNIT=3390,
//
VOL=SER=??????,
//
SPACE=(CYL,(?,?1)),
//
DISP=(NEW,CATLG,DELETE)
//SYSPRINT DD SYSOUT=*
//SYSIN
DD *
BACKUP
CAT (HLVLNOD.USER.CATALOG)
//*
//***************************************************************************
//* READ THE CATALOG PHYSICALLY PAST SOFTWARE EOF TO END OF EXTENT
//***************************************************************************
//*
//* THIS PROGRAM MUST RUN FROM AN AUTHORIZED LIBRARY.
//*
//* SYSUT1 - THE CORRUPTED CATALOG TO BE CORRECTED AND RESTORED
//*
INPUT
//*
//* SYSUT2 - THE CATALOG DATA IN PHYSICAL SEQUENCE
//*
OUTPUT
//*
//* SYSUT3 - THE DEFINE ALIAS COMMANDS REQUIRED TO RECONNECT
//*
OUTPUT
THIS USER CATALOG TO THE MASTER
//*
THIS STEP WILL BUILD AND WRITE THEM TO THIS DD
//*
//*
//DUMPCAT EXEC PGM=XCATDUMP,REGION=0M,
//
COND=(4,LE,BACKUP)
//STEPLIB DD
DISP=SHR,DSN=YOUR.TEST.CREWS.LINKLIB
//SYSPRINT DD
SYSOUT=*
//SYSUT1
DD
DISP=SHR,DSN=HLVLNOD.USER.CATALOG
//SYSUDUMP DD
SYSOUT=*
//SYSUT2
DD
DSN=HLVLNOD.UNLOADED.CAT,DISP=(,CATLG),
// UNIT=3390,VOL=SER=??????,SPACE=(CYL,(?,?))
<<<CHANGE VOLSER
//SYSUT3
DD
DSN=HLVLNOD.DEF.ALIAS,DISP=(,CATLG),
// UNIT=3390,VOL=SER=??????,SPACE=(CYL,(?,?))
<<<CHANGE VOLSER
//SYSIN
DD
*
COPY
//*
96 User Guide
JCL Example and Steps
Step 2: List Alias Control Statements
In this step, the IEBGENER program lists the define Alias control statements generated
by the XCATDUMP program.
//************************************************
//* LIST THE DEFINE ALIAS COMMANDS
//************************************************
//*
//PUNCH
EXEC PGM=IEBGENER
//SYSPRINT DD DUMMY
//SYSIN
DD DUMMY
//SYSUT1
DD DSN=HLVLNOD.DEF.ALIAS,DISP=OLD
//SYSUT2
DD SYSOUT=*
//*
Step 3: Sort the Catalog
In this step, the SORT program sorts the catalog data back into logical sequence
//***********************************************************
//* SORT THE CATALOG DATA BACK INTO LOGICAL SEQUENCE
//***********************************************************
//*
//SORTCAT EXEC PGM=SORT
//SYSOUT
DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SORTIN
DD DSN=HLVLNOD.UNLOADED.CAT,DISP=OLD
//SORTOUT DD DSN=HLVLNOD.UNLOADED.SORTED.CAT,DISP=(,CATLG),
// UNIT=3390,VOL=SER=??????,SPACE=(CYL,(5,5))
<<<CHANGE VOLSER
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(10,10))
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(10,10))
//SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(10,10))
//SYSIN
DD *
SORT FIELDS=(14,45,CH,A)
//*
Job 3: Delete, Redefine, Load, Define, and Reconnect
This job does the following:
■
Deletes and redefines the user catalog
■
Loads the newly defined user catalog
■
Defines the alias pointers and reconnects the catalog entries
Chapter 10: Rebuilding Catalogs 97
JCL Example and Steps
Step 1: Delete and Redefine User Catalog
In this step, the IDCAMS program deletes the original catalog and redefines the user
catalog.
Note: Before you run this job, verify that all steps in the previous job have completed
successfully.
JOB3 JCL:
//JOBNAME JOB (acct number),'pgmr name',CLASS=x,
// MSGCLASS=x,MSGLEVEL=(1,1),NOTIFY=&SYSUID.
//*
//JOBLIB DD DSN= HLVLNOD.CREWS.LINKLIB,DISP=SHR
//*****************************************************************
//*
BEFORE RUNNING THIS JOB
//* PLEASE VERIFY ALL STEPS IN THE PREVIOUS JOB, COMPLETED
//* SUCCESSFULLY.
//*****************************************************************
//*
//*****************************************************************
//* DELETE THE USER CATALOG, BUT DON'T DELETE THE DATA SETS
//* DEFINED IN IT, ALSO DEFINE THE USER CATALOG
//*
//*****************************************************************
//*
//DEFCAT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE (HLVLNOD.USER.CATALOG) USERCATALOG RECOVERY FORCE
DEFINE USERCATALOG –
(NAME('HLVLNOD.USER.CATALOG') VOLUMES(??????) TRACKS(??,??))
/*
>>
CHANGE VOLSER ABOVE AND PRIMARY/SECONDARY ALLOCATIONS <<
//*
*/
Step 2: Load the User Catalog
In this step, the XCATREST program loads the newly defined user catalog.
The XCATREST program reads control statements from the SYSIN DD. These statements
identify the function to be performed. Currently, the only valid function is RESTORE. This
control statement requires no additional parameters. The following table provides an
example and explains the RESTORE statement:
98 User Guide
Example
Explanation
//SYSIN DD *
RESTORE
Required. Identifies the function to be performed, restore
catalog designated in sysut1 dd statement in the JCL. This
control statement must begin in column 1.
JCL Example and Steps
Note: This program must execute from an APF authorized library.
//**************************************************************
//*
RESTORE CORRUPTED CATALOG
//****************************************************************************
//*
//* THIS PROGRAM MUST RUN AUTHORIZED.
//*
//* SYSUT1 - OUTPUT FILE FROM STEP SORTCAT, DD SORTOUT ABOVE
//*
INPUT THE CATALOG DATA IN LOGICAL SEQUENCE (SORTEDRTED).
//*
//* SYSUT2 - THE NAME OF THE CATALOG TO BE RESTORED
//*
OUTPUT SAME NAME AS THE CORRUPTED CATALOG DUMPED D
//*
IN DUMPCAT STEP.
//*
//* LOAD THE CATALOG FROM THE SORTED CATALOG RECORDS
//****************************************************************************
//*
//RESTCAT EXEC PGM=XCATREST,
//
COND=(4,LE,DEFCAT)
//STEPLIB DD
DISP=SHR,DSN=YOUR.TEST.CREWS.LINKLIB
//SYSPRINT DD
SYSOUT=*
//SYSUT1
DD
DISP=SHR,DSN=HLVLNOD.UNLOADED.SORTED.CAT
//SYSUT2
DD
DISP=OLD,DSN=HLVLNOD.USER.CATALOG
//SYSUDUMP DD
SYSOUT=*
//SYSIN
DD
*
RESTORE
Step 3: Define and Reconnect
In this step, the IDCAMS program defines the alias pointers and reconnects the user
catalog entries.
//***********************************
//* RECONNECT THE ALIAS POINTERS
//***********************************
//*
//DEFALIAS EXEC PGM=IDCAMS,
//
COND=(4,LE,RESTCAT)
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
DSN=HLVLNOD.DEF.ALIAS,DISP=OLD
//
DD
*
ALTER HLVLNOD.USER.CATALOG UNLOCK
Chapter 10: Rebuilding Catalogs 99
Chapter 11: Using Real Time Reorg
(CREWSRTR)
When a User Catalog requires reorganization it is necessary to be able to perform that
function while the catalog is open. While the IBM provided LOCK command ensures that
the catalog cannot be updated it also causes jobs that reference the catalog to get JCL
errors. This is not very efficient in a production environment. The CREWS Real Time IFC
Usercatalog Reorg facility, CREWSRTR, will reorganize a User Catalog in real time causing
jobs requiring the catalog to wait until the reorganization is complete. Production
schedules are not disrupted to the extent that jobs have to be monitored and
rescheduled when the reorganization is finished.
Since CREWSRTR issues a hardware RESERVE on the volume on which the ICF Catalog
resides, it is strongly recommended that MIM, GSR or a comparable product be used to
convert the hardware reserve to an ENQ. The MAJOR QNAME used is SYSIGGV2 and the
MINOR QNAME is the dataset name pointed to by the CATALOG DD statement. If you
are reorganizing to a new volser then an additional RESERVE will be issued for the new
device as well. The MAJOR QNAME is CREWSRTR and the MINOR name is the dataset
name pointed to by the CATALOG DD statement. As with above, it is strongly
recommended that MIM, GSR or a comparable product be used to convert the
hardware reserve to an ENQ.
It is highly recommended that CREWSRTR be first executed in TEST mode to:
■
Ensure the validity of any DEFINE USERCATALOG overrides provided in SYSIN.
■
Produce a report containing the attributes of the USER CATALOG that you might
consider overriding for the reorganization.
■
Simulate the backup process and let you know how much space will be required for
the SORTIN/SORTOUT datasets. This is accomplished via message RTR9999I.
■
Produce a dataset containing all of the ALIAS definitions that will be issued after the
data portion of the catalog has been reorganized.
It is also highly recommended that you perform a backup of the catalog prior to the
reorganization.
Chapter 11: Using Real Time Reorg (CREWSRTR) 101
JCL Example and Steps
Note: For information related to RTR messages, see the Message Reference Guide.
This section contains the following topics:
Required JCL (see page 103)
Syntax Statements (see page 106)
Overriding USERCATALOG Parms (see page 108)
Examples (see page 109)
Parameters (see page 110)
Restart Considerations (see page 111)
102 User Guide
Required JCL
Required JCL
CA strongly recommends that before attempting to reorganize a catalog that CREWSRTR
be first executed in TEST mode. The JCL required is:
//jobname JOB
//REORG
..
EXEC PGM=CREWSRTR,PARM='TEST',REGION=0M
//SYSPRINT DD SYSOUT=class
//CATALOG
DD DISP=OLD,DSN=usercatalog.name
//DEFUCAT
DD SYSOUT=*
//RESTART
DD SYSOUT=*
//SYSUDUMP DD SYSOUT=class
Note: DEFUCAT & RESTART are put to a SYSOUT class for your examination. The DEFINE
statement that will be presented to Access Method Services is based on the current
attributes of the usercatalog combined with ALL overrides as defined in SYSIN.
Once TEST mode has been run then use the following JCL to perform the REORG.
To reorganize an ICF user catalog the following JCL statements are required:
//jobname JOB
..
//REORG
EXEC PGM=CREWSRTR,
//
PARM={Optional parameters},REGION=0M
//SYSPRINT DD SYSOUT=class
//CATALOG
DD DISP=OLD,DSN=usercatalog.name
//SORTIN
DD UNIT=SYSDA,DISP=(,DELETE),SPACE=( ..
//SORTOUT
DD UNIT=3390,DISP=(,CATLG,CATLG),DSN=datasetname,
//
SPACE=( ..
//SORTWK01 DD UNIT=SYSDA,DISP=(,DELETE),SPACE=( .
//SORTWK02 DD UNIT=SYSDA,DISP=(,DELETE),SPACE=(
//SORTWK03 DD UNIT=SYSDA,DISP=(,DELETE),SPACE=(
//SYSOUT
DD SYSOUT=class
//ALIAS
DD UNIT=3390,DISP=(,CATLG,CATLG),DSN=datasetname,
//
SPACE=( .
//DEFUCAT
DD UNIT=3390,DISP=(,CATLG,CATLG),DSN=datasetname,
//
SPACE=(TRK,(1)),DCB=BLKSIZE=800
//RESTART
DD UNIT=3390,DISP=(,CATLG,CATLG),DSN=datasetname,
//
SPACE=(TRK,(1)),DCB=BLKSIZE=800
//SYSUDUMP DD SYSOUT=class
//SYSIN
DD *
Following are the statements in the required CREWSRTR JCL:
jobname JOB
Defines the user-specified jobname.
REORG EXEC PGM=CREWSRTR
Specifies CREWSRTR as the program name
Chapter 11: Using Real Time Reorg (CREWSRTR) 103
Required JCL
SYSPRINT DD SYSOUT=class
Specifies the output message dataset
CATALOG DD
Specifies the name of the ICF Usercatalog DSN=catalogname,DISP=OLD to be
reorged.
If DISP=SHR is coded and SHAREOPTIONS are specified as (3,4) then CREWSRTR will
ALTER to SHR(3,3) prior to restoring the catalog and then ALTER to (3,4) when the
restore is complete.
If you are RESTARTING the CREWSRTR process at the DEFINE (implying that the
catalog doesn't exist) then the DD statement must contain the VOLSER and UNIT on
which the catalog is to be allocated.
SORTIN DD
Defines a temporary dataset used to hold the existing catalog records.
Optional when PARM='TEST'. If coded with PARM='TEST' then the CATALOG will be
backed up to this dataset.
SORTOUT DD
Defines a PERMANENT dataset used to contain the sorted catalog records produced
by CREWSRTR. Not used when PARM='TEST'.
SORTWK0x DD
Defines SORT Work files that may be required by the sort. Note that if the sort
supports dynamic sortworks then these statements may not be required. Not used
when PARM='TEST'.
SYSOUT DD
Specifies the output message dataset produced by the SORT. Not used when
PARM='TEST'.
ALIAS DD
Specifies a PERMANENT dataset that will contain control statements produced by
CREWSRTR that will be used to reconnect ALIAS entries. Optional for PARM='TEST'.
If coded then the dataset will contain all of the DEFINE ALIAS statements that
CREWSRTR will present to Access Method Services after the data records have been
restored.
DEFUCAT DD
Specifies a PERMANENT dataset that will contain the IDCAMS DEFINE
USERCATALOG control statements.
If you are RESTARTING CREWSRTR then this dataset contains the IDCAMS control
statements created by CREWSRTR previously. You must change the DISP= to
SHR/OLD. You can modify the control statements prior to executing the RESTART.
There can be no more than 33 card images in this dataset.
104 User Guide
Required JCL
RESTART DD
Specifies a PERMANENT dataset that will contain the JCL required to perform a
RESTART. This JCL is produced for the event that the DEFINE for the USERCATALOG
fails. If this happens then you must modify the DEFINE statement as it appears in
the dataset defined by DEFUCAT correcting the problem that caused the DEFINE to
fail. Modify the JCL in the dataset pointed to by RESTART and submit the job.
SYSUDUMP DD
The dataset that MVS uses when a program check occurs. This dataset provides
diagnostic information that CA will require should a dump be taken.
SYSIN DD
Defines the set of user overrides for the definition of the user catalog. The DD
statement is required; however, all statements are optional.
Chapter 11: Using Real Time Reorg (CREWSRTR) 105
Syntax Statements
Syntax Statements
The SYSIN dataset can be used to supply new values for most USERCATALOG value. For
example, the reorganization may be required because the catalog has taken many
extents. Increasing the allocation will reduce the number of extents.
All statements are freeform. They may be continued onto one or more subsequent
cards. Parameters in {} denote the several ways that they may be defined.
{USERCATALOG/UCAT}(
{CYLINDERS/CYL/CYLS(primary secondary)
TRACKS/TRKS/TRK(primary secondary)
RECORDS/RECS(primary secondary)
KILOBYTES/KB(primary secondary)
MEGABYTES/MB}(primary
secondary)}
{VOLUME/VOL}(volser)
{BUFFERSPACE/BUFSPC/BUFSP}(buffer size)
BUFND(number of data buffers)
BUFNI(number of index buffers)
{CONTROLINTERVALSIZE/CNVSZ/CISZ/CISIZE](size of control interval)
{DATACLASS/DATACLAS}(class)
{MANAGEMENTCLASS/MGMTCLAS}(class)
{STORAGECLASS/STORCLAS}(class)
OWNER(owner id)
{ECSHARING/ECSHR}|{NOECSHARING/NOECSHR}
{FREESPACE/FSPC}(CI-percent CA-percent)
{RECORDSIZE/RECSZ}(average maximum)
{SHAREOPTIONS/SHR}(crossregion crosssystem)
STRNO(number of strings)
TO(date)|FOR(days)
{WRITECHECK/WCK}|{NOWRITECHECK/NWCK}
)
DATA(
{CYLINDERS/CYL/CYLS(primary secondary)
TRACKS/TRKS/TRK(primary secondary)
RECORDS/RECS(primary secondary)
KILOBYTES/KB(primary secondary)
MEGABYTES/MB}(primary
secondary)}
{BUFFERSPACE/BUFSPC/BUFSP}(buffer size)
BUFND(number of data buffers)
{CONTROLINTERVALSIZE/CNVSZ/CISZ/CISIZE](size of control interval)
{FREESPACE/FSPC}(CI-percent CA-percent)
{RECORDSIZE/RECSZ}(average
maximum)
{WRITECHECK/WCK}|{NOWRITECHECK/NWCK}
)
106 User Guide
Syntax Statements
{INDEX/IX}(
{CYLINDERS/CYL/CYLS(primary secondary)
TRACKS/TRKS/TRK(primary secondary)
RECORDS/RECS(primary secondary)
KILOBYTES/KB(primary secondary)
MEGABYTES/MB}(primary
secondary)}
BUFNI(number of index buffers)
{CONTROLINTERVALSIZE/CNVSZ/CISZ/CISIZE](size of control interval)
{WRITECHECK/WCK}|{NOWRITECHECK/NWCK}
)
The values that you specify will be used to REDEFINE the user catalog prior to reloading
the catalog's data records. The rules for these parameters can be found in the document
DFSMS Access Method Services for Catalogs.
Chapter 11: Using Real Time Reorg (CREWSRTR) 107
Overriding USERCATALOG Parms
Overriding USERCATALOG Parms
CREWSRTR fully populates a DEFINE USERCATALOG statement based on the CURRENT
definition of the user catalog.
Any parameter overridden by the USERCATALOG control statements will replace the
CURRENT values. Any parameter specified for the DATA portion will be used to replace
the CURRENT values for the DATA element. Any parameter specified for the INDEX
portion will then override those values.
So, for example:
UCAT(BUFND(6) BUFNI(4))
DATA(BUFND(7))
Will result in 7 buffers given to the DATA and 4 to the INDEX.
If a space parameter is given on the USERCATALOG control statement then the
CURRENT values for the DATA and INDEX will be removed. So, for example; the catalog
was initially defined as MB(200 100) and NO specification was given to the DATA/INDEX
components. Catalog management itself would have created values for the size of the
DATA and INDEX components.
For example:
UCAT(CYLINDERS(150 100))
Will allow Catalog Management to decide on the amount of space given to the DATA
and INDEX components.
UCAT(CYLINDERS(150 100))
DATA(CYLINDERS(125 100))
Will allocate 125 cylinders to the data portion and allow Catalog Management to
compute the INDEX allocation.
UCAT(CYLINDERS(150 100))
DATA(CYLINDERS(125 100))
INDEX(CYLINDERS(37 10))
Will allocate 125 cylinders to the DATA component and 37 cylinders to the INDEX
component. The UCAT specification is basically ignored.
Note: It is illegal to specify INDEX space allocation and NOT specify DATA space
allocation.
108 User Guide
Examples
Examples
Example 1
The user catalog has taken excessive extents. The original allocation for the catalog was
CYLINDERS(20 10). An allocation of CYLINDERS(150 100) would cause the catalog to use
just a single extent:
//SYSIN DD *
USERCATALOG(CYLINDERS(150 100))
/*
Example 2
In addition to multiple extents the catalog has excessive ci and/or ca splits.
//SYSIN DD *
UCAT(FREESPACE(25 20) CYLINDERS(150 100))
Example 3
Changing the number of data/index buffers may improve performance.
//SYSIN DD *
USERCATALOG
(
FREEPACE
(25
20)
CYLS(150,100)
BUFND(7)
BUFNI(4)
)
Note: The statements are freeform. The operands of the USERCATALOG statement are
enclosed in ( ).
Chapter 11: Using Real Time Reorg (CREWSRTR) 109
Parameters
Parameters
There are optional parameters that may be specified as a PARM on the EXEC statement.
They may be specified in any order.
PARM='TEST' will cause CREWSRTR to:
■
Parse the control statements
■
Produce a "report" of the attributes of the catalog named in the CATALOG DD.
■
Simulate/BACKUP the CATALOG. If //SORTIN DD is coded then records will actually
be written to that dataset. Produces messages RTR998I and RTR999I. RTR999I
contains the number of 23440 byte blocks necessary to hold the BACKUP.
■
Terminate WITHOUT reorganizing the user catalog.
PARM='DEBUG' will cause CREWSRTR to:
■
DUMP the input and output areas of the call to the Catalog Services Interface
routine.
■
Produce the DEFINE USERCATALOG statement that would have been submitted to
Access Method Services.
PARM='RESTART' tells CREWSRTR to restart processing at the time that it DEFINES the
user catalog.
Note: See Restart Considerations (see page 111) for more information.
110 User Guide
Restart Considerations
Restart Considerations
You have executed CREWSRTR and the DEFINE of the USERCATALOG failed, possibly
because there is not enough space on the volume specified. The original DEFINE
USERCAT control statements were written to //DEFUCAT. You have modified the card
images in //DEFUCAT and now want to try again. The JCL required to perform the
RESTART was created in the dataset pointed to by the RESTART DD statement in the
previous run.
When you attempt to RESTART CREWSRTR, the following rules are enforced:
■
The 1st statement of DEFUCAT must be DEFINE USERCATALOG( in col 2
■
The 2nd statement must contain NAME(dsn in col 2
■
The DSN specified in the NAME( statement must match the DSN specified in
//CATALOG DD DSN=
■
1st statement of ALIAS must be define alias is col 2
■
2nd statement must be (name( in col 10
■
3rd statement must be relate(dsn in col 10
■
4th statement must be catalog(catdsn in col 10
■
All ALIAS dsnames must = dsn in DEFUCAT and dsn in DEFUCAT must match
CATALOG DD
Note: If the DEFINE failed and no CATALOG exists, you must change the //CATALOG DD
statement to include the VOLSER.
For example:
//CATALOG DD DSN=user.cat,DISP=OLD,VOL=SER=mycvol,UNIT=3390
You have executed CREWSRTR and the DEFINE USERCATALOG actually FAILED due to
one or more parameters you have coded. For example, not enough space exists on the
target volume. Since the DEFINE failed we have NO user catalog. When you use
RESTART, the DD statements for SORTOUT and ALIAS must point to EXISTING datasets.
SORTIN, SYSOUT & the SORTWKnn statements are not used.
PARM='RESTART,TEST' is invalid.
Chapter 11: Using Real Time Reorg (CREWSRTR) 111
Chapter 12: Synchronizing Master Catalogs
In a shared catalog environment, changes made to one master catalog often are not
propagated to all other catalogs. This causes users on different LPARS to have different
views of the intended catalog structure. The Master Catalog Alias Synchronizer (MCAS)
utility provides an automated and efficient process for resolving these types of master
catalog and alias conflicts, and keeps all master catalogs synchronized.
This section contains the following topics:
How the MCAS Works (see page 113)
Types of Problems Detected (see page 114)
Inputs and Outputs (see page 114)
Control Statements (see page 116)
JCL Examples and Steps (see page 117)
How the MCAS Works
The MCAS is a single batch job containing a series of steps. To locate and analyze the
master catalogs in a shared catalog environment, the MCAS utility performs the
following steps:
■
Connects the master catalogs to be analyzed to the master catalog of the system
where the analysis is occurring.
■
Identifies all catalog aliases and catalog definitions that are missing. The names of
the catalogs to be analyzed can be specified explicitly or generically.
■
Locates and reads the requested master catalogs.
■
Analyzes the requested master catalogs for conflicts in the catalogs and aliases.
■
Generates processing and analysis reports. MCAS reports on hazardous conflicts in
catalog alias definitions and in catalog definitions. No corrective action is generated
since these types of analogies must be reviewed and corrected by an individual
familiar with the local catalog environment.
■
Generates IDCAMS control statement commands to resolve the conflicts. These
control statements are placed in a sequential file for subsequent review and
processing.
Chapter 12: Synchronizing Master Catalogs 113
Types of Problems Detected
Types of Problems Detected
As the MCAS process analyzes the contents of multiple master catalogs, it checks for
specific types of anomalies:
Problem
Description
Missing Alias
At least one of the master catalogs did not contain a given
catalog alias definition, while at least one other master catalog
did.
Missing Catalog
Definition
At least one of the master catalogs did not contain a given user
catalog definition, while at least one other master catalog did.
Alias Conflict
Occurs when alias entries for the same catalog alias were found
in multiple master catalogs, but they point to different user
catalogs.
Catalog Definition
Conflict
Occurs when catalog entries for the same catalog are found in
multiple master catalogs, but they indicate different volume
serial numbers and, therefore, are not referring to the same
catalog.
Inputs and Outputs
The inputs and outputs of the MCAS program are:
114 User Guide
DD Name
Description
SYSIN
Required. Input. Control statements used
for catalog selection and filtering.
SYSPRINT
Required. Output. Processing log showing
the control statements that were
processed, syntax problems with the
control statements, errors encountered
during processing, and final totals.
Inputs and Outputs
DD Name
Description
MISSING
Required. Output. A detailed, tabular
report broken into two sections.
The first section identifies the missing
catalog aliases. The report shows only the
ones that are missing and indicates which
catalog needs the definition. This section
of the report is in alias name sequence.
The second section identifies the missing
catalog definitions. The report will show
only the ones that are missing and
indicate which catalog needs the
definition. This section of the report is in
order of the missing catalogs.
CONFLICT
Required. Output. A detailed, tabular
report broken into two sections.
The first section identifies conflicting
conditions found in the alias definitions.
This section of the report is in alias name
sequence.
The second section identifies conflicting
conditions found in catalog definitions.
This section of the report is in order by
catalog definition.
SYSPUNCH
Required. Output. A sequential data set
with LRECL=80 RECFM=FB that contains
the IDCAMS control statements to
perform the corrective actions to the
various master catalogs being analyzed.
This output is in order by the master
catalog being updated.
For each master catalog to be updated, an
IDCAMS comment is generated to flag the
beginning of such a sequence.
Immediately following this, are the
IDCAMS control statements to perform all
the corrective actions for that catalog.
The output contains as many of these
sequences as is required to correct all of
the master catalogs that were found to
have correctable problems.
SYSOUT
Required. Output. Used by internal SORT.
Chapter 12: Synchronizing Master Catalogs 115
Control Statements
Control Statements
The CREWMCAS program reads control statements from the SYSIN DD. These
statements identify the catalogs to be analyzed and other processing options.
Statement
Function
CATALOG(S)
Required. Identifies the master catalogs to be analyzed. The
catalogs can be identified explicitly or generically.
The list can be further filtered with the use of the keyword
EXCEPT.
LOG()
TIMEOUT(n)
116 User Guide
■
Any explicit or generic catalog names found after the
EXCEPT keyword are names to be filtered out.
■
CATALOG can be abbreviated as CAT.
■
If EXCEPT is being used, at least one catalog name
specification must appear before the EXCEPT keyword.
■
Any number of explicit or generic catalog names can be
specified before the EXCEPT keyword. Any number of
explicit or generic catalog names can be coded after the
EXCEPT keyword.
Optional. Used by CA technical support for diagnosis. Valid
values = (TASK) or (ALL)
■
(TASK) logs only subtask related data.
■
(ALL) logs both TASK and Detail data.
Subtask timeout value, where "n" is minutes, max timeout
value is 30. Five minutes is the recommended timeout value.
JCL Examples and Steps
Control Statement Example
Here is an example of a control statement:
CATALOG(ICF.MASTER.*ICF.PRIMARY.*EXCEPT ICF.MASTER.TEST ICF.MASTER.VM*)
These facts apply to the example control statement:
■
The master catalog is named ICF.MASTER.SYSA.
■
ICF.MASTER.SYSA contains these catalog definitions:
–
ICF.MASTER.SYSB
–
ICF.MASTER.SYSC
–
ICF.MASTER.TEST
–
ICF.MASTER.VMTEST1
–
ICF.MASTER.VMTEST2
–
ICF.PRIMARY.SHADA
–
ICF.PRIMARY.SHADB
–
ICF.PRIMARY.SHADC
■
The current system's master catalog, ICF.MASTER.SYSA, is searched for catalog
definitions. If the local system's master catalog name does not match the CATALOG
selection criteria, it is searched only for catalogs to analyze. However, because its
name matches the CATALOG selection criteria, its contents are also analyzed.
■
Based on the selection criteria, the following catalog names are not analyzed:
–
ICF.MASTER.TEST
–
ICF.MASTER.VMTEST1
–
ICF.MASTER.VMTEST2
JCL Examples and Steps
The steps and associated programs in the MCAS utility are described here. An example
of the JCL for each step is shown.
Chapter 12: Synchronizing Master Catalogs 117
JCL Examples and Steps
Step 1: Delete Previous Output
In this step, the IDCAMS program deletes the output from any previous runs of this job.
/JOBNAME JOB (acct number),'pgmr name',CLASS=x,
// MSGCLASS=x,MSGLEVEL=(1,1),NOTIFY=&SYSUID.
//*
//*********************************************************************
//* PURGE OUTPUT DATASETS FROM PREVIOUS JOB EXECUTION
//*********************************************************************
//IDCAMS
EXEC PGM=IDCAMS
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD
*
DELETE HLVLNODE.CREWMCAS.EXCPTNS.SYSPUNCH PURGE
DELETE HLVLNODE.CREWMCAS.EXCPTNS.QSAM
PURGE
Step 2: Locate, Read, and Check
In this step, the CREWMCAS program does the following:
118 User Guide
■
Locates the requested master catalogs
■
Reads the requested master catalogs
■
Performs analysis checking for catalog, volume, and alias conflicts
■
Generates the following output:
–
Master Catalog Alias Synchronizer Processing Report
–
Missing Alias Report by Alias Name Report
–
Missing Catalog Definition Report by Catalog Report
–
Alias Conflict Report by Alias Report
–
Catalog Definition Conflict Report by Catalog
–
Catalog Updates for Catalogs Report
–
Catalog Updates for Catalogs Output Data Set
JCL Examples and Steps
Control Statements (through sysin dd)
This utility enables a fully-qualified and generic selection of catalogs to be scanned
through the CATALOG parameter. An EXCEPT command parameter also is supported,
enabling the exclusion of catalogs when using generic selection. A LOG command is
provided for diagnostic purposes if needed.
Note: This program must execute from an APF authorized library.
//*********************************************************************
//* LOCATE AND READ ALL INTENDED CATALOGS, ANALYZE, REPORT, AND
//* PRODUCE CONTROL STATEMENTS TO RESOLVE CATALOG CONFLICTS
//*********************************************************************
//CREWMCAS EXEC PGM=CREWMCAS,REGION=0M
//SORTWK01 DD
UNIT=SYSDA,SPACE=(CYL,30)
//SORTWK02 DD
UNIT=SYSDA,SPACE=(CYL,30)
//SORTWK03 DD
UNIT=SYSDA,SPACE=(CYL,30)
//SORTWK04 DD
UNIT=SYSDA,SPACE=(CYL,30)
//EXCWORK
DD
DSN=HLVLNODE.CREWMCAS.EXCPTNS.QSAM,
//
VOL=SER=VVVVVV,UNIT=3390,SPACE=(CYL,(10,10)),
//
DISP=(,CATLG,CATLG)
//SYSPUNCH DD
DSN=HLVLNODE.CREWMCAS.EXCPTNS.SYSPUNCH,
//
VOL=SER=VVVVVV,UNIT=3390,SPACE=(CYL,(10,10)),
//
DISP=(,CATLG,CATLG)
//SYSOUT
DD
SYSOUT=*
//SYSPRINT DD
SYSOUT=*
//MISSING
DD
SYSOUT=*
//CONFLICT DD
SYSOUT=*
//SYSIN
DD
*
CATALOG(ICF.MASTER.VMVCAT* EXCEPT ICF.MASTER.VMVCAT39 ICF.MASTER.VMVCAT06)
Step 3: List Control Statements
In this step, the IEBGENER program lists the control statements generated in the output
data set from the CREWMCAS program.
//*********************************************************************
//* LIST CONTROL STATEMENTS GENERATED IN THE OUTPUT DATASET FROM
//* PREVIOUS STEP
//*********************************************************************
//COPY
EXEC PGM=IEBGENER
//SYSPRINT DD DUMMY
//SYSIN
DD DUMMY
//SYSUT1
DD DSN=HLVLNODE.CREWMCAS.EXCPTNS.SYSPUNCH,DISP=SHR
//SYSUT2
DD SYSOUT=*
Chapter 12: Synchronizing Master Catalogs 119
JCL Examples and Steps
Step 4: Synchronize Master Catalogs
In this step, the IDCAMS program lists the control statements generated in the output
data set from the CREWMCAS program and synchronizes the master catalogs.
Note: Before executing this step, it is recommended that you review the output from
the previous IEBGENER program.
//************************************************************************
//* EXECUTE CONTROL STATEMENTS TO SYNCHRONIZE MASTER CATALOGS
//*
//* NOTE: THIS STEP CAN BE COMMENTED OUT FOR REVIEW OF THE
//* COMMAND CONTROL STATEMENTS PRODUCED IN THE CREWMCAS
//* STEP ABOVE, PRIOR TO EXECUTING THE CORRECTIONS (IF NEEDED)
//************************************************************************
//IDCAMS
EXEC PGM=IDCAMS
//SYSPRINT DD
SYSOUT=*
//SYSIN
DD DSN=.CREWMCAS.EXCPTNS.SYSPUNCH,DISP=OLD
120 User Guide
Chapter 13: Interfacing with CA Vantage
SRM
CA CREWS interacts with CA Vantage SRM to provide tools that assist data center
personnel with overseeing and maintaining ICF catalogs.
CA CREWS subcomponents interface with CA Vantage SRM to provide comprehensive
reporting, monitoring, and automation capabilities.
This section contains the following topics:
CREWSCHK Interface (see page 121)
CREWSCA7 Interface (see page 122)
CREWSACE/CREWSABT Interface (see page 123)
CREWSCHK Interface
The CREWSCHK Catalog Checkup tool provides a snapshot of your entire system catalog
environment. It displays all catalogs connected to the target system and various catalog
settings. For example, it detects the catalogs that have grown into more than five
extents or the catalogs that have incurred more than 50 ca-splits. This tool also verifies
that the correct SMF records are being stored for use during possible disaster recovery
situations.
Note: For information about how to use the CREWSCHK tool, see Using the Catalog
Checkup Tool (CREWSCHK).
CREWSCHK Control Statements
CREWSCHK can be run either through CA Vantage SRM using freeform CREWSCHK
control statements or using the defaults for the CREWSCHK control statements. When
you invoke CREWSCHK using the default control statements, the following information is
displayed:
■
Name of the user catalog
■
Volume serial number of the device on which the user catalog is located
■
Number of EXTENTS taken by the user catalog
■
Percentage of user catalog space available
Chapter 13: Interfacing with CA Vantage SRM 121
CREWSCA7 Interface
■
VSAM cross region and cross system share option defined for user catalog
■
ECS flag specifying whether enhanced catalog sharing is permitted
■
Number of control interval splits taken by user catalog
■
Number of control area splits taken by user catalog
■
Number of aliases defined in user catalog
Data Options
After you have extracted data about the system catalog environment, you can use CA
Vantage SRM to do the following:
■
Print data, export data to an Excel spreadsheet, or email data
■
Summarize, sort, and view data as a table, graph, or list
■
Use filters to identify and extract relevant data
■
Back up, restore, or diagnose the named catalog
CREWSCA7 Interface
The CREWSCA7 Catalog Dependency Analysis component extracts catalog information
from the system catalog. It then extracts job-related information from CA 7 and
correlates catalog dependencies of these jobs.
This tool also produces early warnings for possible catalog problems that may occur
during your production job cycle. To use this feature, you must have CA 7 r3.3 or higher.
Note: For more information about using CREWSCA7, see Reporting CA 7 Job
Management Catalog Dependencies.
CREWSCA7 Control Statements
CREWSCA7 can be run through CA Vantage SRM using freeform CREWSCA7 control
statements. A CA Vantage SRM script either can be run at your discretion or you can
schedule it to run on a routine basis to capture complete CREWSCA7 data regarding all
CA 7 systems.
The dynamic interface creates a personal file for the user that made the request while
the script creates a fixed file for the automated request. Each of these files can be
accessed through CA Vantage SRM display objects.
122 User Guide
CREWSACE/CREWSABT Interface
There are six display objects, divided into three categories. Each of the categories
contains a summary display as well as a detail display. The three categories include:
■
CA 7 Catalog Dependency by application system
■
CA 7 Catalog Dependency by catalog
■
CA 7 Catalog Dependency by job
Data Options
You can use CA Vantage SRM to do the following:
■
Print, export to an Excel spreadsheet, or email data
■
Summarize, sort, and view data as a table, graph, or list
■
Use filters to identify and extract relevant data
■
Back up, restore, or diagnose the named catalog
■
Use zoom lists to migrate from the application view to the related catalog view and
obtain detailed information about the user catalog by zooming to the catalog
display object
CREWSACE/CREWSABT Interface
The CREWSACE (Automated Catalog Environment) component automatically gathers
data from the catalog, VTOC, and VVDS exceptions that occur in a catalog environment.
This data is input to CREWSABT for further analysis.
The CREWSABT component provides analysis on the exception dataset produced by
CREWSACE.
Note: For more information about using CREWSACE and CREWSABT, see Working in the
Automated Catalog Environment (ACE)
CREWSACE Control Statements
You can run CREWSACE through CA Vantage SRM using either freeform CREWSACE
control statements, or using a fixed set of control statements that perform a
CATALOG(ALL) VOLUME(ALL) function. You also can schedule a CA Vantage SRM script
to routinely run the fixed control statements. You can run the system script at your own
discretion.
Chapter 13: Interfacing with CA Vantage SRM 123
CREWSACE/CREWSABT Interface
Reporting Objects
Both dynamic interfaces create a VSAM file. You can use the CREWSABT reporting
objects to report about the VSAM file The CREWSABT reporting objects include the
following:
124 User Guide
Reporting Objects
Description
Uncataloged Datasets Lists
Datasets found on the volumes requested
that are not in the catalog that was
specified.
Scratched Datasets Lists
Datasets found in the specified catalog
that were not found on the device to
which the catalog points. These datasets
can be safely uncataloged from the
specified catalog.
Not Mounted Volumes Lists
Datasets found in the specified catalog
that cannot be verified because the
volume to which the catalog points was
not mounted.
Incorrectly Cataloged Datasets Lists
Datasets found in the specified catalog
where it has been determined that they
should have been cataloged into a User
Catalog.
NoAlias Report Lists
Datasets found in the specified catalog
where no alias has been defined.
NoUserCat Report Lists
Datasets found in the specified catalog
where no related user catalog exists.
UnUsedAlias Report Lists
Entries found in the specified catalog that
have no associated dataset.
VVDSVTOC Report Lists
Entries found in the specified catalog
where either the VVDS record or the VTOC
record, or both, is missing.
Index
A
ABR
ARCSYS control statement
option • 28
ARCVOL control statement
option • 28
ACE
batch • 30
batch control statements • 31
BUFSIZE control statement • 29
DELAY control statement • 29
description • 24
Exception panel • 36
All systems
catalog dependency analysis
CREWSCA7 examples • 91
B
Backup
Backup Function • 47
Backup Process • 48
Backup Reporting • 48
Flexible Catalog Backup • 48
IDCAMS DIAGNOSE and EXPORT • 48
Procedure • 48
BUFFERS control statement
diagnostic • 29
BUFSIZE control statement • 29
C
CA CREWS Protection Functions • 47
CA Vantage SRM
Interface with CA-CREWS • 121
CREWSABT • 121
CREWSACE • 121
CREWSCA7 • 121
CREWSCHK • 121
D
DEFALIAS
NOALIAS control statement
parameter • 33
DELAY control statement • 29
DELETE
NOALIAS control statement
parameter • 33
UNCATALOGED control statement
parameter • 32
WRONGCAT control statement
parameter • 33
DMS
ARCSYS control statement
option • 28
ARCVOL control statement
option • 28
E
Exception panel • 36
H
HSM
ARCSYS control statement
option • 28
ARCVOL control statement
option • 28
I
INFO
NOALIAS control statement
parameter • 33
UNCATALOGED control statement
parameter • 32
WRONGCAT control statement
parameter • 33
M
Master Catalog Alias Synchronizer (MCAS)
Alias synchronizer • 113
Synchronizing Master Catalogs • 113
merging user catalogs • 41
MOVE
NOALIAS control statement
parameter • 33
WRONGCAT control statement
parameter • 33
P
Payroll system
Index 125
catalog dependency analysis
CREWSCA7 examples • 91
R
Rebuilding catalogs
Catalog Rebuild Utility • 93
RECATALOG
UNCATALOGED control statement
parameter • 32
Recover
Flexible Catalog Recovery • 50
Procedure • 50
Recover Process • 50
SMF Records and IDCAMS Commands • 50
S
Synchronizing Master Catalogs
Alias synchronizer • 113
Master Catalog Alias Synchronizer (MCAS) • 113
126 User Guide