Mainstar : Backup & Recovery Manager Suite

Transcription

1 Mainstar : Backup & Recovery Manager Suite Installation & Maintenance Guide ABARS Manager All/Star ASAP Product Version 6, Release 01 November 2006 Mainstar Software Corporation P O Box 4132 Bellevue, WA USA Tel Fax Web: Technical Support: Mainstar Technical Support Copyright 2006 Mainstar Software Corporation, Inc. All Rights Reserved. Mainstar Software Corporation is a wholly owned subsidiary of Rocket Software, Inc.

2

3 Installation & Maintenance Guide Fifteenth Edition (November 2006) This edition of the Mainstar: Installation & Maintenance Guide supports Version 6 Release 01 of the Mainstar: selectable products ABARS Manager, All/Star, and ASAP. Restricted Materials Notice Trademarks 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 the Mainstar: Backup & Recovery Manager Suite selectable products ABARS Manager, All/Star, or ASAP from Mainstar Software Corporation. 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 Aggregate LoadBalancer Catalog RecoveryPlus Incremental ABARS All/Star ASAP CATSCRUB 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. IBM DFSMSdss DFSMShsm RACF z/os 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 ASG-Zeke BMC CONTROL-M for z/os Brightstor CA-FAVER Cybermation ESP FDR Unicenter CA-Jobtrac Job Management Unicenter CA-7 Job Management Software AG Allen Systems Group BMC Software, Inc. Computer Associates International, Inc. Cybermation Inc. Innovation Data Processing Computer Associates International, Inc. Computer Associates International, Inc. Copyright by Mainstar Software Corporation All Rights Reserved November 2006 Fifteenth Edition Mainstar Software Corporation 2006 i Contents

4 Installation & Maintenance Guide Contents ii Mainstar Software Corporation 2006

5 Installation & Maintenance Guide Summary of Changes November 2006 Fifteenth Edition Documentation Updates This version of the Mainstar: Installation & Maintenance Guide supports Version 6 Release 01 of the Mainstar:. Updates throughout for: SMP/E install and adding ASAP (17505) removal of Auditing (BRM-39) Update Chapter 1, BRM Suite: Product Installation & Maintenance Overview to: update SI014DC1 Validate Load Module to BRM01MOD and update examples (21482) Update Chapter 4, Configure ABARS Manager, All/Star, and ASAP to: add note to Task 5: Create the ASAP Database, Task 7: Create the DAD Database, and Task 8: Create the BRM IDS, regarding SMS Management Class to prevent autobackup (24668 & 24717) update Task 6: Code BRMINI PARMLIB member variables, from boilerplate update Task 4: Run JCLBUILD from MFA boilerplate update Task 8: Create the BRM IDS, to have upgrades skip that task update Task 10: Create Batch SMF Data Sets, to have upgrades skip that task (BRM-36) Update Chapter 5, ABARS Manager Post-Installation Tasks to: update reference to SI067DC0 to BRM01IKB (21437) move Task 10: Create Prevent BackLevel Data Set to the User's Guide, and remove JCL example create optional task 14 from previous note text Update Chapter 6, All/Star: Post-Installation Tasks to: add task to edit ADABAS_LOADLIB token (22849) add task to Define SAF Class Profiles for AST (23911) Add Chapter 7, ASAP: Post-Installation Tasks, and: update SI067DC0 reference to BRM01IKB (21437) Update Chapter 8, All/Star: Set Up All/Star Tracking (AST) Started Task to: correct step 5 to include the S ASTSMFTK,JOBNAME command and add reference to DAD messages to track in step 6 (21875) add DFSMShsm BACKVOL to the list of backup utilities (22701) change all IEFUJI references to IEFUSI (24384) add new task 8, SAF Class Profiles for Controlling AST (23911) add Warning note regarding deletion of the BIF file add Warning note for upgrades to skip ASTSETUP (BRM-36) Update Chapter 9, BRM Suite: Set Up DADSMFTK Started Task (DAD) to: reference AST message to track (21875) add note to Step 1: Create Data Set Activity Database (DAD) regarding SMS Management class to prevent autobackup (24668 & 24717) Update Chapter 10, ASAP: Install Real-time Selection Process to: Mainstar Software Corporation 2006 iii Contents

6 Installation & Maintenance Guide add Warning note for upgrades to skip RSPSETUP (BRM-36) Update Chapter 12, Apply Maintenance, to: add steps to stop and restart started tasks (BRM-58) Update Appendix A, BRM Suite: Authority Requirements, to: add text for flatfiles (22908) add SAF Class Profiles for AST topic (23911) Update Appendix B, BRM Suite: BRMINI Configuration Values, to: add CATLG_DATA_FOR_LOG_BKUPS token to :ALL/STAR_DUMP_BACKUP_PROCESS_OPTIONS section (21748) add TLMS_DATABASE to :PRODUCT_DATASETS section (22168) add following tokens to :CATSCRUB_OPTIONS section (22218): NONVSAM_NOT_FOUND_DISP NONVSAM_NOT_FOUND_RC NONVSAM_NOT_FOUND_PROC VSAMSPHERE_NOT_FOUND_DISP VSAMSPHERE_NOT_FOUND_RC VSAMSPHERE_NOT_FOUND_PROC add EXPIRATION_WARNING_DAYS token to :PRODUCT_SECURITY section (21482) add :INIMERGE_VALUES section (21482, 24159) add ASAP reference to :PRODUCT_SECURITY section (22105) add FAVER_LOADLIB to :PRODUCT_DATASETS section (16642) add SKELLIB_DEFAULT_FAVER to :ALL/STAR_RESTORE_OPTIONS section (16642) add SKELLIB_DEFAULT_SYNCGENR to :ALL/STAR_RESTORE_OPTIONS section (23002) add SKELLIB_DEFAULT_CFCAMS_REP and SKELLIB_DEFAULT_CFCAMS_EXP to :ALL/STAR_RESTORE_OPTIONS section (23101) update :PRODUCT_SECURITY section to include ASAP (22105) add new section :PROCESS_OPTIONS_ISPF (23071) add ALT_MAIN_MENU token to :PROCESS_OPTIONS_ISPF section (23312) add new HRECOVER tokens to :PROCESS_OPTIONS_ISPF section (22953) add AST_USE_LNKLIST token to :INSTALLATION_DATASETS section (23783) add INCLUDE_BACKVOLS and SKELLIB_DEFAULT_BACKVOL tokens to :ALL_STAR_RESTORE_OPTIONS section (22701) add NEW_HLQ token to :ALL_STAR_RESTORE_OPTIONS section (22961) add SKELLIB_DEFAULT_ADAFULL and SKELLIB_DEFAULT_ADADELTA to :ALL_STAR_RESTORE_OPTIONS section (22849) add ADABAS_LOADLIB to :PRODUCT_DATASETS section (22849) add ASAP tokens and rearrange BRMINI sections (22100) update description of MIGRATION_FACILITY (22858) remove SI050_VALUES (24518) add MSGLIB token to :INSTALLATION_DATASETS section (23835) Contents iv Mainstar Software Corporation 2006

7 Installation & Maintenance Guide add REXXSAMP token to :PRODUCT_DATASETS section (22108) update :CATSCRUB_OPTIONS section for 6.41 (23977) remove REXXSAMP token from :PRODUCT_DATASETS section (25044) change DAD token to DAD_DATASET in :PRODUCT_DATASETS section (24991) changed defaults for JCLOUT, INVENTORY_DATASET, CR+_PARMLIB, TLMS_DATABASE, ASAPDB, and AUDITDB (22108) added a warning to the BKLEVEL keyword to prevent specification prior to disaster recovery Add new Appendix C, SMP/E Configuration Notes Update Appendix D, BRM Suite: Sizing Backup & Recovery Manager Suite Data Sets, to: add text regarding compression of BRM IDS (19970) Add Appendix E, Sizing the ASAP Database Update TOC and Index. Document June 2005 Fourteenth Edition Documentation Updates This version of the Mainstar: Installation & Maintenance Guide supports Version 4 Release 03 of the Mainstar:. Changes throughout to: remove LINKLIST requirement (20198) Update Chapter 1, Product Installation & Maintenance Overview to: add note regarding JCLBUILD (22600) Update Chapter 4, Configure to: add new MIM_GDIF token to Task 4: Code BRMINI PARMLIB variables (20251) Update Chapter 5, ABARS Manager: Post-Installation Tasks to: add task to set RLS token values (19949) add task to set new MIM_GDIF token (20251) Update Chapter 6, All/Star Post-Installation Tasks to: add task to set new MIM_GDIF token (20251) Update Chapter 8, Set Up Incremental ABARS to: clarify Step 6, Start the Incremental ABARS Task (DADSMFTK)(19022) change DADSMFTK to also apply to All/Star add note regarding ABEND 201 (20627) add Step 4 to update BRMBPROC to reflect the DAD database (20474) Update Appendix B, BRMINI Configuration Values to: clarify how the :SI040_VALUES token should be coded (19949) move :SI040_VALUES and :SI050_VALUES sections to end of BRMINI (20297) remove LICENSE token from :DADSMFTK_OPTIONS section (21068) add new token MIM_GDIF in new :RESOURCE_SERIALIZATION section (20251) add new CR+ tokens CR+LOADLIB and CR+PARMLIB to Mainstar Software Corporation 2006 v Contents

8 Installation & Maintenance Guide PRODUCT_DATASETS section, 3 new CR+ SKELLIB tokens to :ALL/STAR_RESTORE_OPTIONS section (19232) add new ASAP_DATABASE token to the :PRODUCT_DATASETS section (17950) add new MIGRATION_FACILITY token to :PROCESS_OPTIONS section (20653) add new INCLUDE_PHYSICAL_DUMPS token to :ALL/STAR_RESTORE_OPTIONS section (20687) add new CATLG_DATA_FOR_PHY_DUMPS token to :ALL/STAR_DUMP_BACKUP_PROCESS section (20686) add new CHANGED_DATASET_TRACKING token to :ALL/STAR_DUMP_BACKUP_PROCESS section (19455) change CCTRIGGER default to N (21257) Update TOC and Index. Document December 2004 Thirteenth Edition Documentation Updates This version of the Mainstar: Installation & Maintenance Guide supports Version 4 Release 1 of the Mainstar:. Updates throughout to: remove LINKLIST requirement (20198) Update Chapter 3, Configure, to: add text for multiple license codes to section (18689) Update Chapter 4, ABARS Manager Post-Installation Tasks to: update task 4 to include access authority for jobs and users. add new Chapter 5 to separate ABARS Manager and All/Star postinstall tasks add new task to define SAF class profiles for CATSCRUB to end of both post-install chapters (19503) Update Chapter 6, Set Up All/Star Tracking (AST) Started Task, to: add new step 1 for adding the LOAD library to the LINKLIST (19125) Update Chapter 7, Set Up Incremental ABARS to: update topic Start the Incremental ABARS Task (DADSMFTK) (19022) Update Appendix A, Authority Requirements, to move the table of primary and line commands from Chapter 4. (19503) Update Appendix B, BRMINI Configuration Values, to: add new :CATSCRUB_OPTIONS section (19125) add 2 new tokens to :ALL/STAR_DUMP_BACKUP_PROCESS_OPTIONS section (19267) add new token 'NO_DS_INCLUDED_IN_SDS_RC = 20' to :BACKUP_OPTIONS section (18054) Update TOC and Index. Contents vi Mainstar Software Corporation 2006

9 Installation & Maintenance Guide Document July 2004 Twelfth Edition Documentation Updates This version of the Mainstar: Installation & Maintenance Guide supports Version 4 Release 1 of the Mainstar:. Update Chapter 1, Product Installation & Maintenance Overview, to: add overview information about new selectable product, All/Star add overview information about cumulative maintenance files remove overview information about service pack files correct PROC names in section 1.9 (17235) add Validate Load Module SI014DC1 Update Chapter 3, Configure, to: add configuration tasks for All/Star add task 14 to track critical DAD messages (16085) add reminders indicating the need for APF authorization and BRMINI updates prior to execution of &BRM.JCL(DEFINVDB). (16189) Update Chapter 4, Post Installation Tasks, to add post-install tasks for All/Star New Chapter 5, Set Up All/Star Tracking started task. New Chapter 6, Set Up Incremental ABARS. Update Chapter 8, Apply Maintenance, to: add procedure for applying cumulative maintenance files remove procedure for applying service pack files Update Appendix A, Authority Requirements to: change Inventory Data Set data set name LLQ from INVDB to IDS (16189) Update Appendix B, BRMINI Configuration Values, to: add INI tokens for All/Star add notes per case (16189) add new INI keyword RECORD_EMPTY_INCR_EVENT to section :BACKUP_OPTIONS (15530) add new INI keyword AGGENQ to section :RECOVERY_OPTIONS (16600) add new INI keyword FDR_LOADLIB to the :PRODUCT_DATASETS section. Update TOC and Index. Eleventh Edition, Document , August 2003 supports product Version 3 Release 2 Tenth Edition, Document , March 2003 supports product Version 3 Release 2 Ninth Edition, Document , November 2002 supports product Version 3 Release 1, Service Pack A Eighth Edition, Document , September 2002 supports product Version 3 Release 1, Service Pack A Seventh Edition, Document , February 2002 supports product Version 3 Release 1 Sixth Edition, Document , July 2001 supports product Version 2 Release 1, Service Pack C Fifth Edition, Document , May 2001 supports product Version 2 Release 1, Service Pack B Fourth Edition, Document , April 2001 supports product Version 2 Release 1, Service Pack A Third Edition, Document , January 2001 supports product Version 2 Release 1 Second Edition, Document , April 2000 supports product Version 1 Release 1 First Edition, Document , March 2000 supports product Version 1 Release 1 Mainstar Software Corporation 2006 vii Contents

10 Installation & Maintenance Guide Contents viii Mainstar Software Corporation 2006

11 Installation & Maintenance Guide Contents Preface.1 Preface.2 About This Book... 1 Where to Find More Information BRM Suite: Product Installation & Maintenance Overview Overview of Install and Selectable Products Software Requirements Product and Maintenance Distributions Base Transfer and Install JCL Files Cumulative Maintenance Transfer and Install JCL Files Fixlist Product Distribution Transmittal (PDT) INFO Data Set Methods of Software Distribution Distributions via File Transmission or CD Distributions via Download from Mainstar CASE System Distributions on Tape Validating Load Module Contents Run MODLEVEL Product Data Sets Product Initialization Member PARMLIB(BRMINI) Replacement of IBM Standard DFHSMABR Procedure (ABARS Manager Only) ABARS Selection Data Set (ABARS Manager Only) Use of the ARCSKEXT and ARCCREXT ABARS Exits (ABARS Manager Only) Use of the Optional ARCBEEXT Exit (ABARS Manager Only) APF Authorization Requirements About Dataspaces View Product Messages Message Identifier Naming Convention Determine Which MESSAGES Member Contains the Message Description View Messages Using ISPF Interface View Messages in MESSAGES Library View Messages Using Quick-Ref Determine Possible Impacts of Running BRM with Your EBCDIC Code Tables Mainstar's Extended ACS Masking Characters in Filtering Pattern Masks Planning the SMP/E Environment DASD Environment Considerations APF Authorization Requirements Tape Management System Considerations Sample Name Representations Contents of Tape MSP SMP/E Maintenance Included Miscellaneous Notes BRM Suite: Install ABARS Manager, All/Star, and ASAP Steps to Install ABARS Manager, All/Star, and ASAP Step 1: Back Up Existing Product Data Sets Step 2A: Copy Files from Tape Step 2B: Unzip Files on PC and Upload to Mainframe Step 3: Edit the Install JCL Step 4: Submit the Install JCL Mainstar Software Corporation 2006 ix Contents

12 Installation & Maintenance Guide 3.7 Step 5: Edit and Submit SMP/E INSTALL Library Members Edit the Procedure Used to Invoke SMP/E (MSCSMPE member) Define the SMP/E Global Zone Environment (BRMS01G member) Define BRM Product CSI, Target Zone, and DLIB Zone Environments (BRMS02 member) SMP/E RECEIVE Processing (BRMS03D member) SMP/E APPLY Processing (BRMS04 member) SMP/E ACCEPT Processing (BRMS05 member) Optional Back Up the SMP/E Environment (BRMS06/BRMS06A members) Step 6: Tailor BRM Suite for Your Installation Step 7: Copy Installed Files to New Production Libraries Step 8: Delete Temporary Data Sets Step 9: Was Maintenance Included with the Release? BRM Suite: Configure ABARS Manager, All/Star, and ASAP Configuration Tasks for ABARS Manager, All/Star, and ASAP Task 1: APF Authorize the Product LOAD Library Task 2: Run INIMERGE Task 3: Code BRMINI PARMLIB Member Variables Define Space Management Method in :ASAP Section (ASAP Only) Modify Library Names in :INSTALLATION_DATASETS Section Set RLS Token Values in :SI040_VALUES Section Set CA-MIM/MII Token Values in :RESOURCE_SERIALIZATION Section Task 4: Run JCLBUILD Task 5: Create the ASAP Database (ASAP Only) Database Space/Size Considerations Database Sharing Considerations Edit PARMLIB Member ASAPDB Edit JCL Member ASAPDEFN Task 6: Create DAD Database (Optional) (ABARS Manager and All/Star) Task 7: Create BRM Suite Inventory Data Set (ABARS Manager and All/Star) How to Expand the BRM Suite Inventory Data Set Compression of the BRM Suite Inventory Data Set Task 8: Ensure Adequate TSO Address Space Region Size Task 9: Verify Product Install/Configuration Task 10: Create Batch SMF Data Sets (Optional) (ASAP Only) Task 11: Specification and Display of EBCDIC Characters Task 12: Complete the Post-Installation Tasks ABARS Manager: Post-Installation Tasks Task 1: Update Cross-System ENQ Lists Task 2: Verify Configuration Values Were Set in BRMINI Task 3: Provide Access Authority Task 4: Update BRMBPROC Member in Product JCL Library Task 5: Add BRMWABAR to the TMOEDMxx File Task 6: Replace IBM Standard DFHSMABR Procedure Task 7: Modify DFSMShsm PARMLIB Member (ARCCMDxx) Set ABARSACTLOGMSGLVL Parameter Activate Required ABARS Exits in DFSMShsm PARMLIB Activate Optional ARCBEEXT Exit in DFSMShsm PARMLIB Task 8: Update ACF$CMDS System Security Command Table (for ACF2 Users) Task 9: Set Up ABARS Monitor Task 10: Optional Set Up SDSL VOL Option in SYS1.PARMLIB Task 11: Optional Load Demo Aggregates Task 12: Optional Add Security for Primary and Line Commands Contents x Mainstar Software Corporation 2006

13 Installation & Maintenance Guide 5.13 Task 13: Optional Define Security Class Profiles (CATSCRUB only) Task 14: Optional Remove All/Star Entries from the BRM IDS Task 15: Continue to Relevant Chapter All/Star: Post-Installation Tasks Task 1: Update Cross-System ENQ Lists Task 2: Verify Configuration Values Were Set in BRMINI Task 3: Provide Access Authority Task 4: Update BRMBPROC and BRMRPROC Members in JCL Library Task 5: Optional Edit FDR_LOADLIB Token in BRMINI Task 6: Optional Edit ADABAS_LOADLIB Token in BRMINI Task 7: Define Security Class Profiles for CATSCRUB Task 8: Define Security Class Profiles for All/Star Tracking (AST) Started Task Task 9: Set Up All/Star Tracking Started Task ASAP: Post-Installation Tasks Task 1: Update Cross-System ENQ Lists Task 2: Specify SMF/JCL Data Collection Method SMF Collection via RSP JCL Collection via RSP Task 3: Verify ASAP Configuration Values Were Set in BRMINI Task 4: Update System Security Table (for ACF2 Users) Task 5: Provide Access Authority Task 6: Define Security Profiles (Optional) Authority Requirements Security Class Profiles for Controlling ASAP Functions Task 7: Set Up Foreground Verification Task 8: Selection Data Sets Must Be Physical Sequential (PS) Task 9: Panel Usage Task 10: Set Up RSP All/Star: Set Up All/Star Tracking (AST) Started Task All/Star Tracking (AST) Started Task Overview What Does the AST Started Task Do? Backup Utilities Tracked by All/Star ASTSMFTK Installation on Multiple Systems Installation Notes Setup Steps for the AST Started Task Step 1: Edit PARMLIB Member BRMINI Step 2: Allocate and Initialize the AST Started Task Data Sets Step 3: Edit ASTSMFTK Started Task and Add to Procedure Library Step 4: Enable Required IEFUSI Exit Step 5: Start the All/Star Tracking Started Task and Individual Subtasks Step 6: Track AST Messages Step 7: Continue to Relevant Chapter BRM Suite: Set Up DADSMFTK Started Task (DAD) DAD Started Task Overview DADSMFTK Installation on Multiple Systems Setup Steps for the DAD Started Task Step 1: Create Data Set Activity Database (DAD) Step 2: Create the LOG File(s) Step 3: Create the MSGQUEUE File Step 4: Modify the BRMBPROC JCL Member Step 5: Edit BRMINI PARMLIB Member Step 6: Modify the DADSMFTK JCL Member Mainstar Software Corporation 2006 xi Contents

14 Installation & Maintenance Guide 9.10 Step 7: Start the DADSMFTK (DAD) Started Task Step 8: Track Critical DAD Messages ASAP: Install Real-time Selection Process (RSP) RSP Installation on Multiple Systems RSP Installation Steps Step 1: Allocate/Initialize RSP Data Sets Step 2: Enable Required Exits and Specify SMF Record Collection Step 3: Edit ASAP BRMINI PARMLIB Member Step 4: Modify JCL for the RSPSMFTK (RSP) Started Task Step 5: Build JOBFLAT File with Job Names to Track (RSPBLDJB) Step 6: Start the ASAP Started Task (RSP) and Subtasks Step 7: Track Critical RSP Messages RSP Performance & Usage Notes Reducing Data to Be Processed by RSP Avoiding Trouble with the RSP Cycles BRM Suite: Apply Maintenance The Cumulative Maintenance (CM) Data Set Procedure to Install Cumulative Maintenance Step 1: Back Up Product Data Sets Step 2: Unzip Transmitted Files and Upload from PC to Mainframe Step 3: Edit the Install JCL Step 4: Submit the Install JCL Step 5: Perform SMP/E Maintenance Step 6: Stop the DAD Started Task Step 7: Stop the RSP Started Task Step 8: Copy/Replace Maintenance to Existing Production Libraries Step 9: Delete the XFRBINR or SMPBINR Data Set Step 10: Refresh LINKLIST Look Aside (if used) Step 11: Run INIMERGE Step 12: Run JCLBUILD Step 13: Restart the DAD Started Task Step 14: Restart the RSP Started Task Step 15: Test the Maintenance Step 16: Stop and Start or Refresh the AST Started Task Encountering/Avoiding Problems When Applying Maintenance Maintenance/PTF BackLevel Problems Custom Programs User Written Programs Implementation Variances A B BRM Suite: Authority Requirements...A-1 A.1 Required Authority by Data Set/Function ABARS Manager...A-2 A.2 Required Authority by Job/User ABARS Manager...A-3 A.3 Required Authority by Data Set/Function Incremental ABARS...A-4 A.4 Required Authority by Job/User Incremental ABARS...A-5 A.5 Required Authority by Data Set/Function All/Star...A-6 A.6 Required Authority by Job/User All/Star...A-7 A.7 Required Authority by Data Set/Function ASAP...A-7 A.8 Required Authority by Job/User ASAP...A-8 A.8 Primary Commands ABARS Manager... A-10 A.9 SAF Class Profiles for All/Star Tracking (AST) Started Task... A-12 A.10 SAF Class Profiles for Controlling CATSCRUB Command Execution... A-12 BRM Suite: BRMINI Configuration Values... B-1 Contents xii Mainstar Software Corporation 2006

15 Installation & Maintenance Guide B.1 Coding the Keyword Values...B-1 B.2 Modifying Data Set Name High Order Nodes...B-2 B.3 ABARS Manager BRMINI Sections...B-2 B.4 Incremental ABARS BRMINI Sections...B-3 B.5 All/Star BRMINI Sections...B-3 B.6 ASAP BRMINI Sections...B-3 B.7 Index of BRMINI Keywords...B-4 B.8 BRMINI PARMLIB Member Keywords/Descriptions...B-9 :INIMERGE_VALUES ABARS Manager, All/Star, and ASAP...B-9 :PRODUCT_INFO ABARS Manager, All/Star, and ASAP...B-9 :PRODUCT_SECURITY ABARS Manager, All/Star, and ASAP...B-10 :INSTALLATION_DATASETS ABARS Manager, All/Star, and ASAP...B-10 :PRODUCT_DATASETS ABARS Manager, All/Star, and ASAP...B-12 :RESOURCE_SERIALIZATION ABARS Manager, All/Star, and ASAP...B-13 :HSM ABARS Manager and All/Star...B-14 :PROCESS_OPTIONS_ISPF ABARS Manager and All/Star...B-14 :PROCESS_OPTIONS ABARS Manager, All/Star, and ASAP...B-17 :BACKUP_OPTIONS ABARS Manager Only...B-19 :ABARS_RC_OVERRIDES ABARS Manager Only...B-29 :RECOVERY_OPTIONS ABARS Manager Only...B-30 :LOAD_ACTIVITY_LOG ABARS Manager Only...B-36 :DADSMFTK_OPTIONS Incremental ABARS and All/Star...B-37 :SI027_VALUES ABARS Manager, All/Star, and ASAP...B-40 :ASTSMFTK All/Star Only...B-40 :ALL/STAR_DUMP_BACKUP_PROCESS_OPTIONS All/Star Only...B-41 :ALL/STAR_RESTORE_OPTIONS All/Star Only...B-42 :ASAP Automatic Selection & Auditing Process ASAP Only...B-44 :ASAPRSP ASAP Real-time Selection Process Section ASAP Only...B-61 :ASAPOPC_PARMS Section ASAP Only...B-64 :CATSCRUB_OPTIONS ABARS Manager and All/Star...B-65 :SI040_VALUES ABARS Manager, All/Star, and ASAP...B-76 :SIS_PROC_PARMS Section ABARS Manager, All/Star, and ASAP...B-80 :JCL_DEFAULTS Section ASAP Only...B-80 C SMP/E Configuration Notes...C-1 C.1 DDDEF Summary...C-1 C.1.1 Target Library DDDEFs...C-1 C.1.2 Distribution Library DDDEFs...C-2 C.1.3 MVS System Library DDDEFs...C-2 C.1.4 SMP/E LOG DDDEFs...C-2 C.1.5 SMP/E Library DDDEFs...C-2 C.2 Global Zone Settings...C-3 C.2.1 Global Zone Data Sets...C-3 C.2.2 GLOBALZONE Entry...C-3 C.2.3 Global Zone OPTIONS Entry...C-3 C.2.4 Global Zone UTILITY Entries...C-3 C.2.5 Global Zone DDDEF Entries...C-3 C.3 Product CSI Cluster...C-4 C.4 Target Zone Settings...C-4 C.4.1 Target Zone Data Sets...C-4 C.4.2 TARGETZONE Entry...C-4 C.4.3 Target Zone DDDEF Entries...C-4 C.5 DLIB Zone Settings...C-5 C.5.1 DLIB Zone Data Sets...C-5 Mainstar Software Corporation 2006 xiii Contents

16 Installation & Maintenance Guide C.5.2 DLIBZONE Entry... C-5 C.5.3 DLIB Zone DDDEF Entries... C-5 D BRM Suite: Sizing Data Sets... D-1 D.1 Sizing Suggestions for BRM Suite Product Libraries... D-1 D.1.1 Estimating Size of BRM Suite Inventory Data Set... D-2 D.1.2 Compression of the BRM Suite Inventory Data Set... D-2 D.1.3 Allocating Work Data Sets...D-3 D.1.4 Back Up, Reorganize, or Resize the BRM Suite IDS... D-3 D.2 Sizing the ASAP Database... D-4 D.2.1 Estimating the Size of Your ASAP Database... D-5 D.2.2 Preventing the ASAP Database from 'Running Out of Space'... D-10 D.2.3 Procedure to Resize the ASAP Database... D-12 Contents xiv Mainstar Software Corporation 2006

17 Installation & Maintenance Guide Figures Figure 1-1: Mainstar's Extended ACS Masking Characters Figure 2-1: INSTALL JCL variables Figure 2-2: Files shipped on BRM tape MSP Figure 3-1: Sample JCL to copy files from distribution tape Figure 3-2: INSTJCL file containing RECEIVE commands for PDS and each member Figure 3-3: SMP/E INSTALL library members to edit and submit Figure 3-4: For SMP/E install BRMS07D JCL to delete temporary data sets Figure 4-1: Main Menu Figure 7-1: Available security class profiles Figure 8-1: Sample PARMLIB Member SMFPRMXX Figure 10-1: Sample PARMLIB Member SMFPRMXX Figure 11-1: INSTJCL file containing RECEIVE commands for PDS and each member Figure 11-2: Legend for zone designations used in SMP/E configuration tables...c-1 Tables Table 3-1: Installation Steps for ABARS Manager, All/Star, and ASAP Table 4-1: Configuration Tasks for ABARS Manager, All/Star, and ASAP Table 5-1: Post-Installation Steps for ABARS Manager Table 6-1: Post-Installation Steps for All/Star Table 7-1: Post-Installation Steps for ASAP Table 8-1: Setup Steps for the AST Started Task Table 9-1: Setup Steps for the DAD Started Task Table 10-1: Installation Steps for Real-time Selection Process (RSP) Table 11-1: Installation Steps for Cumulative Maintenance Mainstar Software Corporation 2006 xv Contents

18 Installation & Maintenance Guide Contents xvi Mainstar Software Corporation 2006

19 Installation & Maintenance Guide Preface Preface.1 About This Book Who Should Use This Book? The primary audience for this Installation and Maintenance Guide is the software installer. This document may also be of interest to Storage Administrators and System Programmers with responsibilities for performing, managing, and monitoring application backup functions, within DFHSM and/or DFSMShsm environments. What Does This Book Contain? This guide provides the necessary information and instructions to successfully install, configure, and maintain the. Please call Mainstar Technical Support at for help with any installation problems. This book contains: An overview of product distribution, product files, configuration activities and authorization requirements you will use to install and apply maintenance for the Backup & Recovery Manager Suite. Planning the SMP/E environment: requirements and considerations for setting up an SMP/E install environment. Installing the : ABARS Manager, All/Star, and ASAP how to install the of products. Configuring the : ABARS Manager, All/Star, and ASAP how to configure the for your site. How to verify successful completion of install and configuration of the Backup & Recovery Manager Suite: ABARS Manager, All/Star, and ASAP. Post-Installation Tasks several additional tasks required to prepare your system to use the functions of the : ABARS Manager, All/Star, and ASAP. Setting up All/Star Tracking started task (All/Star licensed users only) Setting up ABARS Manager Incremental ABARS (ABARS Manager licensed users only) Setting Up DADSMFTK Started Task (DAD), for ABARS Manager and All/Star. Installing Real-time Selection Process (RSP) (ASAP only) Applying Maintenance how to apply maintenance to the Backup & Recovery Manager Suite: ABARS Manager, All/Star, and ASAP. Appendix A provides data set Access Authority Requirements for using the Backup & Recovery Manager Suite. Appendix B contains descriptions and coding information for the configuration keywords in the BRMINI member of the PARMLIB. Appendix C contains notes on configuring SMP/E. Appendix D contains information on sizing data sets for Backup & Recovery Manager Suite. Mainstar Software Corporation Preface

20 Installation & Maintenance Guide Reader s Comments Acronyms 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 to: techsupport@mainstar.com Let us know if you would like a reply, and provide your contact information. ALB AST BIF BRM DAD IDS INC LLA PDT ABARS Aggregate LoadBalancer a feature of ABARS Manager All/Star Tracking started task Batch Intercept File used by All/Star Tracking started task Data Set Activity Database Inventory Data Set (IDS) the database Incremental ABARS selectable feature of ABARS Manager Linklist Look Aside Product Distribution Transmittal Preface 2 Mainstar Software Corporation 2006

21 Installation & Maintenance Guide Preface.2 Where to Find More Information Publications in the Document Set Installation & Maintenance Guide (document GI ) User Guide for ABARS Manager (document SC ) User Guide for All/Star (document SC ) User Guide for ASAP (document SC ) How to Contact Us for Technical Support: Mainstar Technical Support Phone: Fax: How to Contact Us for Product Information: Send an to In North and South America Mainstar Software Corporation Worldwide Headquarters P.O. Box 4132 Bellevue, WA U.S.A. Tel: or Fax: In Europe Mainstar Software Corporation Ltd. Sanderum House Oakley Road Chinnor Oxon OX39 4TW England Tel: +44-(0) Fax: +44-(0) In Asia Pacific Mainstar International Ltd. P.O. Box 1624 Macquarie Centre North Ryde, NSW 2113 Australia Tel: +61-(0) Fax: +61-(0) Visit Our Web Site Current release information Download cumulative maintenance (requires Mainstar authorization) Product information Interesting and informative White Papers and articles Online presentations Sign up for an online seminar Mainstar Software Corporation Preface

22 Installation & Maintenance Guide Preface 4 Mainstar Software Corporation 2006

23 Installation & Maintenance Guide Chapter 1 1 BRM Suite: Product Installation & Maintenance Overview 1.1 Overview of Install and Selectable Products consists of one install for three selectable products: ABARS Manager, All/Star, and ASAP. The authorization to use a selectable product is determined by the LICENSES code. The common install consists of a common set of libraries. ABARS Manager and All/Star share the same Inventory Data Set, and ASAP has its own ASAP Database. 1.2 Software Requirements The operation of products in the : ABARS Manager, All/Star, or ASAP is dependent on the following software levels: z/os 1.4 or higher TSO/E 3.0 DFSMS 1.5 or higher ISPF 5 or higher JES2 or JES3 at any supported level 1.3 Product and Maintenance Distributions Software will be provided as a product distribution formatted for both SMP/E install and binary (non- SMP/E) install, and as cumulative maintenance. The underlined terms below are described in following topics. A product distribution is available in both SMP/E format and binary format, and consists of: a base transfer file associated install JCL file a Product Distribution Transmittal (PDT) containing names of distributed files and any special release notes A cumulative maintenance distribution will be supplied for both SMP/E format and binary format, and consists of: a cumulative maintenance (CM) transfer file containing PTFs associated install JCL file INFO data set sent with the cumulative maintenance Base Transfer and Install JCL Files A base transfer file contains a new version or release of the product. Base installs are available in SMP/E and binary formats. The base install JCL file contains control statements generated by Mainstar to match the contents of the transfer file it is to be run against. Always use the install JCL file sent with the release. The base transfer file is a single file, which when 'received' using the associated install JCL, results in a PDS. The install JCL then 'receives' each member of the PDS and creates all of the required product data sets. The procedure for installing base transfer files is documented in Chapter 3, BRM Suite: Install ABARS Manager, All/Star, and ASAP. Mainstar Software Corporation Chapter 1 BRM Suite: Product Installation & Maintenance Overview

24 Installation & Maintenance Guide Base product releases may be distributed as a: Transmitted file (zipped file) CD (zipped file) Download from the Mainstar CASE system (zipped file) - Requires authorization Tape 3490 format tape cartridge (3480 format is available upon request contact Mainstar Technical Support). The base transfer file is file 2 when sent on a distribution tape, and the base install JCL file is tape file 1. Base Product File Names Distributed via Download, , or CD Binary base product file names when shipped via download, , or CD are: BRMvvrr.XFRBIN for binary base product transfer files BRMvvrr.INSTJCL for binary base product install JCL files SMP/E base product file names when shipped via download, or CD are: BRMvvrr.SMPBIN for SMP/E base product transfer files BRMvvrr.ISMPJCL for SMP/E base product install JCL files Where: vv is the product version level. rr is the product release level. The actual data set names can be found on the Product Distribution Transmittal sent with the distribution. Base Product File Names Distributed on Tape Binary base product file names when shipped on tape are: BRMBvvrr.XFRBINXX for binary base product transfer files BRMBvvrr.INSTJCLX for binary base product install JCL files SMP/E base product file names when shipped on tape are: BRMBvvrr.SMPBINXX for SMP/E base product transfer files BRMBvvrr.ISMPJCLX for SMP/E base product install JCL files Where: B is a static value meaning that this is a base product file and is used as a filler to make the tape file name 17 characters. vv is the product version level. rr is the product release level. X and XX are fillers to make the tape file names 17 characters. The actual data set names can be found on the Product Distribution Transmittal sent with the distribution Cumulative Maintenance Transfer and Install JCL Files Cumulative maintenance contains PTFs (Program Temporary Fixes) accumulated since the base release. When available, cumulative maintenance will be sent with base product distributions to ensure that the most current maintenance is included. Cumulative maintenance (CM) installs are available in both SMP/E and binary formats. The CM install JCL file contains control statements generated by Mainstar to match the contents of the CM transfer file it is to be run against. The CM transfer file is a single file, which when 'received' using the associated install JCL, results in a PDS. The install JCL then 'receives' each member of the PDS and creates all of the required product files. Chapter Mainstar Software Corporation 2006 BRM Suite: Product Installation & Maintenance Overview

25 Installation & Maintenance Guide All libraries in a CM transfer file (except the INFO text data set, which is information only) must be installed, and all members within each library must be installed. This eliminates co-requisite or prerequisite PTF problems. However, if you have installed previous maintenance that contained the same changes, you may skip copying those member(s) again. Locate the INFO data set in the maintenance file. This INFO data set lists changes to members that may have been customized, by PTF and date. Note: If you have modified a JCL member that is being replaced by maintenance, you will need to retrofit your changes into the new JCL member. The procedure for installing cumulative maintenance transfer files is documented in Chapter 4, BRM Suite: Configure ABARS Manager, All/Star, and ASAP. Cumulative maintenance may be distributed as: A zipped transmitted file A download from the Mainstar web site (requires authorization) Cumulative Maintenance (CM) File Names Binary cumulative maintenance (CM) transfer file names are: BRMvvrr.CIyymmdd.XFRBIN for the binary CM transfer file BRMvvrr.CIyymmdd.INSTJCL for the binary CM install JCL file SMP/E cumulative maintenance (CM) file names are: BRMvvrr.CIyymmdd.SMPBIN for the SMP/E CM transfer file BRMvvrr.CIyymmdd.ISMPJCL for the SMP/E CM install JCL file Where: vv is the product version to which this cumulative maintenance applies. rr is the product release to which this cumulative maintenance applies. C is a constant meaning 'cumulative maintenance'. I is the 1-character Mainstar product ID for Backup and Recovery Manager Suite. yymmdd is the year, month, and date Fixlist Cumulative maintenance must only be applied to the matching version/release level. For example: If the cumulative maintenance transfer file name is BRM0601.CI XFRBIN, it can only be applied to version 06, release 01. The actual data set names can be found on the Product Distribution Transmittal sent with the distribution. A Fixlist is a text file of fixes (cases) sent with a product distribution Product Distribution Transmittal (PDT) Please Read the Product Distribution Transmittal sent with product releases. It contains the actual data set names of the software files and any special instructions about the installation and use of the release INFO Data Set Please Read the INFO Data Set sent with the maintenance file. It lists changes to members that may have been customized, by PTF and date, and other information about the maintenance. If you have installed a previous cumulative maintenance file containing the changed member(s), you may skip copying the member(s) again. Mainstar Software Corporation Chapter 1 BRM Suite: Product Installation & Maintenance Overview

26 Installation & Maintenance Guide 1.4 Methods of Software Distribution Software may be distributed: As a transmitted file with associated install JCL file (base product and any cumulative maintenance). As a download from the Mainstar CASE system with associated install JCL file (base product and any cumulative maintenance) requires you to obtain a CASE login, which includes a user id and password, from Mainstar Customer Support. On a CD with associated install JCL file (base product and any cumulative maintenance). On tape with associated install JCL file 3490 format tape cartridge (3480 format is available upon request contact Mainstar Technical Support) Distributions via File Transmission or CD Distributions of base products and cumulative maintenance may be sent as zipped files via file transmission or on a CD. The transfer file and install JCL file must be unzipped and uploaded to the mainframe as binary before the install JCL file can be modified and run against the transfer file to create the product installation files. The procedure for installing a base transfer file received via file transmission or on CD, for both binary and SMP/E installs, is documented in Chapter 3, BRM Suite: Install ABARS Manager, All/Star, and ASAP. The procedure for applying cumulative maintenance received via file transmission is documented in Chapter 11, BRM Suite: Apply Maintenance Distributions via Download from Mainstar CASE System Distributions of the base product, and the most current cumulative maintenance (if any), is available via download as zipped files. This method requires you to obtain a CASE login, which includes a user id and password, from Mainstar Customer Support Distributions on Tape Base product files can be sent on tape. The tape cartridge for is standard label, VOL=SER=MSP012. The product transfer file and associated install JCL file is copied from the distribution tape using IEBGENER. The install JCL file is modified and executed to 'receive' the transfer file imbedded product files to their final destination. The files on the product distribution tape have DCB characteristics of LRECL=80, RECFM=FB, DSORG=PS, BLKSIZE=3120. The output data set on DASD must have the same attributes. The IEBGENER default is to use the DCB characteristics of the input data set for output, so this is not usually a problem. Sample file copy JCL is provided with the procedures. The procedure for installing a base transfer file received via tape, for both binary and SMP/E installs, is documented in Chapter 3, BRM Suite: Install ABARS Manager, All/Star, and ASAP. Chapter Mainstar Software Corporation 2006 BRM Suite: Product Installation & Maintenance Overview

27 Installation & Maintenance Guide 1.5 Validating Load Module Contents Run MODLEVEL Mainstar Technical Support may request that you submit the MODLEVEL JCL to identify the current modification levels of your Mainstar product load modules. If you experience difficulty running the report, or have any questions, contact Mainstar Technical Support at , or MODLEVEL identifies and displays which program PTFs (fixes) and ETRs (enhancements) have been applied to the level of the product you are running. This information is based on information stored internally within load modules. Please note that only the last update (level) will contain the fix and revision number and the change date. All other fixes will have only the ID number. The following is an example of the MODLEVEL JCL. //*JOBCARD JOB 'FIX REPORTER',CLASS=?,MSGCLASS=? //* * //* JCLFIXES * //* SAMPLE JCL FOR LISTING THE BUILD INFORMATION INCLUDED IN * //* MAINSTAR LOAD MODULES. * //* * //* MODIFY JOBCARD TO MEET LOCAL STANDARDS * //* * //* CHANGE THE &HLQ TO MATCH YOUR MAINSTAR PRODUCT LIBRARIES. * //* * //* //FIXRPTR PROC SOUT='SYSOUT-CLASS', LOAD1='?HLQ..LOAD' //BRM01MOD EXEC PGM=BRM01MOD //STEPLIB DD DISP=SHR,DSN=&LOAD1 //SYSUT1 DD DISP=SHR,DSN=&LOAD1 //SYSPRINT DD HOLD=YES,SYSOUT=&SOUT // PEND //* //RUN EXEC FIXRPTR DD statements for the MODLEVEL JCL are described below. DD STATEMENT STEPLIB SYSPRINT SYSUT1 DESCRIPTION Required. Specify the Mainstar product LOAD library. Required. Output DD statement. Required. Specify the primary LOAD library to be processed. continued on next page Mainstar Software Corporation Chapter 1 BRM Suite: Product Installation & Maintenance Overview

28 Installation & Maintenance Guide continued from previous page Execution of the MODLEVEL JCL creates a report containing the last fix and a list of fixes for all of the modules in the SYSUT1 library. The following is an example of the BRM MODLEVEL report. Highest ETR is ETR21657 Member DD Last fix Vers Rev Build Date/Time Macro ALB00001 SYSUT1 LAST SYSUT1 LIST ALB00002 SYSUT1 LAST SYSUT1 LIST /06/09 09:06 EHDR /06/08 16:17 EHDR ASP90100 SYSUT1 LAST ETR SYSUT1 LIST 19163,17950,21482 ASTBKEND SYSUT1 LAST ETR SYSUT1 LIST 17950,21180, /06/08 16:17 MSCHDR 2005/06/08 16:18 MSCHDR ASTBLDFF SYSUT1 LAST ETR /06/08 16:18 MSCHDR SYSUT1 LIST 20228,20198,20295,21179,21482 ASTBLDRJ SYSUT1 LAST ETR /06/09 10:35 MSCHDR SYSUT1 LIST 16639,20687,18862,21179,21308,21482 ASTDADFL SYSUT1 LAST ETR SYSUT1 LIST 20228,21482 ASTDADUP SYSUT1 LAST ETR SYSUT1 LIST 19455,21482 ASTDATRT SYSUT1 LAST ETR SYSUT1 LIST 20198,21482 ASTEMSGX SYSUT1 LAST ETR SYSUT1 LIST 09942,21482 ASTGETJB SYSUT1 LAST ETR SYSUT1 LIST 09942,20013, /06/08 16:19 MSCHDR 2005/06/08 16:19 MSCHDR 2005/06/08 16:19 MSCHDR 2005/06/08 16:19 MSCHDR 2005/06/08 16:19 MSCHDR Chapter Mainstar Software Corporation 2006 BRM Suite: Product Installation & Maintenance Overview

29 Installation & Maintenance Guide 1.6 Product Data Sets The consists of one install for three selectable products: ABARS Manager, All/Star, and ASAP. The authorization to use a selectable product is determined by the LICENSES code. The common install consists of a common set of libraries. You may choose any data set names for the product data sets during installation, which you must identify in the :INSTALLATION_DATASETS and :PRODUCT_DATASETS sections of the BRMINI member of the PARMLIB. If possible, keep the following low level qualifiers. Mainstar documentation and support personnel will refer to these file names. hlq.load hlq.ispplib hlq.parmlib hlq.messages hlq.skellib (All/Star only) hlq.packed (ASAP only) hlq.jcl hlq.rexxsamp (ABARS Manager only) hlq.ids (ABARS Manager and ASAP only) In addition, if possible, keep the following low level qualifiers. Mainstar documentation and support personnel will refer to these file names. hlq.asmsamp hlq.demoaggs.unload (ABARS Manager only) hlq.load hlq.ispplib hlq.parmlib Note: Do not add non-product members or copy product members in the product libraries or JCLBUILD will fail. It is also important to observe this limitation in an SMP/E environment. This library contains the load modules. The LOAD library must be APF authorized before beginning the configuration tasks in Chapter 4, Configure Backup & Recovery Manager Suite. The product LOAD library needs to be APF authorized in either IEAPFxx or PROGxx members. This data set is automatically created during installation. This library contains ISPF panels and messages. It is automatically created when the product is installed. This library contains information needed by during product execution, such as licensing information, configuration information, and information about maintenance that has been applied. This data set is automatically created during installation. hlq.messages This library contains the product messages and their descriptions. This data set is automatically created during installation. Mainstar Software Corporation Chapter 1 BRM Suite: Product Installation & Maintenance Overview

30 Installation & Maintenance Guide hlq.skellib hlq.packed hlq.jcl This library is used by All/Star only and contains the default skeleton restore JCL used during restores of backups tracked by All/Star. This data set is automatically created (if required) during installation. This is the ASAP REXX execution library, which contains REXX EXECs used by ASAP. Some of these EXECs are in a special format used by ASAP and may not appear readable if edited. This data set is automatically created when the product is installed. This library contains JCL and cataloged procedures. Unless directed to do so in this guide, or in the product installation instructions or User Guide, you should not modify the JCL in these members. This data set is automatically created during installation. hlq.rexxsamp hlq.ids hlq.asmsamp This library is used by ABARS Manager only and contains sample REXX source code for optional programs users may choose to modify for use with the ABARS Aggregate LoadBalancer facility. It is the user's responsibility to test and maintain programs used from this library. Please call Mainstar Technical Support for further information or assistance using programs in this library. This data set is automatically created during installation. The Inventory Data Set (BRM IDS) is the information repository for the selectable products ABARS Manager and All/Star. For ABARS Manager, it contains information about which aggregates have been backed up or recovered, which data sets were backed up or recovered as part of an aggregate, ABACKUP or ARECOVER tape volume usage, and so on. For All/Star, it contains information about non-abars backups and which data sets have been backed up. This data set is a VSAM KSDS structure. This data set is not automatically created during installation. You will create and initialize the Backup & Recovery Manager Inventory Data Set as one of the configuration tasks. See Chapter 4, Configure. This library contains sample assembler source code for optional programs you may choose to modify, assemble, and link edit. It is your responsibility to test and maintain programs used from this library. Some programs may be system release dependent. Please call Mainstar Technical Support for further information or assistance using programs in this library. This data set is automatically created during installation. hlq.demoaggs.unload This library is used by ABARS Manager only and contains demo aggregate samples information. You may choose to load this into the Inventory Data Set (BRM IDS). This file is not shipped with the product but is available on request. See Chapter 5, ABARS Manager: Post-Installation Tasks, for procedures. 1.7 Product Initialization Member PARMLIB(BRMINI) The keywords in the BRMINI member of the product PARMLIB allow flexibility for each installation, and in some cases, each user, to customize their control of product execution, and security of system parameters. Customizing the token values in BRMINI is included as a configuration task in Chapter 4, BRM Suite: Configure ABARS Manager, All/Star, and ASAP. Chapter Mainstar Software Corporation 2006 BRM Suite: Product Installation & Maintenance Overview