mainstar : backup & recovery manager suite - ibm - united states

Mainstar®: Backup & Recovery Manager™ Suite User Guide

All/Star Product Version 6, Release 01

SC23-6061-00 November 2006

Mainstar Software Corporation P.O. Box 4132 Bellevue, WA 98009 USA

Tel 1-425-455-3589 Fax 1-425-455-1992 Technical Support: [email protected] Web: www.mainstar.com

Copyright ©2006 Mainstar Software Corporation. All Rights Reserved Mainstar Software Corporation is a wholly owned subsidiary of Rocket Software, Inc.

mailto:[email protected]

http://www.mainstar.com/

Backup and Recovery Manager Suite: All/Star User Guide

Seventeenth Edition (November 2006)

This edition of the Mainstar: Backup & Recovery Manager Suite User Guide supports Version 6 Release 01 of the Mainstar: Backup & Recovery Manager Suite product.

Restricted Materials Notice

This manual contains restricted materials proprietary to Mainstar Software Corporation. Use and possession of this manual is pursuant to the user obtaining a license for Mainstar: Backup & Recovery Manager Suite from Mainstar Software Corporation.

Trademarks

'Mainstar' is a registered trademark of Mainstar Software Corporation in the United States and/or other countries.

The following terms used in this publication have been adopted by Mainstar Software Corporation as trademarks in the United States and/or other countries.

ABARS Manager All/Star

Aggregate LoadBalancer ASAP

Catalog RecoveryPlus CATSCRUB

Incremental ABARS FullRename

Prevent BackLevel

The following terms used in this publication have been adopted by the IBM Corporation as trademarks in the United States and/or other countries.

AIX DFSMSdss z/OS

IBM DFSMShsm

The following terms used in this publication have been adopted by other corporations as trademarks in the United States and/or other countries:

TRADEMARK COMPANY

Adabas™ Software AG

Brightstor® CA-FAVER® Computer Associates International, Inc.

FDR™ Innovation Data Processing

Quick-Ref™ Chicago-Soft

©2000–2006 by Mainstar Software Corporation All Rights Reserved

November 2006 SC23-6061-00 Seventeenth Edition

Mainstar Software Corporation ©2006 i Contents SC23-6061-00

PROPRIETARY: Unauthorized use, reproduction, or distribution prohibited.

User Guide Backup and Recovery Manager Suite: All/Star

Summary of Changes

Document SC23-6061-00 This version of the Backup & Recovery Manager Suite User Guide November 2006 supports Version 6 Release 01 of the Backup & Recovery Manager Suite: Seventeenth Edition All/Star product.

Integrated Maintenance See Fixlist distributed with release for details.

Documentation Updates • Split the Backup & Recovery Manager Suite User Guide into two User Guides, one for ABARS Manager, and one for All/Star. Add ASAP to the BRM Suite documents.

• Update Chapter 2, BRM Suite: Online Dialog, to: − update image in BRMINI Values – Menu Option 2 (24159) − update Define Utility Equivalents panel (24734) − add ABARS Manager and All/Star as needed to Utilities Sub-Menu

(25607) • Update Chapter 3, All/Star: Setup and Configuration – Option 1 to: − add note that BACKVOL is not tracked by All/Star (22701)

• Update Chapter 4, All/Star: Backup and Recovery Management – Option 2 to: − add JCLOUT Dataset Prefix to Select Restore Option panel (22703) − add Include BACKVOL to Set Up RESTORE panel (22701)

• Update Chapter 5, BRM Suite: Features – Option 4 to: − revise CATSCRUB panel & field descriptions for CR+ 0631 (22218) − change the default of CATSCRUB SIMULATE to Y (21875) − revise CATSCRUB panel & field descriptions for CR+ 0641 (23977)

• Update Chapter 6, BRM Suite: Search for Data Set – Option 5 to: − add Quick Search option (23043)

• Update Chapter 7, All/Star Reports – Online Using Option 6 to: − add CA-FAVER to Dataset List Report (16642) − add SYNCGENR to Dataset List Report (23002) − update Jobname List Report Example to include end date and time

(23073) − add Overlap by Application Report (21325) − add CFCAMS to Dataset List Report (23101) − update Jobname List Report to add start/end dates/times (23283) − update Critical in ASAP with No All/Star Backup Record report

example (22854) − update BKUPEND Summary Report example (24015) − add note regarding ICF catalog maintenance (23746) − add ADARUN to Dataset List Report Panel (22849) − add Include BCDS field to BKUPEND Summary Report (23595)

• Update Chapter 8, BRM Suite: History – Option 8 to: − explain how BRM determines how many events to retain for the

History display (24145) − update program types in PGM/Type field description

• Update Chapter 9, All/Star Batch Processing & Output to: − add CA-FAVER to the TYPE parameter of REPORT DSNLIST

(16642) − add OVERLAPA-AST report (21325)

Contents ii Mainstar Software Corporation ©2006 SC23-6061-00



− add date and time parameters to JOBLIST report (23283) − add the BACKVOL command (22701) − add note regarding ICF catalog maintenance (23746) − update AUTODUMP and ASTEXPIRE sections (22361) − update list of utilities in TYPE field description − add INCLBCDS to REPORT BKUPEND command (23595)

• Update Chapter 10, BRM Suite: Dynamic Data Set Backup/Reorganization to:− change all occurrences of SI042DC0 to BRM01BRR (21482)

• Update Chapter 13, All/Star: Build Restore to: − add INCLBACKVOL keyword to BLDREST command (22701) − add NEWHLQ keyword to BLDREST command (22961)

• Update Chapter 14, All/Star: All/Star Tracking Started Task to: − add F AST, STATUS command to display status of the monitor task

(22369) − edit the command description for starting the started task (23004) − AST started task modify command enhanced to accept Reload(all)

command (22816) − update Expiring Backups and Applications from the BRM Inventory

Data Set (22361) − change all IEFUJI references to IEFUSI (24384) − edit the method recommended to start the started task

• Update Chapter 15, BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR to: − revise command syntax and examples to match CR+ 0641 (23977)

• Update Appendix A, All/Star Skeleton Processing and Skeleton Variables to: − add skeleton variable &FAVERLOADLIB (16642) − add skeleton variable &EHSMDATE (22701) − add generic variable &NEWHLQ (22961) − add path variables &PATHESUFX and &PATHSUFX (22961) − add non-VSAM variable &DSNSUFX (22961) − add skeleton command )LEAVE (22701) − add cluster variables &CAIXSUFX and &CDSNSUFX (22961) − add data components &DAIXSUFX and &DDSNSUFX (22961) − add index components &IAIXSUFX and &IDSNSUFX (22961) − add )SET# command (22849) − add generic variable &ADALOADLIB (22849) − add Adabas event fields (22849)

• Update TOC and Index • Changes throughout for: − add SYNCGENR to list of utilities tracked by All/Star (23002) − add DFSMShsm BACKVOL to list of utilities tracked by All/Star

(22701) − add ADARUN to list of utilities tracked by All/Star (22849) − add CFCAMS to list of utilities tracked by All/Star (23101) − add CA-FAVER to list of utilities tracked by All/Star (16642)

Mainstar Software Corporation ©2006 iii Contents SC23-6061-00



Document 005-0202-16 This version of the Mainstar: Backup & Recovery Manager Suite User June 2005 Guide supports Version 4 Release 03 of the Mainstar: Backup & Sixteenth Edition Recovery Manager Suite product.


Documentation Updates • Add Load/Unload IDS options for All/Star (18523) • Add INCLUDE and EXCLUDE filter options to Setup and Configuration

Panel (20013) • Update Chapter 1, About Backup & Recovery Manager Suite to: − add topic describing data set naming restrictions when using

hyphens as last character of a data set name (20236) − update PDS note (23001)

• Update Chapter 2, BRM Suite: Online Dialog to: − Change LOADIDS/UNLOADIDS ALL to have selectable criteria for

both ABARS and All/Star data (21174) • Update Chapter 3, ABARS Manager Setup and Configuration to: − Update PDS note (23001)

• Update Chapter 4, All/Star Setup and Configuration to: − describe new panels for INCLUDE and EXCLUDE filters (20013)

• Update Chapter 5, ABARS Manager: Backup & Recovery Management – Option 2 to: − add GDGGEN0ONLY as an ARECOVER option (19752) − Change LOADIDS/UNLOADIDS ALL Options 4 and 7 on the

UTILITIES sub-menu to provide selectable criteria for both ABARS and All/Star data (21174)

• Update Chapter 6, All/Star Backup and Recovery Management – Option 2 to: − add new sub-option 6, Applications (requires ASAP) to the Backup

and Recovery Management menu (16639) − add new fields to Set Up Restore panel for No Backup Found RC

and No Backup Found Status (21308) • Update Chapter 9, BRM Suite Reports to split into 2 chapters and: − add new Overlap by Dataset Recovery Report (13342) − add INCLEVT and EXCLEVT fields to Overlap by Data Set Report

panel (13437) • Update Chapter 10, All/Star Reports to: − add What Isn't Backed Up report (18865) − add 2 new Critical in ASAP reports 10 and 11 (19163) − move 3 reports from old All Backups Option 3 to new Option 3,

All/Star Backup Reports (19474) − add Backup End Summary report (17950)

• Update Chapter 13, ABARS Manager: Batch Processing & Output to: − add RESETCB keyword to ABACKUP command (18448) − add GDGGEN0ONLY keyword to ARECOVER command (19752) − add instructions for overriding SYSOUT (19864) − add new INCLEVT and EXCLEVT parameters to OVERLAPD

(13437) − add new OVERLAPD-RCV report in batch (13342)

• Update Chapter 14, All/Star: Batch Processing & Output to:

Contents iv Mainstar Software Corporation ©2006 SC23-6061-00



− add REFRESH-AST and BUILD-BIFDSN commands (20332) − document enhancement to the NOBACKUP report (19505) − document OVERLAPE-AST report (9942) − add ASAP2BRM-B and ASAP2BRM-NB reports (19163) − add BKUPEND report (17950)

• Update Chapter 19, ABARS Manager: Incremental ABARS to: − add note about ABEND 201 (20627)

• Add new Chapter 20, All/Star: Application Backup and Restore. − add new BKUPEND command (17950)

• Update Chapter 21, All/Star: Build Restore to: − add note about VOL=RETAIN to section 18.1 − change RESTORE command to BLDREST (9942) − add new APPL selection category to BLDREST command (17950) − add COPY, BADBKUPRC, INCLLOC, and EXCLLOC parameters to

BLDREST command − add USEGEN0ALL and USEGEN0NOBKUP parameters to

BLDREST command (16639) − add NOBKUPFOUND parameter to BLDREST command (21308)

• Update TOC and Index.

Document 005-0202-15 This version of the Mainstar: Backup & Recovery Manager Suite User December 2004 Guide supports Version 4 Release 1 of the Mainstar: Backup & Recovery Fifteenth Edition Manager Suite product.


Documentation Updates • Renumber chapters to accommodate new chapters. • Move Appendix A, Filtering Pattern Masks, to Chapter 1; renumber

Appendix B, All/Star Skeleton Processing and Skeleton Variables, to Appendix A.

• Update Chapter 2, BRM Suite: Online Dialog to: − document new selectable feature CATSCRUB (19145)

• Add new Chapter 7, Features – Option 4, to document new selectable feature CATSCRUB (19145)

• Update Chapter 14, Dynamic Data Set Backup/Reorganization to: − add note regarding Lock Data Set (18349)

• Update Chapter 18 All/Star: All/Star Tracking (AST) Started Task to: − add sections on reorganizing and resizing the IDS (19593)

• Add new Chapter 20, BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes For DR (19145)

• Update Appendix A, All/Star Skeleton Processing and Skeleton Variables to: − add new skeleton variable &NXTVOLSER to generic variables

(PMR 18534) − add new generic variable &EXPDTJCL (19339)

• Update TOC and Index.

Mainstar Software Corporation ©2006 v Contents SC23-6061-00



Document 005-0202-14 This version of the Mainstar: Backup & Recovery Manager Suite User July 2004 Guide supports Version 4 Release 1 of the Mainstar: Backup & Recovery Fourteenth Edition Manager Suite product.


Documentation Updates • Add All/Star documentation and rename Backup & Recovery Manager to ABARS Manager throughout. Rename product to Backup & Recovery Manager Suite.

• Update Chapters 2 & 3 to: − explain how to negate the "do not show this panel again"

specification using the "C" field (ETR 16252) − move content of Chapter 5, Group Filters, into Chapter 2

• Update Chapter 14, ABARS Manager: ABARS Aggregate LoadBalancer, to: − change Aggregate LoadBalancer to sort ML2 by volume

(ETR16337) − change Aggregate LoadBalancer to display intermediate file

variables. • Move 'Reports in Batch' from Chapter 7 to Chapter 10 • Update TOC and Index.

Thirteenth Edition, 005-0202-13, August 2003, supports Backup & Recovery Manager product 3.2 Service Pack A Twelfth Edition, 005-0202-12, March 2003, supports Backup & Recovery Manager product 3.2 Eleventh Edition, 005-0202-11, November 2002, supports Backup & Recovery Manager product 3.1 Service Pack A Tenth Edition, 005-0202-10, September 2002, supports Backup & Recovery Manager product 3.1 Service Pack A Ninth Edition, 005-0202-09, February 2002, supports Backup & Recovery Manager product 3.1 Eighth Edition, 005-0202-08, July 2001, supports Backup & Recovery Manager product 2.1 Service Pack C Seventh Edition, 005-0202-07, June 2001, supports Backup & Recovery Manager product 2.1 Service Pack B Sixth Edition, 005-0202-06, May 2001, supports Backup & Recovery Manager product 2.1 Service Pack B Fifth Edition, 005-0202-05, April 2001, supports Backup & Recovery Manager product 2.1 Service Pack A Fourth Edition, 005-0202-04 TNL, April 2001, supports Backup & Recovery Manager product 2.1 Service Pack A Third Edition, 005-0202-03, January 2001, supports Backup & Recovery Manager product 2.1 Second Edition, 005-0202-02, 2000, supports Backup & Recovery Manager product 1.1 Service Pack A First Edition, 005-0202-01, 2000, supports Backup & Recovery Manager product 1.1

Contents vi Mainstar Software Corporation ©2006 SC23-6061-00



Contents

Preface.1 About This Book ......................................................................................................................... 1

Preface.2 Where to Find More Information................................................................................................ 3

1 About Backup & Recovery Manager Suite ...................................................................................... 1-11.1 About All/Star.................................................................................................................................... 1-1

1.1.1 Benefits of Using All/Star .......................................................................................................... 1-21.1.2 How All/Star Tracks Backups Without JCL Changes ............................................................... 1-31.1.3 Backup Utilities Tracked by All/Star.......................................................................................... 1-31.1.4 Tracking and Restoration of VSAM KSDSs with Alternate Indexes ......................................... 1-41.1.5 Getting Started with All/Star ..................................................................................................... 1-51.1.6 ASTBLDRJ Options and Skeleton Variations to Consider ....................................................... 1-7

1.2 How to Read Command Syntax ....................................................................................................... 1-81.3 Mainstar Extended ACS Filtering Pattern Masks ............................................................................. 1-91.4 Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters .......................... 1-101.5 Data Set Naming Conventions ....................................................................................................... 1-101.6 View Backup & Recovery Manager Suite Messages ..................................................................... 1-10

1.6.1 Message Identifier Naming Convention.................................................................................. 1-101.6.2 Determine Which MESSAGES Member Contains the Message Description ........................ 1-111.6.3 View Messages Using ISPF Interface .................................................................................... 1-111.6.4 View Messages in MESSAGES Library ................................................................................. 1-111.6.5 View Messages Using Quick-Ref ........................................................................................... 1-11

2 BRM Suite: Online Dialog .................................................................................................................. 2-12.1 About the Backup & Recovery Manager Suite Interactive Dialog Panels........................................ 2-1

2.1.1 Panel Types & Usage ............................................................................................................... 2-12.1.2 Panel 'Jump' Convention & Usage ........................................................................................... 2-12.1.3 Format and Fields on a Selection Panel................................................................................... 2-22.1.4 Format and Fields on a Table/List Panel.................................................................................. 2-3

2.2 Backup & Recovery Manager Suite Main Menu .............................................................................. 2-42.3 Sub-Menu Options............................................................................................................................ 2-72.4 MENU Sub-Menu ............................................................................................................................. 2-9

2.4.1 Messages – Menu Option 1...................................................................................................... 2-92.4.2 BRMINI Values – Menu Option 2 ........................................................................................... 2-102.4.3 Exit Backup & Recovery Manager Suite – Menu Option 3..................................................... 2-10

2.5 DIAGNOSTICS Sub-Menu ............................................................................................................. 2-112.5.1 About – Diagnostics Option 1 ................................................................................................. 2-112.5.2 Load Modules – Diagnostics Option 2.................................................................................... 2-112.5.3 Free Memory – Diagnostics Option 3 ..................................................................................... 2-122.5.4 Trace Records – Diagnostics Option 4 – ABARS Manager Only........................................... 2-12

2.6 PREFERENCES Sub-Menu ........................................................................................................... 2-132.6.1 Space Display – Preferences Option 1 – ABARS Manager and All/Star ............................... 2-132.6.2 Job Card (ABARS Manager) – Preferences Option 2 – ABARS Manager Only .................... 2-152.6.3 Job Card (All/Star) – Preferences Option 3 – All/Star Only.................................................... 2-152.6.4 Job Card (CATSCRUB) – Preferences Option 4 – ABARS Manager and All/Star ................ 2-16

2.7 UTILITIES Sub-Menu – ABARS Manager and All/Star .................................................................. 2-172.7.1 Load Activity Log (ABARS Manager) – Utilities Option 1 ....................................................... 2-172.7.2 Load Inventory (ABARS Manager) – Utilities Option 2........................................................... 2-172.7.3 Load Inventory (All/Star) – Utilities Option 3........................................................................... 2-172.7.4 Load Inventory (All) – Utilities Option 4 .................................................................................. 2-192.7.5 Unload Inventory (ABARS Manager) – Utilities Option 5 ....................................................... 2-21

Mainstar Software Corporation ©2006 vii Contents SC23-6061-00



2.7.6 Unload Inventory (All/Star) – Utilities Option 6 ....................................................................... 2-212.7.7 Unload Inventory (All) – Utilities Option 7 ............................................................................... 2-232.7.8 Reset Aggregate Options (ABARS Manager) – Utilities Option 8 .......................................... 2-262.7.9 DAD Monitor (ABARS Manager and All/Star) – Utilities Option 9 .......................................... 2-26

2.8 Admin Sub-Menu – All/Star Only .................................................................................................... 2-292.8.1 Define Utility Equivalents – Admin Option 1 ........................................................................... 2-29

3 All/Star: Setup and Configuration – Option 1 .................................................................................. 3-13.1 Browse/Edit Backup Tracking INCLUDE Filters – Sub-Option 3...................................................... 3-2

3.1.1 Backup Tracking INCLUDE Filters Panel – Primary Commands ............................................. 3-33.1.2 Backup Tracking INCLUDE Filters Panel – Line Commands................................................... 3-33.1.3 Backup Tracking INCLUDE Filters Panel – Field Descriptions ................................................ 3-4

3.2 Browse/Edit Backup Tracking EXCLUDE Filters – Sub-Option 4 .................................................... 3-53.2.1 Backup Tracking EXCLUDE Filters Panel – Primary Commands ............................................ 3-53.2.2 Backup Tracking EXCLUDE Filters Panel – Line Commands.................................................. 3-63.2.3 Backup Tracking EXCLUDE Filters Panel – Field Descriptions ............................................... 3-6

3.3 Test Backup Tracking Filters – Sub-Option 5................................................................................... 3-83.4 Build Batch Intercept File and Refresh AST – Sub-Option 6............................................................ 3-9

4 All/Star: Backup and Recovery Management – Option 2 ............................................................... 4-14.1 Backup and Recovery Management for All/Star – Option 2............................................................. 4-24.2 Full Volume Dumps – Sub-Option 3 – Initial Selection..................................................................... 4-2

4.2.1 About the Full Volume Dumps Panel........................................................................................ 4-44.2.2 Line Command N – View Data Set Name List.......................................................................... 4-74.2.3 Line Command R – All/Star Restore......................................................................................... 4-9

4.3 Jobs Option – Sub-Option 4 – Initial Selection ............................................................................... 4-144.4 About the Jobname List Panel........................................................................................................ 4-16

4.4.1 Line Command S – View Backup Detail Panel....................................................................... 4-184.4.2 Jobname Detail Panel............................................................................................................. 4-19

4.5 Job Groups – Sub-Option 5 – Initial Selection................................................................................4-204.6 About the Job Group List Panel...................................................................................................... 4-21

4.6.1 Add a Job Group..................................................................................................................... 4-224.6.2 Primary Command NOTBYTHIS – Jobname List Not Tracked by This Job Group ............... 4-244.6.3 Primary Command NOJOBGRP – Jobname List Not Tracked by ANY Job Group ............... 4-25

4.7 Applications – Sub-Option 6 – Initial Selection............................................................................... 4-264.8 About the Application List Panel ..................................................................................................... 4-27

5 BRM Suite: Features – Option 4........................................................................................................ 5-15.1 CATSCRUB – Sub-Option 1............................................................................................................. 5-2

6 BRM Suite: Search for Data Set – Option 5 ..................................................................................... 6-16.1 Search for a Specific Data Set Name or Mask ................................................................................. 6-1

6.1.1 Search Selection Menu............................................................................................................. 6-26.1.2 Search for Data Set Setup Panel – Option 1 ............................................................................ 6-26.1.3 Search for Data Set Panel ........................................................................................................ 6-46.1.4 Quick Search for Data Set Setup Panel – Option 2.................................................................. 6-66.1.5 Quick Search for Data Set Panel.............................................................................................. 6-8

6.2 Identifying Data Set Overlaps ......................................................................................................... 6-106.3 Line Command O – Search for Data Set Overlaps ........................................................................ 6-126.4 Line Command R – Select Data Set for Recovery ......................................................................... 6-136.5 Restoring Data Without Knowledge of Which Utility Backed Up the Data Set............................... 6-15

7 All/Star: Reports – Online Using Option 6 .......................................................................................7-1 7.1 All/Star Backup Reports – Sub-Option 2 ..........................................................................................7-1

7.1.1 All/Star Backup Report 1 – Overlap by Data Set ...................................................................... 7-37.1.2 All/Star Backup Report 2 – Overlap by Backup Event.............................................................. 7-57.1.3 All/Star Backup Report 3 – Overlap by Job Groups ................................................................. 7-77.1.4 All/Star Backup Report 4 – Data Set List.................................................................................. 7-9

Contents viii Mainstar Software Corporation ©2006 SC23-6061-00



7.1.5 All/Star Backup Report 5 – Data Set List with Outputs .......................................................... 7-127.1.6 All/Star Backup Report 6 – Full Volume Dump List................................................................ 7-147.1.7 All/Star Backup Report 7 – Jobname List............................................................................... 7-167.1.8 All/Star Backup Report 8 – Jobnames Not Tracked by a Job Group ..................................... 7-197.1.9 All/Star Backup Report 9 – What Isn’t Backed Up ................................................................. 7-217.1.10 All/Star Backup Report 10 – Critical in ASAP with No All/Star Backup Record ..................... 7-247.1.11 All/Star Backup Report 11 – Critical in ASAP with All/Star Backup Record........................... 7-267.1.12 All/Star Backup Report 12 – BKUPEND Summary ................................................................ 7-297.1.13 All/Star Backup Report 13 – Overlap by Application .............................................................. 7-31

8 BRM Suite: History – Option 8 .......................................................................................................... 8-18.1 History Search Setup – Initial Selection ........................................................................................... 8-28.2 About the BRM History Panel........................................................................................................... 8-4

9 All/Star: Batch Processing & Output................................................................................................ 9-19.1 All/Star Error and Product Messages ............................................................................................... 9-29.2 Deleting Individual Versions ............................................................................................................. 9-29.3 All/Star Data Set Support ................................................................................................................. 9-29.4 The AUTODUMP Command ............................................................................................................ 9-3 9.5 The ASTEXPIRE Command............................................................................................................. 9-49.6 The BACKVOL Command................................................................................................................ 9-59.7 The BUILD-BIFDSN and REFRESH-AST Commands .................................................................... 9-59.8 The LOADIDS Command ................................................................................................................. 9-6

9.8.1 Submitting the LOADIDS Command ........................................................................................ 9-69.8.2 LOADIDS Command Syntax .................................................................................................... 9-69.8.3 LOADIDS Command Parameter Definitions............................................................................. 9-79.8.4 LOADIDS Command – Examples ............................................................................................ 9-9

9.9 The UNLOADIDS Command.......................................................................................................... 9-109.9.1 Using UNLOADIDS to Remove ABARS Manager Entries Incurred During a Trial ................ 9-109.9.2 Submitting the UNLOADIDS Command ................................................................................. 9-109.9.3 UNLOADIDS Command Syntax ............................................................................................. 9-109.9.4 UNLOADIDS Command Parameter Definitions ..................................................................... 9-119.9.5 UNLOADIDS Command – Examples ..................................................................................... 9-13

9.10 The REPORT Command................................................................................................................ 9-139.10.1 Submitting the REPORT Command ....................................................................................... 9-14

9.11 OVERLAPD-AST Report Type – Overlap by Data Set .................................................................. 9-159.11.1 REPORT OVERLAPD-AST Command Syntax ...................................................................... 9-159.11.2 REPORT OVERLAPD-AST Command Parameter Definitions .............................................. 9-159.11.3 REPORT OVERLAPD-AST Command Examples ................................................................. 9-169.11.4 Overlap by Data Set Report Example .................................................................................... 9-16

9.12 OVERLAPE-AST Report Type – Overlap by Backup Event .......................................................... 9-179.12.1 REPORT OVERLAPE-AST Command Syntax ...................................................................... 9-179.12.2 REPORT OVERLAPE-AST Command Parameter Definitions............................................... 9-179.12.3 REPORT OVERLAPE-AST Command Examples ................................................................. 9-179.12.4 Overlap by Backup Event Report Example ............................................................................ 9-17

9.13 OVERLAPJOBGRP Report Type – Overlaps by Job Group List ................................................... 9-189.13.1 REPORT OVERLAPJOBGRP Command Syntax .................................................................. 9-189.13.2 REPORT OVERLAPJOBGRP Command Parameter Definitions .......................................... 9-189.13.3 REPORT OVERLAPJOBGRP Command Examples ............................................................. 9-189.13.4 Overlaps by Job Group Report Example................................................................................ 9-18

9.14 DSNLIST-AST Report Type – Data Set List by Data Set Name, Date .......................................... 9-199.14.1 REPORT DSNLIST-AST Command Syntax........................................................................... 9-199.14.2 REPORT DSNLIST-AST Command Parameter Definitions................................................... 9-209.14.3 REPORT DSNLIST-AST Command Examples...................................................................... 9-219.14.4 Data Set List by Data Set Name, Date Report Example ........................................................ 9-21

Mainstar Software Corporation ©2006 ix Contents SC23-6061-00



9.15 DSNLIST-O Report Type – Data Set List by Jobname, Data Set Name, Date w/Outputs ............ 9-229.15.1 REPORT DSNLIST-O Command Syntax ............................................................................... 9-229.15.2 REPORT DSNLIST-O Command Parameter Definitions ....................................................... 9-229.15.3 REPORT DSNLIST-O Command Examples .......................................................................... 9-229.15.4 Data Set List with Outputs Report Example ........................................................................... 9-22

9.16 FVDLIST Report Type – Full Volume Dump List............................................................................ 9-239.16.1 REPORT FVDLIST Command Syntax ................................................................................... 9-239.16.2 REPORT FVDLIST Command Parameter Definitions............................................................ 9-249.16.3 REPORT FVDLIST Command Examples............................................................................... 9-259.16.4 Full Volume Dump List Report Example................................................................................. 9-25

9.17 JOBLIST Report Type – Jobname List........................................................................................... 9-269.17.1 REPORT JOBLIST Command Syntax.................................................................................... 9-269.17.2 REPORT JOBLIST Command Parameter Definitions ............................................................ 9-269.17.3 REPORT JOBLIST Command Examples............................................................................... 9-289.17.4 Jobname List Report Example................................................................................................ 9-28

9.18 NOJOBGRP Report Type – Jobnames Not Tracked By a Job Group ........................................... 9-299.18.1 REPORT NOJOBGRP Command Syntax .............................................................................. 9-299.18.2 REPORT NOJOBGRP Command Parameter Definitions ...................................................... 9-299.18.3 REPORT NOJOBGRP Command Examples .........................................................................9-299.18.4 Jobnames Not Tracked By a Job Group Report Example...................................................... 9-29

9.19 NOBACKUP Report Type – Reports What Is Not Backed Up ....................................................... 9-309.19.1 REPORT NOBACKUP Command Syntax .............................................................................. 9-309.19.2 REPORT NOBACKUP Command Parameter Definitions ...................................................... 9-319.19.3 REPORT NOBACKUP Command Examples .........................................................................9-33

9.20 ASAP2BRM-NB Report Type – Critical in ASAP with No All/Star Backup Record ........................ 9-369.20.1 REPORT ASAP2BRM-NB Command Syntax ........................................................................ 9-369.20.2 REPORT ASAP2BRM-NB Command Parameter Definitions................................................. 9-379.20.3 REPORT ASAP2BRM-NB Command Examples ................................................................... 9-389.20.4 Critical in ASAP with No All/Star Backup Record Report Example ........................................ 9-38

9.21 ASAP2BRM-B Report Type – Critical in ASAP with All/Star Backup Record ................................ 9-389.21.1 REPORT ASAP2BRM-B Command Syntax ........................................................................... 9-389.21.2 REPORT ASAP2BRM-B Command Parameter Definitions ...................................................9-399.21.3 REPORT ASAP2BRM-B Command Examples ...................................................................... 9-409.21.4 Critical in ASAP with All/Star Backup Record Report Example.............................................. 9-40

9.22 BKUPEND Report Type – Backup End Summary.......................................................................... 9-419.22.1 REPORT BKUPEND Command Syntax................................................................................. 9-419.22.2 REPORT BKUPEND Command Parameter Definitions ......................................................... 9-419.22.3 REPORT BKUPEND Command Examples ............................................................................ 9-429.22.4 Backup End Summary Report Example ................................................................................. 9-42

9.23 OVERLAPA-AST Report Type – Overlap by Application ............................................................... 9-439.23.1 REPORT OVERLAPA-AST Command Syntax ...................................................................... 9-439.23.2 REPORT OVERLAPA-AST Command Parameter Definitions............................................... 9-439.23.3 REPORT OVERLAPA-AST Command Examples.................................................................. 9-449.23.4 Overlap by Application Report Example ................................................................................. 9-44

10 BRM Suite: Dynamic Data Set Backup/Reorganization................................................................ 10-110.1 About Dynamic Backup/Reorganization ......................................................................................... 10-1

10.1.1 Usage Considerations............................................................................................................. 10-110.1.2 Product Data Set Applicability ................................................................................................ 10-110.1.3 Lock Data Set ......................................................................................................................... 10-2

10.2 Using the Dynamic Backup/Reorganization Utility ......................................................................... 10-210.2.1 Step 1: Modify SI040 Tokens in the Backup & Recovery Manager Suite PARMLIB ............ 10-210.2.2 Step 2: Use REUSE to Reallocate the BRM Inventory Data Set...........................................10-210.2.3 Step 3: Tailor and Execute the Backup, Reorganization, or Reload Utility JCL .................... 10-3

Contents x Mainstar Software Corporation ©2006 SC23-6061-00



10.3 Execution JCL ................................................................................................................................ 10-310.3.1 BACKUP ................................................................................................................................. 10-310.3.2 REORG................................................................................................................................... 10-510.3.3 RELOAD ................................................................................................................................. 10-7

10.4 BRM01BRR Parm Values .............................................................................................................. 10-810.4.1 BACKUP ................................................................................................................................. 10-810.4.2 REORG................................................................................................................................... 10-810.4.3 RELOAD ................................................................................................................................. 10-8

11 BRM Suite: DADSMFTK (DAD) Started Task ................................................................................. 11-111.1 DADSMFTK Operator Commands ................................................................................................. 11-1

11.1.1 Start the Started Task (DAD) and Individual Subtasks .......................................................... 11-211.1.2 Start the DAD Started Task by Jobname (DAD) and Individual Subtasks ............................. 11-211.1.3 Start the DAD Started Task without the Individual Subtasks ................................................. 11-311.1.4 Stop the Structure/Terminate DADSMFTK............................................................................. 11-311.1.5 Manipulate the IEFU83 Exit .................................................................................................... 11-411.1.6 Manipulate the Dataspace ...................................................................................................... 11-5

11.2 Removing Obsolete Entries from the DAD Database .................................................................... 11-6

12 All/Star: Application Backup and Restore ..................................................................................... 12-112.1 Application Backup and Restore .................................................................................................... 12-1

12.1.1 Comparison of ASAP Critical Data Sets to All/Star Recorded Backups ................................ 12-112.1.2 About Restore by Application ................................................................................................. 12-1

12.2 Restore by Application Process Flow............................................................................................. 12-212.3 ASAP Options When Using All/Star to Track and Restore by Application..................................... 12-2

12.3.1 EXCL_BUT_CRITICAL Filter.................................................................................................. 12-312.4 About the BKUPEND Program ....................................................................................................... 12-3

12.4.1 BKUPEND Execution Placement ........................................................................................... 12-412.5 The BKUPEND Command ............................................................................................................. 12-512.6 Executing BKUPEND ..................................................................................................................... 12-812.7 How to Use Application Backup and Restore................................................................................. 12-912.8 Step 1: Create All/Star Batch Intercept File (BIF) Filters................................................................ 12-912.9 Step 2: Edit BRM Suite BRMINI PARMLIB Member .................................................................... 12-1012.10 Step 3: Modify the BRMBPROC JCL member ............................................................................. 12-1012.11 Step 4: Implement the All/Star ASTEXPIRE Command............................................................... 12-1112.12 Step 5: Define an Application to ASAP ........................................................................................ 12-1212.13 Step 6: Run the Application .......................................................................................................... 12-1212.14 Step 7: Run the ASAP APPLEND Program ................................................................................. 12-1212.15 Step 8: Run the All/Star BKUPEND Program............................................................................... 12-13

12.15.1 CHANGED-SINCE-LAST-BKUP-RC Optional Parameter Setup Steps............................... 12-13

13 All/Star: Build Restore ..................................................................................................................... 13-113.1 The Build Restore Process............................................................................................................. 13-113.2 How to Build and Submit a Restore ............................................................................................... 13-2

13.2.1 Step 1 – Build the Restore JCL .............................................................................................. 13-213.2.2 Step 2 – Submit the Restore JCL ........................................................................................... 13-4

13.3 The Build Restore Commands ....................................................................................................... 13-513.3.1 JOBNAMEOUT Command ..................................................................................................... 13-513.3.2 INCRJOBNAMEOUT Command ............................................................................................ 13-613.3.3 MEMBEROUT Command....................................................................................................... 13-613.3.4 INCRMEMBEROUT Command .............................................................................................. 13-613.3.5 STEPLIMITOUT Command .................................................................................................... 13-713.3.6 BLDREST Command.............................................................................................................. 13-8

13.4 Use of Keywords to Control Job and Member Generation........................................................... 13-1613.4.1 Minimal Required Keywords ................................................................................................. 13-1613.4.2 Generating Different Job Names to Allow Concurrent Initiation ........................................... 13-16

Mainstar Software Corporation ©2006 xi Contents SC23-6061-00



13.4.3 Generating Multiple Output JCL Members ........................................................................... 13-1713.5 Sample Build Restore Scenarios .................................................................................................. 13-18

13.5.1 Build Restore Scenario 1 ...................................................................................................... 13-1813.5.2 Sample Build Restore Scenario 2......................................................................................... 13-1913.5.3 Sample Build Restore Scenario 3......................................................................................... 13-20

14 All/Star: All/Star Tracking (AST) Started Task............................................................................... 14-114.1 All/Star Tracking (AST) Started Task Overview ............................................................................. 14-114.2 The All/Star Tracking (AST) Started Task – ASTSMFTK............................................................... 14-214.3 Backup Utilities Tracked by All/Star................................................................................................ 14-314.4 DFSMShsm ARCINBAK Considerations........................................................................................ 14-414.5 Tracking DFSMShsm Auto Dumps................................................................................................. 14-4

14.5.1 Expiring Backups and Applications from the BRM Inventory Data Set .................................. 14-414.5.2 Track All/Star Tracking (AST) Messages................................................................................ 14-414.5.3 Reducing Data to Be Processed by All/Star Tracking (AST) Started Task ............................ 14-4

14.6 Preparing to Track Backup Data Using All/Star Tracking (AST) Started Task............................... 14-514.7 System Configuration Modes and AST Tasks................................................................................ 14-514.8 AST Commands ............................................................................................................................. 14-6

14.8.1 Start the All/Star Tracking Started Task and Individual Subtasks .......................................... 14-714.8.2 Stop the AST Structure: .......................................................................................................... 14-714.8.3 Updating the In-Storage Batch Intercept File Filters:.............................................................. 14-714.8.4 Manipulate the IEFUSI Exit:.................................................................................................... 14-814.8.5 Manipulate Flatfile Copy Task: ............................................................................................... 14-814.8.6 Summary of Files Used by the All/Star Tracking (AST) Started Task .................................... 14-8

14.9 Back Up, Reorganize, or Resize the BRM Suite IDS ..................................................................... 14-914.10 AST Message Log .......................................................................................................................... 14-9

15 BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR ............................................. 15-115.1 The CATSCRUB Command ...........................................................................................................15-115.2 Using the CATSCRUB Command .................................................................................................. 15-3

15.2.1 What to Do Before You Can Use CATSCRUB ....................................................................... 15-315.3 Submitting the CATSCRUB Command .......................................................................................... 15-315.4 CATSCRUB Command Syntax ...................................................................................................... 15-415.5 CATSCRUB Command Parameter Definitions...............................................................................15-615.6 CATSCRUB Processing Notes..................................................................................................... 15-17

15.6.1 When Would CATSCRUB Be Run? ..................................................................................... 15-1715.6.2 CATSCRUB Simulation Processing ..................................................................................... 15-1715.6.3 Why Delete Catalog Entries With No Matching Physical Data Set? .................................... 15-1715.6.4 How Does CATSCRUB Processing Work? .......................................................................... 15-1815.6.5 Examples .............................................................................................................................. 15-21

15.7 CATSCRUB Benchmark Run Timings ......................................................................................... 15-2215.7.1 Comparative Timings – CATSCRUB vs. IDCAMS ............................................................... 15-22

15.8 Sample CATSCRUB Commands and Output Examples ............................................................. 15-2315.8.1 CATSCRUB – EXECUTE Mode to Cleanup One BCS and Two Volsers ............................ 15-2315.8.2 CATSCRUB – SIMULATE and Premature Termination by END Specification .................... 15-26

A All/Star: Skeleton Processing and Skeleton Variables.................................................................. A-1A.1 Process Flow Overview ....................................................................................................................A-1A.2 Suggestions for Creating New Skeletons or Altering Copies of Distributed Skeletons ....................A-2A.3 Commands........................................................................................................................................A-3A.4 Control Names ..................................................................................................................................A-5

A.4.1 Generic Variables .....................................................................................................................A-7A.4.2 Event Fields ..............................................................................................................................A-9A.4.3 Source File Variables............................................................................................................. A-10A.4.4 Cluster Variables.................................................................................................................... A-11A.4.5 Data Components .................................................................................................................. A-13

Contents xii Mainstar Software Corporation ©2006 SC23-6061-00



A.4.6 Index Components..................................................................................................................A-14A.4.7 Path Variables ........................................................................................................................A-15A.4.8 Non-VSAM Variables..............................................................................................................A-16A.4.9 Non-VSAM Alias Variables .....................................................................................................A-17A.4.10 GDG Base Variables ..............................................................................................................A-17

Mainstar Software Corporation ©2006 xiii Contents SC23-6061-00



Figures Figure 2-1: Types of fields that may be used on a Selection type of panel ..............................................2-2Figure 2-2: Format of Table/List type of panel ..........................................................................................2-3Figure 2-3: Backup & Recovery Manager Suite Main Menu.....................................................................2-4Figure 15-1: CATSCRUB – Single BCS synchronized with two volumes.............................................15-24Figure 15-2: CATSCRUB – Simulate BCS with END termination.........................................................15-26

Tables Table 9-1: LOADIDS Command Parameter Definitions............................................................................9-7Table 9-2: UNLOADIDS Command Parameter Definitions.....................................................................9-11Table 9-3: REPORT Types .....................................................................................................................9-13Table 9-4: REPORT OVERLAPD-AST Command Parameter Definitions..............................................9-15Table 9-5: REPORT OVERLAPD-AST Command Parameter Definitions..............................................9-17Table 9-6: REPORT OVERLAPJOBGRP Command Parameter Definitions..........................................9-18Table 9-7: REPORT DSNLIST-AST Command Parameter Definitions ..................................................9-20Table 9-8: REPORT DSNLIST-O Command Parameter Definitions ......................................................9-22Table 9-9: REPORT FVDLIST Command Parameter Definitions...........................................................9-24Table 9-10: REPORT JOBLIST Command Parameter Definitions .........................................................9-26Table 9-11: REPORT NOJOBGRP Command Parameter Definitions ...................................................9-29Table 9-12: REPORT NOBACKUP Command Parameter Definitions ...................................................9-31Table 9-13: REPORT ASAP2BRM-NB Command Parameter Definitions..............................................9-37Table 9-14: REPORT ASAP2BRM-B Command Parameter Definitions ................................................9-39Table 9-15: REPORT BKUPEND Command Parameter Definitions ......................................................9-41Table 9-16: REPORT OVERLAPA-AST Command Parameter Definitions............................................9-43Table 12-1: BKUPEND Command Parameter Definitions ......................................................................12-5Table 13-1: BLDREST Command Parameter Definitions .....................................................................13-10Table 15-1: CATSCRUB Command Parameter Definitions....................................................................15-6

Contents xiv Mainstar Software Corporation ©2006 SC23-6061-00



Preface Preface.1 About This Book

Who Should Use This Book

This User Guide is provided for Storage Administrators, the users who are responsible for using Backup & Recovery Manager Suite Dialog facilities to manage aggregates, and anyone who needs to understand the capabilities of the Backup & Recovery Manager Suite product.

Organization of This Book

Chapter 1 – About Backup & Recovery Manager Suite provides an overview of Backup & Recovery Manager Suite, and includes information about masking characters, reading syntax, and accessing error messages.

Chapter 2 – BRM Suite: Online Dialog discusses the structure and features of the online dialog panels, including the Menu, Preferences, Utilities, and Diagnostics sub-menus, and how to use them for both ABARS Manager and All/Star.

Chapters 3–8 discuss each of the Options that can be selected from the Backup & Recovery Manager Main Menu.

Chapter 9 – All/Star: Batch Processing & Output documents the syntax, parameter descriptions, and examples of using the All/Star batch commands, and reports in batch mode.

Chapter 10 – BRM Suite: Dynamic Data Set Backup/Reorganization describes how to use the Dynamic Backup/Reorganization utility to allow the BRM Inventory Data Set to be backed up or reorganized without stopping the product, or product programs.

Chapter 11 – BRM Suite: DADSMFTK (DAD) Started Task describes the DADSMFTK started task for both Incremental ABARS and All/Star, and associated operator commands.

Chapter 12 – All/Star: Application Backup and Restore describes additional features that are available if both ASAP and All/Star are licensed.

Chapter 13 – All/Star: Build Restore describes the build restore commands required to submit restores.

Chapter 14 – All/Star: All/Star Tracking (AST) Started Task describes how to set up the started task to enable tracking of backups.

Chapter 15 – BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR describes how to use this very high-speed capability to 'condition' user and master catalogs (BCSs) at a DR site. CATSCRUB is useful for DR methodologies where you take 'populated' catalogs to your DR site, and then 'scrub' them of all or specified entries that don't match the actual data sets that have been restored at your DR site.

Appendix A – All/Star: Skeleton Processing and Skeleton Variables describes the restore variables used by the restore skeletons in order to restore data sets, jobnames, or full volume dumps.

Reader’s Comments

We want to receive your comments about this manual. Your suggestions about the accuracy, clarity, and format of this document will be appreciated.

Please document your observations and email to [email protected] or provide to Mainstar Technical Support via our website.

Let us know if you would like a reply, and provide your contact information.

Mainstar Software Corporation ©2006 1 Preface SC23-6061-00





http://www.mainstar.com/services/support/problem/index.asp

http://www.mainstar.com/services/support/problem/index.asp


Acronyms

ALB Aggregate LoadBalancer

AST All/Star Tracking Started Task

BRM Backup & Recovery Manager Suite

DAD Data Set Activity Database

INC Incremental ABARS

Preface 2 Mainstar Software Corporation ©2006 SC23-6061-00



Preface.2 Where to Find More Information

Publications in the Backup & Recovery Manager Suite Document Set

• Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC236062)

• Backup & Recovery Manager Suite User Guide for ABARS Manager (document SC23-6060) • Backup & Recovery Manager Suite User Guide for All/Star (document SC23-6061) • Backup & Recovery Manager Suite User Guide for ASAP (document SC23-6059)

How to Contact Us for Technical Support

• Mainstar Technical Support • Phone: 425-455-3589 • Fax: 425-455-1992

How to Contact Us for Product Information

• Send an email to:

[email protected]

• In North and South America

Mainstar Software Corporation Worldwide Headquarters P.O. Box 4132 Bellevue, WA 98009 U.S.A. Tel: 1-425-455-3589 or 1-800-233-6838 Fax: 1-425-455-1992

• In Europe

Mainstar Software Corporation Ltd. Sanderum House Oakley Road Chinnor Oxon OX39 4TW England Tel: +44-(0)1844-347173Fax: +44-(0)1844-346627

• In Asia Pacific

Mainstar International Ltd. P.O. Box 1624 Macquarie Centre North Ryde, NSW 2113 Australia Tel: +61-(0)2-9888-1777Fax: +61-(0)2-9888-1588

Visit Our Web Site – www.mainstar.com

• Current release information • Product information • Interesting and informative White Papers and articles • Online presentations

Mainstar Software Corporation ©2006 3 Preface SC23-6061-00


http://www.mainstar.com/services/support/techsupport/index.asp




• Sign up for an online seminar

Preface 4 Mainstar Software Corporation ©2006 SC23-6061-00



Chapter 1 1 About Backup & Recovery Manager Suite

Backup and Recovery Manager Suite consists of one common install, a common inventory data set between ABARS Manager and All/Star, a separate database for ASAP, common panels, and three selectable products. Backup & Recovery Manager Suite is designed to meet your company's business resiliency needs either locally, or in the event of a disaster, from the minor to the catastrophic. Backup and Recovery Manager Suite offers the following products and features:

• ABARS Manager: – enhances and extends ABARS functionality – centralizes management of ABARS to make ABARS easy to use – consolidates and manages essential tracking, status, and resource information – adds functionality not included in native ABARS – provides selectable feature Incremental ABARS for true ABARS incremental support

Selectable features for ABARS Manager:

– CATSCRUB, designed for full volume restore, enables you to quickly synchronize one or more BCS catalogs with associated DASD volumes at your disaster recovery site.

– Incremental ABARS enables you to perform ABARS backups on an incremental basis. • All/Star:

– centralizes and inventories z/OS backups so you can recover anywhere, anytime – identifies what isn’t backed up at your site

Selectable features for All/Star:

– CATSCRUB, designed for full volume restore, enables you to quickly synchronize one or more BCS catalogs with associated DASD volumes at your disaster recovery site.

• ASAP: – identifies critical business data as the application executes – identifies the data that needs to be backed up for business resiliency, either onsite,

offsite, or both, and builds the list as input to a backup utility • ASAP and All/Star, when used together:

– use the list created by ASAP to compare to what was actually backed up – provide documented evidence that critical assets have a backup – provide proof that critical business data is offsite if required – alert on critical assets that don’t have a backup

Backup & Recovery Manager Suite panels provide access to functionality common to all three products, ABARS Manager, All/Star, and ASAP, and are named either Backup & Recovery Manager Suite or BRM. ABARS Manager panels are named either ABARS Manager or ABM, All/Star panels are named either All/Star or AST, and ASAP panels are named either ASAP or ASP.

ABARS Manager and All/Star share the same Backup & Recovery Manager Suite Inventory Data Set, and ASAP has its own ASAP Database.

1.1 About All/Star All/Star intercepts, inventories, and centralizes z/OS backups – without JCL changes, enabling you to be resilient and giving you the ability to recover anywhere, anytime. It consolidates and manages essential backup tracking, status, and resource information for effective backup and recovery.

Mainstar Software Corporation ©2006 1-1 Chapter 1 SC23-6061-00 About Backup & Recovery Manager Suite



All/Star:

• Provides business resiliency for local recovery or disaster recovery, from minor to catastrophic outage.

• Tracks and records backups and data without the need for any JCL changes to existing backup utilities.

• Quickly locates any backup copy recorded in the Backup & Recovery Manager Suite Inventory Data Set (IDS), displays backup details and restores at the touch of a finger

• Provides easy ISPF or batch. • Identifies what isn’t backed up at your site to help ensure you aren’t missing critical data

sets. By tracking and providing an inventory of backups, you can easily find data sets not backed up by comparing them to the Backup & Recovery Manager Suite IDS, DFSMShsm BCDS, or both.

• Identifies multiple data set backups to help reduce resources. • Automatically constructs restore JCL and utility control statements that will reverse the copy

of a backed-up data set. Construction of recovery JCL/control statements may be varied by users via the All/Star file tailoring process.

• Selectable feature CATSCRUB synchronizes catalogs/volumes for Disaster Recovery at blazing speeds. The result is catalogs that correctly reflect the data on physical volumes.

• When used with ASAP, All/Star:

– Uses the list created by ASAP to compare to what was actually backed up – Provides documented evidence that critical assets have a backup – Alerts on critical assets that don’t have a backup – Proves that critical business data is offsite if required

1.1.1 Benefits of Using All/Star • Intercepts backups without JCL changes making tracking backups simple to set up. • Centralization reduces confusion about what is and what isn’t backed up. • Quickly locates backups.

By tracking z/OS backups, All/Star can locate any and all backups of the data set regardless of the utility used by simply entering a desired data set name,.

• Provides for business resiliency both locally and/or for disaster recovery. – Local – used onsite if a data set gets deleted or corrupted, or a backout of a batch process is

required – Disaster Recovery – used offsite if a disaster strikes to easily restore somewhere else and

get back up and running • Identifies what isn’t backed up at your site to help ensure you aren’t missing critical data sets

that require a backup. – Compares data sets on your volumes or in your ICF User Catalogs or both, to the All/Star

Inventory data set, and optionally to the DFSMShsm BCDS. – All/Star will identify data sets that are not recorded in either and thus, have not been tracked

yet, or do not have a backup. • Tracks multiple generations of backups.

All/Star may optionally track multiple generations of a backup, allowing restoration of a backup other than the most current generation.

• View data sets backed up from each utility including full volume dump, and provide data set restore off full volume dumps – rare but sometimes necessary.

• Automatically recovers JCL/control statements.

It is not uncommon for backups to be placed in production with no corresponding restore JCL/control statements created and kept available for quick access. All/Star resolves this issue

Chapter 1 1-2 \Mainstar Software Corporation ©2006 About Backup & Recovery Manager Suite SC23-6061-00



by automatically constructing the restore JCL/control statements that match the utility and commands used to originally back up data sets or volumes.

• Alerts if backups fail.

Processes are not always set to fail or provide an alert if a backup fails. By tracking not only which data sets or volumes are backed up, but by also recording the success or failure, All/Star provides a mechanism for alerting responsible parties that backups have failed.

• Interactive operation – for detailed analysis, error status, research, overlap analysis, and DSCB information.

• Identifies data sets backed up multiple times to save on tape and CPU resources. • Identifies data sets that could possibly be written over during restore caused by:

– Overlaps – between full volume dumps and application backups – Overlaps – multiple applications backing up the same data set

1.1.2 How All/Star Tracks Backups Without JCL Changes To avoid JCL changes, All/Star identifies backups to be tracked by a seamless intercept triggered by matching job names, step names, and utility program names to a user-defined table. Although it is necessary to identify which jobs are backups, the risk and procedural difficulties with changing production JCL are eliminated.

Known backup jobs are identified to All/Star via an ISPF interface to establish Batch Intercept File (BIF) entries. BIF entries identify a backup job/step and identify the expected backup utility.

To intercept backups, All/Star utilizes a started task on each image which installs step initiation exit (IEFUSI). If a backup is to be intercepted, the execute statement is altered to execute a Mainstar intercept program, which in turn executes the true utility.

Subtasks under the started tasks in turn process the results of intercepted utilities and record the pertinent data in the Backup & Recovery Manager Suite (BRM) Inventory Data Set (IDS). For most types of backups, All/Star captures catalog and volume metadata in synchronization with the status of the data set(s) at the time of the backup. This ensures that restore allocations match the status of data sets at the time they were backed up.

1.1.3 Backup Utilities Tracked by All/Star • ABARS backups executed through ABARS Manager • Adabas (ADARUN) • Brightstor CA-FAVER • Catalog RecoveryPlus (CR+) backups • CFCAMS (REPRO and EXPORT) • DFSMSdss (Full volume, physical dump by data set, and logical backups) • DFSMShsm ARCINBAK • DFSMShsm AUTODUMP • DFSMShsm BACKVOL • DFSMShsm Incremental • FDR (FDR, DSF, ABRFDR) • ICEGENER • IDCAMS (REPRO and EXPORT) • IEBCOPY • IEBGENER • SORT • SYNCGENR

Note: DFSMShsm AUTODUMP and BACKVOL are supported through a batch utility.




Note: SORT is generally used as the name implies, to SORT data. Sorts of this kind are not considered backups and should NOT be tracked by All/Star. All/Star's function is to track data sets backed up. All/Star does track SORT because some sites may have a few jobs that sort data to an output file that they do consider a backup. These are valid backups. Ensure that discrete jobnames are specified in the Backup Tracking INCLUDE Filters instead of masks for any SORT job you want tracked, to prevent tracking sort output files that are not a backup, or to prevent failures. SORT functions often use PDS members as input to the SORT, however All/Star requires you to use the full partitioned data set name. Member names are not supported.

1.1.4 Tracking and Restoration of VSAM KSDSs with Alternate Indexes Some backup/restore utilities have a 'Sphere' option which causes the utility to back up all components and associations of a VSAM sphere. Others do not. When using a utility that does not have a sphere option, All/Star requires only that the base cluster be backed up. Backups of AIXes are ignored.

When a backup of a VSAM base cluster is tracked, all association information is saved in the BRM Inventory Data Set. This information is then used to define and rebuild any associated AIXes and define any associated PATHs. This feature provides the sphere backup and restore capability to utilities that do not inherently perform this function.

After satisfying yourself that AIXes and PATHs are correctly restored, you may wish to remove what will be unnecessary backups of AIXes and possibly user procedures to capture catalog PATH information.




1.1.5 Getting Started with All/Star Each of the steps in the step table below is described in the topics that follow.

STEP

1

STEP DESCRIPTION

Create Batch Intercept File (BIF) Filters via the ISPF facility

2 Identify involved images; set up and start the intercept tasks

3 Create test scenarios

4 Consider restore scenarios

Step 1: Create Batch Intercept File (BIF) Filters via the ISPF Facility

The product must be installed, and at a minimum the Backup & Recovery Manager Suite (BRM) Inventory Data Set must have been allocated.

Because the intercept mechanism tracks only those jobs/steps/program names identified by the BIF entries, it is necessary to first create BIF entries. There are two ISPF panels, one for BIF INCLUDES, and one for BIF EXCLUDES. BIF entries may be added later, but before the tracking mechanism will produce any results in the BRM Inventory Data Set, at least some backup jobs must be identified.

Although All/Star tracks backups without application JCL changes, using job and/or step 'masks' can significantly reduce the effort of defining backup jobs, you might want to consider whether some changes to job names might make the task easier.

If changing job names is feasible, also consider whether this might make restoring easier. All/Star offers restoration by:

• JOBNAME • JOBGROUP • DSN • VOL

If data set naming conventions do not easily allow restoring a group of data sets by DSN using masks, it might be more convenient to restore by JOBNAME or JOBGROUP even if this means altering some backup JOBNAMES.

Because All/Star assumes that a match on job name, step name, and program name is a backup, avoid using masks that might cause utility execution to be tracked that are in fact not a backup. For instance, an IDCAMS REPRO may simply be used in a VSAM reorganization process. After some initial tracking has been recorded, review what All/Star 'thinks' is a backup to see if masking in BIF entries is too aggressive.

Step 2: Identify Involved Images; Set Up and Start the Intercept Tasks

The All/Star Tracking (AST) started task must be implemented on any image where backup programs may run. Perform the installation steps necessary for the started tasks. When the tasks are started, tracking will begin.




Step 3: Create Test Scenarios

Rather than wait for executions of various backup utilities and/or types of data sets to present themselves from normal production execution, it is advisable to identify the types of utilities specified in the BIF entries and run some test jobs using these utilities. It will also help in analyzing restore Skeleton options to set up tests for various types of data sets.

Step 4: Consider Restore Scenarios

All/Star will build restore JCL and control statements to match the utility/command used to back up a data set or volume or you can use your own restore JCL.

To consider the options for restoring, first acquaint yourself with:

• the All/Star BUILD RESTORE program parameters (see Chapter 13, All/Star: Build Restore) • the Skeleton Processing procedure (see Appendix A, All/Star: Skeleton Processing and

Skeleton Variables) • the Build Restore (ASTBLDRJ) program, where you select the data sets or volumes to be

restored. Executing ASTBLDRJ drives the Skeleton processing, which controls the generation of actual restore JCL and control statements.

Default and sample skeletons are shipped with All/Star for the utilities/commands that All/Star supports. Although it is possible to create a single skeleton that could generate the appropriate JCL/control statements for any backup utility, to reduce the complexity of skeletons, unless overridden, All/Star uses different skeletons based on the utility/command used for the backup.

All/Star allows you to define what the default skeleton is for each corresponding backup utility/command. You may also create your own default or special usage skeletons either from scratch or by modifying a shipped sample.

Because time is of the essence for either a local restore or a disaster recovery, it is advisable to review which options you should use for the Build Restore parameters and the skeletons so that restoration can be accomplished quickly.




1.1.6 ASTBLDRJ Options and Skeleton Variations to Consider

The following items should be considered regarding ASTBLDRJ options and skeleton variations:

Dependent data sets or volumes

Care must be taken when restoring data sets or volumes where associated data sets or volumes must also be restored to put an application or group of data sets back to the same point in time required for a restart. Although All/Star allows very easy selection of a single data set to be restored, the onus is on the user to know whether associated data sets must also be restored to the same point in time.

Whether for local or disaster recovery, examine how the restore options of ASTBLDRJ can be utilized to recover all data sets or volumes that must be treated as a group.

Restore, replace versus fail

An important strategic decision is how to deal with collisions when restoring data sets. Some utilities allocate target data sets automatically and usually have a 'replace' option to choose whether an existing like-named data set (or just a catalog entry) is to be replaced.

For utilities that require allocation of the target data set, the 'replace or not' decision is made based on how the user codes the restore JCL/control statements, such as first deleting any existing data set and/or catalog entry to make sure a subsequent allocate works.

This is especially important in a disaster recovery plan depending on the initial status of user catalogs. If populated catalogs are restored, with no scrubbing done, all data sets will have catalog entries. Conversely, if catalogs are either selectively recovered or scrubbed, the first attempt to restore a data set should in theory not experience a collision. Notice the product includes skeletons for each utility in two flavors, one that assumes REPLACE or a DELETE prior to allocation, and another that assumes existing data sets should result in an error. The default skeleton JCL is set up not to replace data sets.

Target data set volume location

For SMS managed data sets, the default skeletons include specifying SMS class information for the allocation of target data sets, using the class names from the original data set. Determine whether this is desirable. All/Star has no way of knowing whether SMS class information was supplied during the original allocation of a data set, as opposed to having been derived by the ACS constructs from data set attributes. It is conceivable (e.g. if constructs are not the same as when a data set was originally allocated), that explicitly specifying SMS class information could yield a different class than if the ACS routine is driven without SMS class information. If your ACS constructs do not honor explicitly specified SMS class parameters, this will not be a problem.

For non-SMS data sets, the default skeletons supply the volumes for target data allocation as found for the original data sets backed up. This may not be your preference, if for instance your disaster recovery DASD environment has different volumes or you prefer to allocate using esoterics. Because more than one esoteric can point to the same volume, All/Star cannot work backwards to discover which esoteric might have been used to allocate an original data set.




1.2 How to Read Command Syntax These are the definitions for the various symbols used in the command syntax. These symbols are not to be coded; rather, their function is to denote usage.

{ } braces mean you are required to choose one, and only one, of the items (or a group or items if they are enclosed in brackets) within the braces.

[ ] brackets mean optional parameter(s) or keyword(s). … An ellipsis means you may include multiple values of the type specified prior to the

ellipsis. | A vertical bar (may also be called a 'pipe') means a delimiter between optional

items, from which you may choose only one. Underline An underline denotes the default.

Example of command syntax:

The symbols used in the sample syntax below say the same thing as the sample text from the Keyword Description table:

{ [ ALL-RELATED ] | [ TO-STORAGEGROUP( stgrp1 | stgrpmask1

…stgrpn | stgrpmaskn ) TO-VVDS( volser1 | volsermask1 …volsern | volsermaskn ) ] }

Default: ALL-RELATED Required: Yes Restrictions: • TO-STORAGEGROUP and TO-VVDS can both be specified in one command. • If ALL-RELATED is specified, neither of the TO… keywords can be specified with it.

Default – ALLRELATED is underlined because it is the default.

Required – The braces that enclose this entire example mean that it is required that you choose from among the options within the braces.

Restrictions – There are brackets around the ALL-RELATED keyword, meaning it is one of your options. There are also brackets around the TO-STORAGEGROUP and TO-VVDS keywords, meaning these are your other options. Note that there is no pipe between the TO… keywords, meaning you may choose both. So there are two 'optional groups' within the braces, and it is required that you choose one or the other, and it is OK that you choose both TO-STORAGEGROUP and TO-VVDS if you want.




1.3 Mainstar Extended ACS Filtering Pattern Masks Many commands allow specification of powerful filtering masks. These filtering pattern masks can be specified with Mainstar extended ACS masking characters, as specified below.

Mask Hex

* (Single)

5C n

a wildcard *%

In the example:

PROD* (i.e. *ZREM*

% 6C l % In the example:

are ER6.

< 4C Similar to the % value, the <

. In the example:

CR, the 3rd and 4th

th and 6th ERl

> 6E only

. In the example:

CR, the 3rd and 4th

th and 6th ERl

** ACS and Only used

for The * or **wildcard

In the example:

st qualifiernd

qualifiers.

Description

Represents 0– characters. Can be used before and/or after an item to designate character position. You cannot use an in the middle portion of a single

item (except for data set names). Use the character (see below) for that purpose.

*PROD an item is selected if the last four characters are regardless of the starting characters. Using the character before and after an item ) means that item is to be selected if any character string matches ZREM in its name.

Denotes a single character placeholder value, which can be alpha-numeric or any specia character. The character can be used in any position order.

CRM%%ER6 an item is to be selected if it is 8-characters in length and the first three characters

CRM and the last three characters are The two middle placeholder values can be any characters.

character denotes a placeholder value for only alpha characters The < character can be used in any position order.

CR<<ER* an item is to be selected if the first two characters are characters must be alpha, the 5 characters are , and any remaining characters a lowed.

Similar to the % value, the > character denotes a placeholder value fornumeric characters The > character can be used in any position order.

CR>>ER* an item is to be selected if the first two characters are characters must be numeric, the 5 characters are , with any remaining characters a lowed.

(Double) 5C5C

Allows compatibility with standard DFSMSdss filtering masks. partially qualified data set names. characters can be used in any

qualifier position to denote a node.

CRFM*.*VER.** a data set entry is to be selected if it has at least two qualifiers and the 1starts with CRFM, the 2 qualifier must end with VER, and any remaining

Note: As with common data set name masking, any combination of *, **, %, < and/or > characters can be used for the item mask value.




Mask Hex

! 5A Similar to the % ! only

The ! @ # $

Description

value, the character denotes a placeholder value fornational characters (based on the U.S.A. EBCDIC code set, see topic 'Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters', page 1-10). character can be used in any position order. National characters (based on the U.S.A. EBCDIC code set) are:

1.4 Your EBCDIC Code Tables – Specification and Display of EBCDIC Characters

Data supplied as input to batch programs or input to ISPF panels:

For Mainstar product code shipped in binary, when specifying input where the product takes special action based on specific characters, the user is responsible for entering the EBCDIC character peculiar to their code tables that results in the binary value for the EBCDIC character shown in this document according to the U.S.A. EBCDIC code set.

For instance, if an exclamation mark ( ! ) is called for, and your code tables do not translate the ! character to a hexadecimal 5A, you must enter the character that will translate to a 5A.

Do not change Mainstar distributed ISPF panels:

Mainstar programs may reference ISPF panel attribute bytes. A panel change involving an attribute byte will not be consistent with the program code.

Product output:

Depictions of product output shown in the product manuals are based on the U.S.A. EBCDIC code set. Actual output may vary if your EBCDIC code tables are different.

1.5 Data Set Naming Conventions A hyphen ( - ) can be used as a character in a data set name; however, when a hyphen is used as the last character in a data set name, it may be mistaken for a continuation symbol and failures may occur. This restriction is also documented in the IBM document DFSMShsm Storage Administration Reference.

1.6 View Backup & Recovery Manager Suite Messages Product messages are distributed with the product in MESSAGES library members. The messages can be viewed directly from the MESSAGES members, or via Chicago-Soft's® Quick-Ref™, if it is installed in your environment.

1.6.1 Message Identifier Naming Convention Product message identifiers are in the form pppmmmnnx

Where: ppp is the 3 alpha character product code –

BRM for code shared by ABARS Manager, All/Star, and ASAP AST for All/Star

mmm is the module identifier, nn is the message number and x is the message type indicator – E=error, I=information, W=warning.

Example 1: The message identifier AST02056I would be a message from module AST020, message number of 56, and is an Information only message.

Example 2: The message identifier ASTVSE11E would be a message from module ASTVSE, message number of 11, and is an Error type message.




1.6.2 Determine Which MESSAGES Member Contains the Message Description Messages are in the MESSAGES library in a member name that matches the first six characters of the message identifier (ID).

Example 1: With the first six characters of message identifier AST02056I being AST020, the description would be found in MESSAGES member AST020.

Example 2: With the first six characters of message identifier ASTVSE11E being ASTVSE, the description would be found in MESSAGES member ASTVSE.

1.6.3 View Messages Using ISPF Interface Product messages can be viewed using the ISPF interface. In the ISPF interface, the Action Bar (at the top of the screen) has an option labeled “Menu”. Choose Menu to display a Pull-Down menu; option 1 is messages. Choosing option 1 will start a Browse session of product messages.

1.6.4 View Messages in MESSAGES Library Be sure you always refer to the most current MESSAGES members, as the members may be updated and distributed with a release of the product, cumulative maintenance, and sometimes for PTFs as well.

Use Browse FIND Command to Locate Messages Within a MESSAGES Member:

Within a message member, use the Browse FIND command to locate a specific message identifier (ID) explanation. Message IDs begin in column one. Include the column information in your FIND command to go directly to the main descriptions for the specified message.

F msgid 1

Where: msgid is the specific product message ID.

To Obtain a Hardcopy of Messages in the MESSAGES Members:

Print the MESSAGES members (but remember to print new ones after product releases, cumulative maintenance, or PTFs have been applied).

1.6.5 View Messages Using Quick-Ref You can access messages via Chicago-Soft's Quick-Ref if it is installed in your environment. Request the latest updates from Chicago-Soft if needed.




Chapter 2 2 BRM Suite: Online Dialog

Use the Online Dialog facility of Backup & Recovery Manager Suite as a powerful tool to:

• Easily access critical aggregate Event, Data Set, and Volume information from the Backup & Recovery Manager Suite Inventory Data Set (IDS).

• Perform daily storage management activities critical to your backup and recovery environment.

Storage Administrators: Read this chapter to effectively manage and support your backup activities.

Other users: Read this chapter if you will be directly using Backup & Recovery Manager Suite Dialog facilities to manage All/Star.

2.1 About the Backup & Recovery Manager Suite Interactive Dialog Panels This topic provides general information about using the various Online Dialog facility panel features. Backup & Recovery Manager Suite interactive dialog panels can be used to:

• Set up All/Star • Inquire on the status of backup and recovery events • Perform recoveries • Determine event history • Detect data set overlaps • Perform data set searches • Submit reports

Backup & Recovery Manager Suite panels provide access to functionality common to ABARS Manager, All/Star, and ASAP and are named either Backup & Recovery Manager Suite or BRM. ABARS Manager panels are named either ABARS Manager or ABM, All/Star panels are named either All/Star or AST, and ASAP panels are named either ASAP or ASP.

A common Backup & Recovery Manager Suite (BRM) Inventory Data Set (IDS) is used for both ABARS Manager (ABM) and All/Star. ASAP has its own database. Any references to the BRM IDS refer to data stored in the inventory data set for ABARS Manager and All/Star only.

2.1.1 Panel Types & Usage Backup & Recovery Manager Suite Dialog facility uses two basic types of panels. Examples are shown on the next pages.

• Selection Panels – Select either Aggregate, Data Set and/or Date information using either fully qualified names or wildcard name combinations.

• Table/List Panels – These panels present information in pre-sorted table format. Primary Commands allow you to re-sort the table and refresh the table. Line Commands can be used for selected aggregates or data sets to perform various actions. The available Line Commands vary with the specific Table/List panel.

2.1.2 Panel 'Jump' Convention & Usage On the Command line of any panel (except the Main Menu panel), the '=' character can be used ahead of any Option and/or Sub-option number to directly Jump to an Option panel. Examples: =1 -or- =2 -or- =x

Mainstar Software Corporation ©2006 2-1 Chapter 2 SC23-6061-00 BRM Suite: Online Dialog


.


2.1.3 Format and Fields on a Selection Panel

Fields

. }

(main panel only)

Specific

<VvRr> Backup & Recovery Manager Suite Header Text ....

Command ==>

Aggregate =>

Dataset =>

Date =>

Version/Release Level Panel Header Text Description

Selectable

Command Line Input (Backup & Recovery Manager and ISPF Commands)

Figure 2-1: Types of fields that may be used on a Selection type of panel

The following types of fields may appear on any Backup & Recovery Manager Suite panel.

Field Description

Header Text Description Title information, specific for the information being displayed.

Command Line Standard ISPF input area. Commands and/or ISPF commands may be entered on the Command line.

Specific Selectable Fields These fields are data input fields.

Specific Selectable Fields

From any of the selectable fields, where some input information is required (i.e., aggregate or data set names, etc.), either a fully qualified name, or a mask can be provided using Mainstar extended masking characters (*, %, <, >, #). For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

For example:

*TEST* – Would pick any aggregates (or data sets) that had the characters TEST appearing in any character position with their names.

Chapter 2 2-2 Mainstar Software Corporation ©2006 BRM Suite: Online Dialog SC23-6061-00



2.1.4 Format and Fields on a Table/List Panel

in

C Ti

Wi

Menu Diagnostics Preferences Utilities Adm VvRr Backup & Recovery Manager Suite Header Text . . .

Command ===> __

Table Display Information. . .

Name Date me _ . .Table Entry Data. . . . . . . . . . . .

Confirmation ndow

Primary Command Field

Sub-menus

Line Table Display with Pop-up Windows Command Field selectable fields

Figure 2-2: Format of Table/List type of panel

Field Description

Sub-Menus By placing your cursor on the desired sub-menu and pressing Enter, a list of options under the selected sub-menu will be displayed for selection.

Primary Command Field Enter a Primary Command on the command line. They are used to alter the display or to invoke external functions.

Line Command Field Enter a Line Command next to a table entry to select it for the Line Command action. The available alpha character Line Commands differ from panel to panel. For example: Line Command R keyed next to a backup event on the ABARS Events panel will select the backup for recover.

Table Display with Selectable Fields

The displayed Table/List information depends on the specific panel.

Pop-Up Windows Used by Backup & Recovery Manager Suite to display confirmation requests, related status information and selection lists.




2.2 Backup & Recovery Manager Suite Main Menu This topic provides an overview of the Main Menu options and sub-menu descriptions.

• Panels that provide access to functionality common to both the ABARS Manager and All/Star products are named either Backup & Recovery Manager Suite or BRM

• Panels for ABARS Manager functions are named either ABARS Manager or ABM • Panels for All/Star functions are named either All/Star or AST • Panels for ASAP functions are named either ASAP or ASP

A common Backup & Recovery Manager Suite (BRM) Inventory Data Set (IDS) is used for both ABARS Manager (ABM) and All/Star. Any references to the BRM IDS refer to data stored in the inventory data set.

Options that apply only to ABARS Manager are described in the Backup & Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

The Backup & Recovery Manager Suite Main Menu is shown below.

Menu Diagnostics Preferences Utilities Admin ------------------------------------------------------------------------------V06.01 Backup & Recovery Manager Suite - Main MenuCommand ==>

Enter an option from the list below:

1 Setup and Configuration2 Backup and Recovery Management3 ASAP 4 Features

Miscellaneous Functions 5 Search for Dataset 6 Reports7 Monitor 8 History

X Exit

Copyright (C) 2006 Mainstar Software CorporationAll Rights Reserved

Figure 2-3: Backup & Recovery Manager Suite Main Menu




Main Menu Field Descriptions

Option Description

Use this option to provide setup and configuration Setup and Configuration – information for both ABARS Manager and All/Star. Main Menu Option 1 ABARS Manager Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060). • Sub-option 1, Aggregate Management with SMS

Interface – ABARS Manager option described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

• Sub-option 2, Group Filter Management – ABARS Manager option described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

All/Star • Sub-option 3, Browse/Edit Backup Tracking INCLUDE

Filters – use to add backup INCLUDE filters for the All/Star Tracking started task to intercept, track, and inventory.

• Sub-option 4, Browse/Edit Backup Tracking EXCLUDE Filters – use to EXCLUDE backups you do not want All/Star to track. This panel is used to EXCLUDE backups you do not want All/Star to track.

• Sub-option 5, Test Backup Tracking Filters – select this option to determine if a Jobname / Jobstep / Procstep / Program will be tracked or excluded by AST.

• Sub-option 6, Build Batch Intercept File and Refresh AST – extracts the Tracking Filters entered in Option 3 that are stored in the BRM database and builds the Batch Intercept File (BIF). It also refreshes the AST started task with the new list of jobs.




Option Description

Backup and Recovery Management – Main Menu Option 2

Use this option to monitor event backup or recoveries by name, date and type. This is the primary panel for backups and recoveries. ABARS Manager Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060). • Sub-option 1, ABARS Events

ABARS Manager option described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

• Sub-option 2, Logical Aggregates ABARS Manager option described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

All/Star • Sub-option 3, Full Volume Dumps – allows you to view

full volume dump events, date, time, and data sets backed up by volume and optionally recover the volume or selected data sets.

• Sub-option 4, Jobs – allows you to view jobs tracked, date, time, and data sets backed up by job and optionally recover the job or selected data sets.

• Sub-option 5, Job Groups – optional facility that allows you to assign and view jobs as a group.

• Sub-option 6, Applications (requires ASAP) – optional facility that groups jobs by application.

ASAP – Main Menu Option 3

Use this option to access the features of ASAP. Refer to the Backup and Recovery Manager Suite User Guide: ASAP (SC23-6059) for more information on the options within ASAP.

Features – Main Menu Option 4

Use this option to access panels for separately licensed selectable features. • Sub-option 1, CATSCRUB – helps you to build a

CATSCRUB command to 'scrub' one or several BCSs of all or specified entries that don't match the actual data sets that have been restored at your DR site.

Search for Data Set – Main Menu Option 5

The data set search option provides the ability to search for specific data sets or masks across all backup events. Use this option to identify all data sets containing overlaps that may potentially cause restoration issues during the recovery process.

Reports – Main Menu Option 6

Several reports may be initiated via Online Dialog panels. (You may also initiate the reports in batch mode.)

Monitor – Main Menu Option 7

This option is used to monitor ABARS-only backups and/or recoveries as they are executing.

History – Main Menu Option 8

This option allows the user to view events based on their backup/recovery date. Line commands available within this option allow you to view event detail.




2.3 Sub-Menu Options Sub-menus are available from all primary windows of Backup & Recovery Manager Suite, except that the Utilities and Admin sub-menus are available only from the Main Menu. Sub-menus are located along the very top of the panel. To select a sub-menu, position the cursor over the desired sub-menu and press Enter. A numbered list of selectable sub-menu options will be displayed. Enter the desired option number and press Enter.

The sub-menus and their numbered option lists are shown below. A detailed description of each sub-menu is provided in separate topics.

Menu Sub-Menu

BRMMAIN Menu Diagnostics Preferences Utilities Admin

1. Messages2. INI Values 3. Exit BRM

Diagnostics Sub-Menu


1. About 2. Load Modules 3. Free Memory4. Trace Records

Preferences Sub-Menu


1. Space Display2. Job Card (ABARS Manager)3. Job Card (All/Star)4. Job Card (CATSCRUB)

Utilities Sub-Menu (available only from the Main Menu)


1. Load Activity Log (ABARS Manager)2. Load Inventory (ABARS Manager)3. Load Inventory (All/Star)4. Load Inventory (All)5. Unload Inventory (ABARS Manager)6. Unload Inventory (All/Star)7. Unload Inventory (All)8. Reset Aggregate Options(ABARS Manager)9. DAD Monitor (ABARS Manager and All/Star)




Admin Sub-Menu (available only from the Main Menu)

Menu Diagnostics Preferences Utilities Admin ----------------------------------------------------------------------------

1. Define Utility Equivalents



-----------------------------------------------------------------------

----------------------------------------------------------------------


2.4 MENU Sub-Menu


1. Messages2. INI Values 3. Exit BRM

2.4.1 Messages – Menu Option 1 To view all product messages, select option 1, Messages. An ISPF Browse panel containing a listing of all of the messages is then displayed. Messages can also be found in the product MESSAGES members. For more information on viewing the product messages in the library members, see 'View Backup & Recovery Manager Suite Messages' (page 1-10).

BROWSE -- BRM-MESSAGE-LISTING Line 00000000 Col 001 080 Command ===> Scroll ===> CSR ********************************* Top of Data **********************************ALB01079E: //SYSPRINT failed to open

DESCRIPTION: A critical JCL DD card could not be opened.

ACTION: Call Mainstar technical support

BRM00101I: A NON-BRM FUNCTION FOUND DESCRIPTION: An ABARS function was determined to be non-BRM controlled.

ACTION: None

BRM00102E: ALLOCATION FAILED FOR DD: SKIPDS DESCRIPTION: Dynamic allocation of the data set to be used by theARCSKEXT failed.

ACTION: Processing stops. Fix the problem and retry the job.




2.4.2 BRMINI Values – Menu Option 2 To view BRMINI values, select sub-menu Menu and select option 2, INI Values. An ISPF Browse panel is displayed for the BRMINI member of the BRM PARMLIB.

Menu Utilities Compilers Help-------------------------------------------------------------------------------BROWSE BRM0601X.QABETA.PARMLIB(BRMINI) - 01.18 Line 00000000 Col 001 080 Command ===> Scroll ===> PAGE ********************************* Top of Data ********************************************************************************************************* * * B R M I N I * * Backup and Recovery Manager Suite Initialization Member ( V06.01 ):* COPYRIGHT(c) 2006 MAINSTAR SOFTWARE CORPORATION * *********************************************************************** /*Syntax rules:Section names: :(colon)section-name - changed or added only by MAINSTAR

Tokens: Token names are changed or added only by MAINSTAR except wherenoted. . Token names are the leftmost character string followed by an =.

Token values: Token values are separated from token names by an = symbol.

2.4.3 Exit Backup & Recovery Manager Suite – Menu Option 3 Exit Backup & Recovery Manager Suite.



-------------------------------------------------------------------------------


2.5 DIAGNOSTICS Sub-Menu


1. About 2. Load Modules 3. Free Memory4. Trace Records

2.5.1 About – Diagnostics Option 1 To view product version detail for products used by Backup & Recovery Manager Suite, select submenu Diagnostics and select option 1, About. The About panel will display the various products used by or included with Backup & Recovery Manager Suite, and their release levels.

BRM - About

BRMPSTAT Command ===>

System InformationSysid => DVLP Operating System => z/OS 01.05.00 JES Version/Level => JES2 z/OS 1.5DFSMS/HSM Level => 1.05 TSO/E Release => 3.0 USERID => KAS ISPF Level => 5.5

Product Information BRM Version => V04.03 Inventory Dataset => BRM0403X.INVDB- Aggregate Count => 208- Volume => SMS001 - Extents => 2 HURBA => 61931520 - Percent Used => 93 HARBA => 66355200

2.5.2 Load Modules – Diagnostics Option 2 To view currently active load modules used by Backup & Recovery Manager Suite, select sub-menu Diagnostics and select option 2, Load Modules. The Resident LMOD panel displays the various programs in use and their current use counts. This option is used for debugging purposes only.

BRMLMOD BRM - Resident LMOD Row 1 of 6 Command ===> ________________________________________________ Scroll ===> HALF

Previous Current Change fromCmd Program Use Count Use Count last inquiry

___ BRMLMOD 1 NEW ___ BRMMAIN1 1 NEW ___ BRMMAIN2 1 NEW ___ CMDCHGR 1 NEW ___ EX 0 NEW ___ FLMTABLE 1 NEW




2.5.3 Free Memory – Diagnostics Option 3 To view current memory usage, select sub-menu Diagnostics and select option 3, Free Memory. The following messages are displayed identifying current memory utilization. This option is used for debugging purposes only.

BRM - Free Memory

Command ===>

Memory InformationBelow the line: Current => 7,815,168Change => No previous BELOW value

Above and below (ANY) line:Current => 985,179,648Change => No previous ANY value

2.5.4 Trace Records – Diagnostics Option 4 – ABARS Manager Only Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).




2.6 PREFERENCES Sub-Menu


1. Space Display2. Job Card (ABARS Manager)3. Job Card (All/Star)4. Job Card (CATSCRUB)

2.6.1 Space Display – Preferences Option 1 – ABARS Manager and All/Star Space totals are displayed on various panels throughout ABARS Manager and All/Star. You can decide how you want the space totals to be displayed. Modifications made to space totals are by individual userid only. To specify how space totals will be displayed, select the Preferences submenu and then select option 1, Space Display. The Data Set Space Display Options panel is displayed.

BRMSPOPT BRM - Data Set Space Display OptionsCommand ===> ________________________________________________ Scroll ===> HALF

Commands: END(PF3)/SAVE - to Save record and returnCAN - to Return without Saving

Space Unit. . . . . . . => K All units are based on K=1024 bytesB for Bytes 1 for equivalent 3380-D volumes (630 meg)K for Kilobytes 2 for equivalent 3380-E volumes (1260 meg)M for Megabytes 3 for equivalent 3380-K volumes (1891 meg)G for Gigabytes 4 for equivalent 3390-1 volumes (946 meg)T for Terabytes 5 for equivalent 3390-2 volumes (1892 meg)

6 for equivalent 3390-3 volumes (2838 meg)7 for equivalent 3390-9 volumes (8514 meg)

Note: DASD volume displays assume maximum blocking (half track). Aggregatescontaining data sets with less than half track blocking will require morespace than the volume display indicates.

Places right of decimal => 0 0 for nnnnnnnn 1 for nnnnnn.n 2 for nnnnn.nn 3 for nnnn.nnn

Options chosen here affect panels where data set space information is displayed.




Data Set Space Display Options Panel – Field Descriptions

To select which space option you wish to display, press End (PF3) or key SAVE on the command line and press Enter.

Field Description

Space Unit Space unit to use for space total displays. Valid values are:

B – Bytes 1 – equivalent 3380-D volumes (630 meg)

K – Kilobytes 2 – equivalent 3380-E volumes (1260 meg)

M – Megabytes 3 – equivalent 3380-K volumes (1891 meg)

G – Gigabytes 4 – equivalent 3390-1 volumes (946 meg)

T – Terabytes 5 – equivalent 3390-2 volumes (1892 meg)

6 – equivalent 3390-3 volumes (2838 meg)

7 – equivalent 3390-9 volumes (8514 meg)

Places right of decimal Number of decimal points to display in space totals. Valid values are:

0 for nnnnnnnn 1 for nnnnnn.n 2 for nnnnn.nn 3 for nnnn.nnn




2.6.2 Job Card (ABARS Manager) – Preferences Option 2 – ABARS Manager Only Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

2.6.3 Job Card (All/Star) – Preferences Option 3 – All/Star Only Various options within Backup & Recovery Manager Suite require the submission of JCL to perform certain actions. In order for the jobs to run correctly, a job card must be provided. Upon submission of the options within Backup & Recovery Manager Suite, a job card will be presented to you for modification. By selecting the Preferences Sub-menu and selecting option 3, Job Card (All/Star), users can change their job card at any time. Modifications to job cards are by individual userid only.

ALL/STAR - Job Card OptionsCommand ===> Scroll ===> PAGE


Randomize Last Character of Job Name? N Y or N

BLDREST JOB CARD: => //ASTREST1 JOB (ACCT),'BRM BATCH',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID=> //*=> //*=> //*

LOADIDS/UNLOADIDS JOB CARD:=> //ASTUTIL2 JOB (ACCT),'BRM BATCH',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID=> //*=> //*=> //*

Job Card (All/Star) Panel – Field Descriptions

To save changes to the job cards, press End (PF3) or key SAVE on the command line and press Enter.

Field Description

All/Star BLDREST Job Card

Change this job card to affect how the job card will be used during a restore.

All/Star Load IDS/Unload IDS Job Card

Change this job card to affect how the job card will be used for a Load of an IDS, or an Unload of an IDS.




2.6.4 Job Card (CATSCRUB) – Preferences Option 4 – ABARS Manager and All/Star Various options within Backup & Recovery Manager Suite require the submission of JCL to perform certain actions. In order for the jobs to run correctly, a job card must be provided. Upon submission of the options within Backup & Recovery Manager Suite, a job card will be presented to you for modification. By selecting the Preferences Sub-menu and selecting option 4, Job Card (CATSCRUB), users can change their job card at any time. Modifications to job cards are by individual userid only.

BRM - Job Card Options - CATSCRUBCommand ===> Scroll ===> PAGE


Randomize Last Character of Job Name? N Y or N

CATSCRUB JOB CARD: => //BRMCATSC JOB (ACCT),'BRM BATCH', CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID=> //*=> //*

=> //*




2.7 UTILITIES Sub-Menu – ABARS Manager and All/Star The Utilities sub-menu is only available from the Backup & Recovery Manager Suite Main Menu.


1. Load Activity Log (ABARS Manager)2. Load Inventory (ABARS Manager)3. Load Inventory (All/Star)4. Load Inventory (All)5. Unload Inventory (ABARS Manager)6. Unload Inventory (All/Star)7. Unload Inventory (All)8. Reset Aggregate Options (ABARS Manager)9. DAD Monitor (ABARS Manager and All/Star)

2.7.1 Load Activity Log (ABARS Manager) – Utilities Option 1 Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

2.7.2 Load Inventory (ABARS Manager) – Utilities Option 2 Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

2.7.3 Load Inventory (All/Star) – Utilities Option 3 This option is used to reload All/Star data into the BRM Inventory Data Set from a data set which was previously unloaded. Various options are available on the panel to determine which All/Star unloaded data should be reloaded into the BRM Inventory Data Set.

all All/Star data( )

of all extracted data.

Note: ABARS Manager and All/Star share the same Backup & Recovery Manager Suite (BRM) Inventory Data Set. If you are licensed to use All/Star and you wish to remove ABARS Manager entries from the BRM Inventory Data Set, the easiest way to accomplish this is to execute an All/Star UNLOADIDS to extract the All/Star backups; delete the BRM Inventory Data Set; define a new BRM Inventory Data Set, and LOADIDS the previously unloaded All/Star entries. Note: The default is to load previously extracted from the Inventory Data Set. Optional keywords JOB nn) and GENS(nn can be used to selectively load previously extracted Inventory Data Set data, instead of the default



--------------------------------------------------------------------------


Menu Diagnostics Preferences

BRM5043 All/Star - Load Inventory DatasetCommand ===>

(S) SELECT AN OPTION: Build/Submit JCL Build/View JCL

LOAD OPTIONS: Input File DSN => Output Inventory DSN => 'BRMX.PROD.INVDB'

Include the following: (Leave all fields blank to LOAD ALL All/Star records)Job => Blank for ALL Generations => 0 - 9999, * - ALLReplace => N Y or N

Exclude the following:Job =>

All/Star Load Inventory Data Set Panel – Field Descriptions

Field Description

Build/Submit JCL Initiates a reload of All/Star data into the BRM Inventory Data Set. The JCL will be built using the options supplied on the panel and the Load will be submitted.

Build/View JCL Allows you to view the JCL before actual submission of the Load, or to simply browse the parameters used. The JCL will be built using the options on the panel and the results will be displayed.

Input File DSN Supply the name of the data set that contains the data to load into the BRM Inventory Data Set.

Output Inventory DSN Supply the name of the new BRM Inventory Data Set to load. This parameter will override the default in BRMINI.

Include Job Supply the names/masks of the Job(s) to include in the Load of the Inventory Data Set. Default: All jobs will be loaded.

Include Generations Supply the number of All/Star Jobs generations to include in the Load of the Inventory Data Set. 0–9999 – to specify generations. * – to include all Job generations. Default: All Job generations will be loaded.

Replace Replace current entries.

Exclude Job Supply the names/masks of the Job(s) to exclude from the Load of the Inventory Data Set.



---------------------------------------------------------------------------


2.7.4 Load Inventory (All) – Utilities Option 4 This option is used to reload ABARS Manager and All/Star data into the BRM Inventory Data Set from a data set which was previously unloaded. Various options are available on the panel to determine which data should be reloaded into the BRM Inventory Data Set.


BRM5044 All - Load Inventory DatasetCommand ===>


LOAD OPTIONS: Input File DSN => Output Inventory DSN => 'BRM0403X.INVDB'

Include the following: (Leave all fields blank to UNLOAD ALL records)Event/Logical Aggregate =>Job =>

Blank for ALL Blank for ALL

ABACKUP/Job Generations =>ABACKUP Verifies => ARECOVER Generations => Replace => N

0 - 9999, * - ALL0 - 9999, * - ALL0 - 9999, * - ALLY or N

Exclude the following:Event/Logical Aggregate =>Job => Incomplete EventsEvents with WarningsEvents with Errors

=> N => N => N

Y or N Y or N Y or N




Load Inventory (All) Panel – Field Descriptions

Field Description

Build/Submit JCL Initiates a reload of data into the BRM Inventory Data Set. The JCL will be built using the options supplied on the panel and the Load will be submitted.

Build/View JCL Allows you to view the JCL before actual submission of the Load, or to simply browse the parameters used. The JCL will be built using the options on the panel and the results will be displayed.

Input File DSN Supply the name of the data set that contains the data to load into the BRM Inventory Data Set.

Output Inventory DSN Supply the name of the new BRM Inventory Data Set to load. This parameter will override the default in BRMINI.

Event/Logical Aggregate Supply the names/masks of the event(s) or Logical Aggregate(s) to include in the Load of the Inventory Data Set. Default: All events and Logical Aggregates will be loaded.

Job Supply the names/masks of the Job(s) to include in the Load of the Inventory Data Set. Default: All jobs will be loaded.

ABACKUP/Job Generations Supply the generation number(s) of ABARS ABACKUP generations to include in the Load of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ABACKUP generations. Default: All ABACKUP generations will be loaded.

ABACKUP Verifies Supply the generation number(s) of ABARS ABACKUP VERIFIES to include in the Load of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ABACKUP VERIFIES generations. Default: All ABACKUP VERIFIES generations will be loaded.

ARECOVER Generations Supply the generation number(s) of ABARS ARECOVERs to include in the Load of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ARECOVER generations. Default: All ARECOVER generations will be loaded.

Replace Replace current entries.

Incomplete Events Specify 'Y' to exclude all incomplete events from the Load.

Events with Warnings Specify 'Y' to exclude all events with warnings from the Load.

Events with Errors Specify 'Y' to exclude all events with errors from the Load.




2.7.5 Unload Inventory (ABARS Manager) – Utilities Option 5 Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

2.7.6 Unload Inventory (All/Star) – Utilities Option 6 This option is used to unload All/Star event data from the BRM Inventory Data Set to a specified data set. Various options are available on the panel to determine how the data should be unloaded.

Note: ABARS Manager and All/Star share the same BRM Inventory Data Set. If you are licensed to use All/Star and you wish to remove ABARS Manager entries from the BRM Inventory Data Set, the easiest way to accomplish this is to execute an All/Star UNLOADIDS to extract the All/Star entries; delete the BRM Inventory Data Set; define a new BRM Inventory Data Set, and LOADIDS the previously unloaded All/Star entries.

all All/Star dataload of ALL.

Menu Diagnostics Preferences -----------------------------------------------------------------------BRM5046 All/Star - Unload Inventory DatasetCommand ===>

Inventory Dataset: BRMX.PROD.INVDB

(S) SELECT AN OPTION:Build/Submit JCL Build/View JCL

UNLOAD OPTIONS: Include the following: :Job => Blank for ALL Generations => 0 - 9999, * - ALL

Exclude the following:Job =>

OPTIONAL: Output file DSN =>

If you do not specify an Output Dataset, only aLIST will be provided in the SYSOUT.

Note: The default is to unload from the Inventory Data Set. Optional keywords JOB(nn) and GENS(nn) can be used to selectively un data, instead of the default

Leave all fields blank to UNLOAD ALL All/Star records




Unload Inventory (All/Star) Panel – Field Descriptions

Once all required fields have been entered, select the 'Build/Submit JCL' to build the JCL and execute the Unload, or 'Build/View JCL' to view the JCL before submission.

Field Description

Build/Submit JCL This option will initiate an Unload of All/Star events from the BRM Inventory Data Set. The JCL will be built using the options supplied on the panel and the Unload will be submitted.

Build/View JCL This option will allow you to view the JCL before actual submission of the Unload, or to simply browse the parameters used. The JCL will be built using the options on the panel and the results will be displayed.

Include Job Supply the names/masks of the Job(s) to include in the Unload of the Inventory Data Set. Default: All jobs will be unloaded.

Include Generations Supply the number of All/Star Jobs generations to include in the Unload of the Inventory Data Set. 0–9999 – to specify generations. * – to include all Job generations. Default: All Job generations will be unloaded.

Exclude Job Supply the names/masks of the Job(s) to exclude from the Unload of the Inventory Data Set.

Output File DSN Optional parameter. Use to specify the output data set name to unload Inventory Data Set records to. If the specified Output File DSN does not exist, it will be dynamically allocated, and then deleted at job end. The default allocation is:

SPACE=(CYL,(1,1)),UNIT=SYSALLDA,RECFM=FB,LRECL=6159, BLKSIZE=0

The default file allocation values may be changed by modifying the values for these tokens in the :PROCESSING_OPTIONS section of the BRMINI PARMLIB member:

UNLOADIDS_SPACE = 'CYLINDERS SPACE(1 2)'UNLOADIDS_UNIT = SYSALLDA

Default: All data will be unloaded, but only a report will be created.




2.7.7 Unload Inventory (All) – Utilities Option 7 This option is used to unload All event data from the BRM Inventory Data Set to a specified data set. Various options are available on the panel to determine how the data should be unloaded.

Menu Diagnostics Preferences -----------------------------------------------------------------------------BRM5047 All - Unload Inventory DatasetCommand ===>

Inventory Dataset: BRM0403X.INVDB


UNLOAD OPTIONS: Include the following: (Leave all fields blank to UNLOAD ALL records)Event/Logical Aggregate =>Job =>

Blank for ALL Blank for ALL

ABACKUP/Job Generations =>ABACKUP Verifies => ARECOVER Generations => Management Class =>

0 - 9999, * - ALL0 - 9999, * - ALL0 - 9999, * - ALL

Exclude the following:Event/Logical Aggregate =>Job => Management ClassIncomplete EventsEvents with WarningsEvents with Errors

=> => N => N => N

Y or N Y or N Y or N

OPTIONAL: Output file DSN =>

If you do not specify an Output Dataset, only aLIST will be provided in the sysout.




Unload Inventory Data Set (All) Panel – Field Descriptions

Once all required fields have been entered, select the 'Build/Submit JCL' to build the JCL and execute the Unload, or 'Build/View JCL' to view the JCL before submission.

Field Description

Build/Submit JCL This option will initiate an Unload of All events from the BRM Inventory Data Set. The JCL will be built using the options supplied on the panel and the Unload will be submitted.

Build/View JCL This option will allow you to view the JCL before actual submission of the Unload, or to simply browse the parameters used. The JCL will be built using the options on the panel and the results will be displayed.

Event/Logical Aggregate Supply the names/masks of the ABARS event(s) or Logical Aggregate(s) to include/exclude in the Unload of the Inventory Data Set. Default: All events/Logical Aggregates will be included/excluded in the Unload.

Job Supply the names/masks of the Job(s) to include/exclude in the Unload of the Inventory Data Set. Default: All jobs will be unloaded.

ABACKUP/Job Generations Supply the generation number(s) of ABARS ABACKUP generations to include in the Unload of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ABACKUP generations. Default: All ABACKUP generations will be loaded.

ABACKUP Verifies Supply the generation number(s) of ABARS ABACKUP VERIFIES to include in the Unload of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ABACKUP VERIFIES generations. Default: All ABACKUP VERIFIES generations will be loaded.

ARECOVER Generations Supply the generation number(s) of ARECOVERs to include in the Unload of the Inventory Data Set. 0–9999 – to specify generations. * – to include all ARECOVER generations. Default: All ARECOVER generations will be loaded.

Management Class Supply the name of the management class to include in the Unload of the Inventory Data Set. Default: All management classes will be unloaded.

Incomplete Events Specify Y to exclude all incomplete events from the Unload.

Events with Warnings Specify Y to exclude all events with warnings from the Unload.

Events with Errors Specify Y to exclude all events with errors from the Unload.




Field Description

Output File DSN Optional parameter. Use to specify the output data set name to unload Inventory Data Set records to. If the specified Output File DSN does not exist, it will be dynamically allocated, and then deleted at job end. The default allocation is:

SPACE=(CYL,(1,1)),UNIT=SYSALLDA,RECFM=FB,LRECL=6159, BLKSIZE=0

The default file allocation values may be changed by modifying the values for these tokens in the :PROCESSING_OPTIONS section of the BRMINI PARMLIB member:

UNLOADIDS_SPACE = 'CYLINDERS SPACE(1 2)'UNLOADIDS_UNIT = SYSALLDA

Default: All data will be unloaded, but only a report will be created.



------


2.7.8 Reset Aggregate Options (ABARS Manager) – Utilities Option 8 Options that apply only to ABARS Manager are described in the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

2.7.9 DAD Monitor (ABARS Manager and All/Star) – Utilities Option 9 This option invokes the DAD Started Task Monitor. It will only show data if you are using the DAD started task on your system.


DAD Monitor Command ==> ___________________________________________________________________

1 Display DAD Status2 Display DAD Statistics3 DAD Commands

Display DAD Status – Option 1

Choosing this option displays the status of DAD subtasks. The subtasks from any image (on which a DAD is running) can be displayed by entering the SYSID for that image in the preliminary screen.

BRM - Select SYSID DADSYSID Command ==> _________________________________________

Enter SYSID => DVLP Default is current SYSID

Press ENTER to Continue or Press END(PF3) to Return

Pressing Enter continues to the screen below.


DADMSTAT BRM DAD Task Status by SYSIDCommand ==> ___________________________________________________ SYSID ==> DVLP

To view task status for another image, press END(PF3) to return to theprevious panel, then change the SYSID and press Enter

Task Status -----------------------------DAD Monitor Command Processor => UP DAD Database Read => UP DAD Database UpdateDAD Overflow EXPORT

=> UP => UP

DAD Overflow IMPORT => UP DAD U83 Exit => UP




Display DAD Statistics – Option 2

Choosing this option displays various DAD statistics. The statistics from any image (on which a DAD is running) can be displayed by entering the SYSID for that image in the preliminary screen. Also, statistics can be viewed for the previous four days by changing the date.

BRM - Select SYSID and Date DADSTATP Command ==> __________________________________________

Enter SYSID => DVLP Default is current SYSID

Enter Date => 04/30/05 Default is Today's DateChange Date to view monitor statistics from previous days


Pressing Enter continues to the screen below.


DADSTATS BRM DAD Processing StatisticsCommand ==> ___________________________________________________ SYSID ==> DVLP

Press ENTER to refresh QUERY display

Data Collected since Date/Time => 04/30/05 00:00:12 More: +

U83 Exit Record Processing:16810 => SMF Records moved to DAD Dataspace

0 => SMF Records currently in buffer overflow dataset0 => SMF Records lost - overflow dataset not available 0 => Number of times losses occurred N => Are losses occurring now?

DAD Dataspace Read Buffers:1007 => Total buffers 1006 => Available buffers 18 => Highest number of buffers used0 => Longest time of continuous buffer use in minutes0 => Number of times 80 to 99 percent of buffers in use0 => Number of times 50 to 79 percent of buffers in use0 => Number of times 20 to 49 percent of buffers in use0 => Number of times 20 to 49 percent of buffers in use

2152 => Number of times 00 to 19 percent of buffers in use

Scroll down to finish viewing the panel.




Finish viewing the panel.


DADSTATS BRM DAD Processing StatisticsCommand ==> ___________________________________________________ SYSID ==> DVLP

Press ENTER to refresh QUERY display

Data Collected since Date/Time => 04/30/05 00:00:12 More: -

DAD Dataspace Write Buffers:1007 => Total buffers 900 => Available buffers 234 => Highest number of buffers used0 => Longest time of continuous buffer use in minutes

DAD Database Processing:16810 => Number of database reads 16089 => Number of database updates

0 => Number of pending adds4 => Number of database deletes

Display DAD Commands – Option 3

Choosing this option displays DAD commands. Using the panel below, users can execute DAD commands for the current image. If you want to execute commands for other images, you must log on to that image. The commands below work just like the DAD operator commands.

To select, enter the number on the command line and press Enter.


DADMCMDS BRM DAD Commands Command ==> ___________________________________________________________________

1 STOP DAD Database Read Task 2 START DAD Database Read Task 3 KILL DAD Database Read Task (Use ONLY when STOP fails)

4 STOP DAD Database Update Task5 START DAD Database Update Task6 KILL DAD Database Update Task (Use ONLY when STOP fails)

7 STOP DAD Dataspace Overflow EXPORT Task8 START DAD Dataspace Overflow EXPORT Task

9 STOP DAD Dataspace Overflow IMPORT Task10 START DAD Dataspace Overflow IMPORT Task




2.8 Admin Sub-Menu – All/Star Only Choosing this option allows you to provide backup utility equivalents for All/Star. For example, DFSMSdss executes ADRDSSU. If you use a program name other than ADRDSSU, include it as a DFSMSdss utility equivalent.

To select, enter the number on the command line and press Enter.

Menu Diagnostics Preferences Utilities Admin ----------------------------------------------------------------------------

1. Define Utility Equivalents

2.8.1 Define Utility Equivalents – Admin Option 1 Fill in the backup utility equivalent names after the program name. +---------- ALL/STAR - Define Utility Equivalents ----------+| BRMADMUE Row 1 to 10 of 17 || Command ===> || || Press PF3/15 to Return w/Save or type CAN to Cancel || || Specify Equivalent Utility Names: || --------------------------------------------------------- || ADRDSSU = || ARCINBAK = || BRMBMAIN = || CFCAMS = || CAT00010 = || FDR = || FDRABR = || FDRCPK = || FDRDSF = || IDCAMS = || IEBGENER = || ICEGENER = || IEBCOPY = || SORT = || GVEXPORT = || SYNCGENR = || ADARUN = |+-----------------------------------------------------------+




Chapter 3 3 All/Star: Setup and Configuration – Option 1

Setup and Configuration is Option 1 on the Main Menu. Selecting this option takes you to the setup and configuration options for All/Star.





X Exit


Setup and Configuration Panel

When you select Option 1 from the Main Menu, you will see the Setup and Configuration panel. This chapter describes All/Star sub-options 3–6. For information on ABARS Manager sub-options 1 and 2, see the Backup and Recovery Manager Suite User Guide: ABARS Manager, (document SC236060).

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5100 BRM - Setup and ConfigurationCommand ==> __________________________________________________________________


ABARS Manager1 Aggregate Management with SMS Interface2 Group Filter Management

All/Star3 Browse/Edit Backup Tracking INCLUDE Filters4 Browse/Edit Backup Tracking EXCLUDE Filters5 Test Backup Tracking Filters6 Build Batch Intercept File and Refresh AST

Mainstar Software Corporation ©2006 3-1 Chapter 3 SC23-6061-00 All/Star: Setup and Configuration – Option 1



3.1 Browse/Edit Backup Tracking INCLUDE Filters – Sub-Option 3 When you select sub-option 3 from the Setup and Configuration panel, the Backup Tracking INCLUDE Filters panel is displayed. This panel is where you enter the backups you would like All/Star to track. The intercept mechanism tracks only those jobs/steps/program names identified by these entries.

If you use a name other than the vendor-supplied name of supported programs, see the topic 'Define Utility Equivalents – Admin Option 1' (page 2-29).

All/Star tracks backups without JCL changes and allows you to use job and/or step 'masks' to significantly reduce the effort of defining backup jobs. However, because All/Star assumes that a match on job name, step name, and program name is a backup, avoid using masks that might cause utility executions to be tracked that are in fact not backups.

For instance, an IDCAMS REPRO may simply be used in a VSAM reorganization process. After some initial tracking has been recorded, review what All/Star 'thinks' is a backup to see if masking in these entries is too aggressive. Try to be as specific as possible in defining backup names to track.

i

will be incorrect.

WARNING: Backup jobnames should NOT match restore jobnames. Non-DFSMSdss and FDR type utilities such as IDCAMS REPRO could be tracked and cons dered backups when in fact they are restores. The backup generation results stored in the BRM Suite Inventory Data Set

• HSMAUTODUMP and BACKVOL are not automatically tracked by All/Star. See 'The AUTODUMP Command' (page 9-3), and 'The BACKVOL Command' (page 9-5) for more information on those commands.

• ARCINBAK is tracked by All/Star but requires a special DD. See 'DFSMShsm ARCINBAK Considerations' (page 14-4) for more information.

Note: All/Star supports data set backups, but not PDS member backups.

Note: All/Star tracks data set statistics through a catalog lookup. Data set statistics are not available if data sets are deleted, or renamed prior to completing processing.

Because the number of data sets on full volume dumps can be extensive, it can take considerable time to do the catalog lookups and in turn be reflected in the BRM Suite Inventory Data Set.

BRMINI PARMLIB member token CATLG_DATA_FOR_PHY_DUMPS=Y|N can be set to N to inhibit a catalog lookup. Data set names will still be recorded in the BRM Suite Inventory Data Set, but data set statistics will not be available such as multi-volume information, DSCB information, etc.

Chapter 3 3-2 Mainstar Software Corporation ©2006 All/Star: Setup and Configuration – Option 1 SC23-6061-00


--------------------------------------------------------------------------------



BRM5141 All/Star Backup Tracking INCLUDE Filters Row 1 to 13 of 49Command ===> Scroll ===> CSR

Primary Commands: END(PF3)/SAVE - to Save record and returnCAN - to Return without Saving

Line Commands: D,I,R

C Job Name Job Step Proc Step Program Utility UserID

ASTBJ* * * ASTBJ* * * ASTBJ* * * ASTBJ* * * ASTBJ* * * ASTBJ* * * ASTBJA10 * * ASTBJA2* * * ASTBJA20 * * ASTBJA3* * * ASTBJA30 * * ASTBJB* * * ASTBJ0* * *

FDR FDR IM FDRDSF FDRDSF IM IEBGENER IEBGENER EDP1 FDRABR FDRABR IM FDRCPK FDRCPK IM IDCAMS IDCAMS EDP1 BRMBMAIN BRMBMAIN EDG IEBGENER IEBGENER EDG BRMBMAIN BRMBMAIN EDG IDCAMS IDCAMS EDG BRMBMAIN BRMBMAIN EDG CAT00010 CAT00010 EDG ADRDSSU DSS IM

3.1.1 Backup Tracking INCLUDE Filters Panel – Primary Commands

Primary Command Description

END(PF3)/SAVE Saves the values specified and returns to the previous panel.

CAN To cancel any changes and return to the previous panel.

3.1.2 Backup Tracking INCLUDE Filters Panel – Line Commands

Line Command Description

D Delete a tracking filter.

I Insert a blank line to enter a tracking filter.

R Repeat a tracking filter.




3.1.3 Backup Tracking INCLUDE Filters Panel – Field Descriptions

Backup Tracking INCLUDE Description Filters Field

Program Specify a program for All/Star Tracking (AST) Started Task to track: ADRDSSU, CFCAMS, FDR, FDRABR, FDRCPK, FDRDSF, IDCAMS, IEBGENER, ICEGENER, SYNCGENR, IEBCOPY, SORT, ARCINBAK, BRMBMAIN, CAT00010. or * for all programs. • HSMAUTODUMP and BACKVOL are not automatically tracked

by AST. See 'The AUTODUMP Command' (page 9-3), and 'The BACKVOL Command' (page 9-5) for more information on those commands.

• ARCINBAK is tracked by AST but requires a special DD. See 'DFSMShsm ARCINBAK Considerations' (page 14-4) for more information.


Job Name Specify a job name or job name mask for AST to track. • HSMAUTODUMP and BACKVOL are not automatically tracked



Note: The default of * is not recommended as the started task will track every single job in your environment and you will waste unnecessary resources.

Default: *

Job Step Specify a job step or job step mask for AST to track. Default: *

Proc Step Specify a proc step or proc step mask for AST to track. Default: *

Utility Identifies the associated Utility for the program specified.

UserID Specifies the userid of the last person who updated the fields.



-------------------------------------------------------------------------------


3.2 Browse/Edit Backup Tracking EXCLUDE Filters – Sub-Option 4 When you select sub-option 4 from the Setup and Configuration panel, the Backup Tracking EXCLUDE Filters panel is displayed. This panel is used to EXCLUDE backups you do not want All/Star to track.

If you use a name other than the vendor-supplied name of supported programs, see the topic 'Define Utility Equivalents – Admin Option 1' (page 2-29).

Note: All/Star supports data set backups, but not PDS member backups.

Preferences


BRM5142 All/Star Backup Tracking EXCLUDE Filters Row 1 to 2 of 2 Command ===> Scroll ===> CSR

Primary Commands: END(PF3)/SAVE - to Save record and returnCAN - to Return without Saving


C Job Name Job Step Proc Step Program Utility UserID

ASTBJ010 * * ADRDSSU DSS DH01

3.2.1 Backup Tracking EXCLUDE Filters Panel – Primary Commands


END(PF3)/SAVE Saves the values specified and returns to the previous panel.

CAN To cancel any changes and return to the previous panel.




3.2.2 Backup Tracking EXCLUDE Filters Panel – Line Commands


D Delete a tracking filter.

I Insert a blank line to enter a tracking filter.

R Repeat a tracking filter.

3.2.3 Backup Tracking EXCLUDE Filters Panel – Field Descriptions

Backup Tracking EXCLUDE Description Filters Field

Program Specify a program to EXCLUDE from being tracked by All/Star. These filters are used when tracking INCLUDES by mask and you don’t want to track all the jobs that fit the mask. ADARUN, ADRDSSU, CFCAMS, GVEXPORT, FDR, FDRABR, FDRCPK, FDRDSF, IDCAMS, IEBGENER, ICEGENER, SYNCGENR, IEBCOPY, SORT, ARCINBAK, BRMBMAIN, CAT00010. or * for all programs. • HSMAUTODUMP and BACKVOL are not automatically tracked







Backup Tracking EXCLUDE Filters Field

Description

Job Name Specify a job name or job name mask for AST to track. • HSMAUTODUMP and BACKVOL are not automatically tracked

by AST. See 'The AUTODUMP Command' (page 9-3) for more information.


Note: The default of * is not recommended as the started task will track every single job in your environment and you will waste unnecessary resources.

Default: *

Job Step Specify a job step or job step mask to exclude from being tracked. Default: *

Proc Step Specify a proc step or proc step mask to exclude from being tracked. Default: *

Utility Identifies the associated Utility for the program specified.

UserID Specifies the userid of the last person who updated the fields.



-------------------------------------------------------------------------------


3.3 Test Backup Tracking Filters – Sub-Option 5 When you select sub-option 5 from the Setup and Configuration panel, the Test Backup Tracking Filters Panel is displayed. This panel is used to test filters entered into the INCLUDE and EXCLUDE panels to help ensure you are including and excluding the filters you intend to. For example, if you enter a mask of ASTB* on the INCLUDE panel, then enter ASTBJ* on the EXCLUDE panel, the Test Backup Tracking Filters panel will show you the final results of what will be tracked by All/Star.

Enter the filters you would like to test. An * for all jobnames, a specific jobname, or jobname mask like ASTB* can be entered.

All/Star - Test Backup Tracking Filters SetupBRM514T Command ===>

Specify the criteria to use to compare to the Backup Tracking Filterscurrently stored in the BRM Suite Inventory Dataset:Job Name or Mask ===> * Job Step or Mask ===> *Proc or Mask ===> * Program or Mask ===> *


The following is displayed with the results.


BRM5143 All/Star Test Backup Tracking Filters Row 11 to 20 of 62Command ===> Scroll ===> CSR

NOTE: The filter table shown is what is currently stored in the BRM SuiteInventory Dataset. It may or may not reflect what is loaded into the ASTstarted Task.

Specify search criteria to test what AST will track:

Job Name Job Step Proc Program Status * * * *

ASTBJA30 * * ASTBJB* * * ASTBJ0* * * ASTBJ010 * * ASTBJ1* * * ASTBJ2* * * ASTBJ3* * * ASTBJ4* * * ASTBJ5* * * ASTBJ9* * *

BRMBMAIN INCLUDE CAT00010 INCLUDE ADRDSSU INCLUDE ADRDSSU EXCLUDE IDCAMS INCLUDE ICEGENER INCLUDE IEBGENER INCLUDE SORT INCLUDE IEBCOPY INCLUDE ARCINBAK INCLUDE




3.4 Build Batch Intercept File and Refresh AST – Sub-Option 6 After entering the backups you want All/Star to track, you must update the batch intercept file (BIF) and refresh the All/Star Tracking (AST) started task. Any time you add new job names to All/Star through ISPF, you must refresh the batch intercept file.

When you choose sub-option 6 from the Setup and Configuration panel, the panel below is displayed.

BRMCNF01 Batch Intercept File will be Updatedand AST Started Task will be Refreshed Reply Y to continue- or -Reply N to cancel

Update BIF and Refresh AST?

REPLY ===> Y (Y or N)

Reply Y to update the AST Batch Intercept File (BIF) from the database and refresh the AST Started Task.

A message will then tell you whether the update was successful.

This process uses the filters entered on the Backup Tracking INCLUDE and EXCLUDE Filter Panels, writes the entries to a sequential data set (the data set name specified on the AST_BIF token found in the product PARMLIB member (BRMINI) and signals the AST started task to refresh the current joblist it is tracking.

NOTE: Even though the Refresh was issued, the System Message Log must be checked to verify that the following message was produced on each of the systems to be refreshed:

AST20149I JOB TABLE REFRESHED




Chapter 4 4 All/Star: Backup and Recovery Management – Option 2

Backup and Recovery Management (Option 2) allows you to track backups, perform recoveries, and view detailed information about past backup events. Other line commands available within this option allow you to interface directly with other All/Star options.





X Exit


Mainstar Software Corporation ©2006 4-1 Chapter 4 SC23-6061-00 All/Star: Backup and Recovery Management – Option 2


------------------------------------------------------------------------------


4.1 Backup and Recovery Management for All/Star – Option 2 When you select Option 2 from the Main Menu, the Backup and Recovery Management menu is displayed. This chapter will cover the following All/Star sub-options:

• Sub-option 3 – Full Volume Dumps • Sub-option 4 – Jobs • Sub-option 5 – Job Groups • Sub-option 6 – Applications (Requires ASAP)

For information on ABARS Manager sub-option 1, ABARS Events, and sub-option 2, Logical Aggregates, see the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).


BRM5200 BRM - Backup and Recovery ManagementCommand ==> __________________________________________________________________


ABARS Manager1 ABARS Events 2 Logical Aggregates

All/Star3 Full Volume Dumps4 Jobs 5 Job Groups6 Applications (Requires ASAP)

4.2 Full Volume Dumps – Sub-Option 3 – Initial Selection The first time you select Option 2, Backup & Recovery Management from the Main Menu, then sub-option 3, Full Volume Dumps, the Full Volume Dump Search Setup panel is displayed. Use this panel to display information on your Full Volume Dump backups.

Full Volume Dump Search SetupBRM522A Command ===> _________________________________________________________

Specify the criteria to use when searching for Full Volume Dump Events.Volume or Mask ===> *_____ Auto Expand List ===> N Y or N Event Date ===> __________ *-nnn -(nnn = days) or

Date (Format YYYY/MM/DD,MM/DD/YYYY)RC (FVD/BRM) ===> ___ / ___ n , <n , >n , W -(RC=4), E -(RC>=8)Sort list by ===> V V -Vol, D -Date, E -Errors

Enter "/" to select option_ Store values to be used as default for this USERID _ Don't show this panel again


After you enter your search criteria, press Enter. The Full Volume Dumps panel will be displayed.

If you want to skip the Search Setup panel from now on, select the field 'Don't show this panel again'. The current search criteria will become your default criteria, and the Full Volume Dumps panel will be displayed directly.

Chapter 4 4-2 Mainstar Software Corporation ©2006 All/Star: Backup and Recovery Management – Option 2 SC23-6061-00



Full Volume Dump Search Setup Panel – Field Descriptions

Field Description

Volume or Mask Enter a volume name or mask for the volume whose backup events you want to search for. Can be up to six characters in length. Any of the ACS masking characters can be used to search for a volume name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). Default: *

Auto Expand List Expand/shrink entire event list.

Event Date • Specify a date criteria or exact date to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • If the Date field is left blank, all dates are displayed. • In the following examples, n = 1–999.

*-n – only displays events equal to n relative days from today. Example: '*-4' displays only events four days from today. *=n – displays all events equal to today through n relative days from today. Example: '*=4' displays events starting today through four days from today. *+n – displays all gen 0 events equal to today through n relative days from today. All generations of each event are displayed regardless of date. Example: '*+4' displays all gen 0 events from today through four days from today with each of their subsequent generations regardless of date.

RC (FVD/BRM) Display Full Volume Dump (FVD) and/or All/Star return codes. • Specify E to display all FVD events that ended with return code

8 or greater (Error messages). • Specify W to display all FVD events that ended with return code

4 (Warning messages). • Specify an RC between 0 and 999 to display specific FVD

return codes. Example: '0' – displays only events with RC=0.

'4' – displays only events with RC=4. • Specify a range of FVD return codes:

Example: '<4' – displays all events with RC less than four. '>4' – displays all events with RC more than four.

Sort list by Sort list by Volume, Date or Errors. Valid options are: V = Volume, D = Date, E = Errors

Store values to be used as default for this USERID

Select this field with a '/' to store the volume name or mask as entered on this panel. If selected, the next time the Full Volume Dump Search Setup panel is displayed for your userid, the Name or Mask field, and all other fields will contain the values last entered here. To view/change this panel after it has been stored, key an 'S' or '?' under the 'C' field on the Full Volume Dump panel.



------------------------------------------------------------------------------


Field

ip the Setup

menu.

Description

Don't show this panel again Select this field with a '/' to sk Full Volume Dumps Search panel and go directly to the Full Volume Dumps panel when

you select sub-option 3 from the Backup and Recovery Management

4.2.1 About the Full Volume Dumps Panel The Full Volume Dumps panel displays all events found in the BRM Inventory Data Set that match the search criteria you specified on the Full Volume Dump Search Setup panel.

Menu Diagnostics Preferences ------------------------------------------------------------------------------

ALL/STAR Full Volume Dumps Row 1 to 12 of 35 Command ===> Scroll ===> CSR

Primary Cmds: REFresh,H,SD,SE,SV Date => 2004/07/06Line Cmds: GL,N,R,S,+,- Time => 12:48

Sort => V D,E,V

C Volume +- Jobname Gen PGM/Type RC RCB Date Time Total * - DSNs

ARCHV1 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 147 ARCHV2 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 162 ARCHV3 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 12 ARCHV4 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 4 CATX01 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 278 CATX02 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 258 CATX03 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 208

******************************* Bottom of data *******************************

Full Volume Dumps Panel – Primary Command Descriptions


REFresh Refreshes the display to show full volume dumps that recently ended.

H Displays the History panel.

SD Changes the sort value to 'D' and sorts by date.

SE Changes the sort value to 'E' and sorts errors by date.

SV Changes the sort value to 'V' and sorts by volume.




Full Volume Dumps Panel – Line Command Descriptions

Using line commands is described in more detail in separate topics.


GL Display job groups currently tracking the jobname for this full volume dump.

N List data set names backed up.

R Submit restore of selected volume.

S Select to view backup detail.

+/- Expand/Shrink entire list

Full Volume Dumps Panel – Field Descriptions

Field Description

C Enter 'S' or '?' under the 'C' field to display the Full Volume Dumps Search Setup panel.

Volume Volume or mask of full volume dumps to display.

+- Expand/Shrink entire list.

Jobname Jobname that performed the full volume dump.

Gen Relative generation of the volume backed up.

PGM/Type Program/Utility that performed the full volume dump DSS FVD – DSS FULL VOLUME DUMP FDR FVD – FDR FULL VOLUME DUMP FDR FDR – FDR ABR FDR DUMP HSM AUTO – HSM AUTODUMP

RC Specify an RC between 0 and 999 to display FVD return codes. Examples:

0 – show only events with RC = 0 4 – show only events with RC = 4 <4 – show only events with RC < 4 >4 – show only events with RC > 4 W – show only events with RC = 4 E – show only events with RC >= 8

If the RC is prefixed with '*', then the return code was estimated based on the ending status since no return code could be found in the database.




Field Description

RCB Specify an RC between 0 and 999 to display BRM return codes. Examples:

0 – show only events with RC = 0 4 – show only events with RC = 4 <4 – show only events with RC < 4 >4 – show only events with RC > 4 W – show only events with RC = 4 E – show only events with RC >= 8

If the RCB is prefixed with '*', then the return code was estimated based on the ending status since no return code could be found in the database.

Date Date searches are done against the most current Gen only. Valid options

* for today only *-1 for today and yesterday only *-nnn for today up to 999 days ago

• Date can also be in format YYYY/MM/DD or MM/DD/YYYY. In this case, only volume backups matching that date will be displayed.

• If the date field is left blank, all dates are displayed.

Time No input required. Displays the time of the event.

Total DSNs Displays the total number of data sets in the volume that were backed up.



------------------------------------------------------------------------------

-------------------------------------------------------------------------------


4.2.2 Line Command N – View Data Set Name List To view a list of data set names backed up, enter Line Command N on the Full Volume Dumps Panel.




Sort => V D,E,V


ARCHV1 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 147 ARCHV2 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 162 ARCHV3 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 12

N ARCHV4 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 4 CATX01 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 278 CATX02 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 258 CATX03 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 208

******************************* Bottom of data *******************************

The View Data Set Name List panel is displayed.


All/Star - View Dataset Name List Row 1 of 1 Command ===> Scroll ===> PAGE

Jobname => IMREPRO1 (0) Date/Time => 2004/07/19 09:19:28Stepname/Task => REPRO01 / 1 Type => IDCAMS REPRO Procname => N/ARC ( IDC /AST) => 0 / 0Primary Commands: Res

Line Commands: R,I,L,O DSN Multi

C DSN Level Vol

IM.BRM1.ACCOUNT.INFO.VSAM.FILE PRI NO ******************************* Bottom of data *******************************




View Data Set Name List Panel – Primary Command Descriptions

Res R


Reset the Data Set Name List to the original after has been used.

View Data Set Name List Panel – Line Command Descriptions


R Submit restore of selected volume. See the topic 'Line Command R – All/Star Restore' (page 4-9).

I Inquiry – View data set detail.

L Locate or search for data set across other jobnames.

O Show overlaps. Cross reference data set to determine if any other job is backing up the same data set.



------------------------------------------------------------------------------


4.2.3 Line Command R – All/Star Restore To select a data set, volume, job or job group to restore, select the entry with Line Command R and press Enter. Below is an example of a data set restore.




Sort => V D,E,V*PRESS END(PF3) TO PROCESS SELECTED DSNS


ARCHV1 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 147 ARCHV2 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 162 ARCHV3 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 12

R ARCHV4 + P390BKP6 0 DSS FVD 0 0 2004/07/02 16:08:26 4 CATX01 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 278 CATX02 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 258 CATX03 + P390BKP5 0 DSS FVD 0 0 2004/07/02 16:07:51 208

******************************* Bottom of data *******************************

Press End or (PF3) to process the selected data set names for restore. The Select Restore Option panel is displayed.

Select Restore Option Panel

Select one of the options on this panel. See the panel options below for a more detailed explanation.

Select Restore Option

Command ===>

(S) Select an Option for Restore:_ Quick Restore - Automatically generate Resolved Skeleton JCL using

pre-determined Defaults (see help) and view forSubmit. JCLOUT Dataset Prefix ==> DH01____

_ Set Up Restore - Create JCL using Skeleton Processing Options andview to Save or Optionally Submit





Select Restore Option Panel Options

Field Description

Quick Restore Automatically generates the resolved skeleton JCL using the predetermined defaults so you do not have any options to specify other than to replace an existing data set if one exists, or to bypass the replace. The default for the JCLOUT Dataset Prefix field is the user's defined TSO Prefix. A prefix is required for Quick Restore. You will see the JCL with the supported restore utility commands already resolved. View the restore JCL and submit. Defaults:

JCLOUT DSN = prefix.ASTREST.Ddate.Ttime MEMBEROUT = ASTREST JOBNAMEOUT = ASTREST STEPLIMITOUT = 255 REPLACE = N INCLPHYDUMP = Y

Resolved Skeleton output will be in 1 member using 1 jobname. After selecting Quick Restore, the Resolved Skeleton JCL will be displayed.

Set Up Restore This option creates the 'Build Restore – BLDREST' statements and stores them into a file for you to save or submit. Choosing Set Up Restore takes you to the Set Up RESTORE Panel. This JCL must be submitted in order for the JCLOUT DSN to be populated with the resolved skeleton JCL.




Set Up RESTORE Panel

After selecting Set Up Restore from the Select Restore Option panel, the Set Up RESTORE panel is displayed:

Menu Diagnostics Preferences ----------------------------------------------------------------------------

All/Star - Set Up RESTORECommand ===>

(S) SELECT AN OPTION: Build/View JCL

SKELETON PROCESSING OPTIONS: Skeleton Library ==> 'BRM0601.QABETA.SKELLIB'JCLOUT Dataset ==> 'XYZ.TEST' Alloc JCLOUT Old or New ==> O O or N CopyInclude Location

==> 1 ==>

1-99

Exclude Location ==> Bad Backup Return CodeNew HLQ

==> ==> *

0-9999 Equal to or Greater than

MEMBEROUT name/prefixJOBNAMEOUT name/prefixSteplimit per Job

==> ASTREST1 ==> ASTREST ==> 255 1-255

PER BLDREST STATEMENT: Increment Member name ==> N Y or N Increment Jobname ==> N Y or N Include Physical DumpsInclude BACKVOL

==> Y ==> N

Y or N Y or N

REPLACE Existing DSNsNo Backup Found RCNo Backup Found Status

==> N ==> 8 ==> N

Y or N 0,4,8N -NOBUILD, B -BUILD

RESTORE SUMMARY: DSNs (Include/Exclude)Vols

==> 1 ==> 0

/ 0

Jobs ==> 0 Job StepsJob GroupsApplications

==> 0 ==> 0 ==> 0




Set Up RESTORE Field Descriptions

Field Description

Build/View JCL Select to view created JCL based on parameters specified on this panel.

Skeleton Library Default value is the value assigned to the product PARMLIB, BRMINI token SKELLIB. Use the default or change to a different SKELLIB data set.

JCLOUT Dataset Specify a PDS/PDSE data set name the resolved Skeleton JCL will be stored in.

Alloc JCLOUT Old or New O – identify the specified JCLOUT data set with a Disposition of OLD in the JCL. N – identify the specified JCLOUT data set with a Disposition of NEW in the JCL using the allocation parameters specified in the INI tokens JCLOUT_ALLOC1, JCLOUT_ALLOC2 and JCLOUT_ALLOC3.

Copy Specify the copy number of a multiple copy backup to be used for the restore. Valid values: 1–99.

Include Location Specify one or more fully-qualified tape management location names, or one or more location masks that may be used for restore. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

Exclude Location Specify one or more fully-qualified tape management location names that may not be selected. When used without the Include Location, any location except those that match the Exclude Location can be selected. When used with Include Location, any location that matches the Include Location and does not match the Exclude Location may be selected.

Bad Backup Return Code Specify the return code (nnnn) of the backup jobs All/Star is to consider a bad backup. Any backup job with a return code equal to or higher than the specified RC will be considered bad. Valid values: 0–9999

New HLQ New high level qualifier of the data sets being restored. Depending on how the skeleton is set up, the high level qualifier will either be replaced or appended to the current data set name.




Field Description

MEMBEROUT name/prefix Use the MEMBEROUT field to specify the name(s) of the job JCL members that will be generated. Specify a discrete PDS/PDSE member name, or a mask to be used in generating output member names. A mask specification is required if the Increment Member name field = Y. A member name mask requires at least one ? as a placeholder. If the Increment Member name field = Y, a member name will be generated by substituting an incrementing number in place of the specified ? placeholders. ? placeholders must occupy only the rightmost positions of a member name. For example: Valid – ABCD???? Invalid – ABC?D?

JOBNAMEOUT name/prefix Specify a discrete job name, or a mask to be used in generating output job names. A job name mask requires at least one ? as a placeholder. If multiple job names are required automatically, job names will be generated substituting an incrementing number in place of the specified ? placeholders. ? placeholders must occupy only the rightmost positions of a job name. For example: Valid – ABCD???? Invalid – ABC?D?.

Steplimit per Job The Steplimit per Job field (STEPLIMITOUT) specifies the maximum number of steps per job to be generated in the output job streams. Also see the STEPLIMITOUT Command (page 137). Valid values: 1–255.

Increment Member name (INCRMEMBEROUT)

Y – force the generation of a new output PDS/PDSE member for the next BLDREST encountered. The member name is generated using the mask specified for MEMBEROUT and incrementing the last member name used by 1. N – name specified in the MEMBEROUT field will not be incremented. Also see the INCRMEMBEROUT Command (page 13-6).

Increment Jobname (INCRJOBNAMEOUT)

Y – force the generation of a JOB statement for the next BLDREST encountered. The jobname is generated using the mask specified for JOBNAMEOUT and incrementing the last job name used by 1. N – name specified in the JOBNAMEOUT field will not be incremented. Also see the INCRJOBNAMEOUT Command (page 13-6).

Include Physical Dumps Y – physical dumps are to be included in the restore. (INCLPHYDUMP) N – do not include physical dumps in the restore.

Include BACKVOL (INCLBACKVOL)

Y – The INCLBACKVOL parameter will be added to the JCL, which will allow BACKVOL data sets to be restored. N – The INCLBACKVOL parameter will not be added to the JCL, which will not allow BACKVOL data sets to be restored.




Field Description

REPLACE Existing DSNs Y – delete the existing (cataloged) data set and REPLACE it with the data set to recover. N – data sets to recover that already exist (cataloged) will not be replaced.

No Backup Found RC Specify the desired return code if a matching data set that was included has no backup. Valid values: 0, 4, 8.

No Backup Found Status B – build the JCL if a matching data set that was included has no backup. N – do not build the JCL if a matching data set that was included has no backup.

4.3 Jobs Option – Sub-Option 4 – Initial Selection The first time you select sub-option 4, Jobs, from the Backup and Recovery Management menu, the Jobname List Search Setup panel is displayed. Use this panel to display information on your jobname backups.

If you want to skip the Search Setup panel from now on, select the field 'Don't show this panel again'. The current search criteria will become your default criteria, and the Jobname List panel will be displayed directly.

ALL/STAR - Jobname List Search SetupBRM523A Command ===> _________________________________________________________

Specify the criteria to use when searching for Jobnames.Jobname or Mask ===> *_______ Auto Expand List ===> N Y or N Job Date ===> __________ *-nnn -(nnn = days) or

Date (Format YYYY/MM/DD,MM/DD/YYYY)RC (BKP/AST) ===> ___ / ___ n , <n , >n , W -(RC=4), E -(RC>=8)Sort list by ===> J J -Job, D -Date, E -Errors






Jobname List Search Setup Panel – Field Descriptions

Field Description

Jobname or Mask Enter a jobname or mask for the jobname whose backup events you want to search for. Can be up to eight characters in length. Any of the ACS masking characters can be used to search for a jobname. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). Default: *

Auto Expand List Expand/shrink entire event list.

Job Date Specify a date criteria or exact date to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • If the Date field is left blank, all dates are displayed. • In the following examples, n = 1–999.

*-n – displays only events equal to n relative days from today. Example: '*-4' displays only events four days from today. *=n – displays all events equal to today through n relative days from today. Example: '*=4' displays events starting today through four days from today. *+n – displays all gen 0 events equal to today through n relative days from today. All generations of each event are displayed regardless of date. Example: '*+4' displays all gen 0 events from today through four days from today with each of their subsequent generations regardless of date.

RC (BKP/AST) Display All/Star return codes. • Specify E to display all All/Star events that ended with return

code 8 or greater (Error messages). • Specify W to display all All/Star events that ended with return

code 4 (Warning messages). • Specify an RC between 0 and 999 to display specific All/Star

return codes. Example: '0' – displays only events with RC=0.

'4' – displays only events with RC=4. • Specify a range of ABARS return codes:

Example: '<4' – displays all events with RC less than four. '>4' – displays all events with RC more than four.

Sort list by Sort list by Name, Date, Errors, or Space. Valid options are: J = Job, D = Date, E = Errors

Store values to be used as default Select this field with a '/' to store the jobname or mask as entered for this USERID on this panel. If selected, the next time the Jobname List Search

Setup panel is displayed for your userid, the Name or Mask field, and all other fields will contain the values last entered here. To view/change this panel after it has been stored, key an 'S' or '?' under the 'C' field on the Jobname List panel.



------------------------------------------------------------------------------


Field Description

Don't show this panel again Select this field with a '/' to skip the Jobname List Search Setup panel and go directly to the Jobname List panel when you select sub-option 4 from the Backup and Recovery Management menu. To 'undo' this choice, when the Jobname List panel is displayed, tab twice to the field just below the ‘C’ and key an ‘S’ or a ‘?’. This returns you to the Setup panel where you can remove the ‘/’.

4.4 About the Jobname List Panel The Jobname List panel will display all events found in the BRM Inventory Data Set that match the search criteria you specified on the Jobname List Search Setup panel.


ALL/STAR Jobname List Row 1 to 12 of 39 Command ===> Scroll ===> CSR

Primary Cmds: REFresh,H,SD,SE,SJ Date => 2004/07/06 13:02Line Cmds: GL,N,R,S,+,- Sort => J D,E,J

C Jobname +- RC RCB Date Time * - Gen

ADDB2001 + 0 0 0 2004/07/06 07:30:02ADSCD001 + 0 0 0 2004/07/06 07:34:19ADTSO001 0 0 0 2001/08/23 13:11:46ADTSO002 0 0 0 2001/08/23 13:18:32ASTBJ010 + 0 0 0 2004/06/22 10:36:05ASTBJ011 + 0 0 0 2004/06/22 10:50:37

Jobname List Panel – Primary Command Descriptions


REFresh Refreshes the jobname list displayed.

H Takes you to the History panel.

SD Changes the sort value to 'D' and sorts by date.

SE Changes the sort value to 'E' and sorts by errors by date.

SJ Changes the sort value to 'J' and sorts by jobname.




Jobname List Panel – Line Command Descriptions


GL Displays all job group names currently tracking this jobname.

N List data set names backed up. If more than one step of the job was a tracked AST backup, then all data sets for all steps are displayed.

R Create restore JCL for selected jobname. See 'Line Command R – All/Star Restore' on page 4-9 for more information on All/Star Restore.

S Select to view backup detail. If more than one step of the job was a tracked AST backup, the Jobname Detail panel is displayed. See the 'Jobname Detail Panel' (page 4-19).

+/- Expand/Shrink entire list.

Jobname List Panel – Field Descriptions

Field Description

C Enter 'S' or '?' under the 'C' field to display the Jobname List Search Setup panel.

Jobname Jobname or mask of backup(s) to display.

+- Expand/Shrink entire list.

Gen Relative generation of jobname.

RC Specify an RC between 0 and 999 to display Jobname Return Codes.

Examples: 0 – show only jobs with RC = 0 4 – show only jobs with RC = 4 <4 – show only jobs with RC < 4 >4 – show only jobs with RC > 4 W – show only jobs with RC = 4 E – show only jobs with RC >= 8

If the RC is prefixed with '*', then the return code was estimated based on the ending status since no return code could be found in the database.

RCB Specify an RC between 0 and 999 to display BRM Return Codes. Examples: 0 – show only jobs with RC = 0 4 – show only jobs with RC = 4 <4 – show only jobs with RC < 4 >4 – show only jobs with RC > 4 W – show only jobs with RC = 4 E – show only jobs with RC >= 8

If the RCB is prefixed with '*', then the return code was estimated based on the ending status since no return code could be found in the database.



-------------------------------------------------------------------------------


Field Description

Date Date searches are done against the most current Gen only. Valid options

* for today only *-1 for today and yesterday only *-nnn for today up to 999 days ago

Date can also be in format YYYY/MM/DD or MM/DD/YYYY. In this case, only jobnames matching that date will be displayed. If the date field is left blank, all dates are displayed.

Time No input required. Displays the time of the event.

4.4.1 Line Command S – View Backup Detail Panel When viewing jobs from the Jobname List panel, if a job is selected (S), the View Backup Detail panel is displayed:

ALL/STAR View Backup Detail Row 1 to 1 of 1 Command ===> Scroll ===> CSR

Jobname => ASTBJ010 Stepname/Task => STEP01 / 1Procname => N/ARC ( DSS /AST) => 0 / 0

Date/Time => 2004/06/22 10:36:05Type => DSS Full Volume Dump

Volume Name => TSTN00 (-2)

Output File: BRMX.AST.IVP.J010.NOBACKUP.DUMP1 NOBKP1 ******************************* Bottom of data ********************************



--------------------------------------------------------------------------------


4.4.2 Jobname Detail Panel When viewing jobs from the Jobname List panel, if a job is selected (S) and there are multiple backup steps for that job, the Jobname Detail panel is displayed:

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM523B All/Star - Jobname Detail Row 1 of 2 Command ===> ________________________________________________ Scroll ===> PAGE

Primary Cmds: REFresh Jobname ==> ASTBJ140 Line Cmds: N,R,S Date/Time ==> 2004/06/10 10:17:43

C Stepname Procstep Task Id PGM Type RC RCB Total DSNs

__ STEP1 1 IDC REP 1 0 1 __ STEP1B 1 IDC EXP 0 0 1 ******************************* Bottom of data ********************************

Jobname Detail Panel – Primary Command Descriptions


REFresh Refreshes the Jobname Detail panel.

Jobname Detail Panel – Line Command Descriptions


N List data set names backed up.

R Create restore JCL for selected jobname/step.

S Select to view backup detail.




4.5 Job Groups – Sub-Option 5 – Initial Selection The first time you select sub-option 5, Job Groups, from the Backup and Recovery Management menu, the Job Group List Search Setup panel is displayed. Use this panel to add or display job groups.

If you want to skip the Search Setup panel from now on, select the field 'Don't show this panel again'. The current search criteria will become your default criteria, and the Job Group List panel will be displayed directly.

Job groups may be optionally created to associate a group of backup jobs to a group name.

ALL/STAR - Job Group List Search SetupBRM524A Command ===> _________________________________________________________

Specify the criteria to use when searching for selected Job Groups.

Add NEW Job Group ===> N Y or N - OR -Search for ExistingJob Group Name or Mask ===> *_______



Job Group List Search Setup Panel – Field Descriptions

Field Description

Add NEW Job Group Specify Y or N to add a new job group to All/Star. Job groups may be optionally created to associate a group of backup jobs to a group name.

Search for Existing Job Group Name or Mask

Specify the job group name or mask to search for and display. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

Store values to be used as Select this field with a '/' to store the job group name or mask as default for this USERID entered on this panel. If selected, the next time the Job Group

List Search Setup panel is displayed for your userid, the Name or Mask field, and all other fields will contain the values last entered here. To view/change this panel after it has been stored, key an 'S' or '?' under the 'C' field on the Job Group List Search Setup panel.

Don't show this panel again Select this field with a '/' to skip the Job Group List Search Setup panel and go directly to the Job Group List panel when you select sub-option 5 from the Backup and Recovery Management menu.




4.6 About the Job Group List Panel The Job Group List panel will display all job groups found in the BRM Inventory Data Set that match the search criteria you specified on the Job Groups List Search Setup panel.


ALL/STAR Job Group List Row 1 to 4 of 4 Command ===> Scroll ===> CSR

Primary Cmds: REFresh, ADD, NOJOBGRP Date => 2004/07/06 13:56Line Cmds: D,E,R,S

C Job Group Description*

------------------------------------------------------------------------------- _ AUTODUMP HSM AUTO DUMPS _ TEST TEST ******************************* Bottom of data *******************************

Job Group List Panel – Primary Command Descriptions


REFresh Refreshes the display of Job Groups.

ADD Add a new job group. Displays the Create Job Group panel. For more information on this command, see the topic 'Add a Job Group' (page 4-22).

NOJOBGRP Displays the Jobname List Not Tracked by ANY Job Group panel.

Job Group List Panel – Line Command Descriptions


D Delete a job group.

E Edit a selected job group. See the Add Jobname or Mask to Job Group panel (page 4-23).

R Perform a RESTORE of the job group. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore.

S Display the Jobnames by Job Group panel. See 'About the Jobname List Panel' (page 4-16) for more information on that panel.



-------------------------------------------------------------------------------


Job Group List Panel – Field Descriptions

Field Description

C Enter 'S' or '?' under the 'C' field to display the Job Group List Search Setup panel.

Job Group Enter a name or mask for the job groups you want to search for. Can be up to eight characters in length. Any of the ACS masking characters can be used to search for an aggregate name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). Default: '*' for all job groups.

Description Description of the job group as specified on the Add Jobname to Job Group panel.

4.6.1 Add a Job Group On the Job Group List panel, specify Primary Command ADD to add a new job group.

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5240 ALL/STAR - Job Group ListCommand ===> ADD_____________________________________________ Scroll ===> PAGE

Primary Cmds: REFresh, ADD, NOJOBGRP Date => 2004/05/24 11:14Line Cmds: D,E,R,S

C Job Group Description_ *_______

_ AUTODUMP HSM AUTO DUMPS _ TEST TEST ******************************* Bottom of data *******************************

After specifying 'ADD' on the command line and pressing Enter, the Create Job Group panel is displayed:

Create Job GroupBRM515C Enter a Job Group name to create.

Note: A Job Group name cannotcontain spaces or masking characters

Specify Job Group name:===> payroll___ (Up to 8 Characters)

ENTER=Continue PF3/PF15=Cancel



--------------------------------------------------------------------------------


Specify a job group name up to 8 characters on the Create Job Group panel. No ACS masking characters or spaces are allowed in the job group name. The job group specified must not currently exist.

Entering a new job group name on the Create Job Group panel, or selecting the job group with line command E on the Job Group List panel, will display the Add Jobname or Mask to Job Group panel.

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM515B ALL/STAR Add Jobname or Mask to Job Group Row 1 of 2 Command ===> ________________________________________________ Scroll ===> PAGE

Primary Commands: END(PF3)/SAVE - to Save record and return CAN - to Return without SavingNOTBYTHIS(NBT) - List All Jobs not Tracked by THIS Job GroupNOJOBGRP (NJB) - List All Jobs not Tracked by ANY Job Group


Job Group Name: PAYROLL Job Group Description: ____________________________________________________

C Job Name/Mask

_ A*______ _ ________ ******************************* Bottom of data *******************************

Add Jobname or Mask to Job Group List Panel – Primary Command Descriptions


END(PF3)/SAVE Press End (PF3), or type SAVE on the command line and press Enter to save the jobnames specified in the Jobname/Mask column for the displayed job group.

CAN Type CAN on the command line to cancel and return to the Create Job Group panel.

NOTBYTHIS (NBT) Lists all jobs not tracked by this job group. Displays the Display Jobname or Mask panel.

NOJOBGRP (NJB) Lists all jobs not tracked by any job group. Displays the Jobname List Not Tracked by a Job Group panel.

Add Jobname or Mask to Job Group List Panel – Line Command Descriptions


D Deletes a jobname/mask entry.

I Inserts a blank line.

R Repeats a jobname/entry.



-------------------------------------------------------------------------------


4.6.2 Primary Command NOTBYTHIS – Jobname List Not Tracked by This Job Group If Primary Command NOTBYTHIS is entered on the Job Group List panel, the Display Jobname or Mask panel is displayed.

ALL/STAR - Display Jobname or MaskCommand ===> _____________________________________________________

The Job list may be quite large. Specify a job name or mask tolimit the amount of jobs displayed or specify * for all.

Job Name or Mask ===> pay*_______


Specify a jobname or mask to filter the display of Jobnames Not Tracked by this Job Group. After specifying a jobname or mask, press Enter and the Jobname List Not Tracked by This Job Group panel is displayed:

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM515D ALL/STAR Jobname List Not Tracked by ANY Job Group Row 1 to 2 of 2 Command ===> ________________________________________________ Scroll ===> PAGE

Primary Cmds: S maskLine Cmds: S

Only the most recent execution is displayed.Jobname RC RCB Date Time *_______

_ PAYBJ010 0 0 2004/06/10 10:12:09_ PAYBJ011 8 0 2004/06/10 10:12:42_ PAYBJ020 0 0 2004/06/10 10:13:32

From this panel, jobs can be selected to be added to the current job group you are editing/adding. After all required jobnames have been selected, press PF3(End) to add them to the currently displayed job group. Although jobnames have been added to the job group list, the job group must be saved to update the list.

Jobname List Not Tracked by THIS Job Group Panel – Primary Command Descriptions

S mask


Select jobname or mask to be added to the current Job Group.

Jobname List Not Tracked by THIS Job Group Panel – Line Command Descriptions

S


Select a jobname to add to the Job Group.



-------------------------------------------------------------------------------


4.6.3 Primary Command NOJOBGRP – Jobname List Not Tracked by ANY Job Group If Primary Command NOJOBGRP is entered on the Job Group List panel, the Display Jobname or Mask panel is displayed.

BRM515F ALL/STAR - Display Jobname or MaskCommand ===> _____________________________________________________

The Job list may be quite large. Specify a job name or mask tolimit the amount of jobs displayed or specify * for all.

Job Name or Mask ===> ________


Specify a jobname or mask to filter the display of Jobnames Not Tracked by ANY Job Group. After specifying a jobname or mask, press Enter and the Jobname List Not Tracked by ANY Job Group panel is displayed:

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM515E ALL/STAR - Jobname List Not Tracked by ANY Job Group Row 1 of 3 Command ===> ________________________________________________ Scroll ===> PAGE

Primary Cmds: S maskLine Cmds: S

Only the most recent execution is displayed.Jobname RC RCB Date Time *_______

_ ASTBJ010 0 0 2004/06/10 10:12:09_ ASTBJ011 8 0 2004/06/10 10:12:42_ ASTBJ020 0 0 2004/06/10 10:13:32

From this panel, jobs can be selected to be added to the current job group you are editing/adding. After all required jobnames have been selected, press PF3(End) to add them to the currently displayed job group. Although jobnames have been added to the Job Group list, the job group must be saved to update the list.

Jobname List Not Tracked by ANY Job Group Panel – Primary Command Descriptions

S mask


Select jobname or mask to be added to the current Job Group.

Jobname List Not Tracked by ANY Job Group Panel – Line Command Descriptions

S


Select a jobname to add to the Job Group.




4.7 Applications – Sub-Option 6 – Initial Selection The first time you select sub-option 6, Applications, from the Backup and Recovery Management menu, the Application List Search Setup panel is displayed. This panel will only be used if you are licensed for both ASAP and All/Star. Use this panel to find applications created from the BKUPEND process. For more information, see Chapter 12, All/Star: Application Backup and Restore.

If you want to skip the Search Setup panel from now on, select the field 'Don't show this panel again'. The current search criteria will become your default criteria, and the Application List panel will be displayed directly.

ALL/STAR - Application List Search SetupBRM524A Command ===> _________________________________________________________

Specify the criteria to use when searching for Backup-End Events.Application Name or Mask ===> *Auto Expand List ===> N Y or N

Enter "/" to select optionStore values to be used as default for this USERID Don't show this panel again


Application List Search Setup Panel – Field Descriptions

Field Description

Application Name or Mask Specify the application name or mask to search for and display. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

Store values to be used as Select this field with a '/' to store the application name or mask as default for this USERID entered on this panel. If selected, the next time the Application

List Search Setup panel is displayed for your userid, and the Name or Mask field. To view/change this panel after it has been stored, key an 'S' or '?' under the 'C' field on the Application List panel.

Don't show this panel again Select this field with a '/' to skip the Application List Search Setup panel and go directly to the Application List panel when you select sub-option 6 from the Backup and Recovery Management menu.



-------------------------------------------------------------------------------


4.8 About the Application List Panel The Application List panel will display all applications found in the BRM Suite Inventory Data Set that match the search criteria you specified on the Application List Search Setup panel.


All/Star Application List Row 1 to 5 of 5 Command ===> Scroll ===> CSR

Primary Commands: REFreshLine Commands: +,-,D,N,R

C APPL +- Cycle BKUPEND BKUPEND ASAP * - Date Time Cycle #

BKTEST01 0 2005/04/28 10:30:44 9 BDLY 0 2005/04/27 09:05:13 2 BTCHSMF1 0 2005/04/25 22:18:54 1 DDLY 0 2005/04/27 11:33:49 2 KYTSX 0 2005/04/27 09:05:30 8

******************************* Bottom of data *******************************

Application List Panel – Primary Command Descriptions


REFresh Refreshes the display of Job Groups.

Application List Panel – Line Command Descriptions


D Delete an application.

N List dataset names from the ASAP application and their associated backups as determined at Backup End time.

R Perform a RESTORE of the application. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore.




Application List Panel – Field Descriptions

Field Description

C Enter 'S' or '?' under the 'C' field to display the Application List Search Setup panel.

APPL Enter a name or mask for the job applications you want to search for. Can be up to eight characters in length. Any of the ACS masking characters can be used to search for an aggregate name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). Default: '*' for all job applications.

Cycle Displays the relative cycle number.

BKUPEND Date and Time Displays Date/Time Backup End occurred.

ASAP Cycle # Absolute ASAP Cycle number.




Chapter 5 5 BRM Suite: Features – Option 4

Features is Option 4 on the Main Menu. Selecting this option takes you to a sub-menu of selectable features, which are separately licensed.





X Exit


When you select Option 4 from the Main Menu you will see the BRM – Features panel. CATSCRUB is sub-option 1, the first of many features to be offered.


BRM - Features Command ==>


1 CATSCRUB

Mainstar Software Corporation ©2006 5-1 Chapter 5 SC23-6061-00 BRM Suite: Features – Option 4



5.1 CATSCRUB – Sub-Option 1 CATSCRUB (sub-option 1) helps you to build a CATSCRUB command. For detailed information about the CATSCRUB command, refer to the topic 'CATSCRUB Command Parameter Definitions' (page 15-6).

The Submit CATSCRUB panel is displayed, where you build the CATSCRUB command.

Note: For information on how to protect use of the CATSCRUB command, see Appendix A, Authority Requirements, of the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062).


BRM - Submit CATSCRUB Command ===>

(S) SELECT AN OPTION: Build JCL/Edit for Submit

More: + Required keywords:(S) Selected List

SIMULATE => No catalog(s) selected=> Y Y or N (Execute)

Optional keywords:EXCLUDE-BCS(..)EXCLUDE-KEEP-DSN

=> N => N

Y or N Y or N

EXCLUDE-KEEP-TAPE => N Y or N EXCLUDE-KEEP-VOLSER => N Y or N EXCLUDE-MATCH-VOLSER => N Y or N KEEP-DSN => N Y or N KEEP-TAPE => N Y or N KEEP-VOLSER => N Y or N MATCH-VOLSER => N Y or N MESSAGE-TEXT => F A(bbreviated) or F(ull)

Anomalies:

FATAL-CATALOG-ERR:

D(elete) orK(eep)

Return Code

C(ontinue)or E(nd)

E GDGBASE-NO-ACTIVE-GENS: K 4 C GDS-MIGRATED: K 4 C GDS-MIGRATED-DASD: GDS-MIGRATED-TAPE: GDS-MULTI-VOL-ERR: K 4 C GDS-NOT-FOUND: K 4 C GDS-TAPE: K 4 C NONVSAM-ALIAS-NO-REALNAME: K 4 C NONVSAM-MIGRATED: K 4 C NONVSAM-MIGRATED-DASD NONVSAM-MIGRATED-TAPE NONVSAM-MULTI-VOL-ERR: K 4 C NONVSAM-NOT-FOUND: K 4 C NONVSAM-TAPE: K 4 C OBJECT-ACCESS-METHOD: K 4 C VSAM-SPHERE-MIGRATED: K 4 C VSAM-SPHERE-MIGRATED-DASD: VSAM-SPHERE-MIGRATED-TAPE: VSAM-SPHERE-MULTI-VOL-ERR: K 4 C VSAM-SPHERE-NOT-FOUND: K 4 C

Chapter 5 5-2 Mainstar Software Corporation ©2006 BRM Suite: Features – Option 4 SC23-6061-00



Submit CATSCRUB Panel – Field Descriptions

CATSCRUB Field Description

(S) SELECT AN OPTION Build JCL/Edit for Submit

Build JCL/Edit for Submit controls whether you wish to just validate the other data in the dialog, or validate the data and create the JCL. Key S(elect) to generate the JCL based on the dialog data you choose on the panel. You will then have an opportunity to edit before submission.

Required keywords: (S) Selected List Enter an S to s(elect) from a pop-up list of BCSs connected to the

current master catalog. You may select one or more BCSs from the list. When you the pop-up dialog is dismissed, "No catalog(s) selected" will be replaced by the number of catalogs selected. For example: "3 Catalog(s) selected". If an 'S' is not entered, the required keyword will be generated in the JCL; however, no arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time.

SIMULATE N(o) is the default, which implies EXECUTE. CATSCRUB will be submitted. Y(es) will generate the required keyword in the JCL, permitting you to trial the CATSCRUB without having the process actually performed.

Optional keywords: EXCLUDE-BCS( . . ) N(o) is the default.

When Y(es) is specified, EXCLUDE-BCS will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. Your argument may be coded as data set names or masks. You may specify a mask as a value for the BCS name, and then selectively exclude unwanted catalogs from the list of catalogs that match your mask. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified. Only BCSs that have been selected by your mask may then be effectively excluded. A SIMULATE mode of execution will show which catalogs would be processed by an actual execution.

EXCLUDE-KEEP-DSN N(o) is the default. When Y(es) is specified, the EXCLUDE-KEEP-DSN field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. EXCLUDE-KEEP-DSN works in conjunction with the KEEP-DSN keyword. EXCLUDE-KEEP-DSN specifies one or more data set names or masks that are to be excluded from the list of data set names as specified by the KEEP-DSN keyword. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified. The EXCLUDE-KEEP-DSN will be




CATSCRUB Field Description processed after KEEP-DSN.

EXCLUDE-KEEP-TAPE N(o) is the default. When Y(es) is specified, the EXCLUDE-KEEP-TAPE field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. EXCLUDE-KEEP-TAPE works in conjunction with the KEEPTAPE keyword. EXCLUDE-KEEP-TAPE specifies one or more tape serial numbers or masks that are to be excluded from the list of serial numbers as specified by the KEEP-TAPE keyword. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified. The EXCLUDE-KEEP-TAPE will be processed after KEEP-TAPE.

EXCLUDE-KEEP-VOLSER N(o) is the default. When Y(es) is specified, the EXCLUDE-KEEP-VOLSER field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. EXCLUDE-KEEP-VOLSER works in conjunction with the KEEPVOLSER keyword. EXCLUDE-KEEP-VOLSER specifies one or more disk serial numbers or masks that are to be excluded from the list of serial numbers as specified by the KEEP-VOLSER keyword. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified. The EXCLUDE-KEEP-VOLSER will be processed after KEEPVOLSER.

EXCLUDE-MATCH-VOLSER N(o) is the default. When Y(es) is specified, the EXCLUDE-MATCH-VOLSER field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. EXCLUDE-MATCH-VOLSER works in conjunction with the MATCH-VOLSER keyword. MATCH-VOLSER will specify those volumes to be synchronized with the catalog(s). This feature can be very useful when testing the DR process in SIMULATE mode before moving to the DR site. EXCLUDE-MATCH-VOLSER specifies one or more disk serial numbers or masks that are to be excluded from the list of serial numbers as specified by the MATCH-VOLSER keyword. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified. The EXCLUDE-MATCH-VOLSER will be processed after MATCH-VOLSER.

KEEP-DSN N(o) is the default. When Y(es) is specified, the KEEP-DSN field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. KEEP-DSN works in conjunction with the EXCLUDE-KEEP-DSN keyword, if specified. KEEP-DSN specifies one or more data set names or masks that are to be excluded from CATSCRUB delete




CATSCRUB Field Description processing. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified.

KEEP-TAPE N(o) is the default. When Y(es) is specified, the KEEP-TAPE field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. KEEP-TAPE works in conjunction with the EXCLUDE-KEEP-TAPE keyword, if specified. KEEP-TAPE specifies one or more tape serial numbers or masks that are to be excluded from NONVSAM-TAPE(DELETE) and GDS-TAPE(DELETE) processing. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified.

KEEP-VOLSER N(o) is the default. When Y(es) is specified, the KEEP-VOLSER field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time. KEEP-VOLSER works in conjunction with the EXCLUDE-KEEP-VOLSER keyword, if specified. KEEP-VOLSER specifies one or more disk serial numbers or masks that are to be excluded from the delete processing of the disk-oriented anomalies. Standard mask characters as well as the extended Mainstar ACS mask characters may be specified.

MATCH-VOLSER N(o) is the default. When Y(es) is specified, the MATCH-VOLSER field will generate the required keyword in the JCL; however, no keyword arguments will be generated. Instead, when the JCL is shown for Edit/Submission, you will be able to add argument(s) at that time MATCH-VOLSER will specify those volumes to be synchronized with the catalog(s). This feature can be very useful when testing the DR process in SIMULATE mode before moving to the DR site.

MESSAGE-TEXT The MESSAGE-TEXT field controls the volume of IDCAMS messages printed during the execution of CATSCRUB. One of the following values must be entered: F(ull) (the default) provides a complete process log of all actions taken by the CATSCRUB command, indicating the name of every object processed. A(bbreviated) only a summary report is provided.

The fields below describe the anomaly keywords. The anomalies will control CATSCRUB processing of input catalogs when specific conditions are encountered. Each anomaly, with one exception, provides the following: • DISPOSITION - What is to be done with the catalog entry if it meets the condition. Either DELETE the

catalog entry, or KEEP it. • RETURN CODE - What return code CATSCRUB is to terminate with should a catalog entry meet the

condition. • ACTION - Should CATSCRUB CONTINUE or END if an entry meets the condition. The anomaly, FATAL-CATALOG-ERROR, only supports an ACTION.




CATSCRUB Field Description

FATAL-CATALOG-ERR This anomaly controls CATSCRUB processing when a fatal error occurs when processing a catalog. The default ACTION is to END CATSCRUB processing. Circumvention is to EXCLUDE-BCS those catalogs causing fatal errors. The following BRMINI token in the CATSCRUB_OPTIONS section will control the initial dialog setting for this anomaly: Token: FATAL_CATALOG_ERR_PROC

GDGBASE-NO-ACTIVE-GENS This anomaly controls CATSCRUB processing when the GAT (Generation Aging Table) within a GDG record indicates that there are no GDS associated with the GDG. This may occur either "naturally" or because CATSCRUB "emptied" the GAT as a result of other CATSCRUB processing. The default DISPOSITION is to DELETE the GDG entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: GDGBASE_NO_ACTIVE_GENS_DISP

GDGBASE_NO_ACTIVE_GENS_RC GDGBASE_NO_ACTIVE_GENS_PROC

GDS-MIGRATED This anomaly controls CATSCRUB processing when an individual GDS sub-record indicates that the entry is in migrated status. This anomaly is incompatible with GDS-MIGRATED-DASD and GDS-MIGRATED-TAPE. Care should be taken if DELETE is specified for the DISPOSITION, as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. The default DISPOSITION is to KEEP the GDS entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: GDS_MIGRATED_DISP

GDS_MIGRATED_RC GDS_MIGRATED_PROC

GDS-MIGRATED-DASD This anomaly controls CATSCRUB processing when an individual GDS sub-record indicates that the entry is in migrated status where the device type is disk. This anomaly is incompatible with GDS-MIGRATED. If this anomaly is specified, GDS-MIGRATED-TAPE must also be specified. Care should be taken if DELETE is specified for the DISPOSITION as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. The default DISPOSITION is to KEEP the GDS entry.




CATSCRUB Field Description The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

GDS-MIGRATED-TAPE This anomaly controls CATSCRUB processing when an individual GDS sub-record indicates that the entry is in migrated status where the device type is tape. This anomaly is incompatible with GDS-MIGRATED. If this anomaly is specified, GDS-MIGRATED-DASD must also be specified. Care should be taken if DELETE is specified for the DISPOSITION as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. The default DISPOSITION is to KEEP the GDS entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

GDS-MULTI-VOL-ERR This anomaly controls CATSCRUB processing when an individual GDS sub-record indicates that, for an active multivolume generation, one or more of the referenced volumes is not being processed by CATSCRUB. Care should be taken if DELETE is specified for the DISPOSITION as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. This keyword will be applied to those entries having a volume cell matching a volser in the MATCH-VOLSER list. The default DISPOSITION is to KEEP the GDS entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: GDS_MULTI_VOL_ERR_DISP

GDS_MULTI_VOL_ERR_RC GDS_MULTI_VOL_ERR_PROC

GDS-NOT-FOUND This anomaly controls CATSCRUB processing when an individual GDS sub-record does not physically exist on any of the volumes being processed by the CATSCRUB command. Care should be taken if DELETE is specified for the DISPOSITION as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. The default DISPOSITION is to KEEP the GDS entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: GDS_NOT_FOUND_DISP

GDS_NOT_FOUND_RC GDS_NOT_FOUND_PROC

GDS-TAPE This anomaly controls CATSCRUB processing when an individual GDS sub-record is tape resident. Care should be




CATSCRUB Field Description taken if DELETE is specified for the DISPOSITION as this will affect the number of entries within the GAT and, potentially, produce an unintended result when a relative generation number is specified in the JCL. The default DISPOSITION is to KEEP the GDS entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: GDS_TAPE_DISP

GDS_TAPE_RC GDS_TAPE_PROC

NONVSAM-ALIAS-NO-REALNAME This anomaly controls CATSCRUB processing of the alias entry for a non-VSAM object where the true-name is not found within the volumes being processed by the CATSCRUB command. The default DISPOSITION is to KEEP the Alias entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: NONVSAM_ALIAS_NO_REALNAME_DISP

NONVSAM_ALIAS_NO_REALNAME_RC NONVSAM_ALIAS_NO_REALNAME_PROC

NONVSAM-MIGRATED This anomaly controls CATSCRUB processing when the entry for a non-VSAM data set indicates that the entry is in migrated status. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). This anomaly is incompatible with NONVSAM-MIGRATED-DASD and NONVSAM-MIGRATED-TAPE. The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: NONVSAM_MIGRATED_DISP

NONVSAM_MIGRATED_RC NONVSAM_MIGRATED_PROC K, 4, C

NONVSAM-MIGRATED-DASD This anomaly controls CATSCRUB processing when the entry for a non-VSAM data set indicates that the entry is in migrated status where the device type is disk. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). This anomaly is incompatible with NONVSAM-MIGRATED. If this anomaly is specified, NONVSAM-MIGRATED-TAPE must also be specified. The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

NONVSAM-MIGRATED-TAPE This anomaly controls CATSCRUB processing when the entry for




CATSCRUB Field Description a non-VSAM data set indicates that the entry is in migrated status where the device type is tape. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). This anomaly is incompatible with NONVSAM-MIGRATED. If this anomaly is specified, NONVSAM-MIGRATED-DASD must also be specified. The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

NONVSAM-MULTI-VOL-ERR This anomaly controls CATSCRUB processing when the entry for a non-VSAM data set indicates that, for an active multi-volume generation, one or more of the referenced volumes is not being processed by CATSCRUB. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). This keyword will be applied to those entries having a volume cell matching a volser in the MATCH-VOLSER list. The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: NONVSAM_MULTI_VOL_ERR_DISP

NONVSAM_MULTI_VOL_ERR_RC NONVSAM_MULTI_VOL_ERR_PROC

NONVSAM-NOT-FOUND This anomaly controls CATSCRUB processing when a non-VSAM data set does not physically exist on any of the volumes being processed by the CATSCRUB command, and the NONVSAM-MIGRATE, NONVSAM-MULTI-VOL-ERR and NONVSAM-TAPE conditions do not apply. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: NONVSAM_NOT_FOUND_DISP

NONVSAM_NOT_FOUND_RC NONVSAM_NOT_FOUND_PROC

NONVSAM-TAPE This anomaly controls CATSCRUB processing when a non-VSAM data set is determined to be tape resident. Note that this controls only "A" records (standard non-VSAM objects), not GDS (Generation Data Sets). The default DISPOSITION is to KEEP the non-VSAM entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS




CATSCRUB Field Description section will control the initial dialog settings for this anomaly: Token: NONVSAM_TAPE_DISP

NONVSAM_TAPE_RC NONVSAM_TAPE_PROC

OBJECT-ACCESS-METHOD This anomaly controls CATSCRUB processing when an entry using OAM is met. The default DISPOSITION is to KEEP the OAM-using entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: OBJECT_ACCESS_METHOD_DISP

OBJECT_ACCESS_METHOD_RC OBJECT_ACCESS_METHOD_PROC

VSAM-SPHERE-MIGRATED This anomaly controls CATSCRUB processing when a VSAM cluster sphere record indicates that the entry is in migrated status. This anomaly is incompatible with VSAMSPHERE-MIGRATED-DASD and VSAMSPHERE-MIGRATED-TAPE. The default DISPOSITION is to KEEP the cluster entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: VSAMSPHERE_MIGRATED_DISP

VSAMSPHERE_MIGRATED_RC VSAMSPHERE_MIGRATED_PROC

VSAM-SPHERE-MIGRATED-DASD This anomaly controls CATSCRUB processing when a VSAM cluster sphere record indicates that the entry is in migrated status where the device type is disk. This anomaly is incompatible with VSAMSPHERE-MIGRATED. If this anomaly is specified, VSAMSPHERE-MIGRATED-TAPE must also be specified. The default DISPOSITION is to KEEP the VSAM sphere entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

VSAM-SPHERE-MIGRATED-TAPE This anomaly controls CATSCRUB processing when a VSAM cluster sphere record indicates that the entry is in migrated status where the device type is tape. This anomaly is incompatible with VSAMSPHERE-MIGRATED. If this anomaly is specified, VSAMSPHERE-MIGRATED-DASD must also be specified. The default DISPOSITION is to KEEP the VSAM sphere entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing.

VSAM-SPHERE-MULTI-VOL-ERR This anomaly controls CATSCRUB processing when a VSAM cluster sphere record indicates that, for an active multi-volume object, one or more of the referenced volumes is not being




CATSCRUB Field Description processed by CATSCRUB. This keyword will be applied to those entries having a volume cell matching a volser in the MATCH-VOLSER list. The default DISPOSITION is to KEEP the VSAM sphere entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: VSAMSPHERE_MULTI_VOL_ERR_DISP

VSAMSPHERE_MULTI_VOL_ERR_RC VSAMSPHERE_MULTI_VOL_ERR_PROC

VSAM-SPHERE-NOT-FOUND This anomaly controls CATSCRUB processing when a VSAM cluster does not physically exist on any of the volumes being processed by the CATSCRUB command. The default DISPOSITION is to KEEP the VSAM sphere entry. The default RETURN CODE is 4. The default ACTION is to CONTINUE CATSCRUB processing. The following BRMINI tokens in the CATSCRUB_OPTIONS section will control the initial dialog settings for this anomaly: Token: VSAMSPHERE_NOT_FOUND_DISP

VSAMSPHERE_NOT_FOUND_RC VSAMSPHERE_NOT_FOUND_PROC




The Select for CATSCRUB Panel is displayed when you specify 'S' for 'Selected List'. It displays a list of catalogs where you can choose the value(s) for the BCS keyword.

+------------------BRM- Select for CATSCRUB ------------------+ | Row 22 to 30 of 30 || Command ===> Scroll ===> PAGE || || Master Catalog: || Primary Commands: S(elect) mask, C(lear) mask || || C Enter "S" to select Name(s) || ----------------------------------------------------------- || USERCAT.SCD || USERCAT.UCAT1 || USERCAT.UCAT2 || USERCAT.UCAT3 || USERCAT.VCR01 || USERCAT.VCR02 || USERCAT.VCR03 || USERCAT.VCR04 || USERCAT.VIPLD91 || ********************* Bottom of data ********************** || |+-------------------------------------------------------------+




Chapter 6 6 BRM Suite: Search for Data Set – Option 5

6.1 Search for a Specific Data Set Name or Mask Search for Data Set (Option 5) allows you to search all backup events in the BRM Inventory Data Set for a specific data set name or mask. You will see only the data for which you are licensed. If you are licensed for ABARS Manager, you will see only ABARS data. If you are licensed for All/Star, you will see all other z/OS backup utilities. All/Star does not track ABARS backups but will display ABARS data sets only through the data set search panel if you have both products licensed.

Backup & Recovery Manager Suite also allows you to display HSM Incremental or Command Backups, and hrecover them without knowledge of the HSM HRECOVER command.





X Exit


Select Option 5 from the Main Menu to display the Search Selection menu.

Mainstar Software Corporation ©2006 6-1 Chapter 6 SC23-6061-00 BRM Suite: Search for Data Set – Option 5



6.1.1 Search Selection Menu When you select Option 5 from the Main Menu, the Search Selection menu is displayed.

Option 1, Search for Datasets, displays all available generation numbers for each data set. This may be a lengthy process; however, the search is limited to 50,000 data sets.

Option 2, Quick Search, displays only generation 0 for each data set. There is no limit to the number of data sets.

Menu Diagnostics Preferences ---------------------------------------------------------------------

BRM - Search Selection Command ==>


1 Search for Datasets (Displays All Gens - takes longer)2 Quick Search (Displays Gen 0 only for each DSN found)

6.1.2 Search for Data Set Setup Panel – Option 1 The first time you select Option 1, Search for Datasets, from the Search Selection menu, the Search for Dataset Setup panel is displayed. After you enter your search criteria, press Enter. The Search for Dataset panel will be displayed.

If you want to skip the Search for Dataset Setup panel from now on, select the field 'Don't show this panel again.' The current search criteria will become your default criteria, and you will be presented with the Search for Dataset panel directly.

Search for Dataset SetupBRM551A Command ===>

Specify the criteria to use when searching for selected Dataset(s).

DSN or Mask ===> B* Auto Expand ListSort byDisplay:Overlaps OnlyHSM Incrementals

===> N ===> N

===> N ===> N

Y or N N Dataset Name or D Date

Y or N Y or N

Full Volume Dumps ===> N Y or N All/Star Only

Enter "/" to select option/ Store values to be used as default for this USERIDDon't show this panel again


Chapter 6 6-2 Mainstar Software Corporation ©2006 BRM Suite: Search for Data Set – Option 5 SC23-6061-00



Search for Data Set Setup Panel – Field Descriptions

Field Description

DSN or Mask Enter a data set name or mask up to 44 characters. Any of the ACS masking characters can be used to search for a data set name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

Auto Expand List Shrink/Expand data set list.

Sort by Specify N to sort by Data Set Name or D to sort by Date.

Overlaps Only Remove all data sets from the display not containing data set overlaps.

HSM Incrementals Displays HSM Incremental or Command Backup data sets matching the data set name or mask specified. Valid for ABARS Manager and All/Star licensed products. All/Star Only Display Note: DFSMShsm Incremental backups will not have any generations associated with them in any displays or reports because All/Star tracks backups by jobname. DFSMShsm Incremental backups will be displayed in date/time order and can be viewed in relationship to the rest of the data set backups and respectively restored.

Full Volume Dumps Displays Full Volume Dump data sets matching the data set name or mask specified. This will be displayed but is for All/Star only. If you are licensed for All/Star, by default, data sets in full volume dumps are not displayed. It can appear that generation numbers have been skipped when displaying data sets in the Search for Data Set panel but in fact, they are accounted for. They are not displayed because full volume dump data sets are not generally restored at the data set level. This was done to prevent inadvertent restores.

Store values to be used as Default for this USERID

Select this field with a '/' to store the data set name or mask as entered on this panel. If selected, the next time the Search for Data Set panel is displayed for your userid, the Name or Mask field and all other fields will contain the values last entered here. To view/change this panel after it has been stored, enter 'S' or '?' under the 'C' field on the Search for Data Set panel.

Don't show this panel again Select this field with a '/' to skip the Search for Data Set Setup panel and go directly to the Search for Data Set panel when you select Option 5 from the Main Menu. To undo this choice, when the Search For Data Set panel is displayed, tab twice to the field just below the ‘C’ and enter an ‘S’ or a ‘?’. This returns you to the Setup panel where you can remove the ‘/’.



--------------------------------------------------------------------------------


6.1.3 Search for Data Set Panel Once all required fields have been entered on the Search for Data Set Setup panel, press Enter and the Search for Data Set panel will be displayed.

The Search for

be displayed.

Note: When using the Search for Data Set panel, be as specific as you can. Data Set panel calculates each generation number for each data set, which can be a time-consuming process. To prevent extremely long search times, only the first 50,000 data sets will

Use Quick Search if more than 50,000 data sets need to be viewed.

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5510 BRM Search for Dataset Row 1 to 12 of 113 Command ===> Scroll ===> CSR

Primary Commands: REFresh, RESet, R mask, X mask Sort by => N D,NLine Commands: +,-,I,O,R,S Display overlaps only => N Y or N

Display HSM Incr => N Y or N Display Full Vol Dumps => N Y or N

C Dataset Name or Mask +- Gen PGM/Type Date Time O D* - yy/mm/dd

_ DS01.ABARSMGR.JCLPROF _ DS01.ALB.V1R201.JCL _ DS01.ALBTEST.SDS _ DS01.ALBTEST.SDSE _ DS01.ALB00001.SELDSN.EXTRACT

+ 0 DSS FVD 04/06/12 02:30+ 0 DSS FVD 04/06/12 02:30+ 0 DSS FVD 04/06/12 02:30+ 0 DSS FVD 04/06/12 02:30+ 0 DSS FVD 04/06/12 02:30

See the topic 'Identifying Data Set Overlaps' (page 6-10) for an example of a Search for Data Set, and resulting overlaps.




Search for Data Set Panel – Primary Command Descriptions


REFresh Refresh the display.

RESet Reset screen values to default.

R mask Select the data sets specified by the mask for data set restore.

X mask Select the data sets specified by the mask for data set restore exclusion.

Search for Data Set Panel – Line Command Descriptions


I View data set detail as recorded at backup time.

O View data set overlaps by data set.

R Select a data set for Restore. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore.

S View Backup Event Detail.

Search for Data Set Panel – Field Descriptions

Field Description

Display overlaps only Remove all data sets from the display not containing data set overlaps.

Display HSM Incr Displays HSM Incremental or Command Backup data sets matching the data set name or mask specified.

Display Full Vol Dumps Displays Full Volume Dump data sets matching the data set name or mask specified.

Sort by Specify N to sort by data set name or D to sort by date.

C Enter 'S' or '?' under the 'C' field to display the Search for Data Set Setup panel.

Data Set Name or Mask Enter a data set name or mask up to 44 characters. Any of the ACS masking characters can be used to search for a data set name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

+ / - Shrink/Expand list

Gen No input required. Relative generation of data set.

Backup Name No input required. Name of event that backed up the data set.

Date No input required. Date DSN was backed up.

Time No input required. Time DSN was backed up.

O No input required. This column will contain a '*' for DSNs with overlaps.




6.1.4 Quick Search for Data Set Setup Panel – Option 2 The first time you select Option 2, Quick Search, from the Search Selection menu, the Quick Search for Dataset Setup panel is displayed.

If you want to skip the Quick Search for Dataset Setup panel from now on, select the field 'Don't show this panel again.' The current search criteria will become your default criteria, and you will be presented with the Quick Search for Dataset panel directly.

------------------- Quick Search for Dataset Setup -------------------

Command ===>

Specify the criteria to use when searching for selected Dataset(s).

DSN or Mask ===> B*_________________________________________ Display:HSM Incrementals ===> N Y or N Full Volume Dumps ===> N Y or N All/Star Only






Quick Search for Data Set Setup Panel – Field Descriptions

Field Description

DSN or Mask Enter a data set name or mask up to 44 characters. Any of the ACS masking characters can be used to search for a data set name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

HSM Incrementals Displays HSM Incremental or Command Backup data sets matching the data set name or mask specified. Valid for ABARS Manager and All/Star licensed products. All/Star Only Display Note: DFSMShsm Incremental backups will not have any generations associated with them in any displays or reports because All/Star tracks backups by jobname. DFSMShsm Incremental backups will be displayed in date/time order and can be viewed in relationship to the rest of the data set backups and respectively restored.

Full Volume Dumps Displays Full Volume Dump data sets matching the data set name or mask specified. This will be displayed but is for All/Star only. If you are licensed for All/Star, by default, data sets in full volume dumps are not displayed. It can appear that generation numbers have been skipped when displaying data sets in the Quick Search for Data Set panel but in fact, they are accounted for. They are not displayed because full volume dump data sets are not generally restored at the data set level. This was done to prevent inadvertent restores.

Store values to be used as Default for this USERID

Select this field with a '/' to store the data set name or mask as entered on this panel. If selected, the next time the Quick Search for Data Set panel is displayed for your userid, the Name or Mask field and all other fields will contain the values last entered here. To view/change this panel after it has been stored, enter 'S' or '?' under the 'C' field on the Quick Search for Data Set panel.

Don't show this panel again Select this field with a '/' to skip the Quick Search for Data Set Setup panel and go directly to the Quick Search for Data Set panel when you select Option 5.2 from the Main Menu. To undo this choice, when the Quick Search For Data Set panel is displayed, tab twice to the field just below the ‘C’ and enter an ‘S’ or a ‘?’. This returns you to the Setup panel where you can remove the ‘/’.



--------------------------------------------------------------------------------


6.1.5 Quick Search for Data Set Panel Once all required fields have been entered on the Quick Search for Data Set Setup panel, press Enter and the Quick Search for Data Set panel will be displayed.


BRM - Quick Search for Dataset Row 1 to 31 of 3636 Command ===> Scroll ===> PAGE

Primary Commands: REFresh, RESet Display HSM Incr => N Y or N Line Commands: I,L,O,R,S Display Full Vol Dumps => N Y or N

C Dataset Name or Mask Jobname PGM/Type Date Time B*__________________________________________ yy/mm/dd

BACKUP.ARCHV1.G1112V00 CA1 ABACKUP 05/03/07 12:53BACKUP.ARCHV1.G1113V00 CA1 ABACKUP 05/03/07 12:53BACKUP.ARCHV1.G1114V00 CA1 ABACKUP 05/03/07 12:53BACKUP.ARCHV1.G1115V00 CA1 ABACKUP 05/03/07 12:53BACKUP.ARCHV1.G1116V00 CA1 ABACKUP 05/03/07 12:53BACKUP.ARCHV1.G1119V00 TLMS ABACKUP 05/03/16 12:26BACKUP.ARCHV1.G1120V00 TLMS ABACKUP 05/03/16 12:26BACKUP.ARCHV1.G1121V00 TLMS ABACKUP 05/03/16 12:26BACKUP.ARCHV1.G1122V00 TLMS ABACKUP 05/03/16 12:26BACKUP.ARCHV1.G1123V00 TLMS ABACKUP 05/03/16 12:26BACKUP.ARCHV1.G1129V00 CA1 ABACKUP 05/03/30 10:41

See the topic 'Identifying Data Set Overlaps' (page 6-10) for an example of a Quick Search for Data Set, and resulting overlaps.




Quick Search for Data Set Panel – Primary Command Descriptions


REFresh Refresh the display.

RESet Reset screen values to default.

Quick Search for Data Set Panel – Line Command Descriptions


I View data set detail as recorded at backup time.

O View data set overlaps by data set.

L View all backup generations of the selected data set.

R Select a data set for Restore. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore.

S View Backup Event Detail.

Quick Search for Data Set Panel – Field Descriptions

Field Description

Display HSM Incr Displays HSM Incremental or Command Backup data sets matching the data set name or mask specified.

Display Full Vol Dumps Displays Full Volume Dump data sets matching the data set name or mask specified.

C Enter 'S' or '?' under the 'C' field to display the Quick Search for Data Set Setup panel.

Data Set Name or Mask Enter a data set name or mask up to 44 characters. Any of the ACS masking characters can be used to search for a data set name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

Jobname No input required. Name of job that backed up the data set.

PGM/Type No input required. Program or Type that backed up the data set.

Date No input required. Date DSN was backed up.

Time No input required. Time DSN was backed up.



--------------------------------------------------------------------------------


6.2 Identifying Data Set Overlaps You can identify data set overlaps using either Search for Dataset or Quick Search for Dataset. (The examples in this section are shown only for Search for Dataset.)

In the following panel, all data sets with a high level qualifier of BRMI.IVP are searched for and displayed. As shown below, an '*' in the far right-hand column titled 'O' signify that overlaps exist for this data set. To identify the data set overlaps, enter a '+' under column C next to the data set and press Enter.


BRM - Search for Dataset Row 1 of 5 Command ===> ________________________________________________ Scroll ===> PAGE


Display HSM Incr => Y Y or N

C Dataset Name or Mask +- Gen Backup Date Time O _ BRMI.IVP.**_________________________________ - Name yy/mm/dd

+ BRMI.IVP.CNTL _ BRMI.IVP.FB.DATASET _ BRMI.IVP.FB.DATASET.EMPTY _ BRMI.IVP.FB.DATASET1 _ BRMI.IVP.FB.DATASET2 _ BRMI.IVP.GDG1.G0003V00 _ BRMI.IVP.GDG1.G0004V00 _ BRMI.IVP.GDG1.G0005V00 _ BRMI.IVP.GDG1.G0006V00 _ BRMI.IVP.GDG1.G0007V00

+ 0 IVPSTD 01/08/08 14:02 *+ 0 IVP2SDS 01/07/16 18:16 *+ 0 IVP2SDS 01/07/16 18:16 *+ 0 IVP2SDS 01/07/16 18:16 *+ 0 IVP2SDS 01/07/16 18:16 *

0 IVPSDSNU 01/02/01 08:29+ 0 IVP2SDS 01/07/16 18:16 *+ 0 IVP2SDS 01/07/16 18:16+ 0 IVP2SDS 01/07/16 18:16+ 0 IVP2SDS 01/07/16 18:16



-------------------------------------------------------------------------------


In the following panel, the data set BRMI.IVP.CNTL contains an overlap due to other aggregates backing up the same data set, in this case aggregates IVPSDSL and IVPSDSNU.

Because 'HSM Incrementals ===> Y' was specified in the Search for Data Set Setup panel, HSM Incremental/Command Backups are displayed as well. These HSM backups can be selected for hrecover without knowledge of the HSM HRECOVER syntax. Note however, that it is your responsibility to ensure the data set does not exist on the system (unless using the REPLACE command), or is not migrated. HSM backups are not considered an 'overlap' data set.






BRMI.IVP.CNTL -_ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ BRMI.IVP.FB.DATASET -_ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET

0 IVPSTD 04/08/08 14:02 *-1 IVPSTD 04/08/08 12:02-2 IVPSDSL 04/08/07 11:59- HSM 04/05/10 09:45- HSM 04/03/01 20:39-3 IVPSDSNU 04/03/01 08:12-4 IVPSDSNU 04/02/01 08:290 IVP2SDS 04/07/16 18:16 *-1 IVP2SDS 04/06/08 15:07-2 IVPSDSNU 04/03/01 08:12-3 IVPSDSNU 05/02/01 08:29



-------------------------------------------------------------------------------


6.3 Line Command O – Search for Data Set Overlaps Line Command O can be used to initiate a search for data set overlaps. By specifying Line Command O, the BRM Inventory Data Set will be searched for any other aggregates/events that have backed up the same selected data set.

Search for Data Set Overlaps

To initiate a search for Data Set Overlaps, select a data set using Line Command O on either the Search for Dataset or Quick Search panel. Example using Line Command O on the Search for Dataset panel:






O BRMI.IVP.CNTL - 0 IVPSTD 04/08/08 14:02 *_ - BRMI.IVP.CNTL -1 IVPSTD 04/08/08 12:02_ - BRMI.IVP.CNTL -2 IVPSDSL 04/08/07 11:59

- BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ BRMI.IVP.FB.DATASET -_ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET

- HSM 04/05/10 09:45- HSM 04/03/01 20:39-3 IVPSDSNU 04/03/01 08:12-4 IVPSDSNU 04/02/01 08:290 IVP2SDS 04/07/16 18:16 *-1 IVP2SDS 04/06/08 15:07-2 IVPSDSNU 04/03/01 08:12-3 IVPSDSNU 05/02/01 08:29

After selecting a data set with line command O and overlaps are found, the following panel is displayed.

Overlap Search by Dataset Row 1 to 4 of 4

Command ===> Scroll ===> PAGE

Name => ASTTEST1 Run Date => 2006/02/28 15:12Dataset Name => BRMI.IVP.CNTL DSN Name Date Time ------------------------------------------------------------------------BRMI.IVP.CNTL IVPSTD 2004/08/08 14:02BRMI.IVP.CNTL IVPSTDL 2004/08/07 11:59BRMI.IVP.CNTL HSM 2004/05/10 09:45BRMI.IVP.CNTL IVPSTDNU 2004/03/01 08:12**************************** Bottom of data ****************************



-------------------------------------------------------------------------------


6.4 Line Command R – Select Data Set for Recovery Line Command R can be used to select any data set for recovery or restore. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore. The following example shows you how to recover a data set backed up by an HSM Incremental using the DFSMShsm HRECOVER command.

By specifying Line Command R next to the data set that has HSM as the backup name, the data set is selected for HRECOVER.

Line Command R can be used for both the Search for Dataset and Quick Search for Dataset options.

Example using Line Command R on the Search for Dataset panel:






_ BRMI.IVP.CNTL -_ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTLR - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ - BRMI.IVP.CNTL _ BRMI.IVP.FB.DATASET -_ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET _ - BRMI.IVP.FB.DATASET

0 IVPSTD 04/08/08 14:02 *-1 IVPSTD 04/08/08 12:02-2 IVPSDSL 04/08/07 11:59- HSM 04/05/10 09:45- HSM 04/03/01 20:39-3 IVPSDSNU 04/03/01 08:12-4 IVPSDSNU 04/02/01 08:290 IVP2SDS 04/07/16 18:16 *-1 IVP2SDS 04/06/08 15:07-2 IVPSDSNU 04/03/01 08:12-3 IVPSDSNU 05/02/01 08:29




After specifying Line Command R, an ISPF panel is displayed to select HRECOVER parameters. This panel is displayed when using Line Command R with both Search for Dataset and Quick Search for Dataset.

BRM - HRECOVER Options

Data Set BRMI.IVP.CNTL GEN 000

Specify Newname (if desired - quotes not required)=> ______________________________________________

Replace data set if already cataloged => N Y or N

For System Administrator only:Use HSEND Command => N Y or N Force to NON-SMS => _ Y or N ToVolume => ______ Y or N Unit => ______ Y or N


Data Set Search – HRECOVER OPTIONS

Field Description

Data Set Data set selected for HRECOVER.

GEN Generation selected to HRECOVER.

Specify Newname Specify the new data set name you would like HRECOVER to restore to.

Replace data set if already Y – Issue the REPLACE command on HRECOVER to replace an cataloged existing data set.

N – Do not REPLACE existing data set.

For System Administrator only: The System Administrator feature gives those authorized to issue the HSEND command the ability to enter additional System Administrator keywords. By specifying Y, the HSEND command is issued instead of hrecover. If you do not have System Administrator access, DFSMShsm will fail the command.

Force to NON-SMS The HSM keyword, FORCENONSMS will be submitted to HSM to force the data set to a non-SMS volume.

ToVolume The HSM keyword, TOVOLUME tells HSM which volume the data set should go to.

Unit The HSM keyword, UNIT tells HSM which UNIT to use.

Press Enter to hrecover the selected data set. To replace the data set if it already exists, change 'Replace data set if already cataloged => Y' and press Enter.

By pressing Enter, Backup & Recovery Manager Suite (BRM) will take you back to the data set list panel where you will see: *PRESS END(PF3) TO RESTORE SELECTED DSNS

To cancel this request so the hrecover is not submitted, type RESET on the command line or CANCEL.

Press End (PF3) to hrecover the selected data set and view the HSM hrecover messages.




BRM00099I BRMSDSN SELECT CMD(HRECOVER 'BRMI.IVP.CNTL' GEN(000) REPLACE)*** ARC1007I RECOVER REQUEST 00000716 SENT TO DFSMSHSMARC0778I DATA SET BRMI.IVP.CNTL WAS RECOVERED FROM A BACKUP MADE AT 09:45:49 ARC0778I (CONT.) ON 2001/05/10*** ARC1000I BRMI.IVP.CNTL RECOVER PROCESSING ENDED ***

6.5 Restoring Data Without Knowledge of Which Utility Backed Up the Data Set Backup & Recovery Manager Suite (BRM) will allow you to restore a group of data sets without knowledge of which utilities backed up the data set. For example, let's say you have 1000 IDMS databases you want to restore but you don't want to restore specific aggregates. You will want to review the list and select the IDMS databases you want.

The process to accomplish this is to list the data set names and then use the R Mask/X Mask Primary Commands to select only those you wish to restore. R Mask means restore the data sets. X Mask means exclude the data sets from Restore. A single 'R' or 'X' works as well. The Primary Command X Mask is not required because only data sets with an 'R' next to them will be recovered, but the X Mask is useful when you want to narrow down a category of data sets. For instance, you type 'R IDMS.**' and then 'X IDMS.O*.**'. The 'X IDMS.O*.**' clears the recover field ('R' next to the data set name) to prevent the data set from being selected for recovery. When you have the final list of data sets ready, press PF3. By pressing PF3, all data sets in the list are sorted by the appropriate utility.

If you are licensed for both ABARS Manager and All/Star, and if an ABARS data set was selected for restore, the Restore Warning panel is displayed asking if you would like to recover the data set using the Submit ARECOVER panel or if the data sets should be recovered using skeleton processing.

Restore WarningYou have selected ABARS dsn(s) forrestore. Would you like to restorethe dsn(s) using the Submit ARECOVERpanel or using the Skeletons method?

Use ARECOVER panel or Skeleton JCL?

REPLY ===> A (A or S)

If A is specified, then each aggregate's ARECOVER panel pops up for specific ARECOVER keyword support. See the Backup and Recovery Manager Suite User Guide for ABARS Manager, (document SC23-6060) for more information on ARECOVER.

If S is specified, then the data set will be restored using skeleton processing. See 'Line Command R – All/Star Restore' (page 4-9) for more information on All/Star Restore.




Chapter 7 7 All/Star: Reports – Online Using Option 6

7.1 All/Star Backup Reports – Sub-Option 2 Reports (Option 6) allows you to either submit batch report requests, or create and view reports online. Reports are generated using backup data only. For more information about creating All/Star reports in batch, see Chapter 9, All/Star: Batch Processing & Output.

Missing Generation Numbers: DFSMShsm Incremental backups will not have any generations associated with them in any displays or reports because All/Star tracks backups by jobname.





X Exit


Mainstar Software Corporation ©2006 7-1 Chapter 7 SC23-6061-00 All/Star: Reports – Online Using Option 6


-------------------------------------------------------------------------


To create All/Star reports, select Reports (Option 6) from the Main Menu to display the Reports Menu, then select sub-option 3, All/Star Backup Reports, to display the All/Star Backup Reports Menu.


BRM5600 BRM - ReportsCommand ==>


ABARS Manager1 Backup Reports2 Recovery Reports

All/Star3 Backup Reports

The All/Star Backup Reports menu is displayed. Descriptions of the reports, their report options, and report examples are provided in separate topics.

Menu Diagnostics Preferences --------------------------------------------------------------------------BRM5620 All/Star - Backup Reports MenuCommand ==>

Select a Report from the list below:

1 Overlap by Dataset2 Overlap by Backup Event3 Overlap by Job Groups4 Dataset List 5 Dataset List by Jobname with Outputs6 Full Volume Dump List7 Jobname List 8 Jobnames Not Tracked by a Job Group9 What Isn't Backed Up10 Critical in ASAP with No All/Star Backup Record11 Critical in ASAP with All/Star Backup Record12 BKUPEND Summary Report13 Overlap by Application

(Reports are generated using backup data only)

Chapter 7 7-2 Mainstar Software Corporation ©2006 All/Star: Reports – Online Using Option 6 SC23-6061-00


------------------------------------------------------------------------------


7.1.1 All/Star Backup Report 1 – Overlap by Data Set After selecting report 1 from the All/Star Backup Reports menu, the Overlap by Data Set Report panel is displayed.


All/Star - Overlap by Dataset ReportCommand ===> _________________________________________________________________

(S) SELECT AN OPTION: _ Build/Submit JCL _ Build/View JCL _ Exec/View Online

REPORT OPTIONS: Dataset => ____________________________________________ Name(s) or => ____________________________________________ Mask(s) => ____________________________________________

=> ____________________________________________ => ____________________________________________

Include HSM Incrementals => _ Y or N

Overlap by Data Set Report Panel – Report Options

After entering all of the required fields, select 'Build/Submit JCL', 'Build/View JCL', or 'Exec/View Online'.

Field Description

Build/Submit JCL Build the JCL from the options supplied on the panel and submit.

Build/View JCL Build the JCL from the options supplied on the panel, and then view the JCL.

Exec/View Online Select to execute the report with the options specified and view the report online.

Dataset Name(s) or Mask(s) Specify dataset name(s) or mask(s) to find overlaps on.

Include HSM Incrementals Specify Y to include the BCDS in the search for dataset overlaps.




Overlap by Data Set Report Example

Whether the Overlap by Data Set Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: DATASET => D*

PAGE 1 All/Star - OVERLAP BY DATASET (Vxx.xx) 2004/06/1215:28:09

DATASET NAME EVENT DATE TIME TYPE --------------------------------------------------- -------- ---------- ------- -------DANR.DANR1.ISR0001.BACKUP P390BKP6 2004/06/11 15:59:55 DSS FVD

P390BKP5 2004/06/08 20:57:52 DSS FVD

DANR.SI52.MULTIVOL ASTBJ610 2004/06/11 11:13:37 FDR FVDASTBJ011 2004/06/10 10:12:42 DSS FVDASTBJ010 2004/06/10 10:12:09 DSS FVD

DANR.SI52.MULTIVO2 ASTBJ610 2004/06/11 11:13:37 FDR FVDASTBJ011 2004/06/10 10:12:42 DSS FVDASTBJ010 2004/06/10 10:12:09 DSS FVD

-----------------------------TOTAL DATASETS FOUND: 3




7.1.2 All/Star Backup Report 2 – Overlap by Backup Event After selecting report 2 from the All/Star Backup Reports menu, the Overlap by Backup Event Report panel is displayed.

Menu Diagnostics Preferences -----------------------------------------------------------------------------BRM5632 All/Star - Overlap by Backup Event ReportCommand ===>

(S) SELECT AN OPTION: Build/Submit JCL Build/View JCL Exec/View Online

REPORT OPTIONS: Event Name(s) => ________ ________ ________ ________ ________

Overlap by Backup Event Report Panel – Report Options


Field Description




Event Name(s) (or Mask(s))

Enter up to five event name(s) or mask(s). Any of the ACS masking characters can be used to search for an event name with overlaps. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).




Overlap by Backup Event Report Example

Whether the Overlap by Backup Event Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: EVENT => D*

PAGE 1 All/Star - OVERLAP BY BACKUP EVENT (Vxx.xx) 2005/05/05 15:28:09

DATASET NAME EVENT DATE TIME TYPE --------------------------------------------------- -------- ---------- ------- -------DANR.DANR1.ISR0001.BACKUP P390BKP6 2004/06/11 15:59:55 DSS FVD

P390BKP5 2004/06/08 20:57:52 DSS FVD

DANR.SI52.MULTIVOL ASTBJ610 2004/06/11 11:13:37 FDR FVDASTBJ011 2004/06/10 10:12:42 DSS FVDASTBJ010 2004/06/10 10:12:09 DSS FVD

DANR.SI52.MULTIVO2 ASTBJ610 2004/06/11 11:13:37 FDR FVDASTBJ011 2004/06/10 10:12:42 DSS FVDASTBJ010 2004/06/10 10:12:09 DSS FVD




------------------------------------------------------------------------------


7.1.3 All/Star Backup Report 3 – Overlap by Job Groups After selecting report 3 from the All/Star Backup Reports menu, the Overlap by Job Groups Report panel is displayed.


All/Star - Overlap by Job Groups ReportCommand ===> _________________________________________________________________


REPORT OPTIONS: Job Name(s) => __________ ________ ________ ________ ________

Overlap by Job Groups Report Panel – Report Options


Field Description







Overlap by Job Groups Report Example

Whether the Overlap by Job Groups Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: JOBNAMES => *

PAGE 1 ALL/STAR - OVERLAP BY JOB GROUPS (Vxx.xx) 2004/06/12 15:22:00

JOBNAME RC RCB DATE TIME JOB GROUPS -------- ---- ---- ---------- -------- ---------------------------------------ASTBJ010 0 0 2004/06/10 10:12:09 TEST TEST2

--------------------------------------------------------JOBS FOUND: 1




7.1.4 All/Star Backup Report 4 – Data Set List After selecting report 4 from the All/Star Backup Reports menu, the Data Set List Report panel is displayed.

Menu Diagnostics Preferences ------------------------------------------------------------------------------All/Star - Dataset List ReportCommand ===>

(S) SELECT AN OPTION:Build/Submit JCL Build/View JCL Exec/View Online

REPORT OPTIONS: Dataset => Name(s) orMask(s)

=> => => =>

ADVANCED OPTIONS: Job Name(s) =>

From Date => To Date =>

Date or mask (YYYY/MM/DD, *, *-nnn)Date or mask (YYYY/MM/DD, *, *-nnn)

Type(s) => ABCDFGHIMNSV A -ABARS,B -BACKVOL,C -CR+,D -DSS,F -FDR,G -IEBGENER/ICEGENER/IEBCOPY/SYNCGENR,H -HSM,I -IDCAMS,M -CFCAMS,N -ADARUN,S -SORT,V -CA-FAVER




Data Set List Report Panel – Report Options


Field Description




Dataset Name(s) or Mask(s) Specify a data set name or mask to report on.

Job Name(s) Filter data set report output by jobname(s) or mask.

From Date The starting date or mask of the data set(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999

To Date The ending date or mask of the data set(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999

Type(s) A – data sets backed up by ABARS B – data sets backed up by BACKVOL C – data sets backed up by CR+ D – data sets backed up by DFSMSdss F – data sets backed up by FDR G – data sets backed up by IEBGENER, ICEGENER, IEBCOPY,

or SYNCGENR H – data sets backed up by HSM Incremental, ARCINBAK, and

HSM Auto dump I – data sets backed up by IDCAMS REPRO or EXPORT M – data sets backed up by CFCAMS N – data sets backed up by ADARUN S – data sets backed up by SORT V – data sets backed up by Brightstor CA-FAVER



--------------------------------------------------- -------- ---------- -------- ------


Data Set List Report Example

Whether the Data Set List Report is run from batch or online, a report in the following format is created. If you are licensed for All/Star, by default, data sets in full volume dumps are not displayed. It can appear that generation numbers have been skipped when displaying data sets in the report when in fact, they are accounted for but not displayed.

SEARCH CRITERIA: DATASET => D*

TYPE => DFGHIS

PAGE 1 ALL/STAR - DATASET LIST (Vxx.xx) 2004/06/1216:04:40

DATASET NAME EVENT DATE TIME TYPE

DAD.DADHHATT.DAD.DATA P390BKP5 2004/06/11 15:59:54 DSS FVDP390BKP5 2004/06/10 16:51:24 DSS FVDP390BKP5 2004/06/09 16:42:36 DSS FVDP390BKP5 2004/06/08 20:57:52 DSS FVD

DAD.DADHHATT.DAD.INDEX P390BKP5 2004/06/11 15:59:54 DSS FVDP390BKP5 2004/06/10 16:51:24 DSS FVDP390BKP5 2004/06/09 16:42:36 DSS FVDP390BKP5 2004/06/08 20:57:52 DSS FVD




7.1.5 All/Star Backup Report 5 – Data Set List with Outputs After selecting report 5 from the All/Star Backup Reports menu, the Data Set List with Outputs Report panel is displayed.

Menu Diagnostics Preferences ----------------------------------------------------------------------------BRM5643 All/Star - Dataset List with OutputsCommand ===>


REPORT OPTIONS: Jobname(s) => ________ ________ ________ ________ ________

Data Set List with Outputs Report Panel – Report Options


Field Description




Jobname(s) (or Mask(s))

Enter up to five jobname(s) or mask(s). Any of the ACS masking characters can be used to search for data sets by jobname. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).




Data Set List with Outputs Report Example

Whether the Data Set List with Outputs Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: EVENT => D*

PAGE 1 ALL/STAR – DATASET LIST BY JOBNAME (Vxx.xx) 2005/05/05 15:28:09

JOBNAME: EDGGENER PROC: STEP1 STEP: COPY TASK: 0001 DATE: 2004/10/21 TIME: 14:03:48.89

DATASET NAME LIST -------------------------EDG.TEST.INCRA O:EDG.INCRA.TEST2

------------------------------------TOTAL DATASETS INPUT/OUTPUT: 2



------------------------------------------------------------------------------


7.1.6 All/Star Backup Report 6 – Full Volume Dump List After selecting report 6 from the All/Star Backup Reports menu, the Full Volume Dump List Report panel is displayed.


All/Star - Full Volume Dump List ReportCommand ===> _________________________________________________________________


REPORT OPTIONS: Volume Name(s) => ________ ________ ________ ________ ________

ADVANCED OPTIONS: From Date => __________ Date or mask (YYYY/MM/DD, *, *-nnn)To Date => __________ Date or mask (YYYY/MM/DD, *, *-nnn)

Full Volume Dump List Report Panel – Report Options


Field Description




Volume Name Specify a volume name or mask to report on.

From Date The starting date or mask of the volume(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999

To Date The ending date or mask of the volume(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999




Full Volume Dump List Report Example

Whether the Full Volume Dump List Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: VOLUME => *

PAGE 1 ALL/STAR - FULL VOLUME DUMP LIST (Vxx.xx) 2004/06/1215:13:49

VOLUME PGM TYPE RC RCB DATE TIME PROCSTEP STEPNAME TASK# # DSNS -------- --- ---- --- --- ---------- -------- -------- -------- ----- ------ARCHV1 DSS FVD 0 0 2004/06/11 15:59:54 S1 0001 146

DSS FVD 0 0 2004/06/10 16:51:24 S1 0001 146 DSS FVD 0 0 2004/06/09 16:42:36 S1 0001 146 DSS FVD 0 0 2004/06/08 20:57:52 S1 0001 145 DSS FVD 0 0 2004/06/08 16:40:52 S1 0001 145

ARCHV2 DSS FVD 0 0 2004/06/11 15:59:55 S1 0001 161 DSS FVD 0 0 2004/06/10 16:51:35 S1 0001 161 DSS FVD 0 0 2004/06/09 16:42:53 S1 0001 162 DSS FVD 0 0 2004/06/08 20:57:52 S1 0001 160 DSS FVD 0 0 2004/06/08 16:41:04 S1 0001 158




7.1.7 All/Star Backup Report 7 – Jobname List After selecting report 7 from the All/Star Backup Reports menu, the Jobname List Report panel is displayed.


All/Star - Jobname List ReportCommand ===> _________________________________________________________________


REPORT OPTIONS: Jobname(s) => *_______

- or -Job Group => ________ (Exact name only)

ADVANCED OPTIONS: Use Date Type => S

From Date => ________ From Time => ____ To Date => ________ To Time => ____

GEN => _____

S -Start Date, E -End DateDate or mask (YYYY/MM/DD, *, *-nnn)Time (0000 - 2359)Date or mask (YYYY/MM/DD, *, *-nnn)Time (0000 - 2359)0 to -9999

Jobname List Report Panel – Report Options


Field Description




Jobname(s) Specify a jobname or mask to report on. Cannot be used in conjunction with a job group.

Job Group Specify a job group (exact name only). Cannot be specified in conjunction with a jobname or mask.

Use Date Type Specify whether to use Jobname Start Date/Time or End Date/Time when a From Date or To Date is specified.

From Date The starting date or mask of the jobname(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999

From Time Specify a time to narrow the search of the Jobname List report. If a To Date is not specified, then only jobnames matching the date and time specified will be displayed.




Field Description

To Date The ending date or mask of the jobname(s)/event(s) to search for. • Date must be in format YYYY/MM/DD or MM/DD/YYYY. • Relative date masking is also allowed: − * for today − *-5 for five days back from today, etc. to *-999

To Time Specify a time to narrow the search of the Jobname List report. If a From Date is not specified, then only jobnames matching the date and time specified will be displayed.

GEN Specify a jobname generation number to report only those jobnames matching the GEN specified.




Jobname List Report Example

Whether the Jobname List Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: JOBNAME => *

PAGE 1 ALL/STAR - JOBNAME LIST (V04.03 ) 2005/12/15 16:02:50

JOBNAME PGM/TYPE RC RCB DATE TIME END DATE END TIME PROCSTEP STEPNAME TASK# # DSNS -------- -------- ---- ---- ---------- -------- ---------- -------- -------- -------- ----- ------ADDB2001 HSMAUTO 0 0 2005/12/14 09:30:02 2005/12/14 11:00:07 0001 164

HSMAUTO 0 0 2005/12/13 09:30:02 2005/12/13 10:59:27 0001 164 HSMAUTO 0 0 2005/12/12 09:30:02 2005/12/12 11:00:01 0001 164

ADSCD001 HSMAUTO 0 0 2004/07/14 07:39:12 2005/12/14 09:00:00 0001 170

ADTSO001 HSMAUTO 0 0 2001/08/23 13:11:46 2005/12/13 12:00:01 0001 495



------------------------------------------------------------------------------


7.1.8 All/Star Backup Report 8 – Jobnames Not Tracked by a Job Group After selecting report 8 from the All/Star Backup Reports menu, the Jobnames Not Tracked by a Job Group Report panel is displayed.


All/Star - Jobnames not Tracked by a Job Group ReportCommand ===> _________________________________________________________________


REPORT OPTIONS: Job Name(s) => ________ ________ ________ ________ ________

Jobnames Not Tracked by a Job Group Report Panel – Report Options


Field Description







Jobnames Not Tracked By a Job Group Report Example

Whether the Jobnames Not Tracked By a Job Group Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: JOBNAMES => P390*

1PAGE 1 ALL/STAR - JOBNAMES NOT TRACKED BY A JOB GROUP (V04.03 ) 2004/07/21 13:40:14

JOBNAME RC RCB DATE TIME -------- ---- ---- ---------- --------P390BKP5 0 0 2004/07/20 15:20:45

P390BKP6 0 0 2004/07/20 15:21:04

--------------------------------------------------------JOBS FOUND: 2




7.1.9 All/Star Backup Report 9 – What Isn’t Backed Up After selecting report 9 from the All/Star Backup Reports menu, the What Isn’t Backed Up Report panel is displayed.

The

Menu Diagnostics Preferences -----------------------------------------------------------------------------BRM5634 All/Star - What Isn't Backed Up ReportCommand ===>

(S) SELECT AN OPTION:_ Build/Submit JCL _ Build/View JCL

REPORT OPTIONS: Target IDS => Y Y or N Target BCDS => N Y or N Sort By => N N -Name or V -Vol

SOURCE PARAMETERS: (For additional parms select Build/View JCL)Include DSN or Mask => _____________________________________________ Exclude DSN or Mask => _____________________________________________ Include UCAT or Mask => _____________________________________________ Exclude UCAT or Mask => _____________________________________________ Include Vol or Mask => _____________________________________________ Exclude Vol or Mask => _____________________________________________

Note: You are responsible for the maintenance of the ICF catalogs. If data set entries exist in the catalog that are either no longer on disk, or are cataloged to non-existent volumes, it is considered a catalog maintenance issue. Similarly, if there are disk entries with no associated catalog entry, it is considered a DASD maintenance issue. What Isn't Backed Up Report identifies these reports, but it does not eliminate them.




What Isn’t Backed Up Report Panel – Report Options


Field Description




Target IDS Specify Y to have the SOURCE compared to the BRM Inventory Data Set.

Target BCDS Specify Y to have the SOURCE compared to the DFSMShsm BCDS.

Sort By Specify N to sort the report by data set name. Specify V to sort the report by volume.

Include DSN or Mask Specify a data set name or mask to include in the compare.

Exclude DSN or Mask Specify a data set name or mask to exclude in the compare.

Include UCAT or Mask Specify a user catalog name or mask to include in the compare.

Exclude UCAT or Mask Specify a user catalog name or mask to exclude in the compare.

Include Vol or Mask Specify a volume name or mask to include in the compare.

Exclude Vol or Mask Specify a volume name or mask to exclude in the compare.




What Isn't Backed Up Report Example

Whether the What Isn't Backed Up Report is run from batch or online, a report in the following format is created.

********************************* TOP OF DATA ************** ****************************************************** * WHAT ISN'T BACKED UP * * * * NO BACKUP FOUND FOR THE FOLLOWING: * * NOTE: "+" = MULTI-VOLUME DATASET * ****************************************************** DATASET NAME VOLSER

------------------------------------------------------DSDB.ARCHLOG1.A0000002 WORK03 DSDB.ARCHLOG1.A0000004 FEND24 DSDB.ARCHLOG1.B0000001 FENC03 DSDB.ARCHLOG1.B0000004 FENM05 DSDB.BSDS01 ?????? DSDB.BSDS01.DATA LG1005 DSDB.BSDS01.INDEX LG1005 DSDB.BSDS02 ?????? DSDB.BSDS02.DATA LG2008 DSDB.BSDS02.INDEX LG2008 DSDB.DSNDBC.AASNS001.SSTRINF0.I0001.A001 MIGRAT DSDB.DSNDBC.AASNS001.XSTRINF0.I0001.A001 MIGRAT DSDB.DSNDBC.AASNS001.XSTRINF1.I0001.A001 MIGRAT DSDB.DSNDBC.AASNS001.XSTRINF2.I0001.A001 MIGRAT DSDB.DSNDBC.AASNS001.XSTRINF5.I0001.A001 MIGRAT




7.1.10 All/Star Backup Report 10 – Critical in ASAP with No All/Star Backup Record After selecting report 10 from the All/Star Backup Reports menu, the Critical in ASAP with No All/Star Backup Record Report panel is displayed.

Menu Diagnostics Preferences -----------------------------------------------------------------------------BRM5642 All/Star - Critical in ASAP with No All/Star Backup RecordCommand ===>

(S) SELECT AN OPTION:_ Build/Submit JCL _ Build/View JCL _ Exec/View Online

REPORT OPTIONS: ASAP APPL Name => Include BCDS => N Y or N

Dataset => **______________________________________________ Name(s) or => ________________________________________________ Mask(s) => ________________________________________________

=> ________________________________________________ => ________________________________________________

Critical in ASAP with No All/Star Backup Record Report Panel – Report Options


Field Description




ASAP Application Specify an ASAP application name that a BKUPEND has been executed for to determine which data sets do not have a current backup.

Include BCDS For data sets not found with a backup in the BRM Suite Inventory Data Set, the BCDS will then be searched to see if a backup exists.

Dataset Name(s) or Mask(s) Specify up to five data set names or masks to only include from the selected ASAP Application’s BKUPEND.




Critical in ASAP with No All/Star Backup Record Report Example

Whether the Critical in ASAP with No All/Star Backup Record Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: DATASET => **

ASAP APPLICATION => TEST

PAGE 1 ALL/STAR - CRITICAL WITH NO ALL/STAR BACKUP RECORD (V06.01 ) 2006/02/28 09:14:34

DSN(S) WITH NO BACKUP FOR ASAP APPL: TEST VOLSER MGMTCLAS STORCLAS STORGRP --------------------------------------------------- ------ -------- -------- --------BRMI.AST.IVP.ESDS BRMD01 MCBRMSD SCBRMSD SGBRMSD

BRMI.AST.IVP.JA30.NOBKP.ESDS NOBKP1 MCNOBK SCNOBK SGBRMSD

BRMI.AST.IVP.JB10.KSDS BRMD00 MCBRMSD SCBRMSD SGBRMSD

BRMI.AST.IVP.JB10.NOBKP.KSDS NOBKP2 MCNOBK SCNOBK SGBRMSD

BRMI.AST.IVP.JB11.ESDS BRMD02 MCBRMSD SCBRMSD SGBRMSD

BRMI.AST.IVP.JB11.KSDS BRMD02 MCBRMSD SCBRMSD SGBRMSD

BRMI.AST.IVP.JB11.NOBKP.ESDS NOBKP3 MCNOBK SCNOBK SGBRMSD




7.1.11 All/Star Backup Report 11 – Critical in ASAP with All/Star Backup Record After selecting report 11 from the All/Star Backup Reports menu, the Critical in ASAP with All/Star Backup Record Report panel is displayed.

This report describes the data sets found critical in ASAP for which there is a matching backup record in All/Star. The report is by ASAP application and displays the input data set name backed up, output backup data set name, jobname that created the backup, date, time, type of backup, volser of the output data set, and tape location of the output data set if there is one.

Note: All/Star automatically recognizes the tape management systems CA1, TLMS, and RMM. If your tape management system is TLMS, you must change the name of the TLMSDB statement in the BRMBPROC found in the product JCL library from 'NULLFILE' to the TLMS database name. In addition, you must also update the token TLMS_DB, to your TLMS database name found in the product PARMLIB, member BRMINI. For CA1 or RMM, no JCL or INI changes are required.

Menu Diagnostics Preferences -----------------------------------------------------------------------------BRM5641 All/Star - Critical in ASAP with All/Star Backup RecordCommand ===>

(S) SELECT AN OPTION:_ Build/Submit JCL _ Build/View JCL _ Exec/View Online

REPORT OPTIONS: ASAP APPL Name => Include BCDS => N Y or N

Dataset => **______________________________________________ Name(s) or => ________________________________________________ Mask(s) => ________________________________________________

=> ________________________________________________ => ________________________________________________




Critical in ASAP with All/Star Backup Record Report Panel – Report Options


Field Description




ASAP Application Specify an ASAP application name that a BKUPEND has been executed for to display the critical data sets and the most current backup for those data sets.

Include BCDS Include the BCDS in the search for what is backed up.

Dataset Name(s) or Mask(s) Specify up to five data set names or masks to only include from the selected ASAP Application’s BKUPEND.




Critical in ASAP with All/Star Backup Record Report Example

Whether the Critical in ASAP with All/Star Backup Record Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: DATASET => **

ASAP APPLICATION => BTCHSMF1

PAGE 1 ALL/STAR - CRITICAL WITH ALL/STAR BACKUP RECORD (V04.03 ) 2005/05/06 08:20:59

DATASET NAME JOBNAME DATE TIME TYPE VOLSER -------------------------------------------------- -------- ---------- -------- -------- ------I:KAS.CNTL BMPTEST 2005/04/13 09:17:44 ABACKUPO:EDP.BRM.BMPTEST.TODISK.C.C01V0163 TODSK1 O:EDP.BRM.BMPTEST.TODISK.D.C01V0163 TODSK1

I:KAS.GDG2.G0004V00 O:EDP.BRM.BMPTEST.TODISK.C.C01V0163 O:EDP.BRM.BMPTEST.TODISK.D.C01V0163

BMPTEST 2005/04/13 09:17:44 ABACKUP TODSK1 TODSK1

I:KAS.ISPF.ISPPROF EDPBJ010 2005/03/31 10:31:07 DSS FVDO:EDP.BMT.J010.NOBACKUP.DUMP2 NOBKP3





7.1.12 All/Star Backup Report 12 – BKUPEND Summary After selecting report 12 from the All/Star Backup Reports menu, the BKUPEND Summary Report panel is displayed.

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5644 All/Star ¢ BKUPEND Summary ReportCommand ===>

(S) SELECT AN OPTION:Build/Submit JCL Build/View JCL Exec/View Online

REPORT OPTIONS: ASAP APPL Name =>

Cycle => 0Include BCDS => N

(Exact name only)0 to -9999 Y or N

BKUPEND Summary Report Panel – Report Options


Field Description




ASAP Application Specify an ASAP application name that a BKUPEND has been executed for to display a summary of what backups were found when that BKUPEND was executed.

Cycle Specify a BKUPEND cycle to report on.

Include BCDS When displaying a BKUPEND Summary, also search the BCDS for backup records.



---


BKUPEND Summary Report Example

Whether the BKUPEND Summary Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: ASAP APPLICATION => EDG3

CYCLE => 0

PAGE 1 ALL/STAR - BKUPEND SUMMARY (V06.01 ) 2006/09/28 15:29:50

----- BKUPEND BACKUP ----- - MOST RECENT BACKUP - ---- LAST CHANGED -DATASET NAME JOBNAME DATE TIME RC JOBNAME DATE TIME JOBNME DATE TIME --------------------------------------------BRMI.AST.IVP.J115.PDSE.OLD BRMI.AST.IVP.J115.PRODUCT.TESTX BRMI.TEST3.G0001V00 BRMI.TEST3.G0002V00 BRMI.TEST3.G0003V00

-------------------------- ------------------------ ---------------------TEST3 20060612 1109 0 P390BKPD 20060611 0100 0 ** NO BACKUP FOUND ** NO BACKUP FOUND ** NO BACKUP FOUND

----------------------------TOTAL DATASETS: 5 DATASETS WITH BACKUP: 2 DATASETS W/NO BACKUP: 3




7.1.13 All/Star Backup Report 13 – Overlap by Application After selecting report 13 from the All/Star Backup Reports menu, the Overlap by Application Report panel is displayed.

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5646 All/Star - Overlap by ApplicationCommand ===>


REPORT OPTIONS: Appl Name(s) => ________ ________ ________ ________ ________

Overlap by Application Report Panel – Report Options


Field Description




Appl Name(s) Enter up to five application name(s) or mask(s). Any of the ACS masking characters can be used to search for data sets by application name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).



--------------------------------------------------- -------- ---------- --------

-------------------------------------


Overlap by Application Report Example

Whether the Overlap by Application Report is run from batch or online, a report in the following format is created.

SEARCH CRITERIA: APPLICATION => DS6

PAGE 1 ALL/STAR - OVERLAP BY APPLICATION (V04.03 ) 2005/12/19 13:25:27

DATASET NAME APPL DATE TIME

ASPX.QABETA.ASAPDB

ASPX.QABETA.MSGLOG

ASP5401X.QABETA.LOAD

ASP5401X.QABETA.PARMLIB

DS01.ASAPTEST.KSDS

DS01.ASAPTEST.KSDSDATA

DS01.ASAPTEST.LINKLIB

DS01.ASAPTEST.LOADLIB

TOTAL DATASETS WITH OVERLAPS: 8

DS6 PAYR1

DS6 PAYR1

DS6 PAYR1

DS6 PAYR1

DS01 DS6

DS01 DS6

DS01 DS6

DS01 DS6

2005/12/12 08:58:232005/12/19 09:59:40

2005/12/12 08:58:232005/12/19 09:59:40

2005/12/12 08:58:232005/12/19 09:59:40

2005/12/12 08:58:232005/12/19 09:59:40

2005/12/16 16:12:362005/12/12 08:58:23

2005/12/16 16:12:362005/12/12 08:58:23

2005/12/16 16:12:362005/12/12 08:58:23

2005/12/16 16:12:362005/12/12 08:58:23




Chapter 8 8 BRM Suite: History – Option 8

This option can be used to display events sorted by date, newest to oldest.

History (Option 8) allows the user to view events based on their backup/recovery date. Line Commands available within this option allow you to view event detail.





X Exit


Mainstar Software Corporation ©2006 8-1 Chapter 8 SC23-6061-00 BRM Suite: History – Option 8



8.1 History Search Setup – Initial Selection On initial selection of Option 8 from the Main Menu, the History Search Setup panel is displayed. Use this panel to specify criteria to use when searching for event execution.

If you want to skip the search setup panel from now on, select the 'Don't show this panel again'. The current search criteria will become your default criteria, and the History panel will be displayed directly.

BRM - History Search Setup

Command ===> _________________________________________________________

Specify the criteria to use when searching for selected Backup(s)and Recovery(s).Name or Mask ===> *_______ Event Date ===> __________ *-nnn, *+nnn -(nnn = days) or

Date (Format YYYY/MM/DD,MM/DD/YYYY)Display ABARS ===> Y Y or N Display All/Star ===> Y Y or N

Enter "/" to select option/ Store values to be used as default for this USERID_ Don't show this panel again


Chapter 8 8-2 Mainstar Software Corporation ©2006 BRM Suite: History – Option 8 SC23-6061-00



History Search Setup Panel – Field Descriptions

Field Description

Name or Mask Enter a name or mask for the event whose backup and recovery events you want to search for. Can be up to eight characters in length. Any of the ACS masking characters can be used to search for an aggregate name. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). Default: '*' for all events.

Event Date Specify a date criteria or exact date to search for. Example: * = today

*-1 = show only events from yesterday *+1 = show events from today and yesterday ( - is exclusive and + is inclusive)

or specify date in format YYYY/MM/DD or MM/DD/YYYY If the Date field is left blank, then all dates are displayed.

Display ABARS Displays ABARS events tracked by ABARS Manager.

Display All/Star Displays All/Star events tracked by All/Star.

Store values to be used as Default Select this field with a '/' to store the event name as entered on for this UserID the panel. If selected, the next time the History panel is displayed

for your userid, the Name or Mask field, and all other fields will contain the values last entered here. To view/change this panel after it has been stored, key an 'S' or '?' under the 'C' field on the History panel.

Don't show this panel again Select this field with a '/' to skip the History Search Setup panel and go directly to the History panel when you select Option 8 from the Main Menu.



--------------------------------------------------------------------------------


8.2 About the BRM History Panel After you enter your search criteria, press Enter. The History panel will be displayed.

For All/Star events, the event and data set records are retained if the most recent ASTEXPIR job found that the output files from the backup were still cataloged.

For ABARS events, the event entry is retained if it is within the number of backup gens (or recover gens) to retain specified in the BRM Aggregate Management w/SMS Interface panel.

If the Jobname contains dashes as in the example below, it means that either the job is still active, or that the job did not complete (for example, the job was cancelled or IPL’d over).

Menu Diagnostics Preferences ------------------------------------------------------------------------------BRM5810 BRM History Row 1 to 12 of 443 Command ===> Scroll ===> CSR

Line Commands: BRM,N,S,VA,VE Date: 2004/07/06 16:59 Display ABARS => Y Y or N Display All/Star => Y Y or N

C Date Time Jobname Name PGM/Type RC RC * UTIL BRM

___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/11 15:59:55 P390BKP6 P390BKP6 DSS FVD 0 0 ___ 2004/06/10 17:27:05 KASBACK1 KAS1 AB VER 0 0 ___ 2004/06/10 12:09:22 -------- ARDAILY AB EXEC - -

History Panel – Line Command Descriptions


BRM Display Backup and Recovery Management panel for selected event.

N List data set names backed up and recovered.

S Select to view Backup/Recovery detail.

VA View activity log produced by BACKUP/ARECOVER. (ABARS Manager only)

VE View any errors that may exist. (ABARS Manager only)




History Panel – Input Field Descriptions

Input Field Description

C Enter 'S' or '?' under the 'C' field to display the History Search Setup panel.

Name or Mask Enter a name or mask for the event whose backup and recovery events you want to search for.

Date Specify a date criteria or exact date to search for: • Date must be in format YYYY/DD/MM or MM/DD/YYYY. • If the date field is left blank, all dates are displayed. '*-n' – displays only events equal to n relative days from today. Example: '*-4' displays only events four days from today. '*+n' – displays all events equal to today through n relative days from today. Example: '*+4' displays all events starting today through four days from today.

PGM/Type The PGM/type fields specify the utility and type used to back up the data set. AB VER ABARS ABACKUP Verify AB EXEC ABARS ABACKUP Execute AR VER ABARS ARECOVER Verify AR EXEC ABARS ARECOVER Execute AR PREP ABARS ARECOVER Prepare BACKVOL HSM BACKVOL Command CR+ BCS CR+ BCS Backup CR+ DSN CR+ DSN Backup CR+ VVD CR+ VVDS Backup CA-FAVER Brightstor CA-FAVER CFC REP CFCAMS REPRO CFC EXP CFCAMS EXPORT DSS LD DSS LOGICAL DUMP DSS PD DSS PHYSICAL DATA SET DUMP DSS FVD DSS FULL VOLUME DUMP FDR ABR FDR ABR ABR DUMP FDR APPL FDR APPL DUMP FDR DSF FDRDSF DUMP FDR ADSF FDR ABR DSF DUMP FDR FDR FDR ABR FDR DUMP FDR FVD FDR FULL VOLUME DUMP HSMAUTO HSM AUTODUMP IDC EXP IDCAMS EXPORT IDC REP IDCAMS REPRO ICEGENER ICEGENER IEBGENER IEBGENER IEBCOPY IEBCOPY SORT SORT SYNCGENR SYNCGENR

RC Return code returned from the ABARS / All/Star process.

RCB Return code returned from the BRM process.




Chapter 9 9 All/Star: Batch Processing & Output

Contents:

The topics referenced below document the syntax, parameter descriptions, and examples of use for the All/Star batch commands.

• All/Star Error and Product Messages – page 9-2

• Deleting Individual Versions – page 9-2

• The AUTODUMP Command – page 9-3

• The ASTEXPIRE Command – page 9-4

• The BACKVOL Command – page 9-5

• The BUILD-BIFDSN and REFRESH-AST Commands – page 9-5

• The LOADIDS Command – page 9-6

• The UNLOADIDS Command – page 9-10

• The REPORT Command – page 9-13

Mainstar Software Corporation ©2006 9-1 Chapter 9 SC23-6061-00 All/Star: Batch Processing & Output



9.1 All/Star Error and Product Messages All/Star error or product messages can be found on the MENU Sub-Menu option. See 'Messages – Menu Option 1' (page 2-9) for information on accessing error messages.

All messages are concatenated together and you only need to type in the message number. Messages can also be found in the product MESSAGES members with the following prefixes:

• ALB prefix for Aggregate Load Balancer messages • BRM prefix for ABARS Manager, Incremental ABARS, and CATSCRUB messages • AST prefix for All/Star started task (AST), and All/Star • ASP prefix for ASAP messages

9.2 Deleting Individual Versions Line command D# specified next to a jobname allows you to delete the individual jobname from the BRM Inventory Data Set.

Warning: Using this command could remove valid backups from the BRM Inventory Data Set. Once this command has been issued, there is no way to reload the backup. Caution should be exercised in using this command. This command is purposefully not documented as a line command on any panel.

9.3 All/Star Data Set Support All/Star supports data set backups, but not PDS member backups.

Chapter 9 9-2 \Mainstar Software Corporation ©2006 All/Star: Batch Processing & Output SC23-6061-00



9.4 The AUTODUMP Command DFSMShsm AUTODUMPs are not automatically tracked by All/Star. To update the Backup & Recovery Manager Suite (BRM) Inventory Data Set (IDS) with DFSMShsm AUTODUMPs, schedule the AUTODUMP batch job. The AUTODUMP job adds any new AUTODUMPs found in the BCDS to the BRM IDS. The AUTODUMP JCL member is in the Backup & Recovery Manager Suite JCL library.

When this batch job is running, DFSMShsm is required to be up. If DFSMShsm is not up, the job will end without any updates to the BRM Inventory Data Set.

This job can either be scheduled at known times, triggered by DFSMShsm messages, or run ad hoc.

Note: If no VTOC can be found, there will not be any data sets recorded for the autodump.

An example of the AUTODUMP job follows:

***************************** Top of Data ******************************//AUTODUMP JOB ,'BRM HSM AUTODUMP',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*// JCLLIB ORDER=BRM.JCL//*******************************************************************//* HSM AUTODUMP JCL * //*******************************************************************//* STEP 1: CHANGE JOB STATEMENT TO LOCAL STANDARDS * //* STEP 2: CHANGE JCLLIB STATEMENT TO CORRECT JCLLIB NAME * //* STEP 3: CHANGE ALL &HLQ. TO HLQ FOR YOUR PRODUCT LIBS * //*******************************************************************//HSMAUTO EXEC BRMBPROC,// LOAD1='&HLQ..LOAD',// PARMLIB='&HLQ..PARMLIB',//* DAD='DAD.DADHHATT.DAD',// IDS='&HLQ..IDS' <=== CHANGE TO YOUR IDS //BRMBATCH.SYSIN DD *HSMADUPD /***************************** Bottom of Data ****************************




9.5 The ASTEXPIRE Command The ASTEXPIRE command must be scheduled on a regular basis to remove old jobname cycles for All/Star tracked backups from the BRM Inventory Data Set.

The ASTEXPIRE command is submitted using job ASTEXPIR found in the Backup & Recovery Manager Suite JCL library. The ASTEXPIR job must be set up and executed to expire and remove from the BRM Inventory Data Set any backups that are no longer valid. If a backup job contains multiple backups, the backup jobname will not be removed from the BRM Inventory Data Set until all backups in the job are no longer valid.

For more information on the ASTEXPIRE command, see 'Step 4: Implement the All/Star ASTEXPIRE Command' (page 12-11).

Job ASTEXPIR should be checked at least initially to verify what is being expired.

The ASTEXPIR job JCL is shown below:

********************************* Top of Data **********************************//ASTEXPIR JOB ,'BRMBATCH',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*// JCLLIB ORDER=BRM.JCL//******************************************************//* EXPIREV AST CYCLES//******************************************************//* CHANGE JOB STATEMENT TO LOCAL STANDARDS * //* CHANGE JCLLIB STATEMENT TO CORRECT JCLLIB NAME * //* CHANGE ALL &HLQ. TO HLQ FOR YOUR PRODUCT LIBS * //******************************************************//BRM EXEC BRMBPROC,// LOAD1='&HLQ..LOAD',// PARMLIB='&HLQ..PARMLIB',// IDS='&HLQ..IDS'//BRMBATCH.SYSIN DD * ASTEXPIRE //******************************** Bottom of Data ********************************




9.6 The BACKVOL Command DFSMShsm BACKVOLs are not automatically tracked by All/Star. To update the Backup & Recovery Manager Suite (BRM) Inventory Data Set with DFSMShsm BACKVOLs, schedule the BACKVOL batch job.

The BACKVOL job synchronizes the BRM Inventory Data Set with HSM's BACKVOL VTOC data sets (HSM keeps the most recent two). The BACKVOL JCL member is in the Backup & Recovery Manager Suite JCL library. This job can either be scheduled at known times, triggered by DFSMShsm messages, or run ad hoc.

An example of the BACKVOL job follows:

***************************** Top of Data ******************************//BACKVOL JOB ,'BRM HSM BACKVOL',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*// JCLLIB ORDER=BRM.JCL//*******************************************************************//* HSM AUTODUMP JCL *//*******************************************************************//* STEP 1: CHANGE JOB STATEMENT TO LOCAL STANDARDS *//* STEP 2: CHANGE JCLLIB STATEMENT TO CORRECT JCLLIB NAME *//* STEP 3: CHANGE ALL &HLQ. TO HLQ FOR YOUR PRODUCT LIBS *//*******************************************************************//HSMBKBV EXEC BRMBPROC,// LOAD1='&HLQ..LOAD',// PARMLIB='&HLQ..PARMLIB',//* DAD='DAD.DADHHATT.DAD',// IDS='&HLQ..IDS' <=== CHANGE TO YOUR IDS//BRMBATCH.SYSIN DD *HSMBVUPD

9.7 The BUILD-BIFDSN and REFRESH-AST Commands Any time you add new jobnames to All/Star through ISPF, you must rebuild the contents of the batch intercept file (BIF) with the current information stored in the BRM Inventory Data Set and then refresh the started task so that a new copy of the intercept filters can be loaded into storage. There are several ways to do this:

1. Use the option on the ISPF panel to build the batch intercept file and refresh AST, the started task. This is the most common method. See 'Build Batch Intercept File and Refresh AST – Sub-Option 6' (page 3-5), for more information.

2. Use batch commands BUILD-BIFDSN and REFRESH-AST as shown below. //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *BUILD-BIFDSN REFRESH-AST

3. Use the started task modify command F AST,REFRESH.

This command will be sent to all participating systems. The original filters are valid until this process is complete.




9.8 The LOADIDS Command Use the LOADIDS — Load Inventory Data Set — command to perform a load, in batch, of a backup copy (previously unloaded) of the BRM Inventory Data Set.

9.8.1 Submitting the LOADIDS Command Submit the LOADIDS command as SYSIN to the BRMBPROC member of the BRM JCL library. LOADIDS may also be submitted through the ISPF panels; see 'Load Inventory (All/Star) – Utilities Option 3' (page 2-17).

9.8.2 LOADIDS Command Syntax

ALL .

.

Note: The default is to load data previously extracted from the Inventory Data Set If you own ABARS Manager and All/Star, ALL data refers to all aggregate records from ABARS Manager and all job records from All/Star. Optional parameters can be used to selectively load previously extracted BRM Inventory Data Set data, instead of the default of all extracted data

Caution: If selected loads are required, it is recommended that the selection be made during the UNLOADIDS rather than unloading everything and selectively loading to increase speed.

Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

LOADIDS INFILE( dsn )

All/Star Optional Parameters:

[ JOB(* | jobname1 | jobmask1 ) ][ EXCLJOB( jobname1 | jobmask1 ) ][ GENS( nn ) ] [ REPLACE ]




9.8.3 LOADIDS Command Parameter Definitions Table 9-1: LOADIDS Command Parameter Definitions

LOADIDS SHORT PARAMETER PARAMETER FORM(S) DEFINITION

All/Star required parameters:

LOADIDS LOADIDS command.

Default: Load all unloaded. Required: Yes ABARS Manager and All/Star.

NOTE: If this parameter is used as a stand-alone without optional parameters AG or JOB, all records contained in the BRM Inventory Data Set for both ABARS Manager and All/Star will be loaded. To load ABARS Manager or All/Star records separately or selectively, the AG or JOB parameters are required.

INFILE Specify the data set name of the file containing previously

Default: None unloaded BRM Inventory Data Set records.

Required: Yes Restrictions: Quotes around the data set name are not valid.

All/Star optional parameters:

JOB

Default: If both AG* and JOB are omitted, load all. Required: No Restrictions: All/Star ONLY.

*AG is an ABARS Manager parameter.

Use to specify jobs to be loaded. The JOB parameter is required if you wish to load All/Star data either selectively (i.e. only the jobs you are interested in) or separately from ABARS Manager. The AG parameter is an ABARS Manager ONLY parameter. The relationship between AG and JOB is as follows: • * causes all jobs to be loaded. • If both AG and JOB parameters are omitted, all data is

loaded. • If only one parameter, AG, or JOB is specified, only the

data specified will be loaded. For more information on the AG parameter of LOADIDS and UNLOADIDS for ABARS Manager, refer to the Mainstar: Backup and Recovery Manager Suite User Guide for ABARS Manager (document SC23-6060).

EXCLJOB Specify jobs to exclude from the load. Can be a job or job mask.

Default: None Required: No Restrictions: All/Star ONLY. Valid only with JOB parameter.




LOADIDS SHORT PARAMETER PARAMETER FORM(S) DEFINITION

GENS * nn

Default: Omitting the GENS parameter will automatically unload all generations. Required: No Restrictions: Only one GENS per LOADIDS is allowed. This parameter is shared by ABARS Manager and All/Star.

For unload of selected GENS, use to specify which generations are to be unloaded. nn – the number of generations to unload. If specified, the generations are unloaded in the order 'newest to oldest'. * – causes all generations to be unloaded.

REPLACE Specify to replace current entries.

Default: None Required: No Restrictions: Only one REPLACE per LOADIDS is allowed. This parameter is shared by ABARS Manager and All/Star.




9.8.4 LOADIDS Command – Examples The following example shows how to initiate LOADIDS commands in batch mode using procedure BRMBPROC.

Batch LOADIDS Example 1 – ABARS Manager and All/Star combined: //STEPNAME EXEC BRMBPROC //BRMBATCH.SYSIN DD *

LOADIDS INFILE(dsn)

In this example, all data previously extracted from the Inventory Data Set will be loaded from the specified INFILE(dsn) into the BRM Inventory Data Set. Note: Quotes around the data set name are not valid.

Batch LOADIDS Example 2 – All/Star: //STEPNAME EXEC BRMBPROC //BRMBATCH.SYSIN DD *

LOADIDS INFILE(PROD.BRM.INVDB.UNLOAD.IDS) -JOB(*) EXCLJOB(PA*) GENS(1)

In this example, one generation of all jobs except for those starting with PA* will be loaded from the INFILE(dsn) into the BRM Inventory Data Set. Note: Quotes around the data set name are not valid.

Batch LOADIDS Example 3 – ABARS Manager and All/Star: //STEPNAME EXEC BRMBPROC //BRMBATCH.SYSIN DD *

LOADIDS INFILE(PROD.BRM.INVDB.UNLOAD.IDS) -AG(*) JOB(PAY*) EXCLJOB(PAY1) GENS(3)

In this example, three generation of all aggregates, and three generations of All/Star tracked jobs beginning with PAY* except for PAY1 will be loaded from the INFILE(dsn) into the BRM Inventory Data Set. Note: Quotes around the data set name are not valid.




9.9 The UNLOADIDS Command Use the UNLOADIDS — Unload Inventory Data Set — command to perform an unload, in batch, of the data from the BRM Inventory Data Set, either to be used as a backup, or for other purposes.

9.9.1 Using UNLOADIDS to Remove ABARS Manager Entries Incurred During a Trial ABARS Manager and All/Star share the same BRM Inventory Data Set. If you are licensed to use All/Star and you wish to remove ABARS Manager entries from the BRM Inventory Data Set, the easiest way to accomplish this is to:

1. Execute an All/Star UNLOADIDS to extract only the All/Star entries.

2. Delete the BRM Inventory Data Set.

3. Define a new BRM Inventory Data Set.

4. LOADIDS the previously unloaded All/Star entries.

9.9.2 Submitting the UNLOADIDS Command Submit the UNLOADIDS command as SYSIN to the BRMBPROC member of the BRM JCL library.

9.9.3 UNLOADIDS Command Syntax

.

of the default of ALL.

Note: The default is to unload ALL data from the BRM Inventory Data Set If you own ABARS Manager and All/Star, ALL data refers to all aggregate records from ABARS Manager, and all job records from All/Star. Optional parameters can be used to selectively unload data, instead

Caution: If selected loads are required, it is recommended that the selection be made during the UNLOADIDS rather than unloading everything and selectively loading to increase speed.

Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

UNLOADIDS

All/Star Optional Parameters:

[ JOB( * | jobname1 | jobmask1 ) ][ EXCLJOB( jobname1 | jobmask1 ) ][ GENS( * | nn ) ][ OUTFILE( dsn ) ]




9.9.4 UNLOADIDS Command Parameter Definitions Table 9-2: UNLOADIDS Command Parameter Definitions

UNLOADIDS SHORT PARAMETER PARAMETER FORM(S) DEFINITION

All/Star required parameters:

UNLOADIDS

Default: Unload all ABARS Manager aggregates and all All/Star JOBs. Required: Yes ABARS Manager and All/Star

UNLOADIDS command.

NOTE: If this parameter is used as a stand-alone without optional parameters AG* or JOB, all records contained in the BRM Inventory Data Set for both ABARS Manager and All/Star will be unloaded. To unload ABARS Manager or All/Star records separately or selectively, the AG or JOB parameters are required. *AG is an ABARS Manager UNLOADIDS parameter.

All/Star optional parameters:

JOB

Default: If both AG* and JOB are omitted, load all. Required: No Restrictions: All/Star ONLY.

*AG is an ABARS Manager UNLOADIDS parameter.

Use to specify jobs to be unloaded. The JOB parameter is required if you wish to unload All/Star data either selectively (i.e. only the jobs you are interested in) or separately from ABARS Manager. The AG parameter is an ABARS Manager ONLY parameter. The relationship between AG and JOB is as follows: • * causes all jobs to be unloaded. • If both AG* and JOB parameters are omitted, all data is

unloaded. • If only one parameter, AG, or JOB is specified, only the

data specified will be unloaded. For more information on the AG parameter of LOADIDS and UNLOADIDS for ABARS Manager, refer to the Backup and Recovery Manager Suite User Guide: ABARS Manager (document SC23-6060).

EXCLJOB Specify jobs to exclude from the unload. Can be a job, or

Default: None job mask.

Required: No Restrictions: All/Star ONLY. Valid only with JOB parameter.




UNLOADIDS SHORT PARAMETER PARAMETER FORM(S) DEFINITION

GENS * nn

Default: Omitting the GENS parameter will automatically unload all generations. Required: No Restrictions: Only one GENS per UNLOADIDS is allowed. This parameter is shared by ABARS Manager and All/Star.

For unload of selected GENS, use to specify which generations are to be unloaded. nn – the number of generations to unload. If specified, the generations are unloaded in the order 'newest to oldest'. * – causes all generations to be unloaded.

OUTFILE

Default: If OUTFILE parameter is not specified, all data in the BRM Inventory Data Set will be unloaded, but only a report will be created. Required: No Restrictions: Quotes around the data set name are not valid. Only one OUTFILE per UNLOADIDS is allowed. This parameter is shared by ABARS Manager and All/Star.

Specify the output data set name to unload BRM Inventory Data Set records to. If the dsn specified in the OUTFILE parameter does not exist, it will be dynamically allocated. The default allocation is: SPACE=(CYL,(1,1)),UNIT=SYSALLDA, RECFM=VBS,LRECL=24636,BLKSIZE=32760 The default allocation values may be changed by modifying the values of the following tokens in the :PROCESSING_OPTIONS section of the BRMINI PARMLIB member: UNLOADIDS_SPACE = 'CYLINDERS SPACE(1 2)' UNLOADIDS_UNIT = SYSALLDA If the OUTFILE parameter is not specified, only a report will be created.




9.9.5 UNLOADIDS Command – Examples The following example shows how to initiate UNLOADIDS commands in batch mode using procedure BRMBPROC.

Batch UNLOADIDS Example 1 – All/Star and ABARS Manager combined: //STEPNAME EXEC BRMBPROC //BRMBATCH.SYSIN DD *

UNLOADIDS OUTFILE(dsn)

In this example, all data will be unloaded from the BRM Inventory Data Set into the specified OUTFILE(dsn). This includes both All/Star and ABARS Manager records. If the optional parameter OUTFILE(dsn) is not specified, then only a report, listing the jobs and ABARS aggregates unloaded from the Inventory Data Set, will be produced. Note: Quotes around the data set name are not valid.

Batch UNLOADIDS Example 2 – All/Star: //STEPNAME EXEC BRMBPROC //BRMBATCH.SYSIN DD *

UNLOADIDS OUTFILE(PROD.BRM.INVDB.UNLOAD.IDS) -JOB(PAY*) EXCLJOB(PAY1) GENS(3)

In this example, three generations of jobs beginning with PAY* except for PAY1 will be unloaded from the BRM Inventory Data Set.

Note: Quotes around the data set name are not valid.

9.10 The REPORT Command The REPORT command is used to submit All/Star output reports. Several report types, listed in the table below, can be requested using the REPORT command.

Table 9-3: REPORT Types

REPORT TYPE DESCRIPTION PAGE

OVERLAPD-AST Overlap by Data Set 9-15

OVERLAPE-AST Overlap by Backup Event 9-17

OVERLAPJOBGRP Overlap by Job Groups 9-18

DSNLIST-AST Data Set List 9-19

DSNLIST-O Data Set List with Outputs 9-22

FVDLIST Full Volume Dump List 9-23

JOBLIST Jobname List 9-26

NOJOBGRP Jobnames Not Tracked by a Job Group 9-29

NOBACKUP What Is Not Backed Up 9-30

ASAP2BRM-NB Critical in ASAP with No All/Star Backup Record 9-36

ASAP2BRM-B Critical in ASAP with All/Star Backup Record 9-38

BKUPEND Backup End Summary 9-41

OVERLAPA-AST Overlap by Application 9-43




Notes About All/Star Reports DFSMShsm Incremental backups will not have any generations associated with them in any displays or reports because All/Star tracks backups by jobname.

By default, data sets in full volume dumps are not displayed. It can appear that generation numbers have been skipped when displaying data sets in the report when in fact, they are accounted for but not displayed.

9.10.1 Submitting the REPORT Command REPORT commands are passed to All/Star in batch mode using the BRMBPROC member of the Backup & Recovery Manager Suite JCL library. Submit the REPORT command as SYSIN to the BRMBPROC member of the Backup & Recovery Manager Suite JCL library.

• Any number of REPORT commands may be included as SYSIN in a BRMBPROC invocation.

• Only one report type may be specified with each REPORT command.

Example of a request for multiple report types: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPD-AST DS(dsname1)REPORT DSNLIST-AST DS(dsname1)




9.11 OVERLAPD-AST Report Type – Overlap by Data Set Use the OVERLAPD-AST command to submit a report request for the Overlap by Data Set report in batch. Submit the OVERLAPD-AST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax and parameter descriptions.

9.11.1 REPORT OVERLAPD-AST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT OVERLAPD-AST DS( dsn1 …dsnn | dsnmask1 …dsnmaskn )

9.11.2 REPORT OVERLAPD-AST Command Parameter Definitions

Note: Any number of command parameters may be included in a BRMBPROC invocation.

Table 9-4: REPORT OVERLAPD-AST Command Parameter Definitions

REPORT OVERLAPD-AST PARAMETER

SHORT FORM(S)

PARAMETER DEFINITION

REPORT REPORT command.

OVERLAPD-AST

Default: None Required: Yes Restrictions: None

Sub-command to create 'overlap by data set' report type.

DS dsn


Specify the name(s) or name mask(s) of the data set(s) to be searched for to create the overlap by data set report.




9.11.3 REPORT OVERLAPD-AST Command Examples The following examples show how to initiate Overlap by Data Set reports in batch mode using procedure BRMBPROC.

Batch OVERLAPD-AST Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPD-AST DS(dsname1)

In this example, only one data set is searched for overlaps.

Batch OVERLAPD-AST Example 2:

A second method is to code the same JCL but have more than one data set name in the REPORT OVERLAPD-AST command.

//STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPD-AST DS(dsname1 dsname2*)

In this case multiple overlap by data set searches will be done. Overlaps will be searched for 'dsname1' and any data set matching the mask 'dsname2*'.

9.11.4 Overlap by Data Set Report Example The output for the Overlap by Data Set report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of an Overlap by Data Set report is shown on page 7-4.




9.12 OVERLAPE-AST Report Type – Overlap by Backup Event Use the OVERLAPE-AST command to submit a report request for the Overlap by Backup Event report in batch. Submit the OVERLAPE-AST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.12.1 REPORT OVERLAPE-AST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT OVERLAPE-AST EV( event1/jobname1 …eventn/jobnamen | eventmask1/jobmask1

…eventmaskn/jobmaskn )

9.12.2 REPORT OVERLAPE-AST Command Parameter Definitions


Table 9-5: REPORT OVERLAPD-AST Command Parameter Definitions

REPORT OVERLAPE-AST PARAMETER

SHORT FORM(S)



OVERLAPE-AST


Sub-command to create 'overlap by event/jobname' report type.

EV Event/jobname


Specify the name(s) or name mask(s) of the aggregate event(s) or Jobname(s) to be searched for to create the overlap by event/jobname report.

9.12.3 REPORT OVERLAPE-AST Command Examples The following examples show how to initiate Overlap by Backup Event reports in batch mode using procedure BRMBPROC.

Batch OVERLAPE-AST Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPE-AST EV(DS1)

In this example, only one Event/Jobname is searched for.

9.12.4 Overlap by Backup Event Report Example The output for the Overlap by Backup Event/Jobname report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of an Overlap by Backup Event/Jobname report is shown on page 7-6.




9.13 OVERLAPJOBGRP Report Type – Overlaps by Job Group List Use the OVERLAPJOPGRP command to submit a report request for the Overlaps by Job Group List report in batch. Submit the OVERLAPJOBGRP command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.13.1 REPORT OVERLAPJOBGRP Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT OVERLAPJOBGRP JOB( jobname1 …jobnamen | jobnamemask1 …jobnamemaskn )

9.13.2 REPORT OVERLAPJOBGRP Command Parameter Definitions


Table 9-6: REPORT OVERLAPJOBGRP Command Parameter Definitions

REPORT OVERLAPJOBGRP PARAMETER

SHORT FORM(S)



OVERLAPJOBGRP


Sub-command to create ‘Overlaps by Job Group’ report type.

JOB jobname


Specify the jobname(s) or jobname mask(s) to determine which jobname is tracked by more than one Job Group.

9.13.3 REPORT OVERLAPJOBGRP Command Examples The following example shows how to initiate Overlaps by Job Group reports in batch mode using procedure BRMBPROC.

Batch OVERLAPJOBGRP Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPJOBGRP JOB(jobname1)

In this example, only one jobname is checked to see if more than one Job Group is tracking it.

9.13.4 Overlaps by Job Group Report Example The output for the Overlaps by Job Group report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of an Overlaps by Job Group report is provided on page 7-7.




9.14 DSNLIST-AST Report Type – Data Set List by Data Set Name, Date Use the DSNLIST-AST command to submit a report request for the Data Set List by Data Set Name, Date report in batch. Submit the DSNLIST-AST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax and parameter descriptions.

9.14.1 REPORT DSNLIST-AST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT DSNLIST-AST DS( dsn1 …dsnn | dsnmask1 …dsnmaskn )

Optional Parameters:

[ DATE( fromdate,todate | fromdatemask,todatemask ) ] [ JOB( jobname1 …jobnamen | jobnamemask1 …jobnamemaskn ) ] [ TYPE( type ) ]




9.14.2 REPORT DSNLIST-AST Command Parameter Definitions

Note 1: Required parameters are described first, followed by optional parameters.

Note 2: Any number of command parameters may be included in a BRMBPROC invocation.

Table 9-7: REPORT DSNLIST-AST Command Parameter Definitions

REPORT DSNLIST-AST SHORT PARAMETER PARAMETER FORM(S) DEFINITION

Required parameters:


DSNLIST-AST Sub-command to create 'data set lists' report type.


DS Specify the name(s) or name mask(s) of the data dsn set(s) to be listed in the data set list report.


Optional parameters:

DATE fromdate todate * *-nnn

Default: None Required: No Restrictions: None

fromdate or fromdatemask – specify the starting date or mask of the data set(s) or events(s) to be listed in the data set list report. Dates must be in the format YYYY/MM/DD or MM/DD/YYYY. todate or todatemask – specify the ending date or mask of the data set(s) or event(s) to be listed in the data set list report. For relative date masking use * for today, and *-nnn for today minus a number of days, up to 999. Example: *-5 will search for five days back from today

JOB jobname


Specify any number of jobnames or masks of jobnames to be listed in the data set list report.




REPORT DSNLIST-AST SHORT PARAMETER PARAMETER FORM(S) DEFINITION

TYPE type – specify a utility type to search for data sets in:type A – ABARS

Default: None B – BACKVOL

Required: No C – CR+

Restrictions: None D – DSS F – FDR G – IEBGENER

ICEGENER IEBCOPY SYNCGENR

H – HSM I – IDCAMS M – CFCAMS N – ADARUN S – SORT V – CA-FAVER

9.14.3 REPORT DSNLIST-AST Command Examples The following examples show how to initiate Data Set List by Data Set Name, Date reports in batch mode using procedure BRMBPROC.

Batch DSNLIST-AST Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT DSNLIST-AST DS(dsname1)

In this example, only one data set is searched for.

Batch DSNLIST-AST Example 2:

A second method is to code the same JCL but have more than one jobname in the REPORT DSNLIST-AST command.

//STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT DSNLIST-AST DS(dsname*) -

JOB(jobname1 jobname2*) -TYPE(D) -DATE(*,2001/02/29)

In this case, any data set matching dsname* in jobnames jobname1 or jobname2 type DSS, between today and 2001/02/29, will be displayed.

9.14.4 Data Set List by Data Set Name, Date Report Example The output for the Data Set List by Data Set Name, Date report can be found under the DD name BRMBREPT in the batch SYSOUT. Note that ABARS data sets will not be displayed in the Data Set List Report because full ABARS backups are not tracked by All/Star. ABARS data sets will be displayed on the Search for Data Set panel but not in the Data Set List Report batch report. An example of a Data Set List report is provided on page 7-10.




9.15 DSNLIST-O Report Type – Data Set List by Jobname, Data Set Name, Date w/Outputs Use the DSNLIST-O command to submit a report request for the Data Set List by Jobname, Data Set Name, Date w/Outputs report in batch. Submit the DSNLIST-O command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.15.1 REPORT DSNLIST-O Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT DSNLIST-O JOB( jobname1 …jobnamen | jobmask1 …jobmaskn )

9.15.2 REPORT DSNLIST-O Command Parameter Definitions


Table 9-8: REPORT DSNLIST-O Command Parameter Definitions

REPORT DSNLIST-O PARAMETER

SHORT FORM(S)



DSNLIST-O


Sub-command to create 'Data Set List by Job, Data Set Name, Date w/Outputs' report type.

JOB jobname


Specify the jobname(s) or jobname mask(s) to display input data sets by jobname with their associated output data set(s).

9.15.3 REPORT DSNLIST-O Command Examples The following examples show how to initiate Data Set List with Outputs reports in batch mode using procedure BRMBPROC.

Batch DSNLIST-O Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT DSNLIST-O JOB(jobname1)

In this example, only one Jobname is searched for.

9.15.4 Data Set List with Outputs Report Example The output for the Data Set List with Outputs report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Data Set List with Outputs report is provided on page 7-13.




9.16 FVDLIST Report Type – Full Volume Dump List Use the FVDLIST command to submit a report request for the Full Volume Dump List report in batch. Submit the FVDLIST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax and parameter descriptions.

9.16.1 REPORT FVDLIST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT FVDLIST VOL( volser1 | volsermask1 …volsern | volsermaskn )


[ DATE( fromdate,todate | fromdatemask,todatemask ) ]




9.16.2 REPORT FVDLIST Command Parameter Definitions



Table 9-9: REPORT FVDLIST Command Parameter Definitions

REPORT FVDLIST SHORT PARAMETER PARAMETER FORM(S) DEFINITION



FVDLIST Sub-command to create ‘Full Volume Dump lists'

Default: None report type.

Required: Yes Restrictions: None

VOL Specify the volume name(s) or volume name volume mask(s) of the Full Volume Dumps to be listed.





fromdate or fromdatemask – specify the starting date or mask of the data set(s) or events(s) to be listed in the data set list report. Dates must be in the format YYYY/MM/DD or MM/DD/YYYY. todate or todatemask – specify the ending date or mask of the data set(s) or event(s) to be listed in the data set list report. For relative date masking use * for today, and *-nnn for today minus a number of days, up to 999. Example: *-5 will search for five days back from today




9.16.3 REPORT FVDLIST Command Examples The following examples show how to initiate Full Volume Dump List reports in batch mode using procedure BRMBPROC.

Batch FVDLIST Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT FVDLIST VOL(volname1)

In this example, only one data set is searched for.

Batch FVDLIST Example 2:

A second method is to code the same JCL but have more than one jobname in the REPORT FVDLIST command.

//STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT FVDLIST VOL(volname*) -

DATE(*,2001/02/29)

In this case any volume matching 'volname*' between today and 2001/02/29, will be displayed.

9.16.4 Full Volume Dump List Report Example The output for the Full Volume Dump List report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Full Volume Dump List report is provided on page 7-15.




9.17 JOBLIST Report Type – Jobname List Use the JOBLIST command to submit a report request for the Jobname List report in batch. Submit the JOBLIST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax and parameter descriptions.

9.17.1 REPORT JOBLIST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT JOBLIST JOB( jobname1 …jobnamen | jobnamemask1 …jobnamemaskn ) |

JOBGRP( jobgroup )


[ DATE( fromdate,todate | fromdatemask,todatemask ) ] [ DATETYPE( S | E ) ][ TIME( fromtime, totime ) ] [ GEN( nn ) ]

9.17.2 REPORT JOBLIST Command Parameter Definitions



Table 9-10: REPORT JOBLIST Command Parameter Definitions

REPORT JOBLIST PARAMETER

SHORT FORM(S)




JOBLIST


Sub-command to create ‘Jobname List’ report type.

JOB jobname

Default: None Required: Either JOBGRP or JOB must be specified. Restrictions: Mutually exclusive with JOBGRP.

Specify the jobname(s) or jobname mask(s) of the jobname(s) to be listed in the Jobname List report.




REPORT JOBLIST SHORT PARAMETER PARAMETER FORM(S) DEFINITION

JOBGRP jobgroup

Default: None Required: Either JOBGRP or JOB must be specified. Restrictions: Mutually exclusive with JOB.

Specify the Job Group name of the jobname(s) to be listed in the Jobname List report. jobgroup must specify an absolute name. Job Group may be up to 8 characters in length.




fromdate or fromdatemask – specify the starting date or mask of the jobname(s) to be listed in the Jobname List report. Dates must be in the format YYYY/MM/DD or MM/DD/YYYY. todate or todatemask – specify the ending date or mask of the jobname(s) to be listed in the Jobname List report. For relative date masking, use * for today, and *-nnn for today minus a number of days, up to 999. Example: *-5 will search for five days back from today.

DATETYPE Specify S to use Start Date when comparing to a S specified From Date/To Date.

E Specify E to use End Date when comparing to a

Default: S specified From Date/To Date.

Required: No Restrictions: None

TIME fromtime totime


fromtime requires a fromdate be specified when searching for jobnames. If todate is not specified, then only jobnames matching the date and time specified will be reported. Or specify a To Date/Time to report on a range of jobnames by date/time. totime requires a todate be specified searching for jobnames. If fromdate is not specified, then only jobnames matching the date and time specified will be reported. Or specify a To Date/Time to report on a range of jobnames by date/time.

GEN Specify a jobname generation number to report nn only those jobnames matching the GEN specified.





9.17.3 REPORT JOBLIST Command Examples The following examples show how to initiate Job List reports in batch mode using procedure BRMBPROC.

Batch JOBLIST Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT JOBLIST JOB(jobname1)

In this example, only one jobname is searched for. If found, the jobname will be displayed.

Batch JOBLIST Example 2:

A second method is to code the same JCL but have more than one jobname in the REPORT JOBLIST command.

//STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT JOBLIST JOB(jobname*) -

DATE(*,2001/02/29)

In this case, any jobname matching 'jobname*' between today and 2001/02/29 will be displayed.

9.17.4 Jobname List Report Example The output for the Jobname List report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Jobname List report is provided on page 7-18.




9.18 NOJOBGRP Report Type – Jobnames Not Tracked By a Job Group Use the NOJOBGRP command to submit a report request for the Jobnames Not Tracked By a Job Group report in batch. Submit the NOJOBGRP command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.18.1 REPORT NOJOBGRP Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT NOJOBGRPJOB( jobname1 …jobnamen | jobmask1 …jobmaskn )

9.18.2 REPORT NOJOBGRP Command Parameter Definitions


Table 9-11: REPORT NOJOBGRP Command Parameter Definitions

REPORT NOJOBGRP PARAMETER

SHORT FORM(S)



NOJOBGRP


Sub-command to create 'Jobnames Not Tracked By a Job Group' report type.

JOB jobname


Specify the jobname(s) or jobname mask(s) to determine if the matching jobname is being tracked by a Job Group.

9.18.3 REPORT NOJOBGRP Command Examples The following examples show how to initiate Jobnames Not Tracked By a Job Group reports in batch mode using procedure BRMBPROC.

Batch NOJOBGRP Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT NOJOBGRP JOB(jobname1)

In this example, only one Jobname is searched for.

9.18.4 Jobnames Not Tracked By a Job Group Report Example The output for the Jobnames Not Tracked By a Job Group report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Jobnames Not Tracked By a Job Group report is provided on page 7-19.




9.19 NOBACKUP Report Type – Reports What Is Not Backed Up Use report NOBACKUP to find out which data sets are not backed up in your environment. This report will help ensure that you aren’t missing critical data sets. The NOBACKUP report compares data sets on your volumes or in your ICF User Catalogs (or both), to the BRM Suite Inventory Data Set, and optionally to the DFSMShsm BCDS. All/Star will identify data sets that are not recorded in either and thus either have not been tracked yet, or do not have a backup.

The following report is a batch-only report and does not follow the same command syntax as the other All/Star reports. This topic describes the full command syntax and parameter descriptions.

To execute this report, you will need to execute the NOBACKUP member of the Backup & Recovery Manager Suite JCL library.

The NOBACKUP report automatically excludes data sets identified in the BRM Suite Inventory Data Set as a backup output file.

The NOBACKUP

Note: You are responsible for the maintenance of the ICF catalogs. If data set entries exist in the catalog but are either no longer on disk, or are cataloged to non-existent volumes, it is considered a catalog maintenance issue. Similarly, if there are disk entries with no associated catalog entry, it is considered a DASD maintenance issue. report identifies these reports, but it does not eliminate them.

9.19.1 REPORT NOBACKUP Command Syntax Multiple lines may be continued by leaving at least one blank after the parameter value and adding either a ' + ' or ' - ' character. The subsequent continued lines may start in any position.

REPORT NOBACKUP TARGET( [ IDS BCDS ] ) { SORTBYNAME | SORTBYVOL }

Optional Parameters

[ SOURCE( source parameters( source criteria ) ) ]

Optional SOURCE Keyword Parameters: (

[ EXCLDSN( dsn1 | dsnmask1 … dsnn | dsnmaskn ) ] [ EXCLUCAT( bcs1 | bcsmask1 …bcsn | bcsmaskn ) ] [ EXCLVOL( volser1 | volsermask1 …volsern | volsermaskn ) ] [ INCLDSN( dsn1 | dsnmask1 … dsnn | dsnmaskn ) ] [ INCLUCAT( bcs1 | bcsmask1 …bcsn | bcsmaskn ) ] [ INCLVOL( volser1 | volsermask1 …volsern | volsermaskn ) ] )




9.19.2 REPORT NOBACKUP Command Parameter Definitions Required parameters are listed first, followed by optional parameters.

Table 9-12: REPORT NOBACKUP Command Parameter Definitions

REPORT NOBACKUP SHORT PARAMETER PARAMETER FORM(S) DEFINITION

Required parameters: REPORT Report command

NOBACKUP Sub-command to create a report of what is not

Default: None backed up.


TARGET BCDS IDS

Default: TARGET(IDS) Required: Yes Restrictions: None

T TARGET is used to identify what the data is compared to: the BRM IDS, the DFSMShsm BCDS, or both. It will compare to all data sets if the optional SOURCE parameter has not been specified. IDS (the default) – the source will be compared to the BRM Inventory Data Set. BCDS – the source will be compared to the DFSMShsm BCDS.

SORTYBYNAME SORTBYVOL

Default: SORTBYNAME Required: Yes Restrictions: SORTBYNAME and SORTBYVOL are mutually exclusive.

SORTYBYNAME – specify this parameter to sort the report by data set name. SORTBYVOL – specify this parameter to sort the report by volume.

Optional parameters: SOURCE

optional source parameters

Default: If SOURCE is not specified, TARGET will be compared to all data sets.

S SOURCE identifies selected data to compare to; either by data set name, by data sets on volsers, or by user catalog. The parameters that can be specified for the SOURCE keyword are described in the 'Optional SOURCE Keyword Parameters' table section

Note: A SOURCE parameter is below. recommended to prevent all data sets on the system from being compared. Without a SOURCE parameter, a report will be created that is too large to use easily.





REPORT NOBACKUP SHORT PARAMETER PARAMETER FORM(S) DEFINITION

Optional SOURCE keyword parameters: INCLDSN EXCLDSN


ID ED

INCLDSN and EXCLDSN allow you to specify data set names to be included/excluded in the compare. Specify fully qualified data set names, or masks using ACS masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). INCLDSN and EXCLDSN can be used in conjunction with INCLUCAT/EXCLUCAT and INCLVOL/EXCLVOL.

INCLUCAT EXCLUCAT


IC EC

INCLUCAT and EXCLUCAT allow you to specify user catalog names to be included/excluded in the compare. Specify fully qualified catalog names, or masks using ACS masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). If this option is used, the user catalog is used as the source and there is no volume lookup. INCLUCAT and EXCLUCAT can be used in conjunction with INCLDSN/EXCLDSN and INCLVOL/EXCLVOL.

INCLVOL EXCLVOL


IV EV

INCLVOL and EXCLVOL allow you to specify volume names to be included/excluded in the compare. Specify fully qualified volume names, or masks using ACS masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). If this option is used, the VTOC is used as the source and there is no catalog lookup. INCLVOL and EXCLVOL can be used in conjunction with INCLDSN/EXCLDSN and INCLUCAT/EXCLUCAT.



------------------------------------------------------


9.19.3 REPORT NOBACKUP Command Examples

NOBACKUP Report Command Example 1

The following example will find all K* data sets excluding KR* data sets on volumes that begin with a T, and an S. It will compare data sets found to the BRM IDS and DFSMShsm BCDS and will provide a report sorted by data set name.

//NOBACKUP JOB ,'BRMBATCH',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*// JCLLIB ORDER=BRM.JCL//NOBACKUP PROC SOUT=*,// LOAD1='&HLQ..LOAD',// PARMLIB='&HLQ..PARMLIB',// IDS='&HLQ..IDS'//NOBACKUP EXEC PGM=AST50100,REGION=0M//STEPLIB DD DISP=SHR,DSN=&LOAD1//INI DD DISP=SHR,DSN=&PARMLIB(BRMINI)//ASTIDS DD DISP=SHR,DSN=&IDS//SYSPRINT DD SYSOUT=&SOUT //REPORT DD SYSOUT=&SOUT //SYSABEND DD SYSOUT=&SOUT //SNAP DD SYSOUT=&SOUT // PEND //REPORT EXEC NOBACKUP //NOBACKUP.SYSIN DD * REPORT NOBACKUP -

SOURCE(INCLDSN(K*) -(EXCLDSN(KR*) -(INCLVOL(T* S*)) -

TARGET(IDS BCDS) -SORTBYNAME

//

Example 1 report output.

********************************* TOP OF DATA ******** ****************************************************** * NO BACKUP FOUND FOR THE FOLLOWING: * * NOTE: "+" = MULTI-VOLUME DATASET * ****************************************************** DATASET NAME VOLSER

KAS.C.TEST1 TSO003 KAS.C.TEST2 TSO001 KAS.C.TEST3 TSO001 KAS.C.TEST4 TSO004

AST50115I TOTAL DATASETS FOUND: 4



------------------------------------------------------



The following example will find all KAS.C.** data sets anywhere on the system except for KAS.C.TEST1, and excluding any data sets found on volser TSO003.


SOURCE(INCLDSN(KAS.C.**) -(EXCLDSN(KAS.C.TEST1) -(EXCLVOL(TSO003)) -

TARGET(IDS BCDS)//


****************************************************** * NO BACKUP FOUND FOR THE FOLLOWING: * * NOTE: "+" = MULTI-VOLUME DATASET * ****************************************************** DATASET NAME VOLSER

KAS.C.TEST2 TSO001 KAS.C.TEST3 TSO001 KAS.C.TEST4 TSO004




------------------------------------------------------



The following example will find all D* data sets in any user catalog that matches the user catalog name mask, USERCAT.** except for USERCAT.UCAT1.


SOURCE(INCLUCAT(USERCAT.**) -(INCLDSN(D*.**) -(EXCLUCAT(USERCAT.UCAT1))-

TARGET(IDS BCDS) -//


****************************************************** * NO BACKUP FOUND FOR THE FOLLOWING: * * NOTE: "+" = MULTI-VOLUME DATASET * ****************************************************** DATASET NAME VOLSER

DCF140.ADCFASM Z4DIS1 DCF140.ADCFIMAG Z4DIS1 DCF140.ADCFMAC Z4DIS1 DCF140.ADCFSAMP Z4DIS1 DCF140.AEDFDOW1 Z4DIS1





9.20 ASAP2BRM-NB Report Type – Critical in ASAP with No All/Star Backup Record Use the ASAP2BRM-NB command to submit a report request for the Critical in ASAP with No All/Star Backup Record report in batch. Submit the ASAP2BRM-NB command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.20.1 REPORT ASAP2BRM-NB Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT ASAP2BRM-NB APPL( applname1 )


[ INCLBCDS ] [ DS( dsname1…dsnamen | dsnamemask1…dsnamemaskn )




9.20.2 REPORT ASAP2BRM-NB Command Parameter Definitions



Table 9-13: REPORT ASAP2BRM-NB Command Parameter Definitions

REPORT ASAP2BRM-NB SHORT PARAMETER PARAMETER FORM(S) DEFINITION



ASAP2BRM-NB Sub-command to create ‘Critical in ASAP with No

Default: None All/Star Backup Record’ report type.


APPL application name


Specify the ASAP application name that a BKUPEND was executed for.


INCLBCDS Specify this parameter to include the BCDS in the

Default: None search for what is not backed up.


DS( dsn )


The data sets read from the application specified will be limited to the data set name or mask identified on this parameter.




9.20.3 REPORT ASAP2BRM-NB Command Examples The following example shows how to initiate Critical in ASAP with No All/Star Backup Record reports in batch mode using procedure BRMBPROC.

Batch ASAP2BRM-NB Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT ASAP2BRM-NB APPL(TEST)

In this example, the data sets from the BKUPEND for Application TEST are compared to the BRM Suite Inventory Database to find a current backup.

9.20.4 Critical in ASAP with No All/Star Backup Record Report Example The output for the Critical in ASAP with No All/Star Backup Record report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Critical in ASAP with No All/Star Backup Record report is provided on page 7-25.

9.21 ASAP2BRM-B Report Type – Critical in ASAP with All/Star Backup Record Use the ASAP2BRM-B command to submit a report request for the Critical in ASAP with All/Star Backup Record report in batch. Submit the ASAP2BRM-B command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.21.1 REPORT ASAP2BRM-B Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT ASAP2BRM-BAPPL( applname1 )


[ INCLBCDS ][ DS( dsname1…dsnamen | dsnamemask1…dsnamemaskn )




9.21.2 REPORT ASAP2BRM-B Command Parameter Definitions



Table 9-14: REPORT ASAP2BRM-B Command Parameter Definitions

REPORT ASAP2BRM-B SHORT PARAMETER PARAMETER FORM(S) DEFINITION



ASAP2BRM-B Sub-command to create ‘Critical in ASAP with

Default: None All/Star Backup Record’ report type.




Specify the ASAP application name that a BKUPEND was executed for.


INCLBCDS Specify this parameter to include the BCDS in the

Default: None search for what is not backed up.


DS( dsn )


The data sets read from the application specified will be limited to the data set name or mask identified on this parameter.




9.21.3 REPORT ASAP2BRM-B Command Examples The following example shows how to initiate Critical in ASAP with All/Star Backup Record reports in batch mode using procedure BRMBPROC.

Batch ASAP2BRM-B Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT ASAP2BRM-B APPL(TEST)

In this example, the data sets from the BKUPEND for Application TEST are compared to the BRM Suite Inventory Database to find a current backup.

9.21.4 Critical in ASAP with All/Star Backup Record Report Example This report describes the data sets found critical in ASAP for which there is a matching backup record in All/Star. The report is by ASAP application and displays the input data set name backed up, output backup data set name, jobname that created the backup, date, time, type of backup, volser of the output data set, and tape location of the output data set if there is one.

Note: All/Star automatically recognizes the tape management systems CA1, TLMS, and RMM. If your tape management system is TLMS, you must change the name of the TLMSDB statement in the BRMBPROC found in the product JCL library from 'NULLFILE' to the TLMS database name. In addition, you must also update the token TLMS_DB, to your TLMS database name found in the product PARMLIB, member BRMINI. For CA1 or RMM, no JCL or INI changes are required.

The output for the Critical in ASAP with All/Star Backup Record report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Critical in ASAP with All/Star Backup Record report is provided on page 7-28.




9.22 BKUPEND Report Type – Backup End Summary Use the BKUPEND command to submit a report request for the Backup End Summary report in batch. Submit the BKUPEND command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.22.1 REPORT BKUPEND Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT BKUPEND APPL( applname ) CYCLE( 0 | n )


[ INCLBCDS ( Y | N ) ]

9.22.2 REPORT BKUPEND Command Parameter Definitions



Table 9-15: REPORT BKUPEND Command Parameter Definitions

REPORT BKUPEND PARAMETER

SHORT FORM(S)




BKUPEND


Sub-command to create ‘Backup-End Summary’ report type.



Specify the application name to perform a Backup-End Summary on.

CYCLE 0 | n

Default: 0 Required: Yes Restrictions: None

Specify a Backup-End Cycle number to report on. n = between 0 and 9999. Default: 0




REPORT BKUPEND PARAMETER

SHORT FORM(S)



INCLBCDS ( Y | N )

Default: N Required: No Restrictions: None

Specify this parameter to search the BCDS for backup records.

9.22.3 REPORT BKUPEND Command Examples The following example shows how to initiate Backup End Summary reports in batch mode using procedure BRMBPROC.

Batch BKUPEND Example 1: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT BKUPEND APPL(TEST) CYCLE(0)

In this example, a summary is produced for Application name TEST cycle 0.

9.22.4 Backup End Summary Report Example The output for the Backup End Summary report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of a Backup End Summary report is provided on page 7-30.




9.23 OVERLAPA-AST Report Type – Overlap by Application Use the OVERLAPA-AST command to submit a report request for the Overlap by Application report in batch. Submit the OVERLAPA-AST command as SYSIN to the BRMBPROC member of the BRM JCL library. This topic describes the full command syntax, and parameter descriptions.

9.23.1 REPORT OVERLAPA-AST Command Syntax Multiple lines may be continued using either the ' + ' or ' - ' characters by leaving at least one blank after the parameter value. Continued lines may start in any position.

REPORT OVERLAPA-AST APPL( applname or mask )

9.23.2 REPORT OVERLAPA-AST Command Parameter Definitions


Table 9-16: REPORT OVERLAPA-AST Command Parameter Definitions

REPORT OVERLAPA-AST PARAMETER

SHORT FORM(S)



OVERLAPA-AST


Sub-command to create 'overlap by application report type.

APPL applname or mask


Specify the applname(s) or applname mask(s) to obtain a data set list which is then used to determine if other applications are tracking the same data set(s). If the same data set is found in other application(s) then the 'Overlap by Application' report will be created.




9.23.3 REPORT OVERLAPA-AST Command Examples The following example shows how to initiate the Overlap by Application report in batch mode using procedure BRMBPROC.

Batch OVERLAPA-AST Example 1:

//STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *REPORT OVERLAPA-AST APPL(applname)

In this example, only one application is searched for overlaps.

9.23.4 Overlap by Application Report Example The output for the Overlap by Application report can be found under the DD name BRMBREPT in the batch SYSOUT. An example of an Overlap by Application report is shown on page 7-32.




Chapter 10 10 BRM Suite: Dynamic Data Set Backup/Reorganization

10.1 About Dynamic Backup/Reorganization This utility will allow the BRM Inventory Data Set to be backed up or reorganized without stopping either ABARS Manager or All/Star product programs. This functionality only applies to documented VSAM data sets used by Mainstar products.

The BACKUP utility is provided to get a clean backup of the BRM Inventory Data Set while ABARS Manager or All/Star programs are executing by 'pausing' them. Without Dynamic Backup, a backup of the BRM Inventory Data Set can result in an ABARS Manager or All/Star program failing because the backup has an enqueue on the Inventory Data Set, therefore preventing the executing program from opening and updating the Inventory Data Set.

Dynamic Reorganization of the BRM Inventory Data Set is accomplished by the REORG utility by temporarily pausing access by ABARS Manager or All/Star programs to the BRM Inventory Data Set. ABARS Manager or All/Star programs in progress during the reorganization will 'pause' until the reorganization is finished.

10.1.1 Usage Considerations If possible, the BRM Inventory Data Set should be backed up or reorganized when the product can be quiesced. A drawback of backing up or reorganizing dynamically is the effect that pausing active product programs may have. On the other hand, the advantage of dynamically reorganizing is that the more often a data set is reorganized, the smaller it will be, and the shorter the backup and reorganization time will be.

Since the ABARS Manager and All/Star programs will pause, the backup or reorganization program should be placed in a schedule where that pause will have minimal impact. Pausing includes ISPF access to data sets. No indications will be displayed when programs executed under ISPF pause due to a backup or reorganization executing.

If for instance, heavy batch use of the Backup & Recovery Manager Suite Inventory Data Set begins late in the evening, scheduling the reorganization program after daytime ISPF access but before batch processing begins will minimize the consequences of access pauses.

A minor danger inherent to the process needs to be assessed. Because the Backup & Recovery Manager Suite Inventory Data Set is reloaded, the data set must be defined with the REUSE attribute. Although this is not a problem for Backup & Recovery Manager Suite to use the Inventory Data Set, care must be taken to ensure a non-Mainstar program does not open the Inventory Data Set for output, or the data set contents will be overlaid.

10.1.2 Product Data Set Applicability Dynamic Backup/Reorganization may be used for the BRM Inventory Data Set only.

Mainstar Software Corporation ©2006 10-1 Chapter 10 SC23-6061-00 BRM Suite: Dynamic Data Set Backup/Reorganization



10.1.3 Lock Data Set The lock data set is the name of a small data set to be used as a permanent lock switch. A lock data set is required and any valid data set name can be specified.

The Reorganization utility will not reorganize the BRM Inventory Data Set without the lock data set defined in the Backup & Recovery Manager Suite PARMLIB member BRMINI, :SI040_VALUES section. Refer to Appendix B, BRMINI Configuration Values of the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062) for information.

Do not create any JCL steps to delete the lock data set. It is for use within the Reorganization program only.

BRM01BRR will, at the start of a Reorganization process, free the lock data set with a DISP=(OLD,DELETE) specification, and then allocate the data set. On successful conclusion, the lock data set is deleted.

10.2 Using the Dynamic Backup/Reorganization Utility The steps below discuss how to use the Dynamic Backup/Reorganization utility. A detailed description of each step is provided in this section.

STEP

1

STEP DESCRIPTION

Modify SI040 tokens in the Backup & Recovery Manager Suite PARMLIB.

2 Use REUSE to reallocate the Backup & Recovery Manager Suite Inventory Data Set.

3 Tailor and execute the backup, reorganization, or reload utility JCL.

10.2.1 Step 1: Modify SI040 Tokens in the Backup & Recovery Manager Suite PARMLIB Modify the tokens in the Backup & Recovery PARMLIB member BRMINI for section :SI040_VALUES. BRMX.INVDB.LOCKDSN = BRMX.INVDB.LOCK.THIS.FILE

LOCKDSN.ATTRIB = STORCLAS(DEFAULT) UNIT(SYSALLDA)

For information regarding these tokens, refer to Appendix B, BRMINI Configuration Values of the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062).

10.2.2 Step 2: Use REUSE to Reallocate the BRM Inventory Data Set 1. Back up the BRM Inventory Data Set.

2. Unload the BRM Inventory Data Set using the UNLOAD utility.

3. Delete the BRM Inventory Data Set.

4. Define a new BRM Inventory Data Set with the REUSE attribute.

5. Load the BRM Inventory Data Set using the LOAD utility.

Chapter 10 10-2 Mainstar Software Corporation ©2006 BRM Suite: Dynamic Data Set Backup/Reorganization SC23-6061-00



10.2.3 Step 3: Tailor and Execute the Backup, Reorganization, or Reload Utility JCL Tailor and execute the backup, reorganization, or reload utility JCL found in the Backup & Recovery Manager Suite JCL members:

• BACKUP – to execute a backup of the Inventory Data Set. • REORG – to reorganize the Inventory Data Set. • RELOAD – to reload the Inventory Data Set previously unloaded in the REORG step.

Note: Although the output of the unload phase of REORG is in essence a backup, you may wish to make your own backup for the first attempt using this facility. The unload data set required to rebuild the BRM Inventory Data Set with the REUSE attribute could satisfy this suggestion.

10.3 Execution JCL

10.3.1 BACKUP The JCL statements are numbered on the left to correlate with the notes found on the following page.

1 //???????? JOB ,'DYNAMIC BACKUP',MSGCLASS=?,CLASS=?2 //IDCAMS1 EXEC PGM=IDCAMS 3 //SYSIN DD *,DCB=BLKSIZE=804 DEL hlq.brm.invdb.unload.data set5 SET MAXCC = 0 6 //SYSPRINT DD SYSOUT=*7 //BRM01BRR EXEC PGM=BRM01BRR,PARM=BACKUP8 //STEPLIB DD DISP=SHR,DSN=hlq.brm.LOAD9 //INI DD DISP=SHR,DSN=hlq.brm.PARMLIB(BRMINI)10 //VSAM DD DSN=hlq.brm.inventory.data set.to.be.backed.up,11 // DISP=SHR 12 //QSAM DD DSN= hlq.brm.invdb.unload.data set,13 // DISP=(,CATLG,CATLG),14 // RECFM=VBS,BLKSIZE=0,LRECL=32760,15 // SPACE=(CYL,(??,??)),16 // UNIT=???? 17 //SYSUDUMP DD SYSOUT=?18 //SYSOUT DD SYSOUT=?




Explanation of JCL Statements by Note Number

NUMBER NOTE DESCRIPTION

1 Job card.

2 EXEC IDCAMS to delete unload data set from previous use. Do not DELETE the unload data set if attempting a RELOAD function.

3 SYSIN for IDCAMS step.

4 DEL control statement for reload data set.

5 SET MAXCC if desired.

6 SYSPRINT output of IDCAMS step.

7 EXEC BRM01BRR – BACKUP utility program name. Parm of BACKUP executes backup function. See the description of each parameter option allowed.

8 STEPLIB DD pointing to Backup & Recovery Manager Suite LOAD library.

9 INI DD pointing to BRM product PARMLIB and BRMINI member. Note the BRMINI member must contain the :SI040_VALUES section token providing an associated lock data set name.

10 VSAM DD pointing to BRM Inventory Data Set to be backed up. Data set must have REUSE attribute.

11 VSAM DD DISP parameter – must be SHR.

12 QSAM DD pointing to unload data set.

13 QSAM DD DISP parameter. The unload data set must be kept and cataloged as it is intended for a subsequent RELOAD function.

14 QSAM DD data set attributes – do not change.

15 QSAM DD space attribute – specify enough space via trial and error and pad for variances in VSAM data set size.

16 QSAM DD unit parameter. Specify a unit or appropriate SMS class information.

17 SYSUDUMP DD statement.

18 SYSOUT DD for program output.




10.3.2 REORG The JCL statements are numbered on the left to correlate with the notes found on the following page.

1 //???????? JOB ,'DYNAMIC REORG',MSGCLASS=?,CLASS=?2 //IDCAMS1 EXEC PGM=IDCAMS 3 //SYSIN DD *,DCB=BLKSIZE=804 DEL hlq.brm.invdb.unload.data set5 SET MAXCC = 0 6 //SYSPRINT DD SYSOUT=*7 //BRM01BRR EXEC PGM=BRM01BRR,PARM=REORG8 //STEPLIB DD DISP=SHR,DSN=hlq.brm.LOAD9 //INI DD DISP=SHR,DSN=hlq.brm.PARMLIB(BRMINI)10 //VSAM DD DSN=hlq.brm.inventory.data set.to.be.reorged,11 // DISP=SHR 12 //QSAM DD DSN=hlq.brm.invdb.unload.data set,13 // DISP=(,CATLG,CATLG),14 // RECFM=VBS,BLKSIZE=0,LRECL=32760,15 // SPACE=(CYL,(??,??)),16 // UNIT=???? 17 //SYSUDUMP DD SYSOUT=?18 //SYSOUT DD SYSOUT=?






1 Job card.

2 EXEC IDCAMS to delete unload data set from previous use. Do not DELETE the unload data set if attempting a RELOAD function.

3 SYSIN for IDCAMS step.

4 DEL control statement for reload data set.

5 SET MAXCC if desired.

6 SYSPRINT output of IDCAMS step.

7 EXEC BRM01BRR – REORG utility program name. Parm of REORG executes REORG function. See the description of each parameter option allowed.


9 INI DD pointing to BRM product PARMLIB and BRMINI member. Note the BRMINI member must contain the :SI040_VALUES section token providing an associated lock data set name.

10 VSAM DD pointing to BRM Inventory Data Set to be reorganized. Data set must have the REUSE attribute.


12 QSAM DD pointing to unload data set.

13 QSAM DD DISP parameter. The unload data set must be kept and cataloged for possible use with the RELOAD function should the process fail.

14 QSAM DD data set attributes – do not change.

15 QSAM DD space attribute – specify enough space via trial and error and pad for variances in VSAM data set size.

16 QSAM DD unit parameter. Specify a unit or appropriate SMS class information.






10.3.3 RELOAD The JCL statements are numbered on the left to correlate with the ensuing notes.

1 //???????? JOB ,'DYNAMIC RELOAD',MSGCLASS=?,CLASS=?2 //BRM01BRR EXEC PGM=BRM01BRR,PARM=RELOAD3 //STEPLIB DD DISP=SHR,DSN=hlq.brm.LOAD4 //INI DD DISP=SHR,DSN=hlq.brm.PARMLIB(BRMINI)5 //VSAM DD DSN=hlq.brm.inventory.data set.to.be.reloaded,6 // DISP=SHR 7 //QSAM DD DSN=hlq.brm.invdb.unload.data set,8 // DISP=OLD 9 //SYSUDUMP DD SYSOUT=?10 //SYSOUT DD SYSOUT=?



1 Job card.

2 EXEC BRM01BRR – RELOAD utility program name. Parm of RELOAD executes RELOAD function. See the description of each parameter option allowed.


4 INI DD pointing to Backup & Recovery Manager Suite PARMLIB and BRMINI member. Note the BRMINI member must contain the :SI040_VALUES section token providing an associated lock data set name.

5 VSAM DD pointing to BRM Inventory Data Set to be reloaded. Data set must have REUSE attribute.


7 QSAM DD pointing to unload data set created from previous reorganization or backup.

8 Disp of OLD – must have been previously created.






10.4 BRM01BRR Parm Values

10.4.1 BACKUP The BACKUP parm directs the program to perform just the unloading of the VSAM DD, or BRM Inventory Data Set. The output, 'QSAM DD', is in key sequence and acceptable as input to a REPRO.

A BACKUP taken using BRM01BRR may be executed while ABARS Manager and All/Star programs are accessing the BRM Inventory Data Set or VSAM DD. ABARS Manager and All/Star programs will pause during the backup. The backup may be 'fuzzy' with respect to groups of records representing an event (an ABARS Manager or All/Star backup event).

10.4.2 REORG The REORG parameter directs the program to perform an in-place reorganization of the BRM Inventory Data Set named by the VSAM DD statement. The program unloads the existing VSAM records in key sequence to the data set named by the QSAM DD statement and then reloads the VSAM data set from the QSAM data set. Reorganization is achieved because of the REUSE attribute that allows 'load mode'.

REORG is only possible if:

1. The BRM Inventory Data Set has the REUSE attribute.

2. The required 'LOCKDSN' token has been added to the BRM product PARMLIB BRMINI member.

Any ABARS Manager or All/Star programs accessing the BRM Inventory Data Set will close the data set and pause until the REORG is finished.

The job stream setup should include a method of notifying the appropriate person if the program ABENDs or ends with a non-zero return code. If the reload phase of the program fails for any reason, ABARS Manager or All/Star programs attempting to access the data set will not function.

Should the reload phase of the program fail, the source of the problem must be ascertained, fixed, and BRM01BRR should be run again with the RELOAD parm.

The work data set used by REORG (QSAM DD) may be used as a backup data set. The data set contents are sufficient to be used as input to a subsequent REPRO. You may want to ensure this data set is allocated on a permanent volume.

10.4.3 RELOAD The RELOAD parameter directs the program to perform the reload phase of a previously attempted REORG. This relies on the QSAM DD data set being retained from a previous execution of REORG.




Chapter 11 11 BRM Suite: DADSMFTK (DAD) Started Task

The DADSMFTK (DAD) started task is used by both the ABARS Manager selectable feature Incremental ABARS and an optional feature in All/Star to track new or changed data in the Data Set Activity Database (DAD).

ABARS Manager – if you have ABARS Manager selectable feature Incremental ABARS licensed, the DAD is used to track new or changed data and must be active.

All/Star – if you have both All/Star and ASAP licensed, and plan to track data set changes, the DAD must be active. Tracking data set changes is optional and is done when optional parameter CHANGED-SINCE-LAST-BKUP-RC is used in the BKUPEND program. The CHANGED-SINCE-LAST-BKUP-RC parameter tracks any data set identified as critical by ASAP that has an associated backup in All/Star but the data set has changed since the last backup. See Chapter 12, All/Star: Application Backup and Restore for more information.

11.1 DADSMFTK Operator Commands DADSMFTK performs real-time data set tracking. It maintains the tracked changes in the Data Set Activity Database (DAD), independent of the VTOC 'change' bit.

DADSMFTK uses the following operator commands: S DADSMFTK,JOBNAME=DADF DAD,AUTOSTARTP DAD

All other DAD subtasks can be manipulated using the DAD ISPF Monitor commands. See the topic 'DAD Monitor (ABARS Manager and All/Star) – Utilities Option 9' (page 2-26).

Mainstar Software Corporation ©2006 11-1 Chapter 11 SC23-6061-00 BRM Suite: DADSMFTK (DAD) Started Task



11.1.1 Start the Started Task (DAD) and Individual Subtasks If you want to start the DAD now, issue console command:

F DAD,AUTOSTART

This command starts the DAD started task and all individual subtasks shown below that are required for the DAD to track new (for Incremental ABARS) and changed (for Incremental ABARS and All/Star) data sets. In general, AUTOSTART is the only command needed to start DADSMFTK. See member DADSMFTK in the BRM Suite JCL library. The member/procedure name is DADSMFTK and the started task name is 'DAD'. All modify commands are based on the identifier 'DAD'.

Note: If you stop and start the DAD and get an ABEND 201, it means the previous shutdown wasn’t normal. Just restart the DAD again.

The only variable within the structure is the dataspace size. The number of buffers is controlled by the Dspc_Buffers token in the :DADSMFTK_OPTIONS section of the BRMINI PARMLIB member. The default size used in AUTOSTART is 1,002 buffers but these should be monitored as more data is tracked to ensure you aren’t losing records.

AUTOSTART issues the following commands: F DAD,U83(LOAD)

F DAD,DSPC(CREATE)

F DAD,U83(TURNON)

F DAD,DAD(START)

F DAD,U83(INFO)

11.1.2 Start the DAD Started Task by Jobname (DAD) and Individual Subtasks The started task can also be started using the JOBNAME= parameter. When starting the DADSMFTK, the target PROCLIB member name must be specified on the start command. See member DADSMFTK in the JCL distribution library. The member/procedure name is DADSMFTK and the started task name is DAD. All modify commands are based on the identifier DAD.

To start the SMF collection main task and associated subtasks at the same time you can use the command:

S DADSMFTK,JOBNAME=DAD,PARM=AUTOSTART or S DADSMFTK,JOBNAME=DAD,PARM=A

Also, if the AutoStart token in the :DADSMFTK_OPTIONS section of the BRMINI member is set to YES, the command S DADSMFTK,JOBNAME=DAD will automatically perform an AUTOSTART.

Chapter 11 11-2 Mainstar Software Corporation ©2006 BRM Suite: DADSMFTK (DAD) Started Task SC23-6061-00



11.1.3 Start the DAD Started Task without the Individual Subtasks S DADSMFTK,JOBNAME=DAD

Starts only the started task. Each individual subtask is NOT started or loaded and will need to be done so separately. See member DADSMFTK in the BRM Suite JCL library. The member/procedure name is DADSMFTK and the started task name is 'DAD'. All modify commands are based on the identifier 'DAD.

We recommend the started task DAD and associated subtasks are started at the same time using the autostart functionality.

11.1.4 Stop the Structure/Terminate DADSMFTK P DAD

Stops the DAD structure and terminates the DADSMFTK via the following commands: F DAD,DAD(STOP)

F DAD,U83(TURNOFF)

F DAD,DSPC(DELETE)

F DAD,U83(UNLOAD)




11.1.5 Manipulate the IEFU83 Exit These commands should be entered only at the direction of Mainstar Technical Support. F DAD,U83(...)F DAD,U83(LOAD)

Acquires ECSA space, loads the primary and secondary exits, and places DAD9254Z in the SYS.IEFU83 exit lists.

Errors include not getting ECSA space, unauthorized LOAD libraries, I/O errors during Load SVCs and problems with the dynamic exit processor.

The installation must have IEFU83 defined as an exit within the SMFPRMxx member of SYS1.PARMLIB. IEFU83 can be added without an IPL. F DAD,U83(UNLOAD)

Removes DAD9254Z from the SYS.IEFU83 exit lists and deletes the ECSA space.

There are interlocks preventing the Unload when the VSAM/DAD sub task is active and when the dataspace still exits. F DAD,U83(TURNON)

Activates the exit in the SYS.IEFU83 exit lists and modifies the primary exit to call the secondary exit. This starts the data collection. The installation must be collecting SMF 14, 15, 61, 64, 65, and 66 records. An additional general purpose IEFU83 exit is available for users who wish to suppress the actual logging of these record types or in fact record types needed by any other IEFU83 exits.

If the primary or secondary exit ABENDs twice, MVS will disable the exit. F DAD,U83(TURNOFF)

Deactivates the exit in the SYS.IEFU83 exit list, and modifies the primary exit to not call the secondary exit. F DAD,U83(INFO)

or F DAD,U83

Displays some information about the state of the exits. The information also shows the creation date of the ECSA. F DAD,U83(NEWSECONDARY)

Under some circumstances, it may be necessary to load a new secondary exit without deleting the dataspace (and its buffers). There are interlocks to prevent this command from working while the exits are active.

Follow these steps to load a new secondary exit:

STEP

1

STEP DESCRIPTION

Copy a new exit (DAD9254R) to the LOAD library.

2 Quiesce the exits using the TURNOFF command.

3 Refresh the code with the F DAD,U83(NEWSECONDARY) command.

4 Activate the exits with a TURNON command.




11.1.6 Manipulate the Dataspace These commands should be entered only at the direction of Mainstar Technical Support. F DAD,DSPC(...)

F DAD,DSPC(CREATE)

or F DAD,DSPC(CREATE(...))

Creates the dataspace that contains the record buffers. The number of buffers, usually 1,002, is controlled by the 'Dspc_Buffers' keyword in the startup parameters. The second allows any number of buffers that requires a dataspace of less than 32MB.

Each buffer is 384 bytes long.

Errors would be that no common dataspaces are available for us to use. This, along with any other error, shouldn't happen, so the diagnostic data would be critical. One exception would be a restart after the DADSMFTK was canceled. See '...DELETE...' for a further description. F DAD,DSPC(DELETE)

Deletes the dataspace.

Errors should not occur, since the dataspace was created, therefore we should be able to delete them. One exception to this is starting the DADSMFTK after it was canceled. DADSMFTK will acquire the ECSA (if it still exists). There may be dataspace information in the ECSA keeping a new dataspace from being created, even though none actually exists. A '...DELETE...' command would detect this condition, and clear the ECSA dataspace indicators allowing a new dataspace to be created. F DAD,DSPC(INFO)

or F DAD,DSPC

Displays some information about the state of the dataspace.




11.2 Removing Obsolete Entries from the DAD Database Data set names are recorded in the DAD database when they are found either to be new (Incremental ABARS) or to have changed (Incremental ABARS and All/Star). Some of these entries in the DAD database become obsolete and should be cleaned up as part of normal maintenance. Obsolete entries can exist in the Data Set Activity Database (DAD) for a number of reasons.

• They are not in the current Base/Incremental (Incremental ABARS). • They are old generation data sets (GDG) that haven't been deleted. For Incremental

ABARS, they are no longer in the current Base/Incremental. • They have been deleted.

The 'PURGE_UNCATLG = Y' parameter in the BRMINI member of the PARMLIB will automatically delete entries from the DAD database when an SMF delete is issued for the data set, but note that the other entries are not deleted automatically.

The DAD9254M JCL member shown below is provided in the BRM Suite JCL library. DAD9254M will remove obsolete entries from the DAD database. Use this program on a regular basis with 'DELETE OLDGDGS' to remove obsolete GDG entries from the DAD database. The DAD database does not need to be reorganized after this is run.

//*******************************************************************//* MAKE THE FOLLOWING CHANGES: //* 1. CHANGE JOB CARD TO LOCAL STANDARDS //* 2. CHANGE PARMLIB= THE BRM PARMLIB NAME //* 2. CHANGE LOAD1= TO THE BRM AUTHORIZED LIB NAME //*******************************************************************//JOBNAME JOB ,'...',CLASS=?,MSGCLASS=? <=== SEE NOTE 1 //DAD9254M PROC PARMLIB=BRM.V3R2xx.PARMLIB, <=== SEE NOTE 2 // LOAD1=BRM.V3R2xx.LOAD <=== SEE NOTE 3 //S1 EXEC PGM=DAD9254M //STEPLIB DD DISP=SHR,DSN=&LOAD1//MSCPARM DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* // PEND //*//DAD9254M EXEC DAD9254M//SYSUDUMP DD SYSOUT=* //SYSIN DD *




The valid control cards are shown below. DELETE OLDGDGS DELETE NOT-IN-CAT DELETE SCRATCHED DELETE NAME(...)DELETE NAME(...) NOT-IN-CATDELETE NAME(...) SCRATCHED

Control Card/Keyword Description

DELETE Required. At least one of the following keywords must also be used.

OLDGDGS Optional keyword. Removes uncataloged GDSs.

NOT-IN-CAT Optional keyword. Removes uncataloged data sets.

SCRATCHED Optional keyword. Removes deleted data sets.

NAME Optional keyword. NAME can be either a masked or a pure DSN. Example of masked NAME: NAME(PAY.WEEK01.G>>>>V00)NOT-IN-CAT




Chapter 12 12 All/Star: Application Backup and Restore

12.1 Application Backup and Restore Additional features are available if both ASAP and All/Star are licensed:

• Ability to compare ASAP critical data set list against All/Star tracked backups. • Ability to restore data sets for ASAP applications and specific cycles within an application.

12.1.1 Comparison of ASAP Critical Data Sets to All/Star Recorded Backups ASAP discovers data sets used by applications as they execute and records them in the ASAP database. ASAP includes various controls to set rules for data set criticality. The resultant list of critical data sets may be used as input to a post-application backup.

In many applications, it may be appropriate to imbed backups in the execution of the application in addition to (or instead of) taking backups after the application batch processing completes. Manually placed backups create a maintenance problem, because one might add a new data set to an application but forget to add the corresponding backup.

A backup might also be placed originally such that it occurs after all modifications, only to become invalid if the application process is altered but the position of the backup is not changed. By using Application Backup and Restore, these data sets can be identified and compared to what was backed up. All/Star also ensures that the recovery JCL/control statements match the utility used for the backup.

When All/Star is used in conjunction with ASAP, at whatever point it is known that application backups should be complete for a given cycle, All/Star can search for backups corresponding to ASAP identified critical data sets. This process will:

• Identify critical data sets for which there is no backup. • Identify critical data sets for which there is a backup and display the output file name and

tape location. • Identify backups that may be invalid because the data set has been modified since the last

backup. • Prove that critical data is backed up. • Match the backups to what is offsite.

Once application backups are properly in place, the process can then be used to alert appropriate personnel if an application change has occurred that invalidates the intended backup strategy.

12.1.2 About Restore by Application Restoring by application is often the preferred way to restore data sets in the event of a disaster. Even for the loss of a single data set, it is often necessary to restore all data sets used by the application to cover the situation where multiple data sets must be in synch with each other. It may also be necessary to 'rewind' the application back to something other than the last cycle executed.

All/Star, when used in conjunction with ASAP, saves the critical data set list in All/Star for as many application cycles as desired, (as described below in 'ASAP Options When Using All/Star to Track and Restore by Application', page 12-2) with the backup information appropriate for the cycle. This process permits the restore of the data sets involved with a particular application cycle.

Mainstar Software Corporation ©2006 12-1 Chapter 12 SC23-6061-00 All/Star: Application Backup and Restore



12.2 Restore by Application Process Flow When ASAP is used in conjunction with All/Star to track and allow restoration by application, the flow of events is as follows:

1. Application runs with the ASAP started task, RSP, tracking the referenced data sets.

2. Application completes and an ASAP APPLEND program is executed to signal the end of the application cycle.

Unless overridden by options, APPLEND increments the current cycle number, builds database records for the just-completed cycle while applying any filters, and creates a 'selection data set' or list of data sets which may either be used to drive a post-application cycle backup or be used by BKUPEND to verify that all data sets in the list were backed up in-stream.

3. All/Star BKUPEND program executed.

BKUPEND copies the list of ASAP critical data sets to the Backup and Recovery Manager Suite Inventory Data Set (BRM IDS) while adding the backup information. This process allows recovery by application. An exception report will indicate any data sets for which no backup is found, and if the optional CHANGED_DATASET_TRACKING token in the BRMINI is set to Y, and the DAD started task is up, the report will indicate that although a backup is found, it may be out of date because the data set has changed since the last backup. For example, if BKUPEND is executed at a time when the application data should all be backed up but it is discovered that a data set change has been made, the backup is no longer current. The application could be 24x7, or it could signal that the BKUPEND is in the wrong place. A user may choose return codes to trigger an alert if a backup integrity problem is detected.

12.3 ASAP Options When Using All/Star to Track and Restore by Application The following ASAP options are available to use with All/Star's ability to track and restore by application.

The BACKUP CYCLES TO RETAIN parameter (found in ASAP on the Application SETUP Options panel) defines how many All/Star application cycles will be tracked by All/Star in the Backup & Recovery Manager Suite Inventory Data Set. Whereas the ASAP option (as defined by: Number of RSP Cycles to Retain and Number of JCL Cycles to Retain – found in Option 0 – Setup) allows nn cycles to be tracked, All/Star tracks cycles including the backup information found for each critical data set discovered by ASAP, hence allowing restoration of the data sets peculiar to a given application cycle. The cycle numbers do not need to be the same. Frequently, the ASAP cycle is only required until the next application cycle executes, whereas the All/Star BACKUP CYCLES TO RETAIN can be used for as many application backup cycles as desired.

These records are

i

NOTE: ASAP’s option to track more than one cycle only affects how many cycles' worth of raw input (i.e. SMF and JCL information) are saved in the ASAP database. called Data Set Detail records (DSD). If in the ASAP Application AutoBuild Options menu, Option 0 – Setup, the cycles ("Number of RSP cycles to retain" "Number of JCL cycles to retain"), are set higher than one (in general 1 is used and is not the number of application backup cycles tracked by All/Star), the DSD records for the various cycles are combined, and analyzed, and the result is the creation of Data Set Records (DSR). These records are built for the last cycle completed, and reflect the results of Opt on 0 – Setup Options, and filters. They are used to generate a selection data set (list of data sets). At any time, only one version of the DSR records exist.

Chapter 12 12-2 Mainstar Software Corporation ©2006 All/Star: Application Backup and Restore SC23-6061-00



12.3.1 EXCL_BUT_CRITICAL Filter When ASAP is used to create a selection data set in order to drive a post-application backup, it is typical to use EXCLUDE filters to exclude data sets from the backup because the backups are accomplished elsewhere, such as when they are imbedded in the application or another application is backing up the data set.

However, when the All/Star program BKUPEND is run, one of the program's valuable features is to discover and display any critical data sets that are not backed up. For this comparison to encompass all critical data sets, including those you don’t want in a post-application backup, it will be necessary to use EXCL_BUT_CRITICAL to exclude data sets from the selection data set, yet allow them to be compared to All/Star’s discovery of data set backups, and/or if you wish to use the All/Star Application Backup and Restore feature.

Note: For users with existing ASAP applications, change any EXCLUDE filters to EXCL_BUT_CRITICAL filters if the data sets are backed up somewhere else and the BKUPEND exception report is desired, and/or if you wish to use the All/Star restore by application feature. This step won’t be necessary if you already solved the problem by excluding your backup jobs from the ASAP job list.

12.4 About the BKUPEND Program BKUPEND copies the list of ASAP critical data sets to the Backup and Recovery Manager Suite Inventory Data Set (BRM IDS) while adding the backup information. An exception report will indicate any data sets for which no backup is found, and if the DAD option (CHANGED_DATASET_TRACKING=Y) is used, the report will indicate that although a backup is found, it may be out of date because the data set has changed since the last backup. A user may choose return codes to trigger an alert if a backup integrity problem is detected.

The All/Star BKUPEND program: • locates and matches backups to application critical data sets discovered by ASAP. • saves the list of critical data sets, along with the pertinent backup information, by ASAP

application name (APPL) in the Backup & Recovery Manager Suite Inventory Data Set. • produces a report indicating whether all backups were found. Also, optionally, the report will

indicate whether any data set backups are out of date because the data set changed since the last backup.

• provides return codes a user can set if an alert is desired if not all backups are found or they appear to be out of date.




12.4.1 BKUPEND Execution Placement The All/Star BKUPEND program must be executed after the ASAP APPLEND has been executed for each application and at the point in time when you know all backups associated with the just-completed application cycle should have completed. If all backups are imbedded in the application, BKUPEND can be placed immediately after the APPLEND. If some or all data sets are backed up after the application completes (i.e. after APPLEND), place BKUPEND after the last of all backups are finished.

Take care not to execute more than one BKUPEND for each application cycle but be sure to execute BKUPEND for each application cycle because this is the only opportunity for All/Star to save the list of critical data sets and their associated backups.

NOTE: If a BKUPEND is executed more than once for the same ASAP Application and Cycle, the matching BKUPEND is replaced, and an RC4 is issued with the following messages: AST40109W ASTBKEND A BKUPEND FOR THE CURRENT ASAP APPLICATION AST40109W ASTBKEND AND CYCLE WAS FOUND AND WILL BE REPLACED AST40109W ASTBKEND BY THIS BKUPEND

If the BKUPEND report indicates that some backups are not found, or are out of date, BKUPEND may have been executed prematurely.




12.5 The BKUPEND Command The BKUPEND command provides a summary report in the SYSOUT from the BKUPEND job to identify critical data sets with no backup found. Use the following keywords to control the program return code and whether the associated messages are Informational, Warnings, or Errors.

Table 12-1: BKUPEND Command Parameter Definitions

BKUPEND SHORT PARAMETER PARAMETER FORM(S) DEFINITION


BKUPEND The BKUPEND report provides a list of critical data sets with no backup found. Backups may not be found for various reasons: − if a data set backup was missed so no backup exists

for a data set. − if the BKUPEND was run before the backups

completed. − if a new step or job was added that interfered with

BKUPEND. − if the backup failed. In this case, fix the backup and

run another BKUPEND.

APPL( name ) Specify an ASAP application name that a BKUPEND

Default: None should be performed for.

Required: Yes Restrictions: No masks allowed. Absolute name only.


NO-BKUP-FOUND-RC Specify whether a return code of 0, 4, or 8 should be ( 0 | 4 | 8 )

Default: None Required: No

generated if any data set identified as critical in ASAP does not have a corresponding backup in All/Star. The message AST40210 will be generated if at least one not-found backup is encountered. The message will be

Restrictions: None suffixed with an I, W, or E, depending on whether a return code of 0, 4, or 8 is selected.

BAD-BKUP-RC(0–9999)


If the RC from any backup found is greater than or equal to the RC specified, warning message, AST40212E will be issued.




BKUPEND SHORT PARAMETER PARAMETER FORM(S) DEFINITION

CHANGED-SINCE-LAST-BKUP-RC( 0 | 4 | 8 )


NOTE: This option requires the change tracking feature. This is accomplished by: 1. Defining a DAD database. For more information, refer to Chapter 9, BRM Suite: Set Up DADSMFTK Started Task (DAD), in the Backup and Recovery Manager Suite Installation and Maintenance Guide. 2. Setting the PARMLIB BRMINI token CHANGED_DATASET_TRACKING to Y. 3. Starting the DADSMFTK (DAD) started task.

Specify whether a return code of 0, 4, or 8 should be generated if, during BKUPEND, any data set identified as critical by ASAP has an associated backup in All/Star but the data set has changed since that backup (the last backup). For example, BKUPEND is executed at a time when the application data should all be backed up, however if it is discovered that a data set change has been made, the backup is no longer current. The application could be 24x7, or it could signal that the BKUPEND is in the wrong place. The message AST40211 will be generated if at least one backup is encountered where the data has since changed. The message will be suffixed with an I, W, or E, depending on whether a return code of 0, 4, or 8 is selected. If you are using this option, monitor the size of the DAD database to ensure it is large enough. You will also need to be sure to delete old/invalid records out of the DAD on a regular basis.

NOTE: Data sets from Full Volume Physical Dumps are excluded from this process and not added to the DAD when BRMINI token CHANGED_DATASET_TRACKING = Y.




BKUPEND SHORT PARAMETER

PARAMETER FORM(S) DEFINITION

EXCL-ACCOMPANY This option prevents BKUPEND from looking for a backup in the BRM Inventory Data Set for any ASAP critical data

Default: None set classified in the ASAP application as an ABARS Required: No ACCOMPANY (see the Backup and Recovery Manager

Suite User Guide: ASAP (document SC23-6059) for more Restrictions: None information). If ASAP builds backup control statements (a selection data set) for any utility other than ABARS, data sets classified as ACCOMPANY are switched to an INCLUDE if the utility isn’t ABARS. In this scenario, there isn’t any point in classifying tapes as ACCOMPANY because they end up being copied by other means; nevertheless, BKUPEND should find a backup in All/Star. To avoid misleading 'no backup found' errors in BKUPEND, specify EXCL-ACCOMPANY if you have classified any tape data sets via ASAP as an ABARS ACCOMPANY, but don’t back them up or ACCOMPANY them via an ABARS backup tracked by ABARS Manager. ACCOMPANY is an ABARS term for tape data sets that you do not want copied because your intent is to transport (physically or perhaps by electronic vaulting) the original to a disaster recovery site. This might be done for tapes that may be needed for disaster recovery or simply to archive them even though there may not be a normal need for a local recovery. For tapes classified as an ABARS ACCOMPANY in ASAP, if ASAP builds an ABARS selection data set, the tape data set names are created within the ABARS ACCOMPANY keyword. ABARS does not copy ACCOMPANY data sets but does include the data set names in the control information created during the ABARS backup. If an ABARS backup is tracked by ABARS Manager, the BRM Suite Inventory Data Set will contain an entry indicating that the tape data set was indeed 'accompanied' and BKUPEND will find the match in the BRM Inventory Data Set.




BKUPEND PARAMETER

SHORT FORM(S)


EXCL-ALLOCATE


This option prevents BKUPEND from looking for a backup in the BRM Inventory Data Set for any ASAP critical data set classified in the ASAP application as an ABARS ALLOCATE (see the Backup and Recovery Manager Suite User Guide: ASAP (document SC23-6059) for more information). If ASAP builds backup control statements (a selection data set) for any utility other than ABARS, data sets classified as ALLOCATE are switched to an INCLUDE if the utility isn’t ABARS. The data set is in fact backed up and BKUPEND should find the backups in All/Star. To avoid misleading 'no backup found' errors in BKUPEND, specify EXCL-ALLOCATE if you classify any data set via ASAP as an ALLOCATE, but don’t back them up or ALLOCATE them via an ABARS backup tracked by ABARS Manager. Data sets identified by ASAP as critical may be categorized as ALLOCATE, as opposed to INCLUDE. A typical scenario where ASAP will categorize a data set as ALLOCATE is when the first usage of an existing data set (e.g. DISP OLD) is for output. Because the first usage of the data set is to write over existing data, to save backup time, the data set merely needs to be allocated for a rerun to satisfy the initiator expecting to find it (DISP OLD). If ASAP generates a selection data set in the ABARS format, ALLOCATE data sets are placed within the ABARS ALLOCATE keyword because ABARS has the functionality to collect and save the attributes of a data set so it can allocate the data set during a recovery. If ASAP generates a selection data set for a utility that doesn’t support ALLOCATEs, they are changed to INCLUDEs. If you have ASAP critical data sets marked as ALLOCATE, and ABARS is used and tracked by ABARS Manager, BKUPEND will match them to the All/Star record.

12.6 Executing BKUPEND The BKUPEND program is executed in batch using JCL member BKUPEND, found in the Backup & Recovery Manager Suite JCL library.

Example: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *BKUPEND APPL(BKTEST01)

NO-BKUP-FOUND-RC(4) ---BAD-BKUP-RC(9999)

CHANGED-SINCE-LAST-BKUP-RC(4)




12.7 How to Use Application Backup and Restore After both All/Star and ASAP are licensed and configured, follow these steps to create Application Backup & Restore. Each step is described in more detail in following topics.

STEP STEP DESCRIPTION

1 Create All/Star Batch Intercept File (BIF) Filters.

2 Edit BRM Suite BRMINI PARMLIB Member.

3 Modify the BRM Suite BRMBPROC JCL Member.

4 Implement the All/Star ASTEXPIRE Command.

5 Define an Application to ASAP. • Set the BACKUP CYCLES TO RETAIN in Option 0 – SETUP • Optionally create EXCL_BUT_CRITICAL filters

6 Run the Application.

7 Run the ASAP APPLEND Program.

8 Run the All/Star BKUPEND Program.

12.8 Step 1: Create All/Star Batch Intercept File (BIF) Filters Create the All/Star batch intercept file (BIF) filters via the ISPF facility to enable the started task, AST, to track the application backups you are interested in. Because the intercept mechanism tracks only those jobs/steps/program names identified by the batch intercept file (BIF) entries, it is necessary to first create BIF entries. There are two ISPF panels, one for BIF INCLUDES, and one for BIF EXCLUDES. For more information, see 'Build Batch Intercept File and Refresh AST – Sub-Option 6' (page 3-9).




12.9 Step 2: Edit BRM Suite BRMINI PARMLIB Member Add the ASAP database name to the BRM Suite BRMINI PARMLIB member so All/Star can interface with ASAP.

• Edit the BRM Suite BRMINI PARMLIB member. • Locate the :PRODUCT_DATASETS section. • Add the ASAP database name to token: ASAP_DATABASE =

12.10 Step 3: Modify the BRMBPROC JCL member Add the ASAP database name to the BRM Suite batch procedure, BRMBPROC. BRMBPROC is used to execute the ASTEXPIRE and BKUPEND commands.

• Edit the BRMBPROC batch procedure found in the BRM Suite JCL library. • Change ASAPDB=’NULLFILE’ to the name of the ASAP database. • If your BRMBPROC (found in the product JCL library) does not have an ASADB =

‘NULLFILE’ or the ASAPDB DD statements shown in the example below, then replace ‘NULLFILE’ with the name of your ASAP database.

********************************* Top of Data ************************//BRMBPROC PROC SOUT=*,// LOAD1='&HLQ..LOAD',// PARMLIB='&HLQ..PARMLIB',// DAD='NULLFILE', <== USED FOR INCREMENTAL // BKLEVEL='NULLFILE', <== USED WITH PREVENT_BACKLEVEL// ASAPDB='NULLFILE', <== USED FOR ASAP INTERFACE // IDS='&HLQ..IDS'//BRMBATCH EXEC PGM=BRMBMAIN,PARM='BRMFUNC',REGION=0M,TIME=1440//STEPLIB DD DISP=SHR,DSN=&LOAD1//INI DD DISP=SHR,DSN=&PARMLIB(BRMINI)//SYSTSPRT DD SYSOUT=&SOUT //BRMIDS DD DISP=SHR,DSN=&IDS//DADHHATT DD DISP=SHR,DSN=&DAD <== USED FOR INCREMENTAL //BKLEVEL DD DISP=SHR,DSN=&BKLEVEL <== USED WITH PREVENT_BACKLEVEL//ASAPDB DD DISP=SHR,DSN=&ASAPDB <== USED FOR ASAP INTERFACE //SYSPRINT DD SYSOUT=&SOUT //BRMBREPT DD SYSOUT=&SOUT //SYSOUT DD SYSOUT=&SOUT //SYSABEND DD SYSOUT=&SOUT




12.11 Step 4: Implement the All/Star ASTEXPIRE Command If you have not done so already, the All/Star ASTEXPIRE command must be scheduled on a regular basis to remove old backups tracked by All/Star from the BRM Inventory Data Set. In addition to removing old backups, ASTEXPIRE should be set up to remove old application cycles when using Application Backup and Restore. ASTEXPIRE removes old application cycles as defined by the BACKUP CYCLES TO RETAIN parameter (found in ASAP on the Application SETUP Options panel).

The ASTEXPIRE command is submitted using job ASTEXPIR found in the Backup & Recovery Manager Suite JCL library. For more information, see Chapter 9, All/Star: Batch Processing & Output.

Update ASTEXPIR JCL with the ASAP database name as shown in the example below

********************************* Top of Data ************************//ASTEXPIR JOB ,'BRMBATCH',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*// JCLLIB ORDER=BRM.JCL//******************************************************//* EXPIREV AST CYCLES//******************************************************//* CHANGE JOB STATEMENT TO LOCAL STANDARDS * //* CHANGE JCLLIB STATEMENT TO CORRECT JCLLIB NAME * //* CHANGE ALL &HLQ. TO HLQ FOR YOUR PRODUCT LIBS * //******************************************************//BRM EXEC BRMBPROC,// LOAD1='BRM.LOAD',// PARMLIB='BRM.PARMLIB',// ASAPDB='ASAP.ASAPDB', <= ASAP DATABASE NAME // IDS='BRM.IDS' //BRMBATCH.SYSIN DD * ASTEXPIRE




12.12 Step 5: Define an Application to ASAP To create an interface between ASAP and All/Star, and provide application backup and restore capability, define the application to ASAP by performing the following steps:

1. Define an application to ASAP To define an application to ASAP, see the Backup and Recovery Manager Suite User Guide: ASAP (document SC23-6059), Chapter 1, ASAP Overview. Chapter 1 contains step-by-step instructions on setting up an application for either forward or rerun recovery. Important Note: When setting up an ASAP application in Option 0 – Setup, the GDS Names in Selection Data Set panel option found in the VERIFICATION GDG Options section must be set to either Absolute or Both because relative generations cannot be resolved.

2. Set the BACKUP CYCLES TO RETAIN parameter The BACKUP CYCLES TO RETAIN parameter (found in ASAP on the Application SETUP Options panel) defines how many All/Star application cycles will be tracked by All/Star in the Backup & Recovery Manager Suite Inventory Data Set. For more information, see the Backup and Recovery Manager Suite User Guide: ASAP (document SC23-6059) Chapter 1, ASAP Overview.

3. Optionally create EXCL_BUT_CRITICAL filters Data sets excluded from an ASAP application but considered critical during restore should be added to the ASAP application EXCL_BUT_CRITICAL filter. These could be data sets backed up by other applications yet required when restoring this application. Or these could be data sets excluded from backup because the backup was imbedded in the application. For more information, see the Backup and Recovery Manager Suite User Guide: ASAP (document SC23-6059), Chapter 10, Using Filters and Controls.

12.13 Step 6: Run the Application After all the setup options have been done, run the application you wish to collect data set records for. This step assumes that the ASAP RSPSMFTK (RSP) started task is up, the application has been defined, and the ASAP Job Collection has been completed.

12.14 Step 7: Run the ASAP APPLEND Program When the application cycle completes, run the ASAP APPLEND program found in the ASAP JCL library to signal the end of the application cycle.

Unless overridden by options, APPLEND increments the current ASAP cycle number (as defined by Number of RSP cycles to retain and Number of JCL cycles to retain – found in Option 0 – Setup), builds database records for the just-completed application cycle while applying any filters, and creates a 'selection data set' which may either be used to drive a post-application cycle backup or be used by BKUPEND to verify that all data sets in the list were backed up in-stream.

For more information on APPLEND, see the Backup and Recovery Manager Suite User Guide: ASAP (document SC23-6059), Chapter 7, Real Time Selection Process (RSP).




12.15 Step 8: Run the All/Star BKUPEND Program The BKUPEND program must be executed after the ASAP APPLEND program for each application that has completed, and at the point in time when you know all backups associated with the just-completed application cycle should have completed. If all backups are imbedded in the application, BKUPEND can be placed immediately after APPLEND. If some or all data sets are backed up after the application completes (i.e. after APPLEND), place BKUPEND after the last of all backups are finished. The BKUPEND program can be found in the BRM Suite JCL library, member BKUPEND.

First, review the BKUPEND parameters in the topic 'The BKUPEND Command' (page 12-5). Determine which BKUPEND parameters you wish to use and include them in the BKUPEND job found in the BRM Suite JCL library. If you have decided to use the CHANGED-SINCE-LAST-BKUP-RC(n) parameter, follow the setup steps below before executing BKUPEND.

Example: //STEPNAME EXEC BRMBPROC//BRMBATCH.SYSIN DD *BKUPEND APPL(BKTEST01) -

NO-BKUP-FOUND-RC(4) -BAD-BKUP-RC(9999) -CHANGED-SINCE-LAST-BKUP-RC(4)

/*

12.15.1 CHANGED-SINCE-LAST-BKUP-RC Optional Parameter Setup Steps If during BKUPEND, you wish to use the CHANGED-SINCE-LAST-BKUP-RC parameter, additional steps need to be put in place before you can include the keyword in the BKUPEND job.

1. Set up the DADSMFTK (DAD) started task. See Chapter 9, BRM Suite: Set Up DADSMFTK (DAD) Started Task of the Backup and Recovery Manager Installation and Maintenance Guide.

2. Set the token CHANGED_DATASET_TRACKING to Y in the product PARMLIB member BRMINI.

3. Start the DADSMFTK (DAD) started task. For more information, see the topic 'DADSMFTK Operator Commands' (page 11-1).

4. Add CHANGED-SINCE-LAST-BKUP-RC parameter to the BKUPEND job found in the BRM Suite JCL library.

After the steps above have been set up, when the actual backups run, the data set names found in the backups are added to the Data Set Activity Database (DAD) for changes to be tracked.

NOTE: Data sets from Full Volume Physical Dumps are excluded from this process and not added to the DAD when BRMINI token CHANGED_DATASET_TRACKING = Y.

The RC specified in the CHANGED_DATASET_TRACKING parameter is what the final RC of BKUPEND will be if a data set has been changed since the last backup.




Chapter 13 13 All/Star: Build Restore

13.1 The Build Restore Process The build restore program builds restore JCL and restore utility control statements from one or more specified backups, previously tracked by the All/Star Started Task (AST), and recorded in the Backup & Recovery Manager Suite Inventory Data Set (BRM IDS).

Restore JCL/control statements can be created by selecting from All/Star the backups you want to restore. Backups are selected by one of the five categories allowed by the build restore (BLDREST) command:

• JOBNAME – Backups are tracked within All/Star by the Job/Step/Utility that created the backup, with alternate keys created to locate any backup by data set name.

• JOBGROUP – JOBGROUPs may be optionally created to associate a group of backup jobs. • DSN – For every data set backup tracked by the AST started task, data set attributes are

collected at the time of the backup and saved in the BRM IDS. Attributes are retained to allow queries and to generate restore JCL/control statements. Each attribute is assigned a variable name for subsequent reference in a restore skeleton.

• VOL – Full volume backups are tracked by volume serial number. It is recommended that full volume dumps be done in restores separate from any other kind of backups.

• APPL – ASAP application cycle is added to the BRM Suite Inventory Data Set by executing the BKUPEND command.

The build restore program, ASTBLDRJ, creates the restore JCL/control statements using generic 'skeletons'. Skeletons contain model JCL and control statements, with variables for any values specific to a given backup to be restored. The build restore process creates tailored output files that contain the restore JCL. The restore JCL is created by substituting the data set attributes (such as blksize, etc.) stored in the BRM Suite Inventory Data Set for the backups in place of skeleton variables.

The BLDREST command checks the catalog before building the restore JCL to ensure that the backup is on the same volume as it was at the time of backup. If it was stacked, the new information is used when building the restore.

The ASTBLDRJ program is submitted using the restore procedure, BRMRPROC found in the BRM Suite JCL library. For more information about skeletons or to create your own skeletons, refer to Appendix A, All/Star: Skeleton Processing and Skeleton Variables.

The JCL/control statement requirements for restoring a backup vary, depending on the backup utility used. A common and obvious need is to swap the input and output data set names. Some utilities track the original allocation attributes, and allocate target data sets on a restoration. Other utilities require the restore to include the allocation of the target data set. Non-SMS managed data sets may require that the restore be made to different volumes than the original volume locations.

Rules:

• Multiple commands in a backup step: Each backup command will result in one output step. For example, a backup achieved with an IDCAMS execution containing 3 REPRO commands will result in 3 steps in the output JCL member, each containing one REPRO command to accomplish the restore.

• Partial multivolume data sets from full volume dumps: If restoring from full volume dumps, partial restores of multivolume data sets could result. It is the user’s responsibility to determine if all parts of a multivolume data set are present, to determine the sequence, recatalog them and build PATHs if necessary.

Mainstar Software Corporation ©2006 13-1 Chapter 13 SC23-6061-00 All/Star: Build Restore



• Non-existent generations: If during restore, a data set generation is specifically requested and the generation does not exist, the job will issue a message "Requested Generation Not Found".

• Duplicate data sets: During restore, All/Star checks for duplicate data sets within a command and restores only the latest version. This check prevents restoring the same data set multiple times.

• Multiple restores from the same input tape: If your restore job has multiple steps using the same volume as input, VOL=RETAIN will keep it mounted until the job ends.

• Disaster recovery note: If you are licensed for All/Star, the All/Star started task is required to be up and active at the disaster recovery site. The All/Star started task provides common services for All/Star backups as well restores. If you wish to stop the tracking of backups, but allow the build of the restores, issue the following command on each image where the started task ASTSMFTK (AST) is active: F AST,TURNOFF

13.2 How to Build and Submit a Restore The restore takes place in two steps:

1. Build the restore JCL.

2. Submit the restore JCL.

13.2.1 Step 1 – Build the Restore JCL 1. The build restore program and commands build the actual restore JCL for the utility or utilities

that backed up the data. The build restore commands control the maximum number of steps per job you want generated, the restore jobnames to generate, whether you want to restore by DSN, VOLUME, JOB, JOBGROUP, or APPL, etc. The build restore program, ASTBLDRJ, is executed using procedure BRMRPROC, found in the product JCL library. • Modify BRMRPROC to set up a default JCLOUT statement. Statement JCLOUT specifies

the library where the build restore stores the generated restore JCL. • JCLOUT can be overridden as shown in the example below.

2. When the build restore, BLDREST command is submitted, the build restore program uses skeletons that contain model JCL and control statements to build the restore JCL for the restore utilities. • The default skeleton JCL for each utility can be found in the product SKELLIB library and

should not be replaced or they will be written over during the next install. • You can create your own skeleton defaults using different names if desired (for more

information, see Appendix A, All/Star: Skeleton Processing and Skeleton Variables). • The default skeleton JCL you want to be used for each utility is set in the BRM Suite

PARMLIB(BRMINI) member. They are shipped with product defaults. • Skeletons JCL can also be specified in the BLDREST command by specifying the SKEL

command.

Chapter 13 13-2 Mainstar Software Corporation ©2006 All/Star: Build Restore SC23-6061-00



Example 1 – Build Restore:

In the example below, a build restore command (BLDREST) by JOBNAME was selected using job ASTBJA10. Instead of restoring all of the data sets backed up within JOBNAME(ASTBJA10), the INCLDSN statement is used to select a specific data set for restore. The restore JCL will be built for the data set using the skeleton JCL found in the BRM Suite SKELLIB for the utility that backed it up. The restore JCL will be created in the PDS data set pointed to by JCLOUT=’BRM.RESTORE’ and the member the restore JCL will be stored in is ASTREST. The jobname specified for the actual restore job is RESTBRM.

For disaster recovery preparation, this step can be set up onsite while submitted to do the actual restores when you arrive at the disaster recovery site.

The build restore command syntax can be found in 'The Build Restore Commands' (page 13-5).

//BLDRJ EXEC BRMRPROC,// LOAD1='BRM.LOAD',// PARMLIB='BRM.PARMLIB',// SKELLIB='BRM.SKELLIB',// JCLOUT='BRM.RESTORE',// IDS='BRM.INVDB' //BUILDRJ.CONTROL DD *JOBNAMEOUT RESTDSN MEMBEROUT ASTREST STEPLIMITOUT 255 BLDREST JOBNAME(ASTBJA10)

INCLDSN(BRMI.AST.IVPAST1.NOBKP.DATASET

GEN(0))

INCLPHYDUMP(NO)REPLACE(NO)COPY(1 )

Example 2:

Executing the build restore program and overriding the JCLOUT data set, and the default skeleton library member for the DFSMSdss utility using the SKEL command of BLDREST.

//BLDRJ EXEC BRMRPROC,// LOAD1='BRM.LOAD',// PARMLIB='BRM.PARMLIB',// SKELLIB='BRM.SKELLIB',// JCLOUT='BRM.RESTORE.DATASET',// IDS='BRM.INVDB' //BUILDRJ.CONTROL DD *JOBNAMEOUT RESTDSN MEMBEROUT ASTREST STEPLIMITOUT 255 BLDREST JOBNAME(ASTBJA10)

INCLDSN( --

-BRMI.AST.IVPAST1.NOBKP.DATASET ) -

GEN(0) -INCLPHYDUMP(NO) -REPLACE(NO) -COPY(1 ) -SKEL(DSSLOG)




13.2.2 Step 2 – Submit the Restore JCL To submit the restore JCL, edit the PDS library you specified in JCLOUT, find the member you specified in MEMBEROUT, and submit the job to restore the data.

Example - The data set being restored was backed up by ABARS. Therefore, the ABARS Skeleton JCL was used to create the restore syntax. If the data set had been backed up by DFSMSdss, the DFSMSdss skeleton JCL would have been used and DFSMSdss restore JCL would have been created instead. The same occurs for all utilities.

BRM.RESTORE.DATASET(ASTREST) - 01.00 Columns 00001 ===> Scroll ===> CSR ***************************** Top of Data ******************************//BRMREST JOB ,'ALL/STAR RESTORE',CLASS=A,MSGCLASS=X,// NOTIFY=&SYSUID,REGION=0M//***********************************************//* RECOVER DATA SETS THAT WERE BACKED UP WITH //* ABARS. //* USER MUST HAVE RACF AUTHORIZATION //* TO EXECUTE THE ARECOVER FOR THE SPECIFIC //* AGGREGATE AS WELL AS UPDATE AUTHORITY TO //* THE DATA SETS BEING RECOVERED //***********************************************//BRMB1 EXEC PGM=BRMBMAIN,PARM='BRMFUNC',REGION=0M,TIME=1440//STEPLIB DD DISP=SHR,DSN=BRM.LOAD//INI DD DISP=SHR,DSN=BRM.PARMLIB(BRMINI)//BRMIDS DD DISP=SHR,DSN=BRM.INVDB//SYSTSPRT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSABEND DD SYSOUT=* //SNAP DD SYSOUT=* //SYSIN DD *ARECOVER AG(IVPAST1) -

VEREXE -GEN(0) -COPYSET(1) -DATASETCONFLICT(BYPASS) -TERMMSGS(YES) -NOSTACK -AGGENQ(Y) -XMIT -

INCLUDE( -BRMI.AST.IVPAST1.NOBKP.DATASET -)




13.3 The Build Restore Commands When executing the build restore (BLDREST command), at least one JOBNAMEOUT and at least one MEMBEROUT command must be included before the first BLDREST command. Use the JOBNAMEOUT command to specify the name(s) of the restore jobs to be executed. Use the MEMBEROUT command to specify the name(s) of the job JCL members that will be generated. STEPLIMITOUT, INCRJOBNAMEOUT, INCRMEMBEROUT are optional.

fact it is a restore.

WARNING: Backup jobnames should NOT match restore jobnames. Non-DFSMSdss and FDR type utilities such as IDCAMS REPRO could be tracked and considered a backup when in

The backup generation results stored in the Inventory Data Set will be incorrect.

13.3.1 JOBNAMEOUT Command JOBNAMEOUT{ jobname | jobnamemask }

JOBNAMEOUT REQUIRED PARAMETER PARAMETER DESCRIPTION

Specify a discrete job name, or a mask to be used in generating output job names.

Default: None

JOBNAMEOUT

A job name mask requires at least one ? as a placeholder. Required: Yes If multiple job names are required automatically, job names

will be generated substituting an incrementing a number in Restrictions: At least one JOBNAMEOUT place of the specified ? placeholders. ? placeholders must command must be specified before the first occupy only the rightmost positions of a job name. BLDREST command. For example: Valid – ABCD???? Invalid – ABC?D? At least one JOBNAMEOUT command must be specified before the first BLDREST command. Multiple JOBNAMEOUT commands may be specified to identify a subsequent discrete job name or to identify a new mask to be used. A job name mask is not required; however, if multiple jobs are required and the jobname is discrete, they will all have the same jobname. Generating unique versus duplicate job names is one method to control how many restore jobs can be launched concurrently, and conversely, controlling jobs that are to be run sequentially (MVS initiator rule: no two jobs of the same name will be initiated concurrently).




13.3.2 INCRJOBNAMEOUT Command

INCRJOBNAMEOUT OPTIONAL PARAMETER PARAMETER DESCRIPTION

INCRJOBNAMEOUT forces the generation of a JOB statement for the next BLDREST command encountered.

Default: None

INCRJOBNAMEOUT

The jobname is generated using the mask specified for JOBNAMEOUT and incrementing the last job name used Required: No by 1.

Restrictions: INCRJOBNAMEOUT requires the previous JOBNAMEOUT was specified with a mask.

13.3.3 MEMBEROUT Command MEMBEROUT{ membername | membernamemask }

MEMBEROUT REQUIRED PARAMETER PARAMETER DESCRIPTION

MEMBEROUT Specify a discrete PDS member name, or a mask to be used in generating output member names.

Default: None A mask specification is required to subsequently use an Required: Yes INCRMEMBEROUT command to switch output to a new

member and automatically generate a member name. Restrictions: At least one MEMBEROUT command must be specified before the first A member name mask requires at least one ? as a BLDREST command. placeholder. If a subsequent INCRMEMBEROUT

command is encountered, a member name will be generated by substituting an incrementing number in place of the specified ? placeholders. ? placeholders must occupy only the rightmost positions of a member name. For example: Valid – ABCD???? Invalid – ABC?D? At least one MEMBEROUT command must be specified before the first BLDREST command. Multiple MEMBEROUT commands may be specified to force subsequent output to a different member.

13.3.4 INCRMEMBEROUT Command

INCRMEMBEROUT

None No

INCRMEMBEROUT OPTIONAL PARAMETER PARAMETER DESCRIPTION

Default:Required:Restrictions: INCRMEMBEROUT requires the previous MEMBEROUT was specified with a mask.

INCRMEMBEROUT forces the generation of a new output PDS member for the next BLDREST command encountered. The member name is generated using the mask specified for MEMBEROUT and incrementing the last member name used by 1.




13.3.5 STEPLIMITOUT Command

STEPLIMITOUT 255 nnn

255 No

Restrictions:

STEPLIMITOUT OPTIONAL PARAMETER PARAMETER DESCRIPTION

Default:Required:

STEPLIMITOUT specifies the maximum number of steps per job to be generated in the output job streams.




continued from previous page

[ INCLLOC( location | locationmask …locationn | locationmaskn ) ] [ INCLPHYDUMP( YES | NO ) ] [ NEWHLQ( hlq ) ] [ NOBKUPFOUND( BUILD | NOBUILD,RC( nn | 8 ) ) ] [ REPLACE( Y | N ) ] [ SKEL( skelname ) ] [ USEGEN0ALL | USEGEN0NOBKUP ]

BLDREST Command Parameter Definitions

Note: Required parameters are documented first, in alphabetical order; followed by the optional parameters, in alphabetical order.

Table 13-1: BLDREST Command Parameter Definitions

BLDREST PARAMETER PARAMETER DEFINITION

Required parameters: BLDREST Builds the restore JCL.

Default: None Required: Yes Restrictions: At least one JOBNAMEOUT and one MEMBEROUT command must be specified before the first BLDREST command.

APPL( applname )

Default: None Required: One category must be specified: DSN, JOBNAME, JOBGROUP, VOL or APPL. Restrictions: None

For APPL, specify within parentheses one or more fully-qualified application names, or one or more application name masks matching data sets to be restored. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19).

DSN( dsn | mask )


For DSN, specify within parentheses one or more fully-qualified data set names, or one or more data set name masks matching data sets to be restored. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19).





JOBNAME( jobnames | mask )

Default: None Required: One category must be specified: DSN, JOBNAME, JOBGROUP, VOL, or APPL. Restrictions: The name of the restore job cannot be the same as the name of the backup job.

For JOBNAME, specify within parentheses one or more discrete backup job names, or one or more job name masks matching job names to be restored. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19). If the jobname includes physical dumps and the data sets are multivolume, All/Star will restore the data sets on the selected volume(s), but not put the pieces together.

JOBGROUP( jobgroup )

Default: None Required: One category must be specified: DSN, JOBNAME, JOBGROUP, VOL, or APPL. Restrictions: None

For JOBGROUP, specify within parentheses the name of a job group to be restored. Restore JCL will be built for all backups created by all steps and commands within all jobs defined in the job group. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19).

VOL( volume | mask )


For VOL, specify within parentheses one or more discrete volumes, or one or more masks matching volumes to be restored. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19).

Note: Physical full volume and physical data set dumps. It is recommended that full volume dumps are done in restores separate from any other kind of backups.


BADBKUPRC( nn | 8 )

Default: 8 Required: No Restrictions: None

Specify the return code of the backup jobs AST is to consider a bad backup. Any backup job with a return code equal to or higher than that specified RC will be considered to be bad. nn – is an integer 0 or greater.

CMDNO( * | nnn ) Specify the command within a backup utility to be restored. If multiple backup jobs are selected, CMDNO applies to all

Default: * jobs.

Required: No Restrictions: Valid with JOBNAME only.

Example: If an IDCAMS backup contains 3 REPRO commands, CMDNO(2) will generate restore JCL for only the 2nd REPRO.

COPY( nn )


Specify the copy number of a multiple copy backup to be used for the restore. nn – is an integer 1 or greater.




BLDREST PARAMETER


CYCLE( 0 | -nn )

Default: 0, the most recent application cycle. Required: No Restrictions: Valid with APPL only.

Specify the relative cycle within parentheses of the application or applications to be restored. nn must be 0 or -nn; for example, -1 specifies the next to the last backup. Example: BLDREST APPL(PAYROLL) CYCLE(-1)

EXCLAPPL( appl | mask )

Default: None Required: No Restrictions: Valid with APPL only.

Specify exclusions from the restore list generated via APPL parameter. Specify within parentheses one or more fully-qualified application names, or one or more application name masks to identify applications to be excluded from the generated restore list. Mask must conform to the Mainstar extended masking rules. Example: Shown used with the INCLAPPL keyword, INCLAPPL(PAY**) EXCLAPPL(*OFF) Causes all PAY* applications to be included in the restore except any ending with OFF.

EXCLDSN( dsn | mask )

Default: None Required: No Restrictions: May only be specified when either DSN or INCLDSN parameters are specified in the command.

Specify exclusions from the restore list generated via either the DSN or INCLDSN parameters. Specify within parentheses one or more fully-qualified data set names, or one or more data set name masks to identify data sets to be excluded from the generated restore list. Mask must conform to the Mainstar extended masking rules. Example: Shown used with the INCLDSN keyword, INCLDSN(PAYROLL.**) EXCLDSN(PAYROLL.**.LOGFILE.**) causes all PAYROLL.** data sets to be included in the restore except any with LOGFILE appearing anywhere in nodes 2 through nn.

EXCLJOB( jobname | mask )

Default: None Required: No Restrictions: Valid with JOBNAME, JOBGROUP, and APPL. Not valid with DSN, VOL.

Specify job names to be excluded from those specified in the JOBNAME or JOBGROUP parameter. Specify within parentheses one or more discrete job names, or one or more job name masks to identify job names to be excluded from the generated restore list. Mask must conform to the Mainstar extended masking rules.





EXCLLOC( location | mask ) Specify exclusions from the backup data sets that may be used for restore.

Default: None Required: No

Specify within parentheses one or more fully-qualified tape management location names that may not be selected.

Restrictions: None When used without the INCLLOC, any location except those that match the EXCLLOC can be selected. When used with INCLLOC, any location that matches the INCLLOC and does not match the EXCLLOC may be selected. Example: Shown used with the INCLLOC keyword, INCLLOC(VAULT*) EXCLLOC(*2) causes all VAULT locations except those that end with 2 to be selectable.

EXCLVOL( volser | mask )

Default: None Required: No Restrictions: Valid with VOL only.

Specify one or more volsers to be excluded from the restore list generated from VOL. Specify within parentheses one or more discrete volumes, or one or more volume masks to identify volumes to be excluded from the generated restore list. Mask must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

GEN( 0 | -nn )

Default: 0, the most recent backup. Required: No Restrictions: Not valid with APPL.

Specify the relative generation of the backup to be restored, if more than one backup generation is available. nn must be 0 or -nn; for example, -1 specifies the next to the last backup. When used with DSN, GEN applies to all data sets to be restored within the specified BLDREST DSN command; therefore, utilize multiple BLDREST DSN commands to restore an application where selected data sets must be restored from a different generation. Example: BLDREST DSN(PAYROLL.**) EXCLDSN(PAYROLL.MASTER) BLDREST DSN(PAYROLL.MASTER) GEN(-1)

INCLBACKVOL( NO | YES ) INCLBACKVOL specifies whether or not HSM incremental backups tracked by AST via BACKVOL commands are to

Default: NO be included in the restore.

Required: No Restrictions: Not valid with VOL.





INCLDSN( dsn | mask ) Specify within parentheses one or more fully-qualified data set names, or one or more data set name masks matching

Default: None data sets to be restored. INCLDSN limits the data sets to be restored to ONLY those within the specified job(s) (for JOBNAME and JOBGROUP

Required: No Restrictions: Not valid with DSN. category) or volumes (for VOL category) that are specified

in the command with the INCLDSN parameter. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 19).

INCLLOC( location | mask ) Specify within parentheses one or more fully-qualified tape management location names, or one or more location

Default: None masks that may be used for restore. Masked names must conform to the Mainstar extended masking rules. For more information, see the topic

Required: No Restrictions: Not valid with DSN. 'Mainstar Extended ACS Filtering Pattern Masks' (page 1

9).

Note: All/Star automatically recognizes the tape management systems CA1, TLMS, and RMM. If your tape management system is TLMS, you must change the name of the TLMSDB statement in the BRMRPROC found in the product JCL library from 'NULLFILE' to the TLMS database name to use this keyword. For CA1 or RMM, no JCL changes are required.

INCLPHYDUMP( NO | YES ) INCLPHYDUMP specifies whether matches in the specified category (DSN, JOBNAME, or JOBGROUP) to

Default: NO physical dumps are to be included in the restore. When used with JOBNAME, JOBGROUP, or APPL and N

and JOBGROUP categories. Required: Yes, for the DSN, JOBNAME,

is specified, if the backup chosen is a physical dump, an error message is issued and no restore JCL is produced. Restrictions: Not valid with VOL. When N is used with DSN, physical dumps are ignored when looking for the desired backup generation. You may also set a default by modifying the BRMINI PARMLIB member token INCLUDE_PHYSICAL_DUMPS. INCLPHYDUMP is used only when looking for the GEN(0) backup when USEGEN0NOBKUP or USEGEN0ALL are used. Specifies physical dumps are to be considered when looking for the most recent backups to be included in the restore.

1 to 8 byte node that will be used to build a new name for restored data sets. This value will be used as a high level

Default: None

NEWHLQ( hlq )

qualifier preceding the rest of the original data set name.





BLDREST PARAMETER


NOBKUPFOUND ( BUILD | NOBUILD,RC( nn | 8 ) )

Default: NOBUILD, RC(8) Required: No Restrictions: None

NOBKUPFOUND specifies whether the BLDREST command should be built and the desired return code if a matching data set that was included has no backup.

REPLACE( N | Y )

Default: N Required: No Restrictions: None

N – data sets to recover that already exist (cataloged) will not be replaced. Y – delete the existing (cataloged) data set and REPLACE it with the data set to recover.

SKEL( skelname )


Specify a skeleton library member name to be used in place of the default skeletons. If specified and the backups to be included involve multiple utility types, the skeleton must be capable of generating restore JCL for any anticipated utility types.

STEPNAME( * | stepname ) | STEPNO( * | nn )

Default: * will restore all steps, for both STEPNAME and STPNO Required: No Restrictions: • STEPNAME and STPNO are mutually

exclusive. • Valid with JOBNAME only.

For STEPNAME, specify the step name of the backup to be restored. The default is * (restore all steps). If multiple backup jobs are selected, step name applies to all jobs. If multiple occurrences of step name are found in a job, all matching step names will be restored. For STEPNO, specify the JES step number of the backup to be restored. The default is * (restore all steps). If multiple backup jobs are selected, STEPNO applies to all jobs.

USEGEN0ALL | USEGEN0NOBKUP

Default: None Required: No Restrictions: • USEGEN0ALL and USEGEN0NOBKUP

are mutually exclusive. • Valid with APPL only.

USEGEN0ALL – Always use the latest backup, even if a backup was found at BKUPEND. USEGEN0NOBKUP – Use latest backup for selected data sets if no backup was found at BKUPEND.




13.4 Use of Keywords to Control Job and Member Generation

13.4.1 Minimal Required Keywords Specifying M1 for MEMBEROUT will cause all restore JCL to be generated into one output JCL member named M1.

Because STEPLIMITOUT is not coded, jobs will be populated with up to the max of 255 steps (the default).

If multiple jobs are required, all jobs will be named RESTORE1, the discretely specified job name for JOBNAMEOUT.

Note: If multiple jobs are generated, they will initiate sequentially, due to the job names being the same.

JOBNAMEOUT RESTORE1 MEMBEROUT M1 BLDREST … BLDREST …

13.4.2 Generating Different Job Names to Allow Concurrent Initiation

Method 1 – discretely specified job names:

In this example, RESTORE1 and RESTORE2 are the discrete job names specified as for the JOBNAMEOUT commands.

MEMBEROUT M1 JOBNAMEOUT RESTORE1 BLDREST … BLDREST … JOBNAMEOUT RESTORE2 BLDREST …

Method 2 – automatic incrementing of job name:

Specifying RSTOR??? for JOBNAMEOUT will generate job names of RSTOR001, RSTOR002, etc. MEMBEROUT M1 JOBNAMEOUT RSTOR??? BLDREST … BLDREST … INCRJOBNAMEOUT BLDREST …




13.4.3 Generating Multiple Output JCL Members

Method 1, discretely specified member names:

In this example M1 and M2 are the discrete member names specified for the MEMBEROUT commands.

MEMBEROUT M1 JOBNAMEOUT RESTORE1 BLDREST … BLDREST … MEMBEROUT M2 BLDREST …

Note: Forcing a new output member, either with a specific name or by specifying INCRMEMBEROUT, does not require changing the previously used job name. Using the same job name across members may be desired to serialize initiation if multiple JCL members are submitted concurrently.

Method 2, automatic incrementing of member name:

Specifying M??? for MEMBEROUT and then including INCRMEMBEROUT will generate member names of M001, M002, etc.

MEMBEROUT M??? JOBNAMEOUT RSTOR??? BLDREST … BLDREST … INCRMEMBEROUT INCRJOBNAMEOUT BLDREST …




13.5 Sample Build Restore Scenarios

13.5.1 Build Restore Scenario 1 Note that STEPLIMITOUT is set to 3 to illustrate how the restore JCL may require more jobs and steps than the original backups being restored.

Job A1 Step - IDCAMS

4 REPROs Step - DSS

3 Logical DUMPs

Job A2 Step - IEBGENERStep - IEBCOPY

2 COPYs

MEMBEROUT MEM?????

STEPLIMITOUT 3

JOBNAMEOUT REST1???

BLDREST JOBNAME(A*)

//REST1001 JOB …. (from 1st IDCAMS Skel)

//S1 EXEC PGM=IDCAMS (1st REPRO)//S2 EXEC PGM=IDCAMS (2nd REPRO)

//S3 EXEC PGM=IDCAMS (3rd REPRO)

//REST1001 JOB … (from 4th IDCAMS Skel)

//S1 EXEC PGM=IDCAMS

(4TH REPRO)

//S2 EXEC PGM=ADRDSSU ( 1st RESTORE)

//S3 EXEC PGM=ADRDSSU ( 2nd RESTORE)

//REST1001 JOB … (from 3rd DSS Skel)

//S1 EXEC PGM=ADRDSSU

(3rd RESTORE)

//S2 EXEC PGM=IEBGENER

( 1st Gener)//S3 EXEC PGM=IEBCOPY ( 1st COPY)

//REST1001 JOB … (from 2nd IEBCOPY Skel)

//S1 EXEC PGM=IEBCOPY ( 2nd COPY)

Database Job/Step/Commands

Restore Control Statements Generated Output JCL

Member MEM00001:





4 REPROs Step - DSS

3 Logical DUMPsJob A2 Step - IEBGENERStep - IEBCOPY

2 COPYs

STEPLIMITOUT 3

MEMBEROUT MEMJA1

JOBNAMEOUT REST1???

BLDREST JOBNAME(A1)

MEMBEROUT MEMJA2

INCRJOBNAMEOUT

BLDREST JOBNAME(A2)






(4TH REPRO)





(3rd RESTORE)

//REST1002 JOB




13.5.2 Sample Build Restore Scenario 2



Member MEMJA1:

Member MEMJA2:





4 REPROs Step - DSS

3 Logical DUMPsJob A2 Step - IEBGENERStep - IEBCOPY

2 COPYs

STEPLIMITOUT 3

MEMBEROUT MEMJA1

JOBNAMEOUT REST1???

BLDREST JOBNAME(A1)MEMBEROUT MEMJA2

INCRJOBNAMEOUT

BLDREST JOBNAME(A2)






(4TH REPRO)





(3rd RESTORE)

//REST1002 JOB




13.5.3 Sample Build Restore Scenario 3



Member MEMJA1:

Member MEMJA2:




Chapter 14 14 All/Star: All/Star Tracking (AST) Started Task

All/Star Tracking (AST) started task intercepts supported in-stream backups performed during backup execution and provides a method for tracking them in a database, the Backup & Recovery Manager Suite (BRM) Inventory Data Set (IDS).

Contents:

• All/Star Tracking (AST) Started Task Overview – page 14-1

• The All/Star Tracking (AST) Started Task – ASTSMFTK – page 14-2

• Backup Utilities Tracked by All/Star – page 14-3

• DFSMShsm ARCINBAK Considerations – page 14-4

• Tracking DFSMShsm Auto Dumps – page 14-4

• Preparing to Track Backup Data Using All/Star Tracking (AST) Started Task – page 14-5

• System Configuration Modes and AST Tasks – page 14-5

• AST Commands – page 14-6

• Back Up, Reorganize, or Resize the BRM Suite IDS – page 14-9

14.1 All/Star Tracking (AST) Started Task Overview Backups to be tracked are intercepted by a seamless AST intercept triggered by matching job names, step names, and utility program names entered into a user-defined table. Although it is necessary to identify which jobs are backups, no JCL changes are required, thus the risk and procedural difficulties with changing production JCL are eliminated.

Backup jobs are identified to All/Star via an ISPF interface to establish Batch Intercept File (BIF) entries. Batch Intercept File (BIF) entries are initially stored in the BRM IDS and identify a backup job/step and backup utility. Upon completion of creating BIF entries through ISPF, the Batch Intercept File (physical file) must be refreshed via an ISPF option with the new entries, and the AST started task notified so the newly defined backups can be tracked. Any time you add new job names to All/Star through ISPF, you must refresh the batch intercept file (BIF). See Chapter 3, All/Star: Setup and Configuration – Option 1, for more information on defining backup tasks, and refreshing AST.

All/Star utilizes a started task on each image which installs step initiation exit IEFUSI to intercept backups. If a backup is to be intercepted, execution is altered to execute a Mainstar intercept program, which in turn executes the true utility.

Subtasks under the started tasks then process the results of intercepted utilities and record the pertinent data in the BRM Inventory Data Set. For most types of backups, All/Star captures catalog and volume metadata in synchronization with the status of the data set(s) at the time of the backup. This ensures that restore allocations match the status of data sets at the time they were backed up.

The AST tracked backups are tracked in the BRM IDS by cycle which is recorded as date and time. Each execution of a job that has been tracked is considered a cycle. Within a cycle, the backups are tracked by backup task within job step.

The BRM Inventory Data Set includes job name, step name, name of utility, date time return codes, input, output, data set backed up, etc. The data is viewable via ISPF and allows dynamic recovery of full volume or selected data sets.

Mainstar Software Corporation ©2006 14-1 Chapter 14 SC23-6061-00 All/Star: All/Star Tracking (AST) Started Task



Backups whose output data sets are no longer cataloged on the system* will be expired, or removed from the BRM Inventory Data Set. If a jobname contains multiple backup data sets, the jobname will not be removed from the BRM Inventory Data Set until all backups in the job are no longer cataloged on the system.

*with the exclusion of DFSMShsm AUTODUMPS and BACKVOLS, which are synchronized through the AUTODUMP and BACKVOL jobs.

All/Star consists of:

• The All/Star Tracking (AST) started task • Step initiation exit (IEFUSI) • Batch Intercept File (BIF) • Intercept modules for supported backup utilities • An inventory database, the Inventory Data Set (IDS) • ISPF interface • Batch utilities

14.2 The All/Star Tracking (AST) Started Task – ASTSMFTK The All/Star Tracking (AST) started task name is ASTSMFTK. This task:

• Builds an in-storage job mask table from Batch Intercept File (BIF) • Installs step initiation exit (IEFUSI) • Sets up communication with other participating systems and ISPF users • Attaches a task to find and process 'spun-off' data sets from intercept modules

Chapter 14 14-2 Mainstar Software Corporation ©2006 All/Star: All/Star Tracking (AST) Started Task SC23-6061-00



14.3 Backup Utilities Tracked by All/Star • ABARS backups executed through ABARS Manager • Adabas (ADARUN) • Catalog RecoveryPlus (CR+) backups • CA-FAVER • CFCAMS (REPRO and EXPORT) • DFSMSdss (Full volume, physical dump by data set, and logical backups) • DFSMShsm ARCINBAK • DFSMShsm AUTODUMP • DFSMShsm BACKVOL • DFSMShsm Incremental • FDR (FDR, DSF, ABRFDR) • ICEGENER • IDCAMS (REPRO and EXPORT) • IEBCOPY • IEBGENER • SORT • SYNCGENR

Note: DFSMShsm AUTODUMP and BACKVOL are supported through batch utilities.


Note: All/Star tracks data set statistics through a catalog lookup. Data set statistics are not available if data sets are deleted, or renamed prior to completing processing.

Because the number of data sets on full volume dumps can be extensive, it can take considerable time to do the catalog lookups and in turn be reflected in the BRM Suite Inventory Data Set. BRMINI PARMLIB member token CATLG_DATA_FOR_PHY_DUMPS=Y|N can be set to N to inhibit a catalog lookup. Data set names will still be recorded in the BRM Suite Inventory Data Set, but data set statistics will not be available such as multi-volume information, DSCB information, etc.




14.4 DFSMShsm ARCINBAK Considerations DFSMShsm ARCINBAK jobs are tracked by the All/Star Tracking (AST) started task, if the job matches a jobname mask in the batch intercept file. To track ARCINBAK backups, DD ARCPRINT statement must be present as shown in the following example:

//ASTBJ910 JOB ,'ARCINBAK',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//**********************************************************//* DO HSM INLINE BACKUP OF SEVERAL DATASETS USING ARCINBAK.//* FOR INFORMATION ABOUT ARCINBAK SEE THE//* DFSMShsm STORAGE ADMIN. GUIDE CHAPTER 10//**********************************************************//ARCINBAK EXEC PGM=ARCINBAK//ARCPRINT DD SYSOUT=* //ARCSNAP DD SYSOUT=* //BACK01 DD DISP=SHR,DSN=BRMX.AST.IVP.J910.BACK01//BACK02 DD DISP=SHR,DSN=BRMX.AST.IVP.J910.BACK02//BACK03 DD DISP=SHR,DSN=BRMX.AST.IVP.J910.BACK03

14.5 Tracking DFSMShsm Auto Dumps DFSMShsm auto dumps will not automatically be tracked by AST. See Chapter 9, All/Star: Batch Processing & Output, for more information on tracking and providing an inventory of DFSMShsm auto dump backups.

14.5.1 Expiring Backups and Applications from the BRM Inventory Data Set Backups that are no longer valid should be expired, or removed from the BRM Inventory Data Set by using the ASTEXPIRE command. If a jobname contains multiple backups, the jobname will not be removed from the BRM Inventory Data Set until all backups in the job are no longer valid. If you are licensed for both All/Star and ASAP, and are using All/Star Application Backup & Restore, ASTEXPIRE removes old application cycles as defined by the BACKUP CYCLES TO RETAIN parameter (found in ASAP on the Application SETUP Options panel). For more information on All/Star Application Backup & Restore, see Chapter 12, All/Star: Application Backup and Restore. For more information on expiring backups using the ASTEXPIRE command, see Chapter 9, All/Star: Batch Processing & Output.

14.5.2 Track All/Star Tracking (AST) Messages If you want the All/Star Tracking (AST) started task to continually track backups, you should monitor AST critical messages with an automated operations tool if possible to signal any problems that could arise. This will enable you to be notified immediately so the problem can be fixed. The following message should be tracked.

This message will occur when AST has been suspended for any reason:

AST00000I AST TRACKING SUSPENDED – module name

14.5.3 Reducing Data to Be Processed by All/Star Tracking (AST) Started Task Although AST tracks backups without application JCL changes using discrete jobnames or jobname masks/steps/program names, jobname masks have pros and cons associated with them. Masks can significantly reduce the effort of defining backup jobs, but there will be more data to process.




14.6 Preparing to Track Backup Data Using All/Star Tracking (AST) Started Task Follow these steps to prepare to track backup data using All/Star Tracking (AST) started task:

STEP

1

DESCRIPTION

Create Batch Intercept File (BIF) filters via the ISPF facility. Select Option 1 (Setup and Configuration) from the Backup & Recovery Manager Suite Main Menu. Select Option 3 (Browse/Edit Backup Tracking Filters) from the BRM – Setup and Configuration menu, to define the backup filters for AST to track.

NOTE: Be specific when entering Job Name, Job Step, and Proc Step in the Backup Tracking Filters INCLUDE Panel. This will eliminate unnecessary Jobname tracking and reduce the number of entries stored in the Inventory Data Set.

2 Build Batch Intercept File and refresh AST. Select Option 1 (Setup and Configuration) from the Backup & Recovery Manager Suite Main Menu. Select Option 4 (Build Batch Intercept File and Refresh AST) from the BRM – Setup and Configuration menu, to rebuild the Batch Intercept File (BIF) and Refresh the AST started task.

3 Set up DFSMShsm ARCINBAK backups (optional). DFSMShsm ARCINBAK jobs are tracked by the AST started task, if the job matches a jobname mask in the batch intercept file. To track ARCINBAK backups, DD ARCPRINT statement must be present.

4 Run the backups. The AST started task will track backup information for backups defined, provided they are AST supported utilities.

5 Expiring cycles from the BRM Inventory Data Set. Job ASTEXPIR found in the Backup & Recovery Manager Suite JCL library must be set up and executed for uncataloged backups to be removed from the BRM Inventory Data Set. Job ASTEXPIR should be checked at least initially to verify what is being expired. For more information on expiring backups, see Chapter 9, All/Star: Batch Processing & Output.

14.7 System Configuration Modes and AST Tasks The AST started task can collect data for backups defined to All/Star in either single image or multi-image (SYSPLEX) modes. This capability allows installations to schedule and execute backups on any processor image and still maintain continuous collection of backup data.

The main control program ASTSMFTK controls the AST tasks. The started task, ASTSMFTK, must run on each image you wish to track backups on. The ASTSMFTK task is started with a job name of AST. The AST operator commands are documented below.




14.8 AST Commands

Command Description

S ASTSMFTK,JOBNAME=AST Start Started Task. If BRMINI has AST_AUTOSTART = Y, it also starts all the subtasks below that are required to intercept backup jobs. If AST_AUTOSTART = N, the subtasks below must be started by command.

F AST,AUTOSTART Start everything – the started task and all individual processes shown below that are required for AST to intercept backups.

F AST,TURNOFF Turn IEFUSI exit off.

F AST,TURNON Turn IEFUSI exit on.

F AST,LOAD Load IEFUSI exit.

F AST,UNLOAD Stop IEFUSI exit.

F AST,NEWSECONDARY Replace IEFUSI secondary exit.

F AST,REFRESH Refresh batch intercept file.

F AST,RELOAD(modname) F AST,RELOAD(ALL)

| Special note for F AST,RELOAD(ALL): This command should be issued after the FLATCOPY subtask has been stopped. The following command will stop the FLATCOPY subtask:

F AST,STOPFC

After the F AST,RELOAD(ALL) command has been issued, the FLATCOPY subtask must be re-started. The following command will re-start the FLATCOPY subtask.

F AST,STARTFC

F AST,STARTFC Start flatfile copy task.

F AST,STOPFC Stop flatfile copy task.

F AST,STARTMON Attach monitor subtask.

F AST,STOPMON Detach monitor subtask.

P AST Shut down started task.




14.8.1 Start the All/Star Tracking Started Task and Individual Subtasks If the BRMINI member of the BRM PARMLIB includes AST_AUTOSTART = YES, which is the value that is shipped and Mainstar's strong recommendation, simply issue the following command from the console to start AST:

S ASTSMFTK,JOBNAME=AST (or a jobname of your choosing)

If you specify AUTOSTART=NO in the BRMINI member of PARMLIB, you must first issue the Start command as above and then issue the following command to start the various tasks:

F AST,AUTOSTART

This command starts the AST started task and all individual subtasks shown below that are required for AST to intercept backups. In general, AUTOSTART is the only command needed to start ASTSMFTK. See member ASTSMFTK in the Backup & Recovery Manager Suite JCL library. The member/procedure name is ASTSMFTK and the started task name is 'AST'. All modify commands are based on the identifier 'AST'.

AUTOSTART issues the following commands: F AST,LOAD

F AST,TURNON

F AST,STARTMON

F AST,STARTFC

14.8.2 Stop the AST Structure: P AST

All AST processes are automatically shut down.

14.8.3 Updating the In-Storage Batch Intercept File Filters: F AST,REFRESH

Any time you add new jobnames to All/Star through ISPF, you must refresh the batch intercept file (BIF) so a new copy of the intercept filters can be loaded into storage. There are several ways to do this.

• Use the option on the ISPF panel to refresh the BIF. This is the most common method. See 'Browse/Edit Backup Tracking EXCLUDE Filters – Sub-Option 4' (page 3-5), for more information.

• Use batch command REFRESH-AST. See Chapter 9, All/Star: Batch Processing & Output, for more information on REFRESH-AST.

• Use the started task modify command F AST,REFRESH.

This command will be sent to all participating systems. The original filters are valid until this process is complete.




14.8.4 Manipulate the IEFUSI Exit: F AST,TURNOFF

Turns off the IEFUSI exit and stops AST job intercepts. This may be used if the exit is generating an error, or when preparing to load a new copy of the IEFUSI exit code.

F AST,UNLOAD

Removes the AST IEFUSI exit and deletes its resources. This is done in preparation of loading a new copy of the IEFUSI exit.

F AST,LOAD

Loads the IEFUSI exit.

F AST,TURNON

Activates the IEFUSI exit which will start AST job intercepts.

14.8.5 Manipulate Flatfile Copy Task: When a supported backup job is intercepted by AST, a flatfile containing the intercepted backup data needed to update the BRM IDS is created. The flatfile copy task requires DFSMShsm up to get statistics for migrated data sets. If DFSMShsm is not up, the flatfile copy task issues a message for DFSMShsm to be brought up, and generates error messages.

A task attached by ASTSMFTK will find these data sets. The task will collect catalog, VVDS, and VTOC data for the input, output, and backed-up data sets. The task will then use the accumulated data to update the BRM Inventory Data Set.

To start the flatfile copy task, issue the following command:

F AST,STARTFC

To stop the flatfile copy task, issue the following command:

F AST,STOPFC

To see the status of the monitor task as well as the flatfile copy task, issue the following command:

F AST,STATUS

14.8.6 Summary of Files Used by the All/Star Tracking (AST) Started Task The files used by the All/Star Tracking (AST) started task are described below:

JCL Member Description

ASTSETUP JCL to allocate the AST started task members: MSGLOG – Message log file for informational, warning, and error messages generated from ASTSMFTK. MSGQUEUE – Communication file used to communicate between participating systems and ISPF users. BIF – Batch Intercept File that contains backup jobnames to track.

PARMLIB Contains BRMINI member to be used by ASTSMFTK.




14.9 Back Up, Reorganize, or Resize the BRM Suite IDS The Backup & Recovery Manager Suite Inventory Data Set (BRM IDS) should be backed up on a regular basis, reorganized regularly, and resized as the inventory data set grows. Schedule these processes at a slow time of job tracking. During this time, AST will continue to track backups and create flatfiles with the pertinent backup information. The flatfiles created during this time will be used to update the inventory data set after the flat copy processor has been started again. To back up, reorganize, or resize the BRM IDS, follow the steps listed below.

STEP

1

STEP DESCRIPTION

Stop the flat copy processor by issuing: F AST,STOPFC. If a copy is in progress, it will shut down after it is complete.

2 Back up the BRM Suite Inventory Data Set by executing an IDCAMS REPRO to an output file.

3 Delete and redefine the BRM Suite Inventory Data Set if necessary using HLQ.JCL(DEFINVDB).

4 REPRO (previously REPRO'd BRM Inventory Data Set) back into the new Inventory Data Set.

5 Start the flat copy processor by issuing: F AST,STARTFC.

14.10 AST Message Log The All/Star Tracking (AST) started task maintains and updates the AST Message Log File with diagnostic information only from each processor image. The AST Message Log File is a required file that is allocated via supplied JCL members. To view the AST Message Log, use ISPF Browse – do not use ISPF EDIT.




Chapter 15 15 BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR

The CATSCRUB command is a selectable feature of Backup & Recovery Manager Suite. If you wish to use this feature, contact Mainstar Software Corporation or your Mainstar sales representative to arrange purchase and licensing.

The CATSCRUB command includes a comprehensive facility to ensure that ICF catalogs and data volumes are synchronized when a system is recovered at a disaster recovery (DR) site. CATSCRUB’s simulation capability lets you see the expected deletions before you use the execute form. In addition, using simulation along with MATCH-VOLSER creates an environment at the home site to ensure that the process functions as expected at the DR site.

i (

Note2:

Note: It is important that you read the topic 'How Does CATSCRUB Process ng Work?' page 15-18) thoroughly before running CATSCRUB in EXECUTE mode.

Running CATSCRUB in SIMULATE mode before using EXECUTE mode is a wise work practice.

15.1 The CATSCRUB Command CATSCRUB is oriented to a disaster recovery methodology where the recovery site systems are started with one or more populated catalogs, either as a result of the catalogs being transported from the home site, or the catalogs already being in place as the result of a remote mirror.

In simple terms, the primary function of the CATSCRUB command is to compare each record in the specified catalogs against the actual data sets on the disk storage volumes to be matched. If the catalog record doesn't match up with a data set, the catalog record will be deleted based on your anomaly keyword specifications. This processing logic forces the catalog to correctly reflect the actual contents of the restored volumes at the DR site.

The CATSCRUB command has 'anomaly detection' keywords that indicate the processing to be performed when one of the anomalies is encountered. For example, you may choose to keep a GDG base record although none of the Generation Data Sets are present.

CATSCRUB is a catalog-centric command and its terminology reflects that; specifically:

• The user-specified DELETE action applies to catalog entries only. It is the equivalent of a DELETE NOSCRATCH of the object within the catalog and it never involves any physical deletion of objects on disk or tape volumes.

• CATSCRUB considers a disk data set to be multi-volume if it is defined in the catalog with more than one volume, even if the data set occupies only a single volume. For example, a non-VSAM data set with data on one volume, but with candidate volumes for expansion, is considered to be a multi-volume data set.

• A tape data set differs from a migrated data set in that the tape data set was cataloged to tape. A migrated data set was cataloged to disk and has been migrated to tape or disk.

Examples of the requirement for anomaly processing are: • GDG bases – some GDG bases may be required by subsequent application processing, but

because no active generations exist at the time of an application data set level backup, the GDG base is not restored by the application. Hence, the GDG base must be either kept in the copy of a populated catalog brought or mirrored to the DR site, or re-created with some other procedure.

Mainstar Software Corporation ©2006 15-1 Chapter 15 SC23-6061-00 BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR



• Non-VSAM data set aliases – depending on the data mover that is used for application data set level backups, the backup may not include associated non-VSAM aliases. Hence, a non-VSAM data set alias must either be kept in the copy of a populated catalog brought or mirrored to the DR site, or re-created with some other procedure.

• Multi-volume data sets – you must decide what action is appropriate for your particular situation, if any type of data set is partially found on a volume being matched, but where one or more segments are not found. The worst case for this anomaly is a volume omitted from full volume dumps or from volumes being mirrored. This is an excellent reason to run CATSCRUB with the SIMULATE feature prior to your DR tests to help avoid this problem.

• VSAM spheres – the multi-volume option for VSAM spheres applies to either a missing segment of a component or an entirely missing component (for example, a data component found, but no index component found for a KSDS). This also includes missing AIX components. Like a multivolume anomaly, the worst case scenario is a volume omitted from full volume dumps or mirrors.

• Generation data sets – missing or migrated generation data sets (GDSs) pose a unique problem, because removing only selected GDS catalog entries can destroy the relativity of generations. Active GDSs are represented by catalog cell entries within the GDG base catalog record – not discrete catalog records for each active GDS. When an active GDS is 'deleted' within the GDG base record, the corresponding cell is removed and remaining cell entries are shifted – hence, the possible destruction of relativity for the remaining active GDS entries. It cannot be stressed too much that you must use special care when making the decision whether to delete selected generations.

Chapter 15 15-2 Mainstar Software Corporation ©2006 BRM Suite: CATSCRUB – Synchronize Catalogs/Volumes for DR SC23-6061-00



15.2 Using the CATSCRUB Command

15.2.1 What to Do Before You Can Use CATSCRUB Before you can use CATSCRUB you must:

1. License CATSCRUB with Mainstar Software Corporation.

2. Configure CATSCRUB by setting keyword values in the :PRODUCT_SECURITY and :CATSCRUB_OPTIONS sections of the BRMINI member of the Backup & Recovery Manager Suite PARMLIB.

3. For information on how to protect use of the CATSCRUB command, see Appendix A, Authority Requirements, of the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062).

15.3 Submitting the CATSCRUB Command Batch mode executions may be initiated either interactively using the Online Dialog panels, (refer to 'CATSCRUB – Sub-Option 1', page 5-2) or as batch jobs using the supplied product JCL procedure member BRMBPROC. Submit the CATSCRUB command as SYSIN to the BRMBPROC member of the BRM JCL library.




15.5 CATSCRUB Command Parameter Definitions Table 15-1: CATSCRUB Command Parameter Definitions

CATSCRUB KEYWORD

SHORT FORM(S)

KEYWORD DEFINITION

Required keywords:

CATSCRUB CATSCRUB command.

BCS


BCS specifies one or more BCSs of an ICF catalog that are to be 'scrubbed' with this command. The BCS name (s) specified within parentheses can be one or more fully qualified BCS names, a partial name with a mask value, or the extended ACS filtering mask (**) if all BCSs connected in the system's master catalog are to be scrubbed. Each BCS whose name matches the specified value(s) is processed. If the master catalog is to be processed it must be specified explicitly. It is never selected by a mask value. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

EXECUTE SIMULATE


EXEC SIM

EXECUTE specifies that CATSCRUB is to perform all catalog scrubbing operations, including direct deletion of BCS catalog records that do not find a matching physical data set on the specified 'match' volsers. SIMULATE specifies that CATSCRUB is to perform all command actions as if a normal catalog scrubbing operation was being done, but not make any changes to the BCSs. A complete report of the catalog scrubbing processing is created, allowing you to see the results as if it was actually completed.




CATSCRUB SHORT KEYWORD KEYWORD FORM(S) DEFINITION

Optional keywords:

EXCLUDE-BCS

Alternate keyword form: EXCLUDEBCS


EXCB EXCLUDE-BCS specifies one or more BCSs to be excluded from CATSCRUB processing. The BCS name(s) specified within parentheses can be either one or more fully qualified BCS names, or a partial name with a mask value. Each BCS whose name matches the specified value(s) is excluded from processing. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9). A BCS is only excluded if it was already in the 'include' list created by the BCS operand. In other words, the full list of BCSs to be scrubbed is first built from the specific names or mask values specified on the BCS operand, and then any specific names or masks from the 'exclude' list are removed from the list.

FATAL-CATALOG-ERR CONTINUE END

Alternate keyword form: FATALCATALOGERR

Default: END Required: No Restrictions: None

FATCATERR CONT

FATAL-CATALOG-ERR specifies the action to be taken when CATSCRUB encounters a fatal error while processing a list of catalogs. CONTINUE – allows CATSCRUB processing to continue when a fatal catalog error is encountered. END (the default) – all further CATSCRUB processing is to terminate upon the first occurrence of a fatal catalog error. Circumvention is to EXCLUDE catalogs causing fatal errors. You may set a custom default using the token FATAL_CATALOG_ERR_PROC in the :CATSCRUB_OPTIONS section of BRMINI. Refer to the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062).

GDGBASE-NO-ACTIVE-GENS KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDGBASENOACTIVEGENS

Default: KEEP CONTINUE RC(4) Required: No Restrictions: None

GDGNAG DEL CONT

GDGBASE-NO-ACTIVE-GENS specifies the disposition of a GDG base (the GDG sphere record) that has no active generation data sets (GDSs) currently defined for it, either during initial processing of the GDG sphere record, or if a GDG sphere record is 'emptied' as a result of other CATSCRUB processing that deletes all of the generations. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.





GDS-MIGRATED KEEP | DELETE CONTINUE | END RC

GDSM DEL CONT

GDS-MIGRATED specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record that is found to be in migrated status.

Caution: Give careful consideration before Alternate keyword form: specifying DELETE, as it can result in a GDSMIGRATED change in the relative number of generation

data sets within a GDG. This can produce an Default: unintended result when you are subsequently KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with GDS-MIGRATED-DASD or GDS-MIGRATED-TAPE.

processing by relative generation number.

See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

GDS-MIGRATED-DASD KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDSMIGRATED-DASD

Default: KEEP CONTINUE RC(4) Required: No

GDSMD DEL CONT

GDS-MIGRATED DASD specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record that is found to be in migrated status where the device type is disk.

Caution: Give careful consideration before specifying DELETE, as it can result in a change in the relative number of generation data sets within a GDG. This can produce an unintended result when you are subsequently processing by relative generation number.

Restrictions: Can’t be used with See Step 3 of topic 'How Does CATSCRUB GDS-MIGRATED. Processing Work?' (page 15-18), for a detailed

description of anomaly processing.

GDS-MIGRATED-TAPE KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDSMIGRATEDTAPE


GDSMT DEL CONT

GDS-MIGRATED-TAPE specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record that is found to be in migrated status where the device type is tape.


Restrictions: Can’t be used with See Step 3 of topic 'How Does CATSCRUB GDS-MIGRATED. Processing Work?' (page 15-18), for a detailed

description of anomaly processing.





GDS-MULTI-VOL-ERR KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDSMULTIVOLERR

Default: KEEP CONTINUE RC(4)

GDSMVE DEL CONT

GDS-MULTI-VOL-ERR specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record when any allocated portion of an active multi-volume generation is not found on the volumes processed by the CATSCRUB command. This anomaly keyword will be applied to entries that have a vol cell matching a volser in the MATCH-VOLSER list.

Caution: Give careful consideration before Required: No Restrictions: None

specifying DELETE, as it can result in a change in the relative number of generation data sets within a GDG. This can produce an unintended result when you are subsequently processing by relative generation number.


GDS-NOT-FOUND KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDSNOTFOUND


GDSNF DEL CONT

GDS-NOT-FOUND specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record when it does not physically exist on the volumes being processed by the CATSCRUB command. This anomaly keyword will be applied to entries that have a vol cell matching a volser in the MATCH-VOLSER list.







GDS-TAPE KEEP | DELETE CONTINUE | END RC

Alternate keyword form: GDSTAPE


GDST DEL CONT

GDS-TAPE specifies the disposition of an individual generation data set (GDS) subrecord within the GDG sphere record in the catalog, when it is determined that the data set physically resides on tape.


Restrictions: None See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

KEEP-DSN EXCLUDE-KEEP-DSN

Alternate keyword form(s): KEEPDSN EXCLUDEKEEPDSN

Default: None Required: None Restrictions: None

KD EXCKD

KEEP-DSN specifies one or more fully qualified or partially qualified data set names that will be exempted from CATSCRUB delete processing. EXCLUDE-KEEP-DSN specifies one or more fully qualified or partially qualified data set names that are to be excluded from the list of kept data set names built from the specification in the KEEP-DSN keyword. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

KEEP-TAPE EXCLUDE-KEEP-TAPE

Alternate keyword form(s): KEEPTAPE EXCLUDEKEEPTAPE


KT EXCKT

KEEP-TAPE specifies one or more fully qualified or partially qualified tape volume serial numbers that will be exempted from NONVSAM-TAPE(DELETE) and GDS-TAPE(DELETE) processing. EXCLUDE-KEEP-TAPE specifies one or more fully qualified or partially qualified tape volume serial numbers that are to be excluded from the list of tape volumes built from the specification in the KEEP-TAPE keyword. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).





KEEP-VOLSER EXCLUDE-KEEP-VOLSER

Alternate keyword form(s): KEEPVOLSER EXCLUDEKEEPVOLSER


KV EXCKV

KEEP-VOLSER specifies one or more fully qualified or partially qualified disk volume serial numbers that will be exempted from the delete processing of disk-orientated anomaly keywords. EXCLUDE-KEEP-VOLSER specifies one or more fully qualified or partially qualified disk volume serial numbers that are to be excluded from the list of disk volumes built from the specification in the KEEP-VOLSER keyword. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

MATCH-VOLSER EXCLUDE-MATCH-VOLSER

Alternate keyword form(s): MATCHVOLSER EXCLUDEMATCHVOLSER

Default: None Required: No. If these keywords are omitted, all online disk volumes on the system on which CATSCRUB is run are included in the list of volumes to process. Restrictions: None

MVOL EXCMV

MATCH-VOLSER and EXCLUDE-MATCH-VOLSER are used to customize the list of matched volumes typically for doing a simulation of the DR site while at the home site.

Beware: Restricting the matched volume list in EXECUTE mode, can delete valid catalog entries for data sets on disk volumes not in the matched volume list.

MATCH-VOLSER specifies one or more fully qualified or partially qualified volume serial numbers, indicating the volumes that CATSCRUB is to process in its synchronization of the specified BCSs. EXCLUDE-MATCH-VOLSER specifies one or more fully qualified or partially qualified volume serial numbers that are to be excluded from the list of volumes first built from the specification in the MATCH-VOLSER keyword.

MESSAGE-TEXT ABBREVIATED | FULL

Alternate keyword form: MESSAGETEXT

Default: FULL Required: No Restrictions: None

MSGTXT ABRV

MESSAGE-TEXT indicates the amount of IDCAMS messages printed with the CATSCRUB output. • ABBREVIATED – indicates that only the

summary report is produced. This report provides a count of each type of catalog record that has been deleted from the catalogs processed by CATSCRUB.

• FULL (the default) – provides a list of all of the matched volumes, a complete process log of all actions taken by the CATSCRUB command, indicating the name of every data set record that is deleted from the catalogs processed by CATSCRUB, as well as a summary report at the end which provides a count of each type of catalog records deleted.





NONVSAM-ALIAS-NO-REALNAME KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMALIASNOREALNAME


NVALINR DEL CONT

NONVSAM-ALIAS-NO-REALNAME specifies the disposition of a non-VSAM alias record, where the associated real data set related to this alias is not found within the volumes being matched to the catalogs. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

NONVSAM-MIGRATED KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMMIGRATED

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with NONVSAM-MIGRATED-DASD or NONVSAM-MIGRATED-TAPE.

NVM DEL CONT

NONVSAM-MIGRATED specifies the disposition of a non-VSAM data set catalog record when the data set is found to be in migrated status. Note that this keyword is specified for a standard non-VSAM data set, and does not include generation data sets. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

NONVSAM-MIGRATED-DASD KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMMIGRATEDDASD

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with NONVSAM-MIGRATED.

NVMD DEL CONT

NONVSAM-MIGRATED-DASD specifies the disposition of a non-VSAM data set catalog record when the data set is found to be in migrated status where the device type is disk. Note that this keyword is specified for a standard non-VSAM data set, and does not include generation data sets. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.





NONVSAM-MIGRATED-TAPE KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMMIGRATEDTAPE

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with NONVSAM–MIGRATED.

NVMT DEL CONT

NONVSAM-MIGRATED-TAPE specifies the disposition of a non-VSAM data set catalog record when the data set is found to be in migrated status where the device type is tape. Note that this keyword is specified for a standard non-VSAM data set, and does not include generation data sets. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

NONVSAM-MULTI-VOL-ERR KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMMULTIVOLERR


NVMVE DEL CONT

NONVSAM-MULTI-VOL-ERR specifies the disposition of the catalog record for a non-VSAM data set when any allocated portion of the data set is not found on the disk volumes processed by the CATSCRUB command. Non-SMS-specific candidate volumes are treated the same as a populated segment. This anomaly keyword will be applied to entries that have a vol cell matching a volser in the MATCH-VOLSER list. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

NONVSAM-NOT-FOUND KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMNOTFOUND


NVNF DEL CONT

NONVSAM-NOT-FOUND specifies the disposition of a non-VSAM data set catalog record, when the data set does not exist and it is determined that the NONVSAM-MIGRATE, NONVSAM-MULTI-VOL-ERR, and NONVSAMTAPE keywords do not apply. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.





NONVSAM-TAPE KEEP | DELETE CONTINUE | END RC

Alternate keyword form: NONVSAMTAPE


NVT DEL CONT

NONVSAM-TAPE specifies the disposition of a non-VSAM data set catalog record, when it is determined that the data set was cataloged on tape. See Step 3 of topic How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

OBJECT-ACCESS-METHOD OAM OBJECT-ACCESS-METHOD specifies the KEEP | DELETE DEL disposition of an OAM data set catalog record.

CONTINUE | END RC

CONT See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

Alternate keyword form: OBJECTACCESSMETHOD


VSAMSPHERE-MIGRATED KEEP | DELETE CONTINUE | END RC

Alternate keyword form: VSAMSPHEREMIGRATED

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with VSAMSPHERE-MIGRATED-DASD or VSAMSPHERE-MIGRATED-TAPE.

VM DEL CONT

VSAMSPHERE-MIGRATED specifies the disposition of a VSAM cluster sphere record in the catalog, when the data set is found to be in migrated status. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.





VSAMSPHERE-MIGRATED-DASD KEEP | DELETE CONTINUE | END RC

Alternate keyword form: VSAMSPHEREMIGRATEDDASD

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with VSAMSPHERE-MIGRATED.

VMD DEL CONT

VSAMSPHERE-MIGRATED-DASD specifies the disposition of a VSAM cluster sphere record in the catalog, when the data set is found to be in migrated status where the device type is disk. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

VSAMSPHERE-MIGRATED-TAPE KEEP | DELETE CONTINUE | END RC

Alternate keyword form: VSAMSPHEREMIGRATEDTAPE

Default: KEEP CONTINUE RC(4) Required: No Restrictions: Can’t be used with VSAMSPHERE-MIGRATED.

VMT DEL CONT

VSAMSPHERE-MIGRATED-TAPE specifies the disposition of a VSAM cluster sphere record in the catalog, when the data set is found to be in migrated status where the device type is tape. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.

VSAMSPHERE-MULTI-VOL-ERR KEEP | DELETE CONTINUE | END RC

Alternate keyword form: VSAMSPHEREMULTIVOLERR


VMVE DEL CONT

VSAMSPHERE-MULTI-VOL-ERR specifies the disposition of the cluster sphere record for a VSAM cluster when any allocated portion of the data set is not found on the volumes processed by the CATSCRUB command. See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed description of anomaly processing.





VSAMSPHERE-NOT-FOUND VNF VSAMSPHERE-NOT-FOUND specifies the KEEP | DELETE CONTINUE | END RC

DEL CONT

disposition of a VSAM cluster record when it is determined that the VSAMSPHERE-MIGRATE and VSAMSPHERE-MULTI-VOL-ERR keywords do not apply.

Alternate keyword forms: VSAMSPHERENOTFOUND

See Step 3 of topic 'How Does CATSCRUB Processing Work?' (page 15-18), for a detailed

Default: description of anomaly processing. KEEP CONTINUE RC(4) Required: No Restrictions: None




15.6 CATSCRUB Processing Notes

15.6.1 When Would CATSCRUB Be Run? Typical situations where CATSCRUB might be run are:

• When full volume backups are restored at the recovery site and you need to synchronize one or more catalogs (BCSs) with the restored volumes, eliminating any records from the BCSs that don't match up with the restored volumes.

• Or, right after 'simplexing' the target volumes that are the result of point-in-time (PIT) mirror splits.

15.6.2 CATSCRUB Simulation Processing The CATSCRUB command is very powerful, very fast, and performs direct I/O to the specified user and master catalogs, deleting records (scrubbing) that do not find a matching physical data set on the volumes to be searched. Use of SIMULATE mode is highly recommended, allowing you to test your processes and command setup prior to a DR test, and more importantly, before a real disaster recovery.

When SIMULATE is coded, CATSCRUB performs all of the processing logic of an actual BCS match to the specified volumes, but does not make any changes to any record within the BCSs in the include list. A complete SYSPRINT report is created, as if a real CATSCRUB were executed, enabling you to analyze the report to ensure the command setup, as well as the selected BCSs and volume(s) are correct. When you get to the DR site, you then change SIMULATE to EXECUTE and CATSCRUB is ready to run in 'real' mode.

Generally, the SIMULATE deletes will exactly match the EXECUTE deletes, but the deletes indicated by SIMULATE will vary from EXECUTE if one anomaly keyword deletes an item in EXECUTE mode that has an alias. The EXECUTE keyword, indicates that CATSCRUB is to perform all of it processing logic 'for real', and BCS updates are done for all catalog records that do not match physical data sets on the volumes to be searched, or if the records do not fit in the category of a specified anomaly condition.

15.6.3 Why Delete Catalog Entries With No Matching Physical Data Set? The reasons for eliminating catalog entries that don't find a matching physical data set on the restored volumes include:

• Catalog entries reflecting data sets that will never be restored, possibly because they were on volumes that will not be restored at the recovery site. An example in this category might be migrated data sets.

• Catalog entries reflecting data sets that will be restored later, from data set level backups. If the catalog entries for those data sets remain, they represent an already-existing catalog entry, and causes an error when an attempt is made to restore (and consequently catalog) the real data set.




15.6.4 How Does CATSCRUB Processing Work? Each CATSCRUB run will:

• List all of the anomaly keyword values used, as specified by the command, the INI, and the program defaults.

• List all of the DASD volumes to be specified for MATCH-VOLSER/EXCLUDE-MATCH-VOLSER when MSGTEXT(FULL) is specified.

• List, for each catalog to be scrubbed: – The catalog entries with RC value > 0 in corresponding anomaly keywords. – The catalog entries deleted with EXECUTE or simulated to be delete with SIMULATE. – A summary of catalog entries deleted.

• Produce a summary of catalog entries scrubbed from all catalogs processed.

The following steps describe the processing and the operative keywords at each step.

STEP 1: Create the list of BCSs to be included in the CATSCRUB

Required Keywords: BCS

Optional Keywords: EXCLUDE-BCS

CATSCRUB command processing begins by creating an 'include' list of catalogs (BCSs), based on the value(s) specified for the BCS keyword.

The BCS keyword is required, and the values you may specify are:

• One or more fully-qualified BCS names.

Note: You may choose to scrub one BCS per job and submit all jobs simultaneously, thereby decreasing the overall elapsed time of the CATSCRUB process.

• A BCS name mask – If a BCS name mask value is specified, it is applied against the names of all user catalogs connected in the master catalog for the system on which the CATSCRUB command is run, and every BCS name matching the mask is placed in the include list. For information on how to specify masks, refer to topic 'Mainstar Extended ACS Filtering Pattern Masks' (page 1-9).

• Or (**) – this would include all BCSs that are currently connected to the master catalog on the system on which you are running CATSCRUB.

Note: The master catalog is not placed in the include list, unless it has been explicitly specified. The master catalog is never selected from mask processing.

Invalid entries (a non-existent catalog name or a DSN which is not a catalog) appearing in the named BCSs will be noted in the CATSCRUB output with the following message before being excluded: MSC35029W BCS NOT IN MASTER CATALOG - IGNORED. BCS MASK=bcs mask | bcs name

After the include list is constructed, the command processor checks for specification of the EXCLUDE-BCS keyword, from which a list of BCS names to be excluded from CATSCRUB processing are removed from the include list. The result is the final list of BCS names that CATSCRUB is to process.

STEP 2: Identify the online disk volumes to be matched with the disk oriented BCS records

Optional Keywords: MATCH-VOLSER and EXCLUDE-MATCH-VOLSER

The list of online disk volumes to be matched with the BCS records is constructed by locating every online disk volume.

If you are testing CATSCRUB on your non-DR site in preparation for going to the DR site, you may wish to reduce the matched volume list by specifying MATCH-VOLSER and additionally the




EXCLUDE-MATCH-VOLSER keywords. The use of MATCH-VOLSER in EXECUTE mode other than MATCH-VOLSER(**), is strongly discouraged because it directs CATSCRUB to delete catalog items that may be on online volumes. If used, these keywords will reduce the volumes that are considered to be online. The EXCLUDE-MATCH-VOLSER keyword used with MATCH-VOLSER, reduces the match volume list further.

STEP 3: CATSCRUB processes catalog entries by BCS

Optional Keywords:

OBJECT-ACCESS-METHOD NONVSAM-ALIAS-NO-REALNAME

GDGBASE-NO-ACTIVE-GENS NONVSAM-MIGRATED

GDS-MIGRATED NONVSAM-MIGRATED-DASD

GDS-MIGRATED-DASD NONVSAM-MIGRATED-TAPE

GDS-MIGRATED-TAPE NONVSAM-MULTI-VOL-ERR

GDS-MULTI-VOL-ERR NONVSAM-NOT-FOUND

GDS-NOT-FOUND NONVSAM-TAPE

GDS-TAPE VSAMSPHERE-MIGRATED

VSAMSPHERE-MIGRATED-DASD VSAMSPHERE-MIGRATED-TAPE

VSAMSPHERE-MULTI-VOL-ERR VSAMSPHERE-NOT-FOUND

CATSCRUB processing sequentially reads through each BCS, in its entirety. Catalog entries for disk data sets that are fully established on a disk volume in the matched volume list are kept and CATSCRUB moves on to the next catalog entry. All other catalog entries are associated with one of the anomaly keywords.

Each anomaly keyword has the following syntax:

anomaly-keyword ( DELETE | KEEP, RC( nn | 4 ), END | CONTINUE )

DELETE | KEEP KEEP specifies that CATSCRUB should retain the catalog entry. DELETE (can also be specified as DEL) specifies that CATSCRUB should remove the catalog entry unless the appropriate keywords indicate otherwise. See step 4 below for more information.

RC(numeric value) The numeric value specifies the CATSCRUB return code if it is higher that the current CATSCRUB return code. The valid RC values that can be specified are from 09999. The RC value can be used to show you which anomalies have been found. A value of 4 will cause a CAT092xxW message and a value greater than 4 will cause a CAT09xxE message.




END | CONTINUE END specifies that CATSCRUB should immediately terminate processing after printing messages based on the RC value and then writing a CAT09223I indicating that the END directive applies. If (DELETE,END) is specified, the DELETE will not occur. CONTINUE specifies that CATSCRUB should not terminate, but continue processing. CONTINUE can be specified as CONT.

Each anomaly keyword you specify must have an RC value, either DELETE or KEEP, and either END or CONTINUE. The default values shown are the values that would be used if you did not specify the anomaly keyword. The default value for each anomaly keyword is set by your INI file specifications. Refer to the Backup & Recovery Manager Suite Installation & Maintenance Guide (document GC23-6062), Appendix B, for BRMINI token descriptions. If the INI values originally shipped with the product have not been changed, the keyword default values are the same as those specified in this book.

The catalog entry is kept and CATSCRUB moves on to the next catalog entry if KEEP is specified. The remaining catalog entries are candidates for delete processing as described in Step 4, based on additional keywords.

STEP 4: CATSCRUB anomaly processing for DELETE

Required Keywords: EXECUTE or SIMULATE

Optional Keywords: KEEP-DSN and EXCLUDE-KEEP-DSN

KEEP-VOLSER and EXCLUDE-KEEP-VOLSER

KEEP-TAPE and EXCLUDE-KEEP-TAPE

The following actions are taken when DELETE has been coded for an anomaly keyword that matches the catalog entry. Only when EXECUTE is specified is the catalog entry removed, with SIMULATE the deletes are only reported.

Tape-oriented data sets

Catalog entries referring to tape data sets are managed by tape-anomaly keywords. Tape-anomaly keywords include:

• NONVSAM-TAPE • GDS-TAPE

Their primary volume name will be compared with the KEEP-TAPE criteria. If the catalog entry’s volume matches an entry in the KEEP-TAPE list and does not match an entry in the EXCLUDE-KEEP-TAPE list, the catalog entry will be retained and CATSCRUB moves on to the next catalog entry.

If the catalog entry’s data set name matches an entry in the KEEP-DSN list and does not match an entry in the EXCLUDE-KEEP-DSN list, the catalog entry will be retained and CATSCRUB moves on to the next catalog entry. Otherwise the catalog entry is deleted.

DASD-oriented data sets

Catalog entries referring to disk data sets are managed by disk-anomaly keywords. Disk anomalies occur when the catalog entry doesn’t appear on disk. DASD-anomaly keywords include:

• GDS-MULTI-VOL-ERR • GDS-NOT-FOUND • NONVSAM-MULTI-VOL-ERR • NONVSAM-NOT-FOUND • VSAMSPHERE-MULTI-VOL-ERR • VSAMSPHERE-NOT-FOUND




Their primary volume name will be compared with the KEEP-VOLSER criteria. If the catalog entry’s volume matches an entry in the KEEP-VOLSER list and does not match an entry in the EXCLUDE-KEEP-VOLSER list, the catalog entry will be retained and CATSCRUB moves on to the next catalog entry.

If the catalog entry’s data set name matches an entry in the KEEP-DSN list and does not match an entry in the EXCLUDE-KEEP-DSN list, the catalog entry will be retained and CATSCRUB moves on to the next catalog entry. Otherwise the catalog entry is deleted

Other data sets

The remaining catalog entries are not associated in the catalog with disk or tape volumes, their anomaly keywords include:

• OBJECT-ACCESS-METHOD • GDGBASE-NO-ACTIVE-GENS • GDS-MIGRATED • GDS-MIGRATED-DASD • GDS-MIGRATED-TAPE • NONVSAM-ALIAS-NO-REALNAME • NONVSAM-MIGRATED • NONVSAM-MIGRATED-DASD • NONVSAM-MIGRATED-TAPE • VSAMSPHERE-MIGRATED • VSAMSPHERE-MIGRATED-DASD • VSAMSPHERE-MIGRATED-TAPE

If the catalog entry’s data set name matches an entry in the KEEP-DSN list and does not match an entry in the EXCLUDE-KEEP-DSN list, the catalog entry will be retained and CATSCRUB moves on to the next catalog entry. Otherwise the catalog entry is deleted.

15.6.5 Examples Below are a series of examples that are made progressively complex by adding keywords to the prior example.

Example 1: The simplest CATSCRUB command

The following command has the minimal of keywords and directs CATSCRUB to simulate delete processing on a single user catalog using all of the default values.

CATSCRUB SIMULATE BCS(TESTUCAT.UCAT1)

No catalog entries will be deleted because none of the default anomaly values indicate DELETE and SIMULATE is specified. CATSCRUB will list every catalog entry that it doesn’t find on DASD because the default RC values are each 4.

Example 2: Simulation of CATSCRUB at DR site that runs on home system

The following command might be used on a production site to simulate the environment at a DR site without the DASD volumes that begin with DV.

CATSCRUB SIMULATE BCS(TESTUCAT.UCAT1) -MATCH-VOLSER(**) EXCLUDE-MATCH-VOLSER(DV**)




Example 3: Simulation of CATSCRUB with an alternate value for an anomaly keyword

The following command changes the anomaly action for non-VSAM tape entries of the catalog.

CATSCRUB SIMULATE BCS(TESTUCAT.UCAT1) -MATCH-VOLSER(**) EXCLUDE-MATCH-VOLSER(DV**) -NONVSAM-TAPE(DELETE RC(8) CONTINUE)

The anomaly keyword specification NONVSAM-TAPE, indicates that all non-VSAM tape entries should be deleted were the command to be run in EXECUTE mode. Catalog entries for tape data sets can never be matched with DASD data sets, so all non-VSAM tape entries would be candidates for delete.

Example 4: Simulation of CATSCRUB that retains some non-VSAM tape entries

The following command changes the anomaly action for non-VSAM tape entries of the catalog.

CATSCRUB SIMULATE BCS(TESTUCAT.UCAT1) -MATCH-VOLSER(**) EXCLUDE-MATCH-VOLSER(DV**) -NONVSAM-TAPE( DELETE RC(8) CONTINUE ) -KEEP-DSN(**) EXCLUDE-KEEP-DSN(MYDSN**) -KEEP-TAPE(**) EXCLUDE-KEEP-TAPE(DT**)

The anomaly keyword specification NONVSAM-TAPE, indicates that all non-VSAM tape entries are candidates for delete processing were the command to be run in EXECUTE mode. Catalog entries for tape data sets can never be matched with DASD data sets, so all non-VSAM tape entries would be candidates for delete.

The KEEP-DSN/EXCLUDE-KEEP-DSN and the KEEP-TAPE/EXCLUDE-KEEP-TAPE criteria indicates that only tapes with data set names beginning with MYDSN and volumes beginning with “DT” should be deleted.

15.7 CATSCRUB Benchmark Run Timings

15.7.1 Comparative Timings – CATSCRUB vs. IDCAMS Following are several benchmarks for CATSCRUB, indicating quite impressive performance compared to the time and I/O cost it would require to achieve the same catalog cleanup results with IDCAMS.

The elapsed time can be reduced by simultaneously running individual CATSCRUB commands as separate jobs rather than one CATSCRUB BCS(**) command. By running 47 jobs in 47 initiators, each scrubbing one BCS, an installation was able to overlap 372 minutes into 23 minutes.

Timing 1.

records.

.

Timing 2.

A BCS that contained 976,767 total catalog entries was 'scrubbed' with the CATSCRUB command. Almost 59% of the catalog's records were removed – a total of 573,227

This test was run at a Beta customer site, and the overall system load at the time is not known. The total elapsed run time for CATSCRUB was just over 51 minutes, or 187 catalog entries per secondAn IDCAMS DELETE NOSCRATCH comparison run was not made, but it is estimated that it would have required at least four hours to accomplish this same test.

A CATSCRUB test was run where 127,242 catalog entries were 'scrubbed' from a catalog at a DR test. The elapsed time was 12 minutes. This had previously required over 4 hours to accomplish a similar cleanup with IDCAMS.




15.8 Sample CATSCRUB Commands and Output Examples

15.8.1 CATSCRUB – EXECUTE Mode to Cleanup One BCS and Two Volsers This example of CATSCRUB runs in EXECUTE mode, synchronizing one specifically-named BCS, with two specific volsers. The BCS named CRIUCAT.TESTCRP1 is 'scrubbed', so that only records pointing to volser CRIN00 or CRIN01 remain in it when the processing is complete. If catalog entries pointing to any other volser are encountered in the BCS, they are removed.

For illustration purposes, all of the allowable 'detection anomaly' switches are specified. Each specifies a return code to be raised whenever an anomaly of that class is detected. To assure execution continues, each anomaly class has the keyword CONTINUE specified.

The SYSPRINT output from the CATSCRUB command execution is shown below. The keyword MESSAGE-TEXT(FULL) was specified, so a detailed report of every catalog object processed by the command is listed (only catalog entries that are removed from the catalog are listed). Many lines of the output have been removed from this report, leaving only one example of each situation type. The output has also been slightly edited, to fit the page format.

As you can see from the summary at the bottom, almost 2,000 catalog entries were removed from the catalog (1826 to be exact), including nonVSAM, VSAM, nonVSAM alias, and GDG records. The elapsed time for this run was 7 seconds, which is significantly faster than would be required if the entries were removed with IDCAMS processing.




The command is: CATSCRUB BCS(CRIUCAT.TESTCRP1) -

MATCH-VOLSER(CRIN00 CRIN01) -EXECUTE -MESSAGE-TEXT(FULL) -GDGBASE-NO-ACTIVE-GENS GDS-MIGRATED GDS-MULTI-VOL-ERR GDS-NOT-FOUND GDS-TAPE NONVSAM-MIGRATED NONVSAM-MULTI-VOL-ERR NONVSAM-NOT-FOUND NONVSAM-TAPE NONVSAM-ALIAS-NO-REALNAME OBJECT-ACCESS-METHOD VSAM-SPHERE-MULTI-VOL-ERR VSAM-SPHERE-MIGRATED VSAM-SPHERE-NOT-FOUND

(DELETE RC(12) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(0) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(12) CONTINUE)-(KEEP RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)

The output from this command is shown below.

Figure 15-1: CATSCRUB – Single BCS synchronized with two volumes

CATSCRUB BCS(CRIUCAT.TESTCRP1) -MATCH-VOLSER(CRIN00 CRIN01) -EXECUTE -MESSAGE-TEXT(FULL) –GDGBASE-NO-ACTIVE-GENS GDS-MIGRATED GDS-MULTI-VOL-ERR GDS-NOT-FOUND GDS-TAPE NONVSAM-MIGRATED NONVSAM-MULTI-VOL-ERR NONVSAM-NOT-FOUND NONVSAM-TAPE NONVSAM-ALIAS-NO-REALNAME OBJECT-ACCESS-METHOD VSAM-SPHERE-MULTI-VOL-ERR VSAM-SPHERE-MIGRATED VSAM-SPHERE-NOT-FOUND

(DELETE RC(12) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(0) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(12) CONTINUE)-(KEEP RC(4) CONTINUE)-(DELETE RC(12) CONTINUE)-(DELETE RC(4) CONTINUE)-(DELETE RC(4) CONTINUE)

******************* * RUNTIME OPTIONS * * EXECUTE MODE * ******************* NONVSAM-MULTI-VOL-ERR DISP: DELETE RC: 4 PROC: CONTINUE NONVSAM-MIGRATED DISP: DELETE RC: 0 PROC: CONTINUE NONVSAM-TAPE DISP: DELETE RC: 12 PROC: CONTINUE NONVSAM-NOT-FOUND DISP: DELETE RC: 4 PROC: CONTINUE NONVSAM-ALIAS-NO-REALNAME DISP: DELETE RC: 12 PROC: CONTINUE

VSAM-SPHERE-MULTI-VOL-ERR DISP: DELETE RC: 12 PROC: CONTINUE VSAM-SPHERE-MIGRATED DISP: DELETE RC: 4 PROC: CONTINUE VSAM-SPHERE-NOT-FOUND DISP: DELETE RC: 4 PROC: CONTINUE

Continued on next page




Continued from previous page

GDS-MULTI-VOL-ERR DISP: DELETE RC: 4 PROC: CONTINUE GDS-MIGRATED DISP: DELETE RC: 12 PROC: CONTINUE GDS-TAPE DISP: DELETE RC: 12 PROC: CONTINUE GDS-NOT-FOUND DISP: DELETE RC: 4 PROC: CONTINUE

GDG-BASE-NO-ACTIVE-GENS DISP: DELETE RC: 12 PROC: CONTINUE

OBJECT-ACCESS-METHOD DISP: KEEP RC: 4 PROC: CONTINUE

************************************* * CATALOGS TO BE PROCESSED * * EXECUTE MODE * *************************************

CRIUCAT.TESTCRP1

CATALOGS PROCESSED : 1

******************************************************************* * PROCESSING CATALOG: CRIUCAT.TESTCRP1 * * EXECUTE MODE * ******************************************************************* MS035013I CRISCRP1.ABAR.C11V1111 :ENTRY DELETED - CRIS00 NOT MOUNTED MS035019I CRISCRP1.VSAM.FILE.DATA:TRUENAME ENTRY DELETED- CLUSTER DELETED MS035019I CRISCRP1.VSAM.FILE.INDEX: TRUENAME ENTRY DELETED- CLUSTER DELETED MS035013I CRISCRP1.VSAM.FILE :ENTRY DELETED - CRIS01 NOT MOUNTED MS035016I CRISCRP1.ALIAS.FILE :NON-VSAM ALIAS DELETED- REAL NAME DELETED MS035014W CRISCRP1.GDG1.G0001V00 :GDS-NOT-FOUND - RC= 4 MS035014W CRISCRP1.GDG1.G0002V00 :GDS-NOT-FOUND - RC= 4 MS035015E CRISCRP1.GDG1 :ALL ACTIVE GENERATIONS DELETED- RC=12 MS035022I CRISCRP1.GDG1 :GDG BASE DELETED - ALL ACTIVE

GENERATIONS DELETED MS035014W CRISCRP1.GDSU.G0003V00 :GDS-NOT-FOUND - RC= 4 MS035015E CRISCRP1.GDSU :ALL ACTIVE GENERATIONS DELETED- RC=12 MS035022I CRISCRP1.GDSU :GDG BASE DELETED - ALL ACTIVE

GENERATIONS DELETED

********************************************

* CATALOG SUMMARY: (EXECUTE) *

******************************************** NONVSAM RECORDS DELETED : 94 VSAM SPHERES DELETED : 106 NONVSAM ALIAS RECORDS DELETED: 1 GDS ENTRIES DELETED : 1,602GDG BASES DELETED : 23 OAM DELETED : 0

***************************************************** * GRAND SUMMARY: (EXECUTE) * ***************************************************** NONVSAM RECORDS DELETED : 94 VSAM SPHERES DELETED : 106 NONVSAM ALIAS RECORDS DELETED: 1 GDS ENTRIES DELETED : 1,602GDG BASES DELETED : 23 OAM DELETED : 0

CATALOGS SELECTED/PROCESSED : 1 1

CAT09001I CATSCRUB PROCESSING COMPLETE. HIGHEST RETURN CODE WAS 0




15.8.2 CATSCRUB – SIMULATE and Premature Termination by END Specification This example of CATSCRUB illustrates a SIMULATE run (SIMULATE is the default), testing the command at the home site in preparation for later use at the DR site. In the example, the BCS named USERCAT.UCAT1 is 'scrubbed', and because the MATCH-VOLSER keyword is not specified, the BCS is processed against all volumes online to the system that CATSCRUB is running on.

For illustration purposes, all of the allowable 'detection anomaly' switches are specified. Each specifies a return code to be raised whenever an anomaly of that class is detected. All anomaly classes have the keyword CONTINUE specified, except for TAPE ERROR, which requests END upon first occurrence of that error situation. An error of that type was identified during processing, and CATSCRUB processing was immediately terminated upon the first occurrence. CATSCRUB BCS(USERCAT.UCAT1) SIMULATE -

MESSAGE-TEXT(FULL) -GDGBASE-NO-ACTIVE-GENS (DELETE RC(12) CONTINUE)-GDS-MIGRATED (KEEP RC(12) CONTINUE )-GDS-MULTI-VOL-ERR (KEEP RC(4) CONTINUE) -GDS-NOT-FOUND (KEEP RC(4) CONTINUE) -GDS-TAPE (KEEP RC(12) CONTINUE) -NONVSAM-ALIAS-NO-REALNAME (KEEP RC(12) CONTINUE) -NONVSAM-MIGRATED (KEEP RC(0) CONTINUE) -NONVSAM-MULTI-VOL-ERR (KEEP RC(4) CONTINUE) -NONVSAM-NOT-FOUND NONVSAM-TAPE OBJECT-ACCESS-METHOD

(KEEP RC(8) CONTINUE) -(KEEP RC(12) END) -(KEEP RC(4) CONTINUE) -

VSAM-SPHERE-MIGRATED (KEEP RC(4) CONTINUE) -VSAM-SPHERE-MULTI-VOL-ERR (KEEP RC(4) CONTINUE) -VSAM-SPHERE-NOT-FOUND (KEEP RC(4) CONTINUE)

The SYSPRINT output from the CATSCRUB command execution is shown on the next page. Many lines of the output have been removed from this report, so that the report fits on a single page. The output has also been slightly edited, to fit the page format.

The keyword MESSAGE-TEXT(FULL) was specified, so a detailed report of every catalog object processed by the command is listed (only catalog entries that are removed from the catalog are listed). Due to the premature termination of the command, a summary paragraph is not printed.

Figure 15-2: CATSCRUB – Simulate BCS with END termination

CATSCRUB BCS(USERCAT.UCAT1) SIMULATE -MESSAGE-TEXT(FULL) -GDGBASE-NO-ACTIVE-GENS (KEEP RC(12) CONTINUE) -GDS-MIGRATED (KEEP RC(12) CONTINUE) -GDS-MULTI-VOL-ERR (KEEP RC(4) CONTINUE) -GDS-NOT-FOUND (KEEP RC(4) CONTINUE) -GDS-TAPE (KEEP RC(12) CONTINUE) -NONVSAM-ALIAS-NO-REALNAME (KEEP RC(12) CONTINUE) -NONVSAM-MIGRATED (KEEP RC(0) CONTINUE) -NONVSAM-MULTI-VOL-ERR (KEEP RC(4) CONTINUE) -NONVSAM-NOT-FOUND (KEEP RC(8) CONTINUE) -NONVSAM-TAPE (KEEP RC(12) END) -OBJECT-ACCESS-METHOD VSAM-SPHERE-MIGRATED VSAM-SPHERE-MULTI-VOL-ERR VSAM-SPHERE-NOT-FOUND

Note: 'END'(KEEP RC(4) CONTINUE) -(KEEP RC(4) CONTINUE) -(KEEP RC(4) CONTINUE) -(KEEP RC(8) CONTINUE)






******************* * RUNTIME OPTIONS * * SIMULATE MODE * ******************* NONVSAM-MULTI-VOL-ERR NONVSAM-MIGRATED NONVSAM-TAPE NONVSAM-NOT-FOUND NONVSAM-ALIAS-NO-REALNAME

VSAM-SPHERE-MULTI-VOL-ERR VSAM-SPHERE-MIGRATED VSAM-SPHERE-NOT-FOUND

GDS-MULTI-VOL-ERR GDS-MIGRATED GDS-TAPE GDS-NOT-FOUND

GDG-BASE-NO-ACTIVE-GENS

OBJECT-ACCESS-METHOD

**************************** * CATALOGS TO BE PROCESSED * * SIMULATE MODE * ****************************

USERCAT.UCAT1

DISP: KEEP RC: 4 PROC: CONTINUE DISP: KEEP RC: 0 PROC: CONTINUE DISP: KEEP RC: 12 PROC: END DISP: KEEP RC: 8 PROC: CONTINUE DISP: KEEP RC: 12 PROC: CONTINUE

DISP: KEEP RC: 4 PROC: CONTINUE DISP: KEEP RC: 4 PROC: CONTINUE DISP: KEEP RC: 8 PROC: CONTINUE

DISP: KEEP RC: 4 PROC: CONTINUE DISP: KEEP RC: 12 PROC: CONTINUE DISP: KEEP RC: 12 PROC: CONTINUE DISP: KEEP RC: 4 PROC: CONTINUE

DISP: KEEP RC: 12 PROC: CONTINUE

DISP: KEEP RC: 4 PROC: CONTINUE

CATALOGS PROCESSED : 1

******************************************************************** * PROCESSING CATALOG: USERCAT.UCAT1 * * SIMULATE MODE * ******************************************************************** MS035015E AB01.EXTRACT.G0001V00 :GDS-MIGRATED - RC=12 MS035015E AB01.EXTRACT.G0002V00 :GDS-MIGRATED - RC=12 MS035015E AMPW.TEST.GDG :GDG-BASE-NO-ACTIVE-GENS - RC=12 MS035013I BB01.ISPF.CATALOG.ERROR:ENTRY DELETED - NOT ON VOLUME MS035015E BK.ASAPTEST.GDG1 :GDG-BASE-NO-ACTIVE-GENS - RC=12 MS035015E BK.CRSU.TESTGDG2 :GDG-BASE-NO-ACTIVE-GENS - RC=12 MS035013I DCD.NO.DASD :ENTRY DELETED - NOT ON VOLUME MS035013I DCD.NO.DASD.MISS :ENTRY DELETED - NOT ON VOLUME MS035013I DCD.NO.DASD.NOVOL :ENTRY DELETED - 386003 NOT MOUNTED MS035015E DH.GDG1.G0012V00 :GDS-MIGRATED - RC=12 MS035015E DH.OPEN.ISSUES.G0010V00:GDS-MIGRATED - RC=12 MS035015E DH.OPEN.ISSUES.G0011V00:GDS-MIGRATED - RC=12 MS035013I DR03.NVSAM1 :ENTRY DELETED - NOT ON VOLUME MS035015E DS01.ASAP.ABCD.G0009V00:GDS-MIGRATED - RC=12 MS035015E DS01.ASAP.ABCD.G0010V00:GDS-MIGRATED - RC=12 MS035015E DS01.ASAP.ABCD.G0011V00:GDS-MIGRATED - RC=12 MS035015E DS01.ASAP.ABCD.G0012V00:GDS-MIGRATED - RC=12 MS035015E DS01.ASAP.ABCD.G0013V00:GDS-MIGRATED - RC=12 MS035015E DS01.DS7.C.C01V0007 :NONVSAM-TAPE - RC=12

MS035015E CATSCRUB PROCESSING PREMATURELY TERMINATED DUE TO 'END' REQUEST ON NON-VSAMERROR ANOMALY

******************************************** * CATALOG SUMMARY: (SIMULATE) * ******************************************** NONVSAM RECORDS DELETED : 2 VSAM SPHERES DELETED : 3 NONVSAM ALIAS RECORDS DELETED: 0 GDS ENTRIES DELETED : 0 GDG BASES DELETED : 3






******************************************** * GRAND SUMMARY: (SIMULATE) * ******************************************** NONVSAM RECORDS DELETED : 2 VSAM SPHERES DELETED : 3 NONVSAM ALIAS RECORDS DELETED: 0 GDS ENTRIES DELETED : 0 GDG BASES DELETED : 3

CAT01008I COMMANDS PROCESSED: 1 CAT01009I CATSCRUB EXECUTION COMPLETE. HIGHEST RETURN CODE WAS 12




Appendix A A All/Star: Skeleton Processing and Skeleton Variables

A.1 Process Flow Overview Restore JCL and utility control statements are constructed by running the ASTBLDRJ program.

Desired data sets and/or volumes to be restored are selected by the parameters supplied to ASTBLDRJ. From the information stored in the Backup & Recovery Manager Suite (BRM) Inventory Data Set when data sets and/or volumes were backed up, All/Star determines the utility and in some cases the option that was used within a utility to perform the backup(s).

Associated with each utility/backup option is a default skeleton name to be used in the generation of restore JCL and utility control statements.

Skeletons consist of model JCL and utility control statements that, when merged with data set and volume attributes stored in the BRM Inventory Data Set, create output tailored to the requirements for restoring a specific data set or volume.

In order to support conditional generation of selected output, and to deal with arrays of data, skeleton processing includes the programming language functionality of IF/THEN/ELSE logic and looping.

Output syntax responsibility

• The author of a skeleton is responsible for the syntax of any generated output. • The file tailoring process is in fact unaware of what any model line represents – i.e. that it

might be JCL, IDCAMS control statements, etc. • In addition to adhering to syntax rules, the author is responsible for including only those

variables where after substitution the value will be appropriate.

Variables

• A basic function of the file tailoring process is the ability to substitute a value for a variable specified in a skeleton model line. Variables are denoted by an & as the first character.

• Many variables are set by All/Star using data set attributes stored from the backup in the BRM Inventory Data Set. These variables names are fixed. Not all may be set to a valid value depending on the applicability for the data set of concern.

• User chosen variables may be defined and set to a value using the skeleton )SETC and )SETN commands. )SETC is for character type variables and )SETN is for numeric type variables.

• Any variable name referenced in a skeleton must have been previously declared. Note that all documented All/Star variables are declared but may not be set to a valid value if not appropriate for the type of data set being processed.

Restore methodologies

The user is responsible for using skeletons to generate restore JCL/control statements that reflect the strategies in a DR plan.

For instance:

Deletion before allocation

For restores where the utility does not allocate the target data set, the default skeletons generate a DELETE followed by a DELETE NOSCRATCH prior to allocation of the target data set. This assumes the data set about to be restored should replace any existing data set or an existing catalog

Appendix A A-1 Mainstar Software Corporation ©2006 All/Star: Skeleton Processing and Skeleton Variables SC23-6061-00

PROPRIETARY: Unauthorized use, reproduction or distribution prohibited.


entry. DELETE NOSCRATCHs are issued to cover situations where a catalog entry exists but the corresponding data set is not found.

All/Star methodology for VSAM KSDSs with AIXs

All/Star does not track backups of AIXs and consequently assumes AIXs will be rebuilt rather than restored. For backup/restore utilities that do not offer a SPHERE option, the default All/Star skeletons upon encountering a VSAM base cluster generate defines and rebuilds for any associated AIXs, using the association data saved in the BRM Inventory Data Set when the base cluster was backed up. Likewise the default skeletons include the generation of associated PATH statements, again from data saved in the BRM Inventory Data Set.

A.2 Suggestions for Creating New Skeletons or Altering Copies of Distributed Skeletons

Maintain a copy of the skeletons as they were distributed by Mainstar

• During product maintenance, new versions of the skeletons will be installed. Thus any skeleton changes made by the customer will be replaced.

Make sure variables are appropriate where used

• Because the file tailoring process is unaware of the types of statements being generated, and the intended result of the output, All/Star file tailoring cannot ascertain whether the use of a variable will make sense for the desired output.

• Use )IF / THEN / )ELSE logic to assure that variables are appropriate for the type of data set being restored and the type of VSAM structure.

Make sure after substitution the generated statement will be syntactically correct

• Some data set attributes are always set to one of some number of valid keywords, such as VSAM REUSE | NOREUSE. These types of variables can usually be placed in a skeleton model output line with no concern.

• For attributes that can have no value, if in doubt about whether the resulting model output line will be valid if no value is substituted, surround the model line with an )IF/ )ENDIF statement testing the variable for a NULL value such that the model line will not be generated if the variable value is null.

• Arrays of volume serial numbers can be tricky depending on the required output syntax. For this reason, the distributed Skeleton library has a number of common skeletons designed to be used in a nested skeleton scenario for generating the required JCL and control statements.

• To avoid continuation problems, where possible, as in situations where parameters are enclosed with parentheses, isolate the open and close parentheses to lines with no other parameters so the lines within the parentheses can always include the continuation character.

Mainstar Software Corporation ©2006 A-2 Appendix A SC23-6061-00 All/Star: Skeleton Processing and Skeleton Variables



A.3 Commands Commands known to skeleton processing are denoted by a ) as the first character.

COMMAND DESCRIPTION AND USAGE

)COPY member name

• This instructs the skeleton processor to copy member name into the current skeleton before continuing processing.

• The member being copied may contain )COPY commands but nested )COPY commands may copy the same member only once. In other words, the process does not support recursive )COPYs.

• The limit for nested )COPY statements is 50. • Use nested )COPYs to simplify skeletons and/or ensure that common

requirements are generated the same way. Also use )COPY statements rather than employ PROCs. PROCs are not allowed within skeletons.

)COPYJOBSTMT member name

• This must be the first statement in each skeleton member. Use the )COPYJOBSTMT rather than a native JOB statement in skeletons. This allows for the file tailoring process to determine when and if an expanded skeleton should contain a JOB statement.

• The member name is the name of the member in the skeleton library that contains the JOBCARD skeleton to use if All/Star decides a job card is needed. See Chapter 13, All/Star: Build Restore, for the rules and user control over when )COPYJOBSTMTs are in fact expanded.

• A member specified by the )COPYJOBSTMT command cannot contain another )COPYJOBSTMT command or a )COPY command.

)ELSE • This allows alternate processing when the )IF evaluation is false. • It must be between )IF and )ENDIF statements at the same nesting level. • Only one )ELSE is allowed for an )IF level.

)ENDIF Terminates the )IF statement at the same nesting level.

)ENDLOOP Terminates a )LOOP structure.

)IF var1 comparator value | var2

• var1 specifies a declared variable name. • comparator specifies how var1 will be compared to value or var2. • For character type variables, the valid comparators are EQ or NE. • For numeric type variables, the valid comparators are EQ, NE, LT, GT, LE,

or GE. • value specifies a literal value to be compared to var1. • var2 specifies a variable to be compared to var1. • value, or the contents of var2, must be the same data type as var1. • The relational expression is evaluated for a true or false condition. If the

condition is true, the skeleton input records between the )IF and the corresponding )ENDIF or )ELSE are processed. If the condition is false, the records down to the next )ELSE or )ENDIF are skipped. These statements may be nested. There is no nesting limit.

• The )IF must be terminated by an )ENDIF.




COMMAND DESCRIPTION AND USAGE

)IF / )ELSE / )ENDIF Usage Notes If/then/else logic may be required to control conditional generation of output. The most obvious need for this is already eliminated if the default selection of skeleton member by utility is used. However, even within a given utility it may be necessary to conditionally generate output. If conditional output generation becomes too complex, another option is to create a specific skeleton and supply it in the ASTBLDRJ parameter list as an override to the default.

)LEAVE Exit the current loop structure.

)LOOP ON #DSNCNT | #BVOLCNT | #CVOLCNT | #DVOLCNT | #IVOLCNT

• )LOOP ON provides the ability to generate multiple output records or groups of output records from a single input source. Two situations may require this, one where a single backup command resulted in multiple data sets backed up that need to be explicitly specified in a restore, and the other where multiple VOLSERs need to be specified in the restore JCL/control statements.

• ON is a required keyword for )LOOP meaning loop on a count. The loop count is specified by supplying one of the All/Star control variables (denoted by a # as the first character): #DSNCNT, #BVOLCNT, #CVOLCNT, #DVOLCNT, and #IVOLCNT.

• Associated with each control variable is a variable to be used in the body of the loop whose value will change during each pass through the loop. The correlations between control variables and value variables are found in the 'Control Names' table in the next section.

• All statements between the )LOOP and )ENDLOOP are repeated for each pass through the loop.

• )LOOP commands may be nested. There is no nesting limit. • )LOOP ON does not alter the value of control variables.

)SET# • Set the value of a control name. • Operand must be one of the control names. • Operand 2 may be either a value or an existing numeric character type

variable. Example: )SET# #DSNCNT 20

)SETC var1 value | variable-name

• Declares a new character type variable or changes the value of an existing one.

• Operand 1 must be a new or existing character type variable name. • Operand 2 may be either a value or an existing character type variable.

)SETN var1 value | var2 [ + | - number ]

• Declares a new numeric type variable or changes the value of an existing one.

• Operand 1 must be a new or existing numeric type variable name. • Operand 2 may be either a value or an existing numeric character type

variable. • Optionally, a value (number) may be add to or subtracted from var1 after its

value has been set or changed. Examples: )SETN &STEPNO 1

)SETN &MYCOUNT &MYCOUNT + 1




A.4 Control Names For use with LOOP ON commands only.

#CONTROL NAME DESCRIPTION AND USAGE

#AIXCNT Count of the AIXs (alternate indexes) associated with a VSAM base cluster. When used to control a LOOP ON, each time through the loop the VSAM attribute variables will reflect each AIX cluster. The intended restore procedure for VSAM clusters with AIXs is to first define and reload the base cluster followed by a loop that contains the define and rebuild for each AIX. This should be followed by another loop to define all PATHs – see #PATHCNT. In a LOOP ON #AIXCNT the variable &AIXNAME will contain the name of the AIX cluster and variable &CDSNAME will contain the name of the associated base cluster.

#BVOLCNT Backup volser count

#BVOLCNT contains the count of restore input volumes (output from the backup). When used to control a LOOP ON, each time through the loop the value of &VOLSER will be set to the next volser the data set was backed up to. Use this control variable with &VOLSER in skeletons where you need to specify the restore input volumes.

#CVOLCNT Cluster volser count

#CVOLCNT contains the count of VSAM cluster volumes the cluster original resided on. When used to control a LOOP ON, each time through the loop the value of &CVOLUMES will be set to the next volser the cluster of concern was allocated on.

Note: Although provided, control variables and associated volume variables are supplied for the data and index components if you desire to restore the data and index components to the same respective volumes they were originally allocated on.

#DSNCNT Data set name count

Count of data sets backed up by the current utility command. When used to control a LOOP ON, each time through loop the value of &DSNAME will be set to the next backed-up data set name from the array of names saved in the BRM Inventory Data Set. Example when restoring from a FDR or DSS logical dump //FILTDD DD*

INCLUDE( -)LOOP ON #DSNCNT

&DSNAME )ENDLOOP

)

#DVOLCNT Data component volser count

#DVOLCNT contains the count of VSAM data component volumes the original data component resided on. When used to control a LOOP ON, each time through the loop the value of &DVOLUMES will be set to the next volser the data component of concern was allocated on.




#CONTROL NAME DESCRIPTION AND USAGE

#IVOLCNT Index component volser count

#IVOLCNT contains the count of VSAM index component volumes the original index component initially resided on. When used to control a LOOP ON, each time through the loop the value of &IVOLUMES will be set to the next volser the data component of concern was allocated on.

#PATHCNT Count of the PATHs associated with AIXs for a VSAM base cluster. When used to control a LOOP ON, each time through the loop the PATH variables will reflect each PATH associated with an AIX. The intended restore procedure for VSAM clusters with AIXes is to first define and reload the base cluster, followed by a loop that contains the define and rebuild for each AIX, followed by a loop to define all PATHs.

#VOLCNT Non-VSAM volser count

#VOLCNT contains the count of non-VSAM volumes the original data set resided on. Non-VSAM data sets only. When used to control a LOOP ON, each time through the loop, the value of &VOLSER will be set to the next volser the data set of concern was allocated on. Use this control variable with &VOLSER in skeletons where you wish to allocate the output from the restore to the same volumes the data set originally resided on.




A.4.1 Generic Variables

Note: In addition to the comparators shown, NULL can be used to test for a variable with no assigned value.

GENERIC VARIABLE NAME VALID COMPARATORS DESCRIPTION AND USAGE

&ACCOUNTING EQ | NE Accounting data (32 bytes)

&ADALOADLIB EQ | NE LINKLIST | name of Adabas LOADLIB For decision about whether to insert a STEPLIB in Adabas Restore jobs. LINKLIST indicates no STEPLIB.

&DSNTYPE EQ | NE A typical use of &DSNTYPE is to vary the statements generated by a skeleton based on the type of data set being restored. See distributed SKELLIB member REPRO01 for an example of allocation differences between types of VSAM structures and non-VSAM data sets. ALIAS ESDS GDGBASE GDS HFS KSDS LDS NONVSAM PATH PDS PDSE RRDS USERCAT VRRDS

&EXPDT EQ | NE YYYYDDD Julian date for the EXPDT parameter for the TO parameter of IDCAMS. Places the same expiry date on the restored data set as the original data set had.

&EXPDTJCL EQ | NE YYYY/DDD Julian date for the EXPDT parameter of JCL. Places the same expiry date on the restored data set as the original data set had.

&FAVERLOADLIB EQ | NE LINKLIST | name of CA-FAVER LOADLIB For decision about whether to insert a STEPLIB in CA-FAVER Restore jobs. LINKLIST indicates no STEPLIB.




GENERIC VARIABLE NAME VALID COMPARATORS DESCRIPTION AND USAGE

&FDRLOADLIB EQ | NE LINKLIST | name of FDR LOADLIB For decision about whether to insert a STEPLIB in FDR Restore jobs. LINKLIST indicates no STEPLIB.

&NXTVOLSER EQ | NE Contains the next volume serial of a list or an * which indicates the next volume is a candidate volume.

&NEWHLQ EQ | NE High-level qualifier to be used when doing an AST restore with a new name. The value of this variable comes from the INI token RENAME_HLQ. Note: If RENAME_HLQ = *, the value of this variable will be 'null'.

&REPLACE EQ | NE Y | N For data set restores, should the restore delete the original data set?

&SELECTDSN EQ | NE Y | N For selective data set restore from a full volume dump.

&SMS EQ | NE Y | N Test &SMS wherever a difference is required in output statements, depending on whether the data set being restored was originally SMS managed or not. Testing &SMS EQ Y is one way to ensure other SMS-only related variables are used only when appropriate.

&USERCAT EQ | NE The user catalog where the data set of concern was originally cataloged.

&VOLSER EQ | NE The volume serial a non-VSAM data set originally resided on (input to backup). Use &VOLSER in conjunction with #VOLCNT to restore a data set to the same volumes it originally resided on, such as for non-SMS managed data sets where you wish to allocate to specific volumes rather than using an esoteric.




A.4.2 Event Fields


EVENT FIELDS VALID COMPARATORS DESCRIPTION

&ADADBNAME EQ | NE Adabas database name.

&ADADB# EQ | NE Adabas database number.

&ADAMODE EQ | NE Mode specified at backup time. M = Multi S = Single

&ADADEVICE EQ | NE Device name specified at backup time.

&ADASVC EQ | NE SVC number specified at backup time.

&ADAAMODE EQ | NE AMODE at backup time

&EABARSGEN EQ | NE Relative generation of an ABARS backup tracked by ABM.

&EABARSSTACK EQ | NE STACK | NOSTACK option specified for an ABARS backup tracked by ABM.

&EABARSUNIT EQ | NE HSM unit name for an ABARS backup tracked by ABM.

&EAGGNAME EQ | NE ABARS aggregate name if data is to be restored from an aggregate backup.

&ECMDNUMBER EQ | NE | GT | GE | LT | LE Command number. Where the execution of a backup utility includes multiple commands, AST internally numbers each command beginning with the number 1.

&EDAD EQ | NE DSN of BRM’s DAD data set. Used only when necessary to insert the DAD file name in Restore JCL.

&EDEVNAME EQ | NE Device name for volume that has been dumped.

&EHSMDATE EQ | NE Date HSM BACKVOL command was executed.

&EINVDB EQ | NE DSN of BRM’s INVDB data set. Used only when necessary to insert the INVDB file name in Restore JCL.

&EJOBNAME EQ | NE Job name of the backup event.

&EPARMLIB EQ | NE DSN of BRM’s PARMLIB data set. Used only when necessary to insert the P file name in Restore JCL.

&EPROCNAME EQ | NE Proc name of the backup event.

&EREADERDATE none Reader date (SMF date) of the backup event.




EVENT FIELDS VALID COMPARATORS DESCRIPTION

&EREADERTIME none Reader time (SMF time) of the backup event.

&ERETCODE1 EQ | NE | GT | GE | LT | LE Return code from the backup utility.

&ERETCODE2 EQ | NE | GT | GE | LT | LE Return code from AST’s tracking of the utility.

&ESTEPDATE none Start date of the backup step.

&ESTEPNAME EQ | NE Step name of the backup.

&ESTEPTIME none Start time of the backup step.

&ESYSID EQ | NE System ID of the image the backup was executed on.

&EVOLSER EQ | NE Source volser for volume dumps.

&LOADLIB EQ | NE DSN of BRM’s LOAD1 data set. Used only when necessary to insert the LOAD1 file name in Restore JCL.

A.4.3 Source File Variables Source file variables contain information relating to the data set and volume(s) input to the backup utility tracked, hence the variables beginning with 'B' for backup.

Note: In addition to the comparators shown, NULL can be used to test for a variable with no assigned value. Member names cannot be restored, only data sets.

SOURCE FILE VARIABLE VALID COMPARATORS DESCRIPTION

&BDEVNAME EQ | NE Device name

&BDSNAME EQ | NE Backup output data set name

&BFILENO EQ | NE | GT | GE | LT | LE File number (1st volume)

&BMEMBER EQ | NE Member name (if a PDS)

&BVERSION EQ | NE | GT | GE | LT | LE Version number (HSM backup only)

&BVOLCNT EQ | NE | GT | GE | LT | LE Number of volumes in &BVOLUMES

&BVOLUMES EQ | NE All source volumes




A.4.4 Cluster Variables Cluster variables pertain to the information available at the cluster level for a VSAM data set. Some attributes are available at both the cluster and component level. Distributed default skeletons that allocate VSAM data sets opt to define attributes at the data and index levels rather than at the cluster level where there is a choice.


CLUSTER VARIABLE VALID COMPARATORS VALUE

&CAIXNAME EQ | NE AIX name related to base cluster

&CAIXSUFX EQ | NE AIX cluster name suffix. This is the AIX cluster name minus the high level qualifier.

&CALLOCTYPE EQ | NE BLK | CYL | TRK

&CBUFFERSPACE EQ | NE | GT | GE | LT | LE Buffer size

&CBWO EQ | NE TYPECICS | TYPEIMS | NO

&CCISIZE EQ | NE | GT | GE | LT | LE CI size

&CDATACLAS EQ | NE SMS data class

&CDEVNAME EQ | NE Generic device name (e.g. 3390)

&CDSNAME EQ | NE Base cluster name

&CDSNSUFX EQ | NE Cluster name suffix. This is the cluster name minus the high level qualifier.

&CERASE EQ | NE ERASE | NOERASE

&CEXCEPEXIT EQ | NE Exception exit name

&CFREESPACECA EQ | NE | GT | GE | LT | LE CA free space

&CFREESPACECI EQ | NE | GT | GE | LT | LE CI free space

&CIMBED EQ | NE IMBED | NOIMBED

&CINHIBIT EQ | NE INHIBIT | UNINHIBIT

&CKEYLEN EQ | NE | GT | GE | LT | LE Key length

&CKEYOFFSET EQ | NE | GT | GE | LT | LE Key offset

&CMAXLRECL EQ | NE | GT | GE | LT | LE Maximum LRECL

&CMAXRECORDS EQ | NE | GT | GE | LT | LE Maximum record (RRDS)

&CMGMTCLAS EQ | NE SMS management class

&CORDERED EQ | NE ORDERED | UNORDERED

&COWNER EQ | NE Owner

&CREPLICATE EQ | NE REPLICATE | NOREPLICATE

&CREUSE EQ | NE REUSE | NOREUSE

&CSHROPT1 EQ | NE Cross region share option




A.4.5 Data Components


DATA COMPONENT VALID COMPARATORS VALUE

&DAIXNAME EQ | NE AIX name

&DAIXSUFX EQ | NE Data component name suffix. This is the data component name minus the high level qualifier.

&DALLOCTYPE EQ | NE BLK | CYL | TRK

&DBUFFERSPACE EQ | NE | GT | GE | LT | LE Data buffer space

&DCISIZE EQ | NE | GT | GE | LT | LE CI size

&DCLUSTER EQ | NE Cluster name

&DDEVNAME EQ | NE Generic device name (e.g. 3390)

&DDSNAME EQ | NE Data component name

&DDSNSUFX EQ | NE Data component name suffix. This is the data component name minus the high level qualifier.

&DERASE EQ | NE ERASE | NOERASE

&DEXCEPEXIT EQ | NE Exception exit name

&DFREESPACECA EQ | NE | GT | GE | LT | LE CA free space

&DFREESPACECI EQ | NE | GT | GE | LT | LE CI free space

&DKEYLEN EQ | NE | GT | GE | LT | LE Key length

&DKEYOFFSET EQ | NE | GT | GE | LT | LE Key offset

&DMAXLRECL EQ | NE | GT | GE | LT | LE Maximum LRECL

&DOWNER EQ | NE Owner

&DSHROPT1 EQ | NE Cross region share option

&DSHROPT2 EQ | NE Cross system share option

&DSPACEPRI EQ | NE | GT | GE | LT | LE Primary space

&DSPACESEC EQ | NE | GT | GE | LT | LE Secondary space

&DVOLCNT EQ | NE | GT | GE | LT | LE Number of volumes in &DVOLUMES

&DVOLUMES none All data volumes




A.4.6 Index Components


INDEX COMPONENT VALID COMPARATORS VALUE

&IAIXNAME EQ | NE AIX name

&IAIXSUFX EQ | NE Index component name suffix. This is the index component name minus the high level qualifier.

&IALLOCTYPE EQ | NE BLK | CYL | TRK

&IBUFFERSPACE EQ | NE | GT | GE | LT | LE Index buffer space

&ICISIZE EQ | NE | GT | GE | LT | LE CI size

&ICLUSTER EQ | NE Cluster name

&IDEVNAME EQ | NE Generic device name (e.g. 3390)

&IDSNAME EQ | NE Index component name

&IDSNSUFX EQ | NE Data component name suffix. This is the data component name minus the high level qualifier.

&IERASE EQ | NE ERASE | NOERASE

&IEXCEPEXIT EQ | NE Exception exit

&IFREESPACECA EQ | NE | GT | GE | LT | LE CA free space

&IFREESPACECI EQ | NE | GT | GE | LT | LE CI free space

&IKEYLEN EQ | NE | GT | GE | LT | LE Key length

&IKEYOFFSET EQ | NE | GT | GE | LT | LE Key offset

&IMAXLRECL EQ | NE | GT | GE | LT | LE Maximum LRECL

&IOWNER EQ | NE Owner

&ISHROPT1 EQ | NE Cross region share option

&ISHROPT2 EQ | NE Cross system share option

&ISPACEPRI EQ | NE | GT | GE | LT | LE Primary space

&ISPACESEC EQ | NE | GT | GE | LT | LE Secondary space

&IVOLCNT EQ | NE | GT | GE | LT | LE Number of volumes in &IVOLUMES

&IVOLUMES none All index volumes




A.4.7 Path Variables


PATH VARIABLE VALID COMPARATORS VALUE

&PATHENTRYNAME EQ | NE Path entry name

&PATHESUFX EQ | NE Path entry name suffix. This is the path entry name minus the high level qualifier.

&PATHNAME EQ | NE Path name

&PATHSUFX EQ | NE Path name suffix. This is the path name minus the high level qualifier.

&PATHOWNER EQ | NE Path owner

&PATHUPDATE EQ | NE UPDATE | NOUPDATE




A.4.8 Non-VSAM Variables


NON-VSAM VARIABLES VALID COMPARATORS VALUE

&ACCOUNTING EQ | NE Accounting information

&ALLOCTYPE EQ | NE BLK | CYL | TRK

&BLKSIZE EQ | NE | GT | GE | LT | LE Block size

&DATACLAS EQ | NE SMS data class

&DEVNAME EQ | NE Generic device name (e.g., 3390) for original data set

&DIRBLKS EQ | NE | GT | GE | LT | LE Directory blocks for PDSes

&DSNAME EQ | NE Backup input data set name

&DSNSUFX EQ | NE Backup input data set name suffix. This is the backup input data set name minus the high level qualifier.

&DSORG EQ | NE Data set organization. Valid values: DA, IS, PO, PS, U, VE, VK, VL, VR, VS, VV

&GDSSTATUS none ACTIVE | DEFERRED | ROLLEDOUT

&LRECL EQ | NE | GT | GE | LT | LE LRECL

&MGMTCLAS EQ | NE SMS Management class

&OWNER EQ | NE Owner

&RECFM EQ | NE Record format. Valid values: F, FA, FAS, FB, FBA, FBAM, FBAS, FBM, FBMS, FBS, FM, FMS, FS, V, VA, VAS, VB, VBA, VBAM, VBAS, VBM, VBMS, VBS, VM, VMS, VS, U, UBA, UBAM, UBAS, UBM, UBMS, UBS

&SPACEPRI EQ | NE | GT | GE | LT | LE Primary space

&SPACESEC EQ | NE | GT | GE | LT | LE Secondary space

&STORCLAS EQ | NE Storage class

&VOLCNT EQ | NE | GT | GE | LT | LE Number of volumes &VOLUMES

&VOLUMES EQ | NE All Volumes




A.4.9 Non-VSAM Alias Variables

Note on non-VSAM aliases and GDG base attributes: Variables are supplied that could be used to recreate non-VSAM aliases and GDG base catalog entries. However, it is not uncommon to initially establish catalogs in DR scenarios such that all aliases and GDG base definitions are established as part of the initial conditioning of the catalogs.


NON-VSAM ALIAS VARIABLE VALID COMPARATORS DESCRIPTION

&ALIASNAME EQ | NE Alias name. This variable only supports a single alias. If multiple aliases exist for a true name &ALIASNAME will be set to the last alias name found in the association record.

&ALIASRELATED EQ | NE Data set alias is related to (truename). &DSNAME1 can also be used to specify the related true name if defining an alias.

A.4.10 GDG Base Variables

Note on non-VSAM aliases and GDG base attributes: Variables are supplied that could be used to recreate non-VSAM aliases and GDG base catalog entries. However, it is not uncommon to initially establish catalogs in DR scenarios such that all aliases and GDG base definitions are established as part of the initial conditioning of the catalogs.


GDG BASE VARIABLE VALID COMPARATORS DESCRIPTION

&GDGEMPTY EQ | NE EMPTY | NOEMPTY attribute captured from the GDG base catalog record at the time of the backup.

&GDGLIMIT EQ | NE | GT | GE | LT | LE GDG limit value captured from the GDG base catalog record at the time of the backup.

&GDGSCRATCH EQ | NE SCRATCH | NOSCRATCH attribute captured from the GDG base catalog record at the time of the backup.




Index +

+/- (Field Description) Jobname List Panel.......................................... 4-17 Search for Data Set Panel.................................. 6-5

+/- (Line Command) Full Volume Dumps Panel .................................. 4-5 Jobname List Panel.......................................... 4-17

A ABACKUP Verifies

Load Inventory (All) Panel ................................ 2-20 Unload Inventory Data Set (All) Panel .............. 2-24

ABACKUP/Job Generations Load Inventory (All) Panel ................................ 2-20 Unload Inventory Data Set (All) Panel .............. 2-24

ABARS ABACKUPS ...............................................6-1 ACS masking ..........................................................1-9 ADD

Job Group List Panel ........................................ 4-21 Add Jobname or Mask to Job Group List Panel

CAN – cancel ................................................... 4-23 D – delete a job name/mask............................. 4-23 END(PF3)/SAVE .............................................. 4-23 I – insert a blank line ........................................ 4-23 NOJOBGRP ..................................................... 4-23 NOTBYTHIS..................................................... 4-23 R – repeat an entry........................................... 4-23

ADMIN Sub-menu ..........................................2-7, 2-29 Option 1 – Define Utility Equivalents ................ 2-29

All/Star batch commands ................................................ 9-1 batch processing ................................................ 9-1 overview ............................................................. 1-2 skeleton processing............................................ A-1 using with ASAP............................................... 12-1

All/Star Backup Reports report 1

Overlap by Dataset Report ..............................7-3 report 10

Critical with No All/Star Backup Record Report7-24 report 11

Critical with All/Star Backup Record Report...7-26 report 12

BKUPEND Summary Report .........................7-29 report 13

Overlap by Application...................................7-31 report 2

Overlap by Backup Event Report.....................7-5 report 3

Overlap by Job Groups Report ........................7-7 report 4

Data Set List Report ........................................7-9 report 5

Data Set List with Outputs .............................7-12 report 6

Full Volume Dump List Report .......................7-14 report 7

Jobname List Report......................................7-16 report 8

Jobnames Not Tracked by a Job Group ........7-19 report 9

What Isn't Backed Up Report.........................7-21 All/Star Load Inventory Panel

Build/Submit JCL .............................................. 2-18 Build/View JCL ................................................. 2-18 Exclude Job ...................................................... 2-18 Include Generations ......................................... 2-18 Include Job ....................................................... 2-18 Input File DSN .................................................. 2-18 Output Inventory DSN ...................................... 2-18 Replace ............................................................ 2-18

All/Star Reports .......................................................7-1 All/Star Tracking

started task ....................................................... 14-1 All/Star Unload Inventory Panel

Build/Submit JCL .............................................. 2-22 Build/View JCL ................................................. 2-22 Exclude Job ...................................................... 2-22 Include Generations ......................................... 2-22 Include Job ....................................................... 2-22 Output File DSN ............................................... 2-22

Alloc JCLOUT Old or NewSet Up RESTORE Panel .................................. 4-12

anomaly detection and processing CATSCRUB command ................................... 15-19

anomaly detection keywords CATSCRUB command ..................................... 15-1

anomaly processing CATSCRUB ISPF panel ..................................... 5-5

APPL Application List Panel ....................................... 4-28 BKUPEND parameters ..................................... 12-5 BLDREST command ...................................... 13-10 REPORT ASAP2BRM-NB parameters............. 9-37 REPORT BKUPEND parameters ..................... 9-41 REPORT OVERLAPA-AST parameters ........... 9-43

Appl Name(s) Overlap by Application Report Panel................ 7-31

APPLEND ...........................................................12-12 application backup and restore .............................12-1 Application List Panel

APPL Field........................................................ 4-28 ASAP Cycle Field ............................................. 4-28 BKUPEND Date and Time Field ....................... 4-28 C (Field Description)......................................... 4-28 Cycle Field........................................................ 4-28 Field Descriptions ............................................. 4-28 R – Perform a Restore of the Job Group .......... 4-27 REFresh ........................................................... 4-27

Application List Search Setup Panel Don't show this panel again.............................. 4-26 Store values to use as default for this userid .... 4-26

Applications overview ............................................................. 2-6

ARECOVER Generations

Mainstar Software Corporation ©2006 i Index SC23-6061-00



Load Inventory (All) Panel.................................2-20 Unload Inventory Data Set (All) Panel...............2-24

ASAP using with All/Star..............................................12-1

ASAP Application BKUPEND Summary Report Panel...................7-29 Critical in ASAP with All/Star Backup Record Report

Panel .............................................................7-27 Critical with No All/Star Backup Record Report Panel

......................................................................7-24 ASAP Cycle

Application List Panel........................................4-28 ASAP2BRM-B report

REPORT command ..........................................9-39 ASAP2BRM-B sub-command

REPORT command ..........................................9-39 ASAP2BRM-NB report

REPORT command ..........................................9-37 ASAP2BRM-NB sub-command

REPORT command ..........................................9-37 AST

preparing for data collection..............................14-5 started task .......................................................14-1

ASTBLDRJ .............................................................A-1 ASTEXPIRE command ................................9-4, 12-11 Auto Expand List

Full Volume Dumps Search Setup Panel ............4-3 Jobname List Search Setup Panel ....................4-15 Search for Data Set Setup Panel ........................6-3

AUTODUMP ........................................................... 9-3

B backing up the BRM IDS....................................... 14-9 Backup & Recovery Manager Suite

error and product messages view ................................................................. 2-9

BACKUP CYCLES TO RETAIN.................12-2, 12-12 Backup Name

Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel ..................................6-5

Backup Tracking EXCLUDE Filters Panel .............. 3-5 Backup Tracking Filters EXCLUDE Panel

CAN – cancel ......................................................3-5 D – delete a tracking filter ...................................3-6 END(PF3)/SAVE .................................................3-5 I – insert a blank line ...........................................3-6 Job Name............................................................3-7 Job Step ..............................................................3-7 Proc Step ............................................................3-7 Program ..............................................................3-6 R – repeat a tracking filter ...................................3-6 UserID.................................................................3-7 Utility ...................................................................3-7

Backup Tracking Filters INCLUDE Panel CAN – cancel ......................................................3-3 END(PF3)/SAVE .................................................3-3 line commands ....................................................3-6 UserID.................................................................3-4 Utility ...................................................................3-4

Backup Tracking INCLUDE Filters Panel................ 3-2 D – delete a tracking filter ...................................3-3 I – insert a blank line ...........................................3-3 Job Name............................................................3-4

Job Step ..............................................................3-4 line commands ....................................................3-3 Proc Step ............................................................3-4 Program ..............................................................3-4 R – repeat a tracking filter ...................................3-3

backups back up or reorganize the BRM IDS..................14-9 expiring..............................................................14-4 monitor ........................................................ 2-6, 4-1 perform................................................................4-1 submit.......................................................... 2-6, 4-1

BADBKUPRC BLDREST command .......................................13-11 Set Up RESTORE Panel...................................4-12

BAD-BKUP-RC BKUPEND parameters......................................12-5

batch commands LOADIDS ............................................................9-7 REPORT ...........................................................9-13 REPORT ASAP2BRM-B ...................................9-39 REPORT ASAP2BRM-NB.................................9-37 REPORT BKUPEND .........................................9-41 REPORT DSNLIST-AST ...................................9-20 REPORT DSNLIST-O .......................................9-22 REPORT FVDLIST............................................9-24 REPORT JOBLIST............................................9-26 REPORT NOJOBGRP ......................................9-29 REPORT OVERLAPA-AST...............................9-43 REPORT OVERLAPD-AST...............................9-15 REPORT OVERLAPE-AST...............................9-17 REPORT OVERLAPJOBGRP...........................9-18 UNLOADIDS ........................................... 2-25, 9-11

Batch Intercept File ...............................................14-1 update using ISPF panels ...................................3-9

batch processing.....................................................9-1 AUTODUMP overview.........................................9-3 REPORT Overview ...........................................9-13

BCDS REPORT-NOBACKUP parameters ...................9-31

BCS keyword CATSCRUB command......................................15-6

BIF Batch Intercept File ...........................................14-1 update using ISPF panels ...................................3-9

binary value for EBCDIC character .......................1-10 BKUPEND Date and Time

Application List Panel ........................................4-28 BKUPEND parameters ................................12-5, 12-6

APPL .................................................................12-5 BAD-BACKUP-RC.............................................12-5 CHANGED-SINCE-LAST-BKUP-RC.................12-6 EXCL-ACCOMPANY.........................................12-7 EXCL-ALLOCATE.............................................12-8 NO-BACKUP-FOUND-RC.................................12-5

BKUPEND program ..............................................12-3 BKUPEND report

REPORT command...........................................9-41 BKUPEND sub-command

REPORT command...........................................9-41 BKUPEND Summary Report

All/Star Backup Reports, report 12 ....................7-29 BKUPEND Summary Report Panel

ASAP Application ..............................................7-29 Build/Submit JCL...............................................7-29

Index ii Mainstar Software Corporation ©2006 SC23-6061-00



Build/View JCL ................................................. 7-29 Cycle ................................................................ 7-29 Exec/View Online ............................................. 7-29

BLDRESTJob Card........................................................... 2-15

BLDREST command.............................................13-8 APPL .............................................................. 13-10 BADBKUPRC ................................................. 13-11 CMDNO.......................................................... 13-11 COPY ............................................................. 13-11 CYCLE ........................................................... 13-11 DSN................................................................ 13-10 EXCLAPPL..................................................... 13-12 EXCLDSN ...................................................... 13-12 EXCLJOB ....................................................... 13-12 EXCLLOC....................................................... 13-12 EXCLVOL....................................................... 13-13 GEN ............................................................... 13-13 INCLDSN........................................................ 13-13 INCLLOC........................................................ 13-14 INCLPHYDUMP ............................................. 13-14 JOBGROUP ................................................... 13-11 JOBNAME ...................................................... 13-10 NEWHLQ........................................................ 13-14 NOBKUPFOUND ........................................... 13-14 REPLACE....................................................... 13-14 SKEL .............................................................. 13-15 STEPNAME.................................................... 13-15 STEPNO......................................................... 13-15 USEGEN0ALL................................................ 13-15 USEGEN0NOBKUP ....................................... 13-15 VOL ................................................................ 13-11

BRM (Line Command) History Panel ...................................................... 8-4

BRM Inventory Data Set backing up ........................................................ 14-9 remove ABARS Manager entries ..................... 9-10 remove All/Star entries from ............................. 2-21 reorganizing...................................................... 14-9

BRMBPROC procedure .............................12-10, 15-3 submit LOADIDS ..................................... 2-17, 2-19 submit UNLOADIDS ......................................... 2-21

BRMINI values ............................................................... 2-10 view .................................................................. 2-10

BRMMSG ................................................................2-9 Browse/Edit Backup Tracking EXCLUDE Filters

overview ............................................................. 2-5 panel .................................................................. 3-5

Browse/Edit Backup Tracking INCLUDE Filters overview ............................................................. 2-5 panel .................................................................. 3-2

Build Batch Intercept File and Refresh ASToverview ............................................................. 2-5

Build JCL/Edit for Submit Submit CATSCRUB panel.................................. 5-3

Build Restore Commands INCRJOBNAMEOUT........................................ 13-6 INCRMEMBEROUT ......................................... 13-6 JOBNAMEOUT ................................................ 13-5 MEMBEROUT .................................................. 13-6 STEPLIMITOUT ............................................... 13-7

Build/Submit JCL All/Star Load Inventory Panel ........................... 2-18

All/Star Unload Inventory Panel........................ 2-22 BKUPEND Summary Report Panel .................. 7-29 Critical in ASAP with All/Star Backup Record Report

Panel............................................................. 7-27 Critical with No All/Star Backup Record Report Panel

...................................................................... 7-24 Data Set List Report Panel ............................... 7-10 Data Set List with Outputs Report Panel .......... 7-12 Full Volume Dump List Report Panel................ 7-14 Jobname List Report Panel .............................. 7-16 Jobnames Not Tracked by a Job Group Report Panel

...................................................................... 7-19 Load Inventory Data Set Panel......................... 2-20 Overlap by Application Report Panel................ 7-31 Overlap by Backup Event Report Panel ............. 7-5 Overlap by Data Set Report Panel ..................... 7-3 Overlap by Job Groups Report Panel ............. 7-7Unload Inventory Data Set (All) Panel .............. 2-24 What Isn't Backed Up Report Panel ................. 7-22

Build/View JCL All/Star Load Inventory Panel ........................... 2-18 All/Star Unload Inventory Panel........................ 2-22 BKUPEND Summary Report Panel .................. 7-29 Critical in ASAP with All/Star Backup Record Report

Panel............................................................. 7-27 Critical with No All/Star Backup Record Report Panel

...................................................................... 7-24 Data Set List Report Panel ............................... 7-10 Data Set List with Outputs Report Panel .......... 7-12 Full Volume Dump List Report Panel................ 7-14 Jobname List Report Panel .............................. 7-16 Jobnames Not Tracked by a Job Group Report Panel

...................................................................... 7-19 Load Inventory (All) Panel ................................ 2-20 Overlap by Application Report Panel................ 7-31 Overlap by Backup Event Report Panel ............. 7-5 Overlap by Data Set Report Panel ..................... 7-3 Overlap by Job Groups Report Panel................. 7-7 Set Up RESTORE Panel .................................. 4-12 Unload Inventory Data Set (All) Panel .............. 2-24 What Isn't Backed Up Report Panel ................. 7-22

BUILD-BIFDSN .......................................................9-5

C C (Field Description)

Application List Panel ....................................... 4-28 Full Volume Dumps Panel .................................. 4-5 History Panel ...................................................... 8-5 Job Group List Panel ........................................ 4-22 Jobname List Panel .......................................... 4-17 Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel .................................. 6-5

CAN Add Jobname or Mask to Job Group List Panel 4-23 Backup Tracking Filters EXCLUDE Panel .......... 3-5 Backup Tracking Filters INCLUDE Panel ........... 3-3

CATSCRUB command.................................. 5-2, 15-6 anomaly detection and processing ................. 15-19 build command using ISPF................................. 5-2 comparative run timings ................................. 15-22 examples ............................................. 15-23, 15-26 how CATSCRUB processing works................ 15-18 processing notes ............................................ 15-17

Mainstar Software Corporation ©2006 iii Index SC23-6061-00



simulation capability ..........................................15-1 simulation processing......................................15-17 synchronize ICF catalogs and data volumes.....15-1 syntax................................................................15-4

CATSCRUB ISPF panel anomaly processing ............................................5-5

CHANGED-SINCE-LAST-BKUP-RC BKUPEND parameters......................................12-6

CHANGED-SINCE-LAST-BKUP-RC parameter . 12-13cluster variables....................................................A-11 CMDNO

BLDREST command.......................................13-11 command line

how to use...........................................................2-1 jump to other option panel...................................2-1

Command LineField Type ...........................................................2-2

commands ASTEXPIRE .............................................9-4, 12-11 AUTODUMP........................................................9-3 BUILD-BIFDSN ...................................................9-5 CATSCRUB ........................................................5-2 CATSCRUB overview .......................................15-1 CATSCRUB syntax ...........................................15-4 LOADIDS ............................................................9-6 LOADIDS examples ............................................9-9 LOADIDS parameter definitions ..........................9-7 LOADIDS syntax .................................................9-6 REFRESH-AST...................................................9-5 UNLOADIDS .....................................................9-10 UNLOADIDS examples.....................................9-13 UNLOADIDS parameter definitions...................9-11 UNLOADIDS syntax..........................................9-10

comparative run timings CATSCRUB command....................................15-22

continuation symbol .............................................. 1-10 control names .........................................................A-5 Copy

Set Up RESTORE Panel...................................4-12 COPY

BLDREST command.......................................13-11 Critical in ASAP with All/Star Backup Record Panel

ASAP Application ..............................................7-27 Data Set Name(s) or Mask(s)............................7-27 Exec/View Online ..............................................7-27 Include BCDS....................................................7-27

Critical in ASAP with All/Star Backup Record Report Panel Build/Submit JCL...............................................7-27 Build/View JCL ..................................................7-27

Critical with All/Star Backup Record Report All/Star Backup Reports, report 11....................7-26

Critical with No All/Star Backup Record Report All/Star Backup Reports, report 10....................7-24

Critical with No All/Star Backup Record Report Panel ASAP Application ..............................................7-24 Build/Submit JCL...............................................7-24 Build/View JCL ..................................................7-24 Data Set Name(s) or Mask(s)............................7-24 Exec/View Online ..............................................7-24 Include BCDS....................................................7-24

current active load modules view...................................................................2-11

current memory usage

view ...................................................................2-12 Cycle

Application List Panel ........................................4-28 BKUPEND Summary Report Panel...................7-29

CYCLE BLDREST command .......................................13-11 REPORT BKUPEND parameters ......................9-41

D D (Line Command)

Add Jobname or Mask to Job Group List Panel 4-23 Application List Panel ........................................4-27 Backup Tracking Filters EXCLUDE Panel...........3-6 Backup Tracking INCLUDE Filters Panel ............3-3 Job Group List Panel.........................................4-21

DAD started task........................................................11-1

DAD Databaseremove obsolete entries ....................................11-6

DAD Monitor Panel Option 1 – Display DAD Status .........................2-26 Option 2 – Display DAD Statistics .....................2-27 Option 3 – Display DAD Commands .................2-28

DAD9254M JCL Procedure...................................11-6 DADSMFTK

messages..........................................................11-2 operator commands ..........................................11-1 started task........................................................11-1

data components ................................................. A-13 data set

search ......................................................... 2-6, 6-1 Data Set

HRECOVER Options Panel ..............................6-14 Data Set List Report

All/Star Backup Reports, report 4 ........................7-9 Data Set List Report Panel

Build/Submit JCL...............................................7-10 Build/View JCL ..................................................7-10 Data Set Name(s) or Mask(s)............................7-10 Exec/View Online ..............................................7-10 From Date .........................................................7-10 Job Name..........................................................7-10 To Date .............................................................7-10 Type(s) ..............................................................7-10

Data Set List with Outputs All/Star Backup Reports, report 5 ......................7-12

Data Set List with Outputs Report Panel Build/Submit JCL...............................................7-12 Build/View JCL ..................................................7-12 Event Name(s) or Mask(s) ................................7-12 Exec/View Online ..............................................7-12

Data Set Name or Mask Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel...................................6-5

Data Set Name(s) or Mask(s) Critical in ASAP with All/Star Backup Record Report


......................................................................7-24 Data Set List Report Panel................................7-10

Data Set Space Display Options Panel Places right of decimal ......................................2-14 Space Unit.........................................................2-14

Index iv Mainstar Software Corporation ©2006 SC23-6061-00



data volumes synchronize with ICF catalogs.......................... 15-1

Date Full Volume Dumps Panel .................................. 4-6 History Panel ...................................................... 8-5 Jobname List Panel........................................ 4-18Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel.................................. 6-5

DATEREPORT DSNLIST-AST parameters ............... 9-20 REPORT FVDLIST parameters........................ 9-24 REPORT JOBLIST parameters........................ 9-27

DATETYPE REPORT JOBLIST parameters........................ 9-27

default search criteria..............................................4-2 defaults for anomaly detection keywords

CATSCRUB command ................................... 15-19 Description

Job Group List Panel ........................................ 4-22 DFSMShsm

AUTODUMP....................................................... 9-3 DIAGNOSTICS Sub-menu.............................2-7, 2-11

Option 1 – Products used by Backup & RecoveryManager ....................................................... 2-11

Option 2 – Active Load Modules....................... 2-11 Option 3 – Free Memory................................... 2-12

Display Full Vol Dumps Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel.................................. 6-5

Display HSM Incr Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel.................................. 6-5

Display overlaps only Search for Data Set Panel.................................. 6-5

Don't show this panel again Application List Search Setup Panel ................ 4-26 History Search Setup Panel ............................... 8-3 Job Group List Search Setup Panel ................. 4-20 Jobname List Search Setup Panel ................... 4-16 Quick Search for Data Set Setup Panel ............. 6-7 Search for Data Set Setup Panel ....................... 6-3

DS REPORT ASAP2BRM-B parameters ............... 9-39 REPORT ASAP2BRM-NB parameters............. 9-37 REPORT DSNLIST-AST parameters ............... 9-20 REPORT OVERLAPD-AST parameters........... 9-15

DSN BLDREST command ...................................... 13-10

DSN or Mask Quick Search for Data Set Setup Panel ............. 6-7 Search for Data Set Setup Panel ....................... 6-3

DSNLIST-AST report examples .......................................................... 9-21 REPORT command.......................................... 9-20

DSNLIST-AST sub-commandREPORT command.......................................... 9-20

DSNLIST-O report about ................................................................ 9-22 examples .......................................................... 9-22 parameters ....................................................... 9-22 REPORT command.......................................... 9-22 syntax ............................................................... 9-22

DSNLIST-O sub-command REPORT command.......................................... 9-22

Dynamic Backup/Reorganization overview ........................................................... 10-1

E E (Line Command)

Application List Panel ....................................... 4-27 Job Group List Panel ........................................ 4-21

EBCDIC code tables .............................................1-10 email address.............................................................3 END(PF3)/SAVE

Add Jobname or Mask to Job Group List Panel 4-23 Backup Tracking Filters EXCLUDE Panel .......... 3-5 Backup Tracking Filters INCLUDE Panel ........... 3-3

error and product messages .................. 1-10, 2-9, 9-2 EV

REPORT OVERLAPE-AST parameters ........... 9-17 Event Date

Full Volume Dumps Search Setup Panel ........... 4-3 History Search Setup Panel ............................... 8-3

event fields ............................................................. A-9 Event Name(s) or Mask(s)

Data Set List with Outputs Report Panel .......... 7-12 Overlap by Backup Event Panel ......................... 7-5

Event/Logical Aggregate Load Inventory (All) Panel ................................ 2-20 Unload Inventory Data Set (All) Panel .............. 2-24

Events with Errors Load Inventory (All) Panel ................................ 2-20 Unload Inventory Data Set (All) Panel .............. 2-24

Events with Warnings Load Inventory (All) Panel ................................ 2-20 Unload Inventory Data Set (All) Panel .............. 2-24

examples CATSCRUB.................................................... 15-26 CATSCRUB command ................................... 15-23 DSNLIST-AST .................................................. 9-21 DSNLIST-O ...................................................... 9-22 FVDLIST........................................................... 9-25 JOBLIST ........................................................... 9-28 LOADIDS............................................................ 9-9 OVERLAPJOBGRP.......................................... 9-18 REPORT ASAP2BRM-B .................................. 9-40 REPORT ASAP2BRM-NB ................................ 9-38 REPORT BKUPEND ........................................ 9-42 REPORT NOJOBGRP ..................................... 9-29 REPORT OVERLAPA-AST .............................. 9-44 REPORT OVERLAPD-AST .............................. 9-16 REPORT OVERLAPE-AST .............................. 9-17 UNLOADIDS..................................................... 9-13

EXCL_BUT_CRITICAL ............................. 12-3, 12-12 EXCL-ACCOMPANY

BKUPEND parameters ..................................... 12-7 EXCL-ALLOCATE

BKUPEND parameters ..................................... 12-8 EXCLAPPL

BLDREST command ...................................... 13-12 EXCLDSN

BLDREST command ...................................... 13-12 REPORT-NOBACKUP parameters .................. 9-32

EXCLJOB BLDREST command ...................................... 13-12 LOADIDS parameters......................................... 9-7 UNLOADIDS parameters ................................. 9-11

Mainstar Software Corporation ©2006 v Index SC23-6061-00



EXCLLOC BLDREST command.......................................13-12

EXCLUCATREPORT command ..........................................9-32

Exclude DSN or Mask What Isn't Backed Up Report Panel ..................7-22

Exclude Job All/Star Load Inventory Panel............................2-18 All/Star Unload Inventory Panel ........................2-22

Exclude Location Set Up RESTORE Panel...................................4-12

Exclude UCAT or Mask What Isn't Backed Up Report Panel ..................7-22

Exclude Vol or Mask What Isn't Backed Up Report Panel ..................7-22

EXCLUDE-BCS field Submit CATSCRUB panel ..................................5-3

EXCLUDE-BCS keyword CATSCRUB command......................................15-7

EXCLUDE-KEEP-TAPE field Submit CATSCRUB panel ...........................5-4, 5-4

EXCLUDE-KEEP-VOLSER field Submit CATSCRUB panel ..................................5-4

EXCLUDE-MATCH-VOLSER field Submit CATSCRUB panel ..................................5-4

EXCLUDE-MATCH-VOLSER keyword CATSCRUB command....................................15-11

EXCLVOL BLDREST command.......................................13-13 REPORT-NOBACKUP parameters...................9-32

Exec/View Online BKUPEND Summary Report Panel...................7-29 Critical in ASAP with All/Star Backup Record Report


......................................................................7-24 Data Set List Report Panel................................7-10 Data Set List with Outputs Report Panel...........7-12 Full Volume Dump List Report Panel ................7-14 Jobname List Report Panel...............................7-16 Jobnames Not Tracked by a Job Group Report Panel

......................................................................7-19 Overlap by Application Report Panel ................7-31 Overlap by Backup Event Report Panel..............7-5 Overlap by Data Set Report Panel ......................7-3 Overlap by Job Groups Report Panel .................7-7 What Isn't Backed Up Report Panel ..................7-22

EXECUTE keyword CATSCRUB command......................................15-6

expiring backups ................................................... 14-4 extended masking characters ................................. 2-2

F FATAL-CATALOG-ERR field

Submit CATSCRUB panel ..................................5-6 FATAL-CATALOG-ERR keyword

CATSCRUB command......................................15-7 Field Descriptions

All/Star Load Inventory Dataset Panel ..............2-18 All/Star Unload Inventory Panel ........................2-22 Application List Panel........................................4-28 Backup Tracking Filters EXCLUDE Panel...........3-6 Backup Tracking INCLUDE Filters Panel............3-4

BKUPEND Summary Report Panel...................7-29 Critical in ASAP with All/Star Backup Record Report


......................................................................7-24 Data Set List Report Panel................................7-10 Data Set List with Outputs Report Panel ...........7-12 Full Volume Dump List Report Panel ................7-14 Full Volume Dumps Panel...................................4-5 History Panel.......................................................8-5 History Search Setup Panel ................................8-3 HRECOVER Options Panel ..............................6-14 Job Group List Panel.........................................4-22 Jobname List Panel...........................................4-17 Jobname List Report Panel ...............................7-16 Jobnames Not Tracked by a Job Group Report Panel

......................................................................7-19 Load Inventory (All) Panel .................................2-20 Overlap by Application Report Panel.................7-31 Overlap by Backup Event Report Panel ..............7-5 Overlap by Data Set Report Panel ......................7-3 Overlap by Job Groups Report Panel..............7-7Quick Search for Data Set Setup Panel ..............6-7 Search for Data Set Panel...................................6-5 Search for Data Set Setup Panel ........................6-3 Submit CATSCRUB panel...................................5-3 Unload Inventory Data Set (All) Panel...............2-24 What Isn't Backed Up Report Panel ..................7-22

Field Type Command Line....................................................2-2 Header Text Description......................................2-2 Line Command....................................................2-3 Pop-Up Windows.................................................2-3 Primary Command ..............................................2-3 Specific Selectable Fields ...................................2-2 Sub-menus..........................................................2-3 Table Display ......................................................2-3

filters extended ACS masking.......................................1-9 filtering pattern masks .........................................2-2 masks for pattern filtering ....................................1-9

For System Administrator only HRECOVER Options Panel ..............................6-14

Force to NON-SMS HRECOVER Options Panel ..............................6-14

From Date Data Set List Report Panel................................7-10 Full Volume Dump List Report Panel ................7-14 Jobname List Report Panel ...............................7-16

From TimeJobname List Report Panel ...............................7-16

Full Volume Dump List Report All/Star Backup Reports, report 6 ......................7-14

Full Volume Dump List Report Panel Build/Submit JCL...............................................7-14 Build/View JCL ..................................................7-14 Exec/View Online ..............................................7-14 From Date .........................................................7-14 To Date .............................................................7-14 Volume Name ...................................................7-14

Full Volume Dumps overview ..............................................................2-6 Quick Search for Data Set Setup Panel ..............6-7 Search for Data Set Setup Panel ........................6-3

Index vi Mainstar Software Corporation ©2006 SC23-6061-00



Full Volume Dumps Panel C (Field Description)........................................... 4-5 Date.................................................................... 4-6 Field Descriptions ............................................... 4-5 GL – Displays job groups currently tracking the

jobname for this Full Volume Dump................ 4-5 H (Primary Command)........................................ 4-4 N – List data set names backed up .................... 4-5 R – submit restore .............................................. 4-5 RC ...................................................................... 4-5RCB.................................................................... 4-6 REFresh ............................................................. 4-4 S – Select to view backup detail ......................... 4-5 SD (Primary Command) ..................................... 4-4 SE (Primary Command) ..................................... 4-4 SV (Primary Command) ..................................... 4-4 Time ................................................................... 4-6 Total DSNs ......................................................... 4-6 Volume ............................................................... 4-5

Full Volume Dumps Search Setup Panel Auto Expand List ................................................ 4-3 Event Date.......................................................... 4-3 RC (FVD/BRM)................................................... 4-3 Sort list by........................................................... 4-3 Store values to use as default for this userid...... 4-3 Volume or Mask ................................................. 4-3

fully qualified names.........................................2-1, 2-2 functions

catalog record delete with CATSCRUB ............ 15-1 compare catalog records to data sets with

CATSCRUB .................................................. 15-1 FVDLIST report

examples .......................................................... 9-25 REPORT command.......................................... 9-24

FVDLIST sub-commandREPORT command.......................................... 9-24

G GDG base variables............................................. A-17 GDGBASE-NO-ACTIVE-GENS field

Submit CATSCRUB panel.................................. 5-6 GDGBASE-NO-ACTIVE-GENS keyword

CATSCRUB command ..................................... 15-7 GDS-MIGRATED field

Submit CATSCRUB panel.................................. 5-6 GDS-MIGRATED keyword

CATSCRUB command ..................................... 15-8 GDS-MIGRATED-DASD field

Submit CATSCRUB panel.................................. 5-7 GDS-MIGRATED-DASD keyword

CATSCRUB command ..................................... 15-8 GDS-MIGRATED-TAPE field

Submit CATSCRUB panel.................................. 5-7 GDS-MIGRATED-TAPE keyword

CATSCRUB command ..................................... 15-8 GDS-MULTI-VOL-ERR field

Submit CATSCRUB panel.................................. 5-7 GDS-MULTI-VOL-ERR keyword

CATSCRUB command ..................................... 15-9 GDS-NOT-FOUND field

Submit CATSCRUB panel.................................. 5-7 GDS-NOT-FOUND keyword

CATSCRUB command ..................................... 15-9

GDS-TAPE field Submit CATSCRUB panel .................................. 5-8

GDS-TAPE keyword CATSCRUB command ................................... 15-10

Gen Search for Data Set Panel .................................. 6-5

GEN BLDREST command ...................................... 13-13 HRECOVER Options Panel.............................. 6-14 REPORT JOBLIST parameters ........................ 9-27

generic variables .................................................... A-7 GENS

LOADIDS parameters......................................... 9-8 UNLOADIDS parameters ................................. 9-12

GL (Line Command) Full Volume Dumps Panel .................................. 4-5 Jobname List Panel .......................................... 4-17

H H (Primary Command)

Full Volume Dumps Panel .................................. 4-4 Jobname List Panel .......................................... 4-16

Header Text Description Field Type........................................................... 2-2

History Panel BRM (Line Command)........................................ 8-4 C (Field Description)........................................... 8-5 Date.................................................................... 8-5 Field Descriptions ............................................... 8-5 N (Line Command) ............................................. 8-4 Name or Mask .................................................... 8-5 PGM/Type (Field Description) ............................ 8-5 RC ...................................................................... 8-5 RCB.................................................................... 8-5 S (Line Command) ............................................. 8-4 VA (Line Command) ........................................... 8-4 VE (Line Command) ........................................... 8-4

History Search Setup Panel Don't show this panel again................................ 8-3 Event Date.......................................................... 8-3 Name or Mask .................................................... 8-3 Store values to use as default for this UserID..... 8-3

HRECOVER Options Panel ..................................6-14 Data Set ........................................................... 6-14 For System Administrator only.......................... 6-14 Force to NON-SMS .......................................... 6-14 GEN.................................................................. 6-14 Replace data set if already cataloged............... 6-14 Specify Newname............................................. 6-14 ToVolume ......................................................... 6-14 Unit ................................................................... 6-14

HSM Incremental backups ......................................6-1 HSM Incrementals

Quick Search for Data Set Setup Panel ............. 6-7 Search for Data Set Setup Panel........................ 6-3

hyphen in data set name ............................................... 1-10

II (Line Command)

Add Jobname or Mask to Job Group List Panel 4-23 Backup Tracking Filters EXCLUDE Panel .......... 3-6 Backup Tracking INCLUDE Filters Panel ........... 3-3

Mainstar Software Corporation ©2006 vii Index SC23-6061-00



Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel ..................................6-5 View Data Set Name List Panel ..........................4-8

ICF catalogs synchronize with data volumes .........................15-1

IDS...................................See also Inventory Data Set REPORT-NOBACKUP parameters...................9-31

IEFU83 SMF exit turn off...............................................................11-4 turn on...............................................................11-4

INCLBCDS REPORT ASAP2BRM-B parameters ................9-39 REPORT ASAP2BRM-NB parameters .............9-37 REPORT BKUPEND parameters......................9-42

INCLDSN BLDREST command.......................................13-13 REPORT-NOBACKUP parameters...................9-32

INCLLOC BLDREST command.......................................13-14

INCLPHYDUMP BLDREST command.......................................13-14

INCLUCATREPORT command ..........................................9-32

Include BACKVOL Set Up RESTORE Panel...................................4-13

Include BCDS Critical in ASAP with All/Star Backup Record Report


......................................................................7-24 Include DSN or Mask

What Isn't Backed Up Report Panel ..................7-22 Include Generations

All/Star Load Inventory Panel............................2-18 All/Star Unload Inventory Panel ........................2-22

Include HSM Incrementals Overlap by Data Set Report Panel ......................7-3

Include Job All/Star Load Inventory Panel............................2-18 All/Star Unload Inventory Panel ........................2-22

Include Location Set Up RESTORE Panel...................................4-12

Include Physical Dumps Set Up RESTORE Panel...................................4-13

Include UCAT or Mask What Isn't Backed Up Report Panel ..................7-22

Include Vol or Mask What Isn't Backed Up Report Panel ..................7-22

INCLVOL REPORT-NOBACKUP parameters...................9-32

Incomplete Events Load Inventory (All) Panel.................................2-20 Unload Inventory Data Set (All) Panel...............2-24

Increment Jobname Set Up RESTORE Panel...................................4-13

Increment Member NameSet Up RESTORE Panel...................................4-13

Incremental ABARS DADSMFTK operator commands......................11-2

INCRJOBNAMEOUTBuild Restore Command ...................................13-6

INCRMEMBEROUTBuild Restore Command ...................................13-6

index components.................................................A-14

INFILE LOADIDS parameters .........................................9-7

INI file defaults for anomaly detection keywords CATSCRUB command....................................15-19

Input File DSNAll/Star Load Inventory Panel............................2-18 Load Inventory (All) Panel .................................2-20

interactive dialog panels how to use...........................................................2-1

Internet address ......................................................... 4 Inventory Data Set

load (re-load) event data into BRM Inventory Data Set .................................................................2-17

load/reload event data into BRM Inventory Data Set219

remove ABARS Manager entries ......................9-10 remove all entries ..............................................2-23 remove All/Star entries ......................................2-21 unload event data into IDS ................................2-21

ISPF interface view messages..................................................1-11 view product messages.....................................1-11

ISPF panel attribute bytes.....................................1-10 ISPF panels

Submit CATSCRUB Panel ..................................5-2

J JCL

ALB00002 program .............................................2-1 DAD9254M........................................................11-6

JCLOUT Dataset Set Up RESTORE Panel...................................4-12

Job Load Inventory (All) Panel .................................2-20 Unload Inventory Data Set (All) Panel...............2-24

JOB LOADIDS parameters .........................................9-7 REPORT ASAP2BRM-B parameters ................9-39 REPORT DSNLIST-AST parameters ................9-20 REPORT DSNLIST-O parameters ....................9-22 REPORT JOBLIST parameters.........................9-26 REPORT NOJOBGRP parameters ...................9-29 REPORT OVERLAPJOBGRP parameters........9-18 UNLOADIDS parameters ..................................9-11

Job Cardload IDS ............................................................2-15 unload IDS ........................................................2-15

Job Card PanelBLDREST Job Card ..........................................2-15 Load IDS/Unload IDS Job Card ........................2-15

Job Date Jobname List Search Setup Panel ....................4-15

Job Group Job Group List Panel.........................................4-22 Jobname List Report Panel ...............................7-16

Job Group List Panel ADD...................................................................4-21 C (Field Description)..........................................4-22 D – Delete a Job Group........................... 4-21, 4-27 Description Field ...............................................4-22 E – Edit a Selected Job Group ................ 4-21, 4-27 Field Descriptions..............................................4-22 Job Group Field.................................................4-22

Index viii Mainstar Software Corporation ©2006 SC23-6061-00



NOJOBGRP ..................................................... 4-21 R – Perform a Restore of the Job Group .......... 4-21 REFresh ........................................................... 4-21 S – Display the Jobnames by Job Group panel 4-21

Job Group List Search Setup Panel Don't show this panel again.............................. 4-20 Store values to use as default for this userid.... 4-20

Job NameBackup Tracking Filters EXCLUDE Panel .......... 3-7 Backup Tracking INCLUDE Filters Panel ........... 3-4 Data Set List Report Panel ............................... 7-10

Job Step Backup Tracking Filters EXCLUDE Panel .......... 3-7 Backup Tracking INCLUDE Filters Panel ........... 3-4

JOBGROUP BLDREST command ...................................... 13-11

JOBGRP REPORT JOBLIST parameters........................ 9-27

JOBLIST report examples .......................................................... 9-28 REPORT command.......................................... 9-26

JOBLIST sub-command REPORT command.......................................... 9-26

Jobname Jobname List Panel.......................................... 4-17 Jobname List Report Panel .............................. 7-16 Overlap by Data Set Report Panel ..................... 7-3

JOBNAME BLDREST command ...................................... 13-10

Jobname Detail Panel N – List Data Set Names Backed Up ............... 4-19 R – Create Restore JCL for Selected Jobname/Step

...................................................................... 4-19 REFresh ........................................................... 4-19 S – Select to view backup detail ....................... 4-19

Jobname List Not Tracked by ANY Job Group panel S (Line Command) ........................................... 4-25 S-Mask ............................................................. 4-25

Jobname List Not Tracked by THIS Job Group panel S (Line Command) ........................................... 4-24 S-Mask ............................................................. 4-24

Jobname List Panel +/- (Field Description) ....................................... 4-17 +/- (Line Command) ......................................... 4-17 C (Field Description)......................................... 4-17 Date ................................................................. 4-18Field Descriptions............................................. 4-17 GL (Line Command) ......................................... 4-17 H (Primary Command)...................................... 4-16 Jobname........................................................... 4-17 N (Line Command) ........................................... 4-17 R (Line Command) ........................................... 4-17 RC .................................................................... 4-17 RCB ................................................................. 4-17REFresh ........................................................... 4-16 S (Line Command) ........................................... 4-17 SD (Primary Command) ................................... 4-16 SE (Primary Command) ................................... 4-16 SJ (Primary Command) .................................... 4-16 Time ................................................................. 4-18

Jobname List Report All/Star Backup Reports, report 7 ..................... 7-16

Jobname List Report Panel Build/Submit JCL.............................................. 7-16

Build/View JCL ................................................. 7-16 Exec/View Online ............................................. 7-16 From Date......................................................... 7-16 From Time ........................................................ 7-16 Job Group......................................................... 7-16 Jobname........................................................... 7-16 To Date............................................................. 7-17 To Time ............................................................ 7-17 Use Date Type.................................................. 7-16

Jobname List Search Setup Panel Auto Expand List .............................................. 4-15 Don't show this panel again.............................. 4-16 Job Date ........................................................... 4-15 Jobname or Mask ............................................. 4-15 RC (BKP/AST).................................................. 4-15 Sort list by......................................................... 4-15 Store values to use as default for this userid .... 4-15

Jobname or Mask Jobname List Search Setup Panel ................... 4-15

JOBNAMEOUTBuild Restore Command .................................. 13-5

JOBNAMEOUT name/prefixSet Up RESTORE Panel .................................. 4-13

Jobnames Not Tracked by a Job Group Report All/Star Backup Reports, report 8 ..................... 7-19

Jobnames Not Tracked by a Job Group Report Panel Build/Submit JCL .............................................. 7-19 Build/View JCL ................................................. 7-19 Exec/View Online ............................................. 7-19

Jobs overview ............................................................. 2-6

Jump to an Option panel .........................................2-1

K KEEP-DSN keyword

CATSCRUB command ................................... 15-10 KEEP-TAPE field

Submit CATSCRUB panel ........................... 5-5, 5-5 KEEP-TAPE keyword

CATSCRUB command ................................... 15-10 KEEP-VOLSER field

Submit CATSCRUB panel .................................. 5-5 KEEP-VOLSER keyword

CATSCRUB command ................................... 15-11

L L (Line Command)

View Data Set Name List Panel.......................... 4-8 Line Command

Field Type........................................................... 2-3 Line Commands

Add Jobname or Mask to Job Group List Panel 4-23 Application List Panel ....................................... 4-27 Full Volume Dumps Panel .................................. 4-5 History Panel ...................................................... 8-4 Job Group List Panel ........................................ 4-21 Jobname Detail Panel ...................................... 4-19 Jobname List Not Tracked by ANY Job Group panel

...................................................................... 4-25 Jobname List Not Tracked by THIS Job Group panel

...................................................................... 4-24 Jobname List Panel .......................................... 4-17 Quick Search for Data Set Panel........................ 6-9

Mainstar Software Corporation ©2006 ix Index SC23-6061-00


1


Search for Data Set Panel ..................................6-5 View Data Set Name List Panel ..........................4-8

Load (re-load) BRM Inventory Data Set ...................................2-17

Load External Inventory data requests in batch..............................2-17, 2-19

Load IDS Job Card ...........................................................2-15

Load IDS/Unload IDS Job Card Job Card Panel .................................................2-15

Load Inventory (All) Panel ABACKUP Verifies ............................................2-20 ABACKUP/Job Generations..............................2-20 ARECOVER Generations .................................2-20 Build/Submit JCL...............................................2-20 Build/View JCL ..................................................2-20 Event/Logical Aggregate ...................................2-20 Events with Errors .............................................2-20 Events with Warnings........................................2-20 Incomplete Events.............................................2-20 Input File DSN...................................................2-20 Job ....................................................................2-20 Output Inventory DSN .......................................2-20 Replace.............................................................2-20

load modules currently active ..................................................2-11

load/reload BRM Inventory Data Set ...................................2-19

LOADIDS batch processing .................................................9-7 command

as SYSIN to BRMBPROC ....................2-17, 2-19 examples.............................................................9-9 parameters ..........................................................9-7

EXCLJOB ........................................................ 9-7 GENS .............................................................. 9-8 INFILE ............................................................. 9-7 JOB ................................................................. 9-7

Lock Data Set ....................................................... 10-2

M Main Menu

Option 1 – Setup and Configuration .............2-5, 3-1 Option 2 – Backup and Recovery Management2-6, 4

Option 4 – DR Tools............................................2-6 Option 5 – Search for Data Set ....................2-6, 6-1 Option 6 – Reports ..............................................2-6 Option 7 – Monitor...............................................2-6 Option 8 – History ........................................2-6, 8-1

Mainstar extended masking characters .................. 2-2 Management Class

Unload Inventory Data Set (All) Panel...............2-24 masks .......................................................2-2, 2-6, 6-1

for pattern filtering ...............................................1-9 MATCH-VOLSER field

Submit CATSCRUB panel ..................................5-5 MATCH-VOLSER keyword

CATSCRUB command....................................15-11 MEMBEROUT

Build Restore Command ...................................13-6 MEMBEROUT name/prefix

Set Up RESTORE Panel...................................4-13

MENU Sub-menu.............................................2-7, 2-9 Option 1 – Messages ..........................................2-9 Option 2 – BRMINI Values ................................2-10 Option 3 – Exit BRM..........................................2-10

messages view from MESSAGES message text members1-11 view from Quick-Ref ..........................................1-11 view messages..................................................1-11 view using ISPF interface..................................1-11

Messages.............. See Error and Product Messages MESSAGE-TEXT field

Submit CATSCRUB panel...................................5-5 MESSAGE-TEXT keyword

CATSCRUB command....................................15-11 Modify space totals display option ........................2-14 Monitor

event backups or recoveries ...............................2-6 multi-image ...........................................................14-5

N N (Line Command)

Full Volume Dumps Panel...................................4-5 History Panel.......................................................8-4 Jobname List Panel................................. 4-17, 4-19

Name or MaskHistory Panel.......................................................8-5 History Search Setup Panel ................................8-3

New HLQ MEMBEROUT name/prefix ...............................4-12 Set Up RESTORE Panel...................................4-12

NEWHLQ BLDREST command .......................................13-14

No Backup Found RCSet Up RESTORE Panel...................................4-14

No Backup Found Status Set Up RESTORE Panel...................................4-14

NOBACKUP sub-command REPORT command...........................................9-31

NO-BACKUP-FOUND-RC BKUPEND parameters......................................12-5

NOBKUPFOUND BLDREST command .......................................13-14

NOJOBGRP Add Jobname or Mask to Job Group List Panel 4-23 Job Group List Panel.........................................4-21

NOJOBGRP report REPORT command...........................................9-29

NOJOBGRP sub-command REPORT command...........................................9-29

non-VSAM alias variables .................................... A-17 non-VSAM variables ............................................ A-16 NONVSAM-ALIAS-NO-REALNAME field

Submit CATSCRUB panel...................................5-8 NONVSAM-ALIAS-NO-REALNAME keyword

CATSCRUB command....................................15-12 NONVSAM-MIGRATED field

Submit CATSCRUB panel...................................5-8 NONVSAM-MIGRATED keyword

CATSCRUB command....................................15-12 NONVSAM-MIGRATED-DASD field

Submit CATSCRUB panel...................................5-8 NONVSAM-MIGRATED-DASD keyword

CATSCRUB command....................................15-12

Index x Mainstar Software Corporation ©2006 SC23-6061-00



NONVSAM-MIGRATED-TAPE keyword CATSCRUB command ................................... 15-13

NONVSAM-MIGRATED-TAPED field Submit CATSCRUB panel.................................. 5-9

NONVSAM-MULTI-VOL-ERR field Submit CATSCRUB panel.................................. 5-9

NONVSAM-MULTI-VOL-ERR keyword CATSCRUB command ................................... 15-13

NONVSAM-NOT-FOUND field Submit CATSCRUB panel.................................. 5-9

NONVSAM-NOT-FOUND keyword CATSCRUB command ................................... 15-13

NONVSAM-TAPE field Submit CATSCRUB panel................................ 5-10

NONVSAM-TAPE keyword CATSCRUB command ................................... 15-14

NOTBYTHIS Add Jobname or Mask to Job Group List Panel 4-23

O O (Field Description)

Search for Data Set Panel.................................. 6-5 O (Line Command)

Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel.................................. 6-5 View Data Set Name List Panel ......................... 4-8

OBJECT-ACCESS-METHOD field Submit CATSCRUB panel................................ 5-10

OBJECT-ACCESS-METHOD keyword CATSCRUB command ................................... 15-14

obsolete entries remove from DAD Database ............................ 11-6

online dialog panels how to use .......................................................... 2-1

operational considerations back up or reorganize the BRM IDS................. 14-9

Option 1 ADMIN Sub-menu ............................................ 2-29 DAD Monitor Panel........................................... 2-26 DIAGNOSTICS Sub-menu ............................... 2-11 Main Menu................................................... 2-5, 3-1 PREFERENCES Sub-menu .................... 2-13, 2-14

Option 2 DAD Monitor Panel........................................... 2-27 DIAGNOSTICS Sub-menu ............................... 2-11 Main Menu................................................... 2-6, 4-1 MENU Sub-menu ............................................. 2-10

Option 3 DAD Monitor Panel........................................... 2-28 DIAGNOSTICS Sub-menu ............................... 2-12 MENU Sub-menu ............................................. 2-10 PREFERENCES Sub-menu ............................. 2-15 UTILITIES Sub-menu ....................................... 2-17

Option 4 Main Menu.......................................................... 2-6 UTILITIES Sub-menu ....................................... 2-19

Option 5 Main Menu................................................... 2-6, 6-1

Option 6 Main Menu.......................................................... 2-6 UTILITIES Sub-menu ....................................... 2-21

Option 7 Main Menu.......................................................... 2-6

UTILITIES Sub-menu ....................................... 2-23 Option 8

Main Menu................................................... 2-6, 8-1 Option 9

UTILITIES Sub-menu ....................................... 2-26 OUTFILE

UNLOADIDS parameters ................................. 9-12 Output File DSN

All/Star Unload Inventory Panel........................ 2-22 Unload Inventory Data Set (All) Panel .............. 2-25

Output Inventory DSN All/Star Load Inventory Panel ........................... 2-18 Load Inventory (All) Panel ................................ 2-20

Overlap by Application All/Star Backup Reports, report 13 ................... 7-31

Overlap by Application ReportAppl Name(s).................................................... 7-31

Overlap by Application Report Panel Build/Submit JCL .............................................. 7-31 Build/View JCL ................................................. 7-31 Exec/View Online ............................................. 7-31

Overlap by Backup Event Report All/Star Backup Reports, report 2 ....................... 7-5

Overlap by Backup Event Report Panel Build/Submit JCL ................................................ 7-5 Build/View JCL ................................................... 7-5 Event Name(s) or Mask(s).................................. 7-5 Exec/View Online ............................................... 7-5

Overlap by Data Set Report Panel Build/Submit JCL ................................................ 7-3 Build/View JCL ................................................... 7-3 Exec/View Online ............................................... 7-3 Include HSM Incrementals ................................. 7-3 Jobname............................................................. 7-3

Overlap by Dataset Report All/Star Backup Reports, report 1 ....................... 7-3

Overlap by Job Groups ReportAll/Star Backup Reports, report 3 ....................... 7-7

Overlap by Job Groups Report PanelBuild/Submit JCL.............................................. 7-7Build/View JCL ................................................... 7-7 Exec/View Online ............................................... 7-7

OVERLAPA-AST report REPORT command.......................................... 9-43

OVERLAPA-AST sub-command REPORT command.......................................... 9-43

OVERLAPD-AST report typeREPORT command.......................................... 9-15

OVERLAPD-AST sub-command REPORT command.......................................... 9-15

OVERLAPE-AST sub-command REPORT command.......................................... 9-17

OVERLAPJOBGRP report REPORT command.......................................... 9-18

OVERLAPJOBGRP sub-command REPORT command.......................................... 9-18

Overlaps OnlySearch for Data Set Setup Panel........................ 6-3

overviewAll/Star ................................................................ 1-2

P panel attribute bytes ..............................................1-10

Mainstar Software Corporation ©2006 xi Index SC23-6061-00



parameters ASAP2BRM-NB ................................................9-36 DSNLIST-AST...................................................9-19 DSNLIST-O.......................................................9-22 FVDLIST ...........................................................9-23 JOBLIST ...........................................................9-26 NOBACKUP ......................................................9-30 NOJOBGRP ......................................................9-29 OVERLAPD-AST ..............................................9-15 OVERLAPE-AST...............................................9-17 OVERLAPJOBGRP ..........................................9-18 REPORT ASAP2BRM-B ..........................9-38, 9-39 REPORT ASAP2BRM-NB ................................9-37 REPORT BKUPEND.........................................9-41 REPORT DSNLIST-AST...................................9-20 REPORT DSNLIST-O .......................................9-22 REPORT FVDLIST ...........................................9-24 REPORT JOBLIST............................................9-26 REPORT NOJOBGRP ......................................9-29 REPORT OVERLAPA-AST...............................9-43 REPORT OVERLAPA-AST...............................9-43 REPORT OVERLAPD-AST ..............................9-15 REPORT OVERLAPE-AST...............................9-17 REPORT OVERLAPJOBGRP...........................9-18

PARMLIB BRMINI member ...............................................2-10

path variables .......................................................A-15 perform backups and recoveries............................. 4-1

Backup Tracking Filters EXCLUDE Panel...........3-6 Backup Tracking INCLUDE Filters Panel ............3-4

Q Quick Restore

Select Restore Option Panel .............................4-10 Quick Search for Data Set Panel

Backup Name......................................................6-9 C (Field Description)............................................6-9 Data Set Name or Mask ......................................6-9 Date.....................................................................6-9 Display Display Full Vol Dumps ..........................6-9 Display HSM Incr.................................................6-9 I (Line Command) ...............................................6-9 Line Commands ..................................................6-9 O (Line Command)..............................................6-9 Primary Commands.............................................6-9 R (Line Command) ..............................................6-9 REFresh ..............................................................6-9 RESet..................................................................6-9 S (Line Command) ..............................................6-9 Time ....................................................................6-9

Quick Search for Data Set Setup Panel Don't show this panel again.................................6-7 DSN or Mask.......................................................6-7 Field Descriptions................................................6-7 Full Volume Dumps .............................................6-7 HSM Incrementals...............................................6-7

PGM/Type (Field Description) Store values to use as default for this userid.......6-7 History Panel.......................................................8-5 Quick-Ref

phone numbers.......................................................... 3 view BRM messages.........................................1-11 Places right of decimal

Data Set Space Display Options Panel.............2-14 RPop-Up Windows

Field Type ...........................................................2-3 R (Line Command)

PREFERENCES Sub-menu ..........................2-7, 2-13 Add Jobname or Mask to Job Group List Panel 4-23

Option 1 – Space Display Options ...........2-13, 2-14 Application List Panel ........................................4-27

Option 3 – Job Card ..........................................2-15 Backup Tracking Filters EXCLUDE Panel...........3-6

Primary Command Backup Tracking INCLUDE Filters Panel ............3-3

Field Type ...........................................................2-3 Full Volume Dumps Panel...................................4-5

Primary Commands Job Group List Panel.........................................4-21

Add Jobname or Mask to Job Group List Panel 4-23 Jobname Detail Panel .......................................4-19

Application List Panel........................................4-27 Jobname List Panel...........................................4-17

Backup Tracking Filters EXCLUDE Panel...........3-5 Quick Search for Data Set Panel ........................6-9

Backup Tracking Filters INCLUDE Panel............3-3 Search for Data Set Panel......................... 6-5, 6-13

Full Volume Dumps Panel...................................4-4 View Data Set Name List Panel ..........................4-8

Job Group List Panel.........................................4-21 R mask Search for Data Set Panel...................................6-5 Jobname Detail Panel .......................................4-19

Jobname List Not Tracked by ANY Job Group panel RCFull Volume Dumps Panel ................................4-5......................................................................4-25

Jobname List Not Tracked by THIS Job Group panel History Panel.......................................................8-5 Jobname List Panel...........................................4-17 ......................................................................4-24

Jobname List Panel...........................................4-16 Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel ..................................6-5 View Data Set Name List Panel ..........................4-8

Proc Step

RC (BKP/AST)Jobname List Search Setup Panel ....................4-15

RC (FVD/BRM) Full Volume Dumps Search Setup Panel ............4-3

RCB

Backup Tracking Filters EXCLUDE Panel...........3-7 Full Volume Dumps Panel...................................4-6

Backup Tracking INCLUDE Filters Panel............3-4 History Panel.......................................................8-5 Jobname List Panel.........................................4-17processing notes recoveriesCATSCRUB command....................................15-17

Product version detail DIAGNOSTICS Sub-menu ................................2-11

Program

monitor ........................................................ 2-6, 4-1 perform........................................................ 2-6, 4-1 submit.......................................................... 2-6, 4-1

Index xii Mainstar Software Corporation ©2006 SC23-6061-00



REFresh Full Volume Dumps Panel .................................. 4-4 Job Group List Panel ............................... 4-21, 4-27 Jobname Detail Panel ...................................... 4-19 Jobname List Panel.......................................... 4-16 Quick Search for Data Set Panel........................ 6-9 Search for Data Set Panel.................................. 6-5

refresh batch intercept file .......................................9-5 REFRESH-AST.......................................................9-5 remove

ABARS Manager entries from BRM IDS .......... 9-10 all entries from BRM IDS .................................. 2-23 All/Star entries from BRM IDS .......................... 2-21

reorganizing the BRM IDS ....................................14-9 Replace

All/Star Load Inventory Panel ........................... 2-18 Load Inventory (All) Panel ................................ 2-20

REPLACE BLDREST command ...................................... 13-14 LOADIDS parameters......................................... 9-8

Replace data set if already cataloged HRECOVER Options Panel.............................. 6-14

REPLACE Existing DSNs Set Up RESTORE Panel .................................. 4-14

REPORT ASAP2BRM-B about ................................................................ 9-38 batch processing .............................................. 9-39 examples .......................................................... 9-40 parameters .............................................. 9-38, 9-39

DS..................................................................9-39 INCLBCDS ....................................................9-39 JOB................................................................9-39

syntax ............................................................... 9-38 REPORT ASAP2BRM-NB

about ................................................................ 9-36 batch processing .............................................. 9-37 examples .......................................................... 9-38 parameters .............................................. 9-36, 9-37

APPL .............................................................9-37 DS..................................................................9-37 INCLBCDS ....................................................9-37

syntax ............................................................... 9-36 REPORT BKUPEND

about ................................................................ 9-41 batch processing .............................................. 9-41 examples .......................................................... 9-42 parameters ....................................................... 9-41

APPL .............................................................9-41 CYCLE...........................................................9-41 INCLBCDS ....................................................9-42

syntax ............................................................... 9-41 REPORT command

about ................................................................ 9-13 ASAP2BRM-B report type ....................... 9-38, 9-39 ASAP2BRM-NB report type..................... 9-36, 9-37 BKUPEND report type ...................................... 9-41 DSNLIST-AST .................................................. 9-19 DSNLIST-AST report type ................................ 9-20 DSNLIST-O ...................................................... 9-22 DSNLIST-O report type .................................... 9-22 FVDLIST........................................................... 9-23 FVDLIST report type ........................................ 9-24 JOBLIST report type......................................... 9-26 NOBACKUP ..................................................... 9-30

NOBACKUP report type ................................... 9-31 NOJOBGRP ..................................................... 9-29 NOJOBGRP report type ................................... 9-29 OVERLAPA-AST ..................................... 9-43, 9-44 OVERLAPA-AST report type ............................ 9-43 OVERLAPD-AST..................................... 9-15, 9-16 OVERLAPD-AST report type............................ 9-15 OVERLAPE-AST .............................................. 9-17 OVERLAPE-AST report type ............................ 9-17 OVERLAPJOBGRP report type........................ 9-18

REPORT DSNLIST-AST about ................................................................ 9-19 batch processing .............................................. 9-20 parameters .............................................. 9-19, 9-20

DATE .............................................................9-20 DS..................................................................9-20 JOB................................................................9-20 TYPE .............................................................9-21

syntax ............................................................... 9-19 REPORT DSNLIST-O

batch processing .............................................. 9-22 parameters ....................................................... 9-22

JOB................................................................9-22 REPORT FVDLIST

about ................................................................ 9-23 batch processing .............................................. 9-24 parameters .............................................. 9-23, 9-24

DATE .............................................................9-24 VOL................................................................9-24

syntax ............................................................... 9-23 REPORT JOBLIST

about ................................................................ 9-26 batch processing .............................................. 9-26 parameters ....................................................... 9-26

DATE .............................................................9-27 DATETYPE....................................................9-27 GEN ...............................................................9-27 JOB................................................................9-26 JOBGRP ........................................................9-27 TIME ..............................................................9-27

syntax ............................................................... 9-26 REPORT NOBACKUP

about ................................................................ 9-30 parameters ....................................................... 9-30

BCDS.............................................................9-31 EXCLDSN......................................................9-32 EXCLVOL ......................................................9-32 IDS.................................................................9-31 INCLDSN .......................................................9-32 INCLVOL .......................................................9-32 SORTBYNAME..............................................9-31 SORTBYVOL.................................................9-31 SOURCE .......................................................9-31 TARGET ........................................................9-31

syntax ............................................................... 9-30 REPORT NOJOBGRP

about ................................................................ 9-29 batch processing .............................................. 9-29 examples .......................................................... 9-29 parameters ....................................................... 9-29

JOB................................................................9-29 syntax ............................................................... 9-29

REPORT OVERLAPA-ASTabout ................................................................ 9-43

Mainstar Software Corporation ©2006 xiii Index SC23-6061-00



batch processing ...............................................9-43 examples...........................................................9-44 parameters ........................................................9-43

APPL ............................................................. 9-43 syntax................................................................9-43

REPORT OVERLAPD-ASTabout .................................................................9-15 batch processing ...............................................9-15 examples...........................................................9-16 parameters ........................................................9-15

DS ................................................................. 9-15 syntax................................................................9-15

REPORT OVERLAPE-ASTabout .................................................................9-17 batch processing ...............................................9-17 parameters ........................................................9-17

EV ................................................................. 9-17 REPORT command ..........................................9-17 syntax................................................................9-17

REPORT OVERLAPJOBGRPabout .................................................................9-18 batch processing ...............................................9-18 examples...........................................................9-18 parameters ........................................................9-18

JOB ............................................................... 9-18 syntax................................................................9-18

report type ASAP2BRM-B ...................................................9-39 ASAP2BRM-NB ................................................9-37 BKUPEND.........................................................12-5 BKUPEND.........................................................9-41 DSNLIST-AST...................................................9-20 DSNLIST-O.......................................................9-22 FVDLIST ...........................................................9-24 JOBLIST ...........................................................9-26 NOBACKUP ......................................................9-31 NOJOBGRP ......................................................9-29 OVERLAPA-AST...............................................9-43 OVERLAPD-AST ..............................................9-15 OVERLAPE-AST...............................................9-17 OVERLAPJOBGRP ..........................................9-18

REPORT-NOBACKUP parameters

EXCLUCAT ................................................... 9-32 INCLUCAT .................................................... 9-32

Reports All/Star Reports ...................................................7-1

Res (Primary Command) View Data Set Name List Panel ..........................4-8

RESet Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel ..................................6-5

restore by application............................................ 12-1

S S (Line Command)

Full Volume Dumps Panel...................................4-5 History Panel.......................................................8-4 Job Group List Panel.........................................4-21 Jobname Detail Panel .......................................4-19 Jobname List Not Tracked by ANY Job Group panel

......................................................................4-25

Jobname List Not Tracked by THIS Job Group panel......................................................................4-24

Jobname List Panel...........................................4-17 Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel...................................6-5

SD (Primary Command) Full Volume Dumps Panel...................................4-4 Jobname List Panel...........................................4-16

SE (Primary Command) Full Volume Dumps Panel...................................4-4 Jobname List Panel...........................................4-16

search criteria default .................................................................4-2

Search for Data Set ................................................2-6 Search for Data Set Panel

+/- (Field Description) ..........................................6-5 Backup Name......................................................6-5 C (Field Description)............................................6-5 Data Set Name or Mask ......................................6-5 Date.....................................................................6-5 Display Display Full Vol Dumps ..........................6-5 Display HSM Incr.................................................6-5 Display overlaps only ..........................................6-5 Field Descriptions................................................6-5 Gen .....................................................................6-5 I (Line Command) ...............................................6-5 Line Commands ..................................................6-5 O (Field Description) ...........................................6-5 O (Line Command)..............................................6-5 Primary Commands.............................................6-5 R (Line Command) .................................... 6-5, 6-13 R mask ................................................................6-5 REFresh ..............................................................6-5 RESet..................................................................6-5 S (Line Command) ..............................................6-5 Sort by.................................................................6-5 Time ....................................................................6-5 X mask ................................................................6-5

Search for Data Set Setup Panel Auto Expand List .................................................6-3 Don't show this panel again.................................6-3 DSN or Mask.......................................................6-3 Field Descriptions................................................6-3 Full Volume Dumps .............................................6-3 HSM Incrementals...............................................6-3 Overlaps Only .....................................................6-3 Sort by.................................................................6-3 Store values to use as default for this userid.......6-3

Select Restore Option Panel Quick Restore ...................................................4-10 Set Up Restore..................................................4-10

Selected List Submit CATSCRUB panel...................................5-3

selection panelshow to use...........................................................2-1

Set Up Restore Select Restore Option Panel .............................4-10

Set Up RESTORE Panel Alloc JCLOUT Old or New.................................4-12 BADBKUPRC....................................................4-12 Build/View JCL ..................................................4-12 Copy..................................................................4-12 Exclude Location...............................................4-12 Include BACKVOL.............................................4-13

Index xiv Mainstar Software Corporation ©2006 SC23-6061-00



Include Location ............................................... 4-12 Increment Jobname.......................................... 4-13 Increment Member Name................................. 4-13 JCLOUT Dataset .............................................. 4-12 JOBNAMEOUT name/prefix............................. 4-13 MEMBEROUT name/prefix .............................. 4-13 No Backup Found RC ...................................... 4-14 No Backup Found Status.................................. 4-14 REPLACE Existing DSNs................................. 4-14 Skeleton Library ............................................... 4-12 Steplimit per Job............................................... 4-13

Setup and Configuration ..................................2-5, 2-6 SIMULATE field

Submit CATSCRUB panel.................................. 5-3 SIMULATE keyword

CATSCRUB command ..................................... 15-6 simulation processing

CATSCRUB command ................................... 15-17 single image ..........................................................14-5 SJ (Primary Command)

Jobname List Panel.......................................... 4-16 SKEL

BLDREST command ...................................... 13-15 Skeleton Library

Set Up RESTORE Panel .................................. 4-12 skeleton processing ............................................... A-1 S-Mask

Jobname List Not Tracked by ANY Job Group panel...................................................................... 4-25

Jobname List Not Tracked by THIS Job Group panel...................................................................... 4-24

Sort bySearch for Data Set Panel.................................. 6-5 Search for Data Set Setup Panel ....................... 6-3

Sort ByWhat Isn't Backed Up Report Panel ................. 7-22

Sort list byFull Volume Dumps Search Setup Panel ........... 4-3 Jobname List Search Setup Panel ................... 4-15

SORTBYNAME sub-command REPORT command.......................................... 9-31

SORTBYVOL sub-commandREPORT command.......................................... 9-31

source file variables ............................................. A-10 SOURCE sub-command

REPORT command.......................................... 9-31 space totals

modify display option ........................................ 2-13 space options ................................................... 2-13

Space Unit Data Set Space Display Options Panel ............ 2-14

Specific Selectable Fields Field Type........................................................... 2-2

Specify Newname HRECOVER Options Panel.............................. 6-14

started task All/Star Tracking ............................................... 14-1 DADSMFTK...................................................... 11-1

Steplimit per Job Set Up RESTORE Panel .................................. 4-13

STEPLIMITOUTBuild Restore Command .................................. 13-7

STEPNAME BLDREST command ...................................... 13-15

STEPNO BLDREST command ...................................... 13-15

Store values to use as default for this userid...........4-2 Application List Search Setup Panel................. 4-26 Full Volume Dumps Search Setup Panel ........... 4-3 Job Group List Search Setup Panel ................. 4-20 Jobname List Search Setup Panel ................... 4-15 Quick Search for Data Set Setup Panel ............. 6-7 Search for Data Set Setup Panel........................ 6-3

Store values to use as default for this Userid History Search Setup Panel ............................... 8-3

Sub-menus Field Type........................................................... 2-3

submit AUTODUMP ....................................................... 9-3

using batch processing ....................................9-3 backups or recoveries ................................. 2-6, 4-1 LOADIDS............................................................ 9-6 REPORT .......................................................... 9-14

using batch processing ..................................9-14 REPORT ASAP2BRM-B .................................. 9-39 REPORT ASAP2BRM-NB ................................ 9-37 REPORT BKUPEND ........................................ 9-41 REPORT DSNLIST-AST .................................. 9-20 REPORT DSNLIST-O ...................................... 9-22 REPORT FVDLIST........................................... 9-24 REPORT JOBLIST ........................................... 9-26 REPORT NOJOBGRP ..................................... 9-29 REPORT OVERLAPA-AST .............................. 9-43 REPORT OVERLAPD-AST .............................. 9-15 REPORT OVERLAPE-AST .............................. 9-17 REPORT OVERLAPJOBGRP .......................... 9-18 UNLOADIDS..................................................... 9-10

Submit CATSCRUB panel Build JCL/Edit for Submit.................................... 5-3 EXCLUDE-BCS .................................................. 5-3 EXCLUDE-KEEP-TAPE field....................... 5-4, 5-4 EXCLUDE-KEEP-VOLSER ................................ 5-4 EXCLUDE-MATCH-VOLSER ............................. 5-4 FATAL-CATALOG-ERR ..................................... 5-6 GDGBASE-NO-ACTIVE-GENS.......................... 5-6 GDS-MIGRATED................................................ 5-6 GDS-MIGRATED-DASD .................................... 5-7 GDS-MIGRATED-TAPE ..................................... 5-7 GDS-MULTI-VOL-ERR....................................... 5-7 GDS-NOT-FOUND ............................................. 5-7 GDS-TAPE ......................................................... 5-8 KEEP-TAPE ................................................ 5-5, 5-5 KEEP-VOLSER field........................................... 5-5 MATCH-VOLSER field ....................................... 5-5 MESSAGE-TEXT ............................................... 5-5 NONVSAM-ALIAS-NO-REALNAME................... 5-8 NONVSAM-MIGRATED ..................................... 5-8 NONVSAM-MIGRATED-DASD .......................... 5-8 NONVSAM-MIGRATED-TAPE........................... 5-9 NONVSAM-MULTI-VOL-ERR ............................ 5-9 NONVSAM-NOT-FOUND................................... 5-9 NONVSAM-TAPE............................................. 5-10 OBJECT-ACCESS-METHOD........................... 5-10 Selected List ....................................................... 5-3 SIMULATE.......................................................... 5-3 VSAM-SPHERE-MIGRATED ........................... 5-10 VSAM-SPHERE-MIGRATED-DASD ................ 5-10 VSAM-SPHERE-MIGRATED-TPE ................... 5-10

Mainstar Software Corporation ©2006 xv Index SC23-6061-00



VSAM-SPHERE-MULTI-VOL-ERR ...................5-11 VSAM-SPHERE-NOT-FOUND .........................5-11

SV (Primary Command) Full Volume Dumps Panel...................................4-4

syntaxASAP2BRM-B report type.................................9-38 ASAP2BRM-NB report type ..............................9-36 BKUPEND report type.......................................9-41 BLDREST .........................................................13-8 CATSCRUB command......................................15-4 DSNLIST-AST...................................................9-19 DSNLIST-O.......................................................9-22 FVDLIST ...........................................................9-23 JOBLIST report type .........................................9-26 NOBACKUP report type....................................9-30 NOJOBGRP report type....................................9-29 OVERLAPA-AST report type ............................9-43 OVERLAPD-AST report type ............................9-15 OVERLAPE-AST report type ............................9-17 OVERLAPJOBGRP report type ........................9-18

T Table Display

Field Type ...........................................................2-3 table/list Panels

how to use...........................................................2-1 TARGET

REPORT-NOBACKUP parameters...................9-31 Target BCDS

What Isn't Backed Up Report Panel ..................7-22 Target IDS

What Isn't Backed Up Report Panel ..................7-22 Test Backup Tracking Filters

overview..............................................................2-5 Test Backup Tracking Filters Panel ........................ 3-8 Time

Full Volume Dumps Panel...................................4-6 Jobname List Panel...........................................4-18 Quick Search for Data Set Panel ........................6-9 Search for Data Set Panel ..................................6-5

TIME REPORT JOBLIST parameters.........................9-27

To Date Data Set List Report Panel................................7-10 Full Volume Dump List Report Panel ................7-14 Jobname List Report Panel...............................7-17

To TimeJobname List Report Panel...............................7-17

Total DSNs Full Volume Dumps Panel...................................4-6

ToVolumeHRECOVER Options Panel ..............................6-14

track backup data with AST .................................. 14-5 TYPE

REPORT DSNLIST-AST parameters................9-21 Type(s)

Data Set List Report Panel................................7-10

U U.S.A. EBCDIC code set ...................................... 1-10 Unit

HRECOVER Options Panel ..............................6-14 Unload

BRM Inventory Data Set....................................2-21 Unload External Inventory

data requests in batch .......................................2-21 Unload IDS

Job Card............................................................2-15 Unload Inventory Data Set (All) Panel

ABACKUP Verifies ............................................2-24 ABACKUP/Job Generations..............................2-24 ARECOVER Generations..................................2-24 Build/Submit JCL...............................................2-24 Build/View JCL ..................................................2-24 Event/Logical Aggregate ...................................2-24 Events with Errors .............................................2-24 Events with Warnings........................................2-24 Incomplete Events.............................................2-24 Job ....................................................................2-24 Management Class ...........................................2-24 Output File DSN ................................................2-25

UNLOADIDS batch processing ...............................................9-11 command

as SYSIN to BRMBPROC .............................2-21 examples...........................................................9-13 parameters ........................................................9-11

EXCLJOB ......................................................9-11 GENS ............................................................9-12 JOB ...............................................................9-11 OUTFILE .......................................................9-12

Use Date TypeJobname List Report Panel ...............................7-16

USEGEN0ALL BLDREST command .......................................13-15

USEGEN0NOBKUP BLDREST command .......................................13-15

UserID Backup Tracking Filters EXCLUDE Panel...........3-7 Backup Tracking Filters INCLUDE Panel ............3-4

UTILITIES Sub-menu.....................................2-7, 2-17 Option 3 – Load Inventory (All/Star) ..................2-17 Option 4 – Load Inventory (All)..........................2-19 Option 6 – Unload Inventory..............................2-21 Option 7 – Unload Inventory (All) ......................2-23 Option 9 – DAD Monitor ....................................2-26

Utility Backup Tracking Filters EXCLUDE Panel...........3-7 Backup Tracking Filters INCLUDE Panel ............3-4

V

VA (Line Command) History Panel.......................................................8-4

variables cluster............................................................... A-11 GDG base ........................................................ A-17 generic ............................................................... A-7 non-VSAM........................................................ A-16 non-VSAM alias ............................................... A-17 path .................................................................. A-15 source file......................................................... A-10

VE (Line Command) History Panel.......................................................8-4

viewBRM error and product messages ......................2-9 BRMINI values ..................................................2-10

Index xvi Mainstar Software Corporation ©2006 SC23-6061-00



current memory usage...................................... 2-12 currently active load modules ........................... 2-11 Incremental ABARS messages .......................... 2-9 infrastructure messages ..................................... 2-9 product version detail ....................................... 2-11 space totals display options.............................. 2-13

View Data Set Name List PanelI – inquiry............................................................ 4-8 L – locate data set .............................................. 4-8 O – show overlaps.............................................. 4-8 R – restore.......................................................... 4-8 Res ..................................................................... 4-8

VOL BLDREST command ...................................... 13-11 REPORT FVDLIST parameters........................ 9-24

VolumeFull Volume Dumps Panel .................................. 4-5

Volume NameFull Volume Dump List Report Panel ............... 7-14

Volume or MaskFull Volume Dumps Search Setup Panel ........... 4-3

VSAM-SPHERE-MIGRATED field Submit CATSCRUB panel................................ 5-10

VSAMSPHERE-MIGRATED keyword CATSCRUB command ................................... 15-14

VSAM-SPHERE-MIGRATED-DASD field Submit CATSCRUB panel................................ 5-10

VSAMSPHERE-MIGRATED-DASD keyword CATSCRUB command ................................... 15-15

VSAM-SPHERE-MIGRATED-TAPE field Submit CATSCRUB panel................................ 5-10

VSAMSPHERE-MIGRATED-TAPE keyword CATSCRUB command ................................... 15-15

VSAM-SPHERE-MULTI-VOL-ERR field

Submit CATSCRUB panel ................................ 5-11 VSAMSPHERE-MULTI-VOL-ERR keyword

CATSCRUB command ................................... 15-15 VSAM-SPHERE-NOT-FOUND field

Submit CATSCRUB panel ................................ 5-11 VSAMSPHERE-NOT-FOUND keyword

CATSCRUB command ................................... 15-16

W web site address ........................................................4 What Isn't Backed Up Report

All/Star Backup Reports, report 9 ..................... 7-21 What Isn't Backed Up Report Panel

Build/Submit JCL .............................................. 7-22 Build/View JCL ................................................. 7-22 Exclude DSN or Mask ...................................... 7-22 Exclude UCAT or Mask .................................... 7-22 Exclude Vol or Mask......................................... 7-22 Exec/View Online ............................................. 7-22 Include DSN or Mask........................................ 7-22 Include UCAT or Mask ..................................... 7-22 Sort By.............................................................. 7-22 Target BCDS .................................................... 7-22 Target IDS ........................................................ 7-22

wildcardsfor pattern filtering............................................... 1-9 name combinations ............................................ 2-1

windowsdialog status information..................................... 2-3

X

X mask Search for Data Set Panel .................................. 6-5

Mainstar Software Corporation ©2006 xvii Index SC23-6061-00


Technical Support Mainstar Technical Support

Product Information [email protected]

Visit Our Web Site www.mainstar.com

Worldwide Headquarters and North and South America Sales Mainstar Software Corporation P.O. Box 4132 Bellevue, WA 98009 U.S.A. Tel: 1-425-455-3589 or 1-800-233-6838 Fax: 1-425-455-1992

European Sales Mainstar Software Corporation Ltd. Sanderum House Oakley Road Chinnor Oxon OX39 4TW England Tel: +44-(0)1844-347173 Fax: +44-(0)1844-346627

Asia Pacific Sales Mainstar International Ltd. P.O. Box 1624 Macquarie Centre North Ryde, NSW 2113 Australia Tel: +61-(0)2-9888-1777 Fax: +61-(0)2-9888-1588

http://www.mainstar.com/services/support/techsupport/index.asp



mainstar : backup & recovery manager suite - ibm - united states

Documents