Home

Bloomfield 8780 Coffeemaker User Manual

1. T NP AL621EDA MP AL621EDI EPP AEX621AM EAP AEX621AA EIP DCIINSTL ASUDOPT ASUDOPD1 ACTDOPT ACTDOPD1 ACVPLAN ACV621DM DEFERUIX N R Default Option Listing DOPTs LANE SONE e F OP F O e FF O F F O F F e F O e F F F F O F F FF F F O F KF F Note The R in the variable syntax indicates that the value specified will refresh the existing value of the variable in the user s ISPF profile data set if the timestamp of the DOPTS is later than that in the user s ISPF profile member BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 11 Default Option Descriptions Default Option Descriptions This section describes the DOPTs listed in Figure 5 1 on page 5 9 In some cases the default value for the option is listed ACTDOPT ACTDOPD1 The name of the CATALOG MANAGER product s DOPTS module that the GUI for ALTER will use to interact with CATALOG MANAGER This parameter is used only if CATALOG MANAGER is installed ACVPLAN ACVyrmDM The main DB2 plan for the GUI for ALTER ALLOC N The allocation units to use for data sets that are managed by System Managed Storage SMS If the AMS is set to Y then this option determines how ALTER and CHANGE MANAGER allocate space for VCAT defined DB2 objects that SMS manages The DOPTs parameters are defined as follows cylinders kilobytes megabytes SMS not in use default tracks AZZA A
2. Table 3 12 Collection Name Variables Variable Represents prd product code vrm version release and maintenance level c exploited DB2 version B 3 1 C 4 1 D 5 1 and E 6 1 or later y access D direct l indirect a unique qualifier for the indirect catalog on that subsystem Note The access type for DASD MANAGER PLUS must be direct D With CATALOG MANAGER 3 4 and later you can have more than one indirect catalog Each indirect catalog requires a unique collection name Table 3 13 Examples of Collection Names Example Description ACT621_I_1_MAIN CATALOG MANAGER 6 2 01 indirect access first instance of indirection ACM621E_D_MAIN CHANGE MANAGER 6 2 01 DB2 Version 6 direct access ASU613_D_MAIN DASD MANAGER PLUS 6 1 03 direct access Collection Nicknames You can assign a meaningful nickname to the collection name This nickname provides CATALOG MANAGER users with easy to remember names of collections Table 3 14 shows an example of collection names that are on the test system DB2T that access indirect copies of production systems DB2P1 and DB2P2 and the corresponding nicknames that could be used Table 3 14 Examples of Collection Nicknames Collection Name Collection Nickname ACT621_ _1_MAIN DB2P1I ACT621_ 2 MAIN DB2P2I The nickname can be up to 13 characters long and cannot contain any blanks BMC Software Inc Confidential and Proprietary Information 3 26 Adm
3. 1 4 Estimated Space Requirements 1 4 ALTER Space Estimates L LL 1 5 CATALOG MANAGER Space Estimates 1 6 CHANGE MANAGER Space Estimates 1 7 DASD MANAGER PLUS Space Estimates 1 8 Understanding the Install System 1 9 Merging Data Sets from Multiple Tapes 1 9 Understanding Checkpoints LL 1 9 Installation Modes L LL 1 10 International Language Support LL 1 10 Installation Paths tate a AA Gu advan at il 1 10 Determining Product Status 1 11 Determining Version Release and Maintenance Levels 1 12 Determining Installation Paths 000005 1 13 Bull Installations n ou reale 1 14 Maintenance Installation LL 1 14 SSID Installation i rea de 1 15 Multiple SSID Installation 1 17 Installation Data Sets 1 18 Installation User Profile L LL 1 19 Searching for the Installation Profile 1 19 Reusing the User Profile LL 1 19 BMC Software Inc Confidential and Proprietary Information Contents v Chapter 2 Chapter 3 Installation Default Options 1 20 Rules for Running Multiple Product Releases in a Single Subsystem 1 21 Product Naming Conventions LL 1 22 Using the Install System Getting Started siii heh as Keto Re a e Bde eee es 2 2 Processing an ESD Image Li 2 3 Unloading the Install System 0 0 0 0 eee eee eee 2 6 Starti
4. Specifies whether text propagation for extended views is supported by ALTER or CHANGE MANAGER Y or N Indicates the version release level maintenance level and DB2 exploited version where B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 31 Post Installation Considerations WDC The Data Facility Storage Management Subsystem DFSMS or SMS data class name used at data set allocation time to define the allocation attributes of the data set A data class name is not required even for SMS data sets WDC will appear as DATACLAS in the JCL for workfiles WDSN amp amp PREFIX amp amp SSID amp amp WORKID WLPS 15 WLSS 5 WLU SYSDA WMC WPS 10 WSC WSS 2 WU SYSDA Defines the default data set name for a worklist that Analysis generates Defines the default primary space allocation for the worklist in 3120 byte blocks Defines the default secondary space allocation for the worklist in 3120 byte blocks Defines the default worklist unit The SMS management class name used at data set allocation time to define the migration retention and backup requirements of the data set WMC will appear as MGMTCLAS in the JCL for workfiles Defines the default work data set primary space allocation The SMS storage class name used at da
5. E lt IEW2307S 1032 CURR OF INVALID DATA GI NT INPUT MODULE NOT INCLUDED BECAUSE COPY FAILI INCLUDE D FOR MEMBER prdTBL3n FAILURE IN IEWBIND ETURN CODE 8 REASON CODE 83000507 Ww E wo T In these messages the variable prd is the three character product code and n is either P permanent or T temporary See Product Authorization Tables on page A 3 for more information If you receive any of these messages use the IEBCOPY utility to copy the tables Do not use the IEBCOPY COPYMOD parameter when copying the product authorization tables BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide How to Obtain Passwords How to Obtain Passwords Table A 2 describes the situations in which you need to obtain passwords For each scenario the table indicates the type of password that you need temporary or permanent what the password does and how to obtain it Table A 2 Password Scenarios Password Scenario Type Password Function How to Obtain You want to begin a temporary temporarily bypasses BMC Software sales free trial period authorization checking and representative allows you to run the product on any CPU for a limited time You purchase a permanent adds a designated CPU to the list BMC Software Contracts license for a new of CPUs that
6. 4 4 4 CEER G EGE GG Index BMC Software Inc Confidential and Proprietary Information 6 JDEVT 6 22 DSTP 6 22 JESTP 6 22 JC1 6 22 JC2 6 22 JC3 6 22 JC4 6 22 JC5 6 22 KSTP 6 22 JLL1 6 23 LSTP 6 23 JPLAN 6 23 PSTP 6 23 JRDSP 6 23 RSTP 6 23 SCPR 6 23 SCSE 6 23 SDEV 6 23 SERAUT 6 23 SERNAM 6 23 SRPR 6 23 JSRSE 6 23 JSRUN 6 23 SWPR 6 23 JSWSE 6 23 SWVL 6 24 JUSTP 6 24 VDEV 6 24 VDPR 6 24 VDSE 6 24 JVDSP 6 24 VSTP 6 24 WEPR 6 24 JWESE 6 24 WFUN 6 24 JWFVL 6 24 WLPR 6 24 JWLSE 6 24 WLUN 6 24 JWLVL 6 24 JXSTP 6 24 VIEWDEP 6 24 VIEWS 6 25 VMAX 6 25 VMAXU 6 25 VOLUMES 6 25 WDC 6 25 WDSN 6 25 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 Ge eereeeaeeaece eceecd 4 ec ec 4 4 4 4 4 4 4 4 4 Gee eee oad Cee Ce eC eae oe eta WLDSN 6 25 WMC 6 25 WSC 6 25 XDSN 6 25 CATALOG MANAGER plans ACTvrmDE 6 5 ACTvrmDH 6 5 ACTvrmDK 6 5 ACTvrmDL 6 6 ACTvrmDM 6 6 ACTvrmDU 6 6 catalog to catalog comparison 7 7 CATAUDIT DOPT 5 14 7 21 8 9 CATOP DOPT 6 12 CATRECOV DOPT 5 15 7 22 8 10 CCSID DOPT 5 15 7 22 CDLDSN DOPT 7 22 CDLPS DOPT 7 22 CDLRDSN DOPT 7 22 CDLSS DOPT 7 22 CDLU DOPT 7 22 CHANGE MANAGER BMC Software Utilities interface 3 6 catalog to catalog comparison 7 7 client installation 9 2 Compare component 7 6 controlling access 7 9 default option descriptions 7 18 default option listing 7 14 DOPTs 7 14 Execution plans 7 12 INFOBMC command 7 6 installation considerations 7 5
7. A 22 Processing a Temporary Password 0 0 0 0 eee eee A 23 Displaying Product Authorization 02000 e eee A 24 Displaying Current Processor Information A 26 Batch Product Authorization LL A 27 Running Batch Product Authorization LL A 27 Control Statements and Keywords LL A 29 Return Codes iii LR A 30 BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 1 Overview Overview When the Contracts Administration department of BMC Software processes a license agreement for a product it issues CPU authorization passwords These passwords authorize specific CPUs also referred to as processors to run the licensed product Because BMC Software licenses its products for use on individual CPUs the passwords are product specific and CPU specific one license per product per CPU To delete or replace an authorized CPU you must also have a password The types of passwords are as follows e Temporary passwords are issued for product trials or in other special circumstances for example when a hardware failure prevents you from using the authorized CPU e Permanent passwords are issued when you convert to a permanent license delete or replace a CPU or modify the properties of a CPU or the product authorization tables You use the BMC Software Product Authorization utility to apply passwords and to change your
8. Chapter 6 Installing CATALOG MANAGER 6 25 Post Installation Considerations Post Installation Considerations After installation refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for CATALOG MANAGER BMC Software Inc Confidential and Proprietary Information 6 26 Administrative Products for DB2 Installation Guide Chapter 7 Installing CHANGE MANAGER This chapter presents the following topics OVGIVICW una ei So tema RA A ews 7 2 CM PILOT Component 7 3 Installation Considerations L LL 7 5 Installation Defaults 0 0 0 ee eee 7 5 Using INFOBMC in the Compare Component 7 6 Performing a Catalog to Catalog Comparison 7 6 Controlling Access i iii sint e eRe Reed 7 9 CHANGE MANAGER Specification and Analysis Plans 7 10 CHANGE MANAGER Execution Plans 7 12 CHANGE MANAGER Object Security 0 7 13 JSI JES Interface Installation 2 0 0 0 eee eee eee 7 13 Default Option Listing DOPTS LL 7 14 Default Option Descriptions 0 0 0 cece eee nee 7 18 Post Installation Considerations LL LL 7 32 BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 4 Overview Overview This chapter provides information about how to prepare to install the BMC Software CHANGE MANAGER for DB
9. SYSTYPE S PIC N LOG N SL1 BMCADMN V621 D61 LOAD R ELE T Gi w x pes SL2 SYS3 DBDB DSNEXIT R SL3 SYS2 DB2V61M DSNLOAD R SLAS t Ships T t ISPSLIB BMCADMN V621 D61 SLIB R TSOSX N JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 JC3 NOTIFY amp amp USERID JC4 JC5 DBRM1 DBRM2 DBRM3 DBRMLIB N WU SYSDA WPS 10 WSS 2 WDC WSC WMC SWU SYSDA SWPS 10 SWSS 2 WDSN amp amp PREFIX amp amp SSID amp amp WORKID WLU SYSDA WLPS 15 FF F F FF F FF FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F F FF F F KF OF BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 15 Default Option Listing DOPTs Figure 7 1 7 16 WLSS DLD DLU DLP DLS DLR RPT JDSN JDSN JDSN JDSN JDSN JDSN DSN DSN DSN MPD MPD ASD WaQqQqaAa n AAGWWHANNYEA HA AAA SYSR SYSC SYSC SYSC SYSC SYSC SYSC LRP 5 SN amp amp PREFIX amp amp SSID CDL CDL SYSDA S 15 S 5 DSN amp amp PR DSN amp amp PR amp amp PR B EFIX COMPARE R Eal EFIX BASELINE R EPORT CHANGE MANAGER Default Options Listing Part 2 of 4 PORT BG
10. Where to Go From Here 9 10 After you install the client you can start and configure it See Starting and Configuring the Client on page 9 18 BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Installing the Client Using Distribution Software Installing the Client Using Distribution Software Summary By using distributed systems software such as the Microsoft SMS product or any other product that supports packages you can install the Database Administration product on every desktop in your organization to which you have access When combined with the consistency of the command line silent installation this means of product distribution provides a faster more consistent approach to updating and distributing software Step 1 Copy the client images to your hard drive or to a shared network drive The client images are located in the client directory Note Be sure to copy the client images to a directory that is different from the directory where you copied the server images Step 2 Modify the PDB_Install ini file to make product and directory selections When editing the file specify 0 to disable a selection and specify 1 to enable a selection The only requirement when editing this file is that you must select a product in the Selections section See Figure 9 1 on page 9 9 for an example of a PDB_Install ini file Step3 Run the distributed system s
11. Fully test the Administrative Products without catalog indirection before you implement it Catalog indirection is an optional feature that you can implement only after the product is installed Installation You can install catalog indirection for one or more Administrative Products on one DB2 subsystem at a time Implement catalog indirection to create a copy or view of the DB2 catalog if you have not previously created one Maintenance You can apply maintenance to catalog indirection on one or more Administrative Products on one DB2 subsystem at a time Perform maintenance if you have an existing copy or view of the DB2 catalog and have performed a new installation of the Administrative Products If you are applying maintenance to catalog indirection you must specify the synonym qualifier that is currently the owner of the products synonyms This qualifier must be the qualifier that you supplied when you originally installed catalog indirection for the products The Install System automatically sets the qualifier status to USED REUSE Catalog indirection maintenance does not create any new DB2 objects but it does recreate the existing synonyms Because the Install System automatically sets the qualifier status to USED REUSE the synonyms are dropped and then re created BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 21 Using Catalog Indirection Synonym Qua
12. Note ALTER and CHANGE MANAGER must be installed in a separate library for each DB2 version Use the Full installation path to install the product for each DB2 version that you want to use with it Authorization to Run the Installation Batch Jobs When you install BMC Software products for DB2 you must have a DB2 authorization of SYSADM to run the batch jobs that the Install System generates However you do not need DB2 authorization to run the Install System or to generate the batch jobs Estimated Space Requirements During the unload process the Install System allocates various data sets according to the products that you select for installation The following sections describe the data sets that the Install System allocates for each product on the tape HLO represents the high level qualifier that you have chosen for the BMC Software Products To determine your total space requirements add up the space required for each product that you are installing Note If you are using DB2 defined objects you must have a previously defined storage group STOGROUP The Install System does not define STOGROUPs BMC Software Inc Confidential and Proprietary Information 1 4 Administrative Products for DB2 Installation Guide Estimated Space Requirements ALTER Space Estimates Table 1 1 and Table 1 2 provide space estimates for ALTER objects and distribution data sets Table 1 1 Space Estimates f
13. Step 4 Step 5 This procedure describes how to provide full access to the files on the CD by copying the installation image from the CD to a shared network drive and then installing the product locally This option provides anyone who wants to install the client on their local hard drive full access to the range of product offerings The following procedure uses n for the network drive If your network drive is mapped to another letter substitute the correct drive letter Insert the Database Administration product s CD into the client s CD ROM drive The Database Administration product s Setup program launches automatically Click Cancel and then click the Exit Setup button Copy the files from the CD to a shared network drive From Windows Explorer choose the CD ROM drive and select all of the files on the drive Copy the highlighted files to a shared network drive Start the Database Administration products Setup program From Windows Explorer double click setup exe from the location on the network where the Database Administration installation files reside Alternatively click the Start button and choose Run Enter n install_dir setup exe in the Run dialog box The Welcome page of the Setup program appears Follow Step 2 through Step 8 in the task Installing a Client to Run Locally on page 9 6 BMC Software Inc Confidential and Proprietary Information 9 8 Administrative Products for DB2 Installa
14. WDC Default Option Descriptions For DB2 Version 5 1 and later specifies whether the tables that RUNSTATS indicates as empty are unloaded For DB2 Version 5 1 and later specifies which statistics are updated The DOPTs parameters are defined as follows A All The DASD tables and the DB2 Catalog tables are updated BMCSTATS is selected B BMC DASD tables Only the DASD tables are updated BMCSTATS is selected C DB2 Catalog Only the DB2 Catalog tables are updated RUNSTATS is selected Determines whether other utilities or a copy utility creates an image copy during loads Y Image copies are created by utilities other than the copy utilities whenever possible If the utilities cannot create a copy a separate copy step is generated N A separate copy step generates all copies that the specific copy utility takes either the IBM COPY utility or the BMC Software COPY PLUS utility Specifies whether text propagation for extended views is supported by ALTER or CHANGE MANAGER Y or N Indicates the version release level maintenance level and DB2 exploited version where B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later The Data Facility Storage Management Subsystem DFSMS or SMS data class name used at data set allocation time to define the allocation attributes of the data set A data class name is not required even for SMS data sets WDC will appear a
15. silent setup command setup located in the client images folder that you copied to your hard drive This command accepts the following options isuninst f pathname pdba_log isu f indicates the location of the pdba_log isu log file and pathname indicates where the product was installed The pdba_log isu log file is created during the installation The installation program uses the file to perform cleanup tasks Note Do not include a space between the f option and the double quotes BMC Software Inc Confidential and Proprietary Information 9 16 Administrative Products for DB2 Installation Guide Reinstalling a Product Reinstalling a Product Summary This task describes how you can reinstall a product if you want to change the existing installation or if files in the product directories were deleted or corrupted Step 1 Use the same installation instructions that you used for the previous installation The program prompts you to confirm information that you provided during the previous installation Step 2 Verify the installed files Note The disk space requirements in this chapter are for an initial installation Disk space requirements for a reinstallation are reduced by the amount of disk space that you used for the initial installation Where to Go From Here After you reinstall the product you can start and configure the client See Starting and Configuring the Client on page 9 18 BMC S
16. 3 12 Synonym Qualifier Variables 0 0 0 0 3 23 Examples of Synonym Qualifiers 0 0 0 0 cee eee ee eee 3 23 DOPTs Module Variables 0 0 0 0c eee cece 3 24 Examples of DOPTs Modules 0 0 0 0 e eee ee eee 3 24 Plan Name Variables LL 3 25 Examples of Plan Names 3 25 Collection Name Variables 0 00 cece cece eee eee 3 26 Examples of Collection Names 0 0 0 cece ee eee eee 3 26 Examples of Collection Nicknames 0 0000 e eee eee ee 3 26 Migrating DB2 Version 5 to Version6 0 e eee eee 3 30 Creating a New DB2 Version 6 Catalog 3 34 Migrating DB2 Version 4 to Version 5 0 02 eee ee eee 3 35 Creating a New DB2 Version 5 Catalog 3 39 SYSCOPY and SYSRECV DOPTS LL 4 16 Fast Path Navigation Commands L LL 4 21 BMC Software Inc Confidential and Proprietary Information Tables xiii xiv Table 4 3 Table 4 4 Table 4 5 Table 4 6 Table 5 1 Table 6 1 Table 6 2 Table 7 1 Table 8 1 Table 9 1 Table 9 2 Table 9 3 Table A 1 Table A 2 Table A 3 Table A 4 Table A 5 Table A 6 Table B 1 MVS Commands iii i aa ae el 4 29 APPC MVS Configuration Parameter Descriptions 4 34 Installation Parameters L LL 4 42 Code Page Values ila wi oes oe hehe as 4 43 ALTER Installation Default Values 0 00 5 3 CATALOG MANAGER Installation Default Values 6 3 Examples of CATA
17. A 30 reverting to a previous level 2 6 2 27 RMAX DOPT 6 19 RMAXU DOPT 6 19 ROUTINA DOPT 6 20 ROUTINE DOPT 6 20 RPLAN DOPT 8 12 RPTPL DOPT 7 28 S SCHEMAA DOPT 6 20 SCRIPT data set ALTER 1 5 CHANGE MANAGER 1 7 SDSN DOPT 5 20 6 20 7 28 SDSNE DOPT 5 20 7 28 Index 17 SEARCH command GRANT 3 20 SECEPADD A 13 SECEPCPU A 26 SECEPDEL A 15 SECEPPRI A 11 SECEPREP A 17 SECEPTBL A 24 SECEPUPD A 20 SEQI DOPT 5 20 7 28 severity codes messages B 3 silent installation clients 9 9 single options module 3 17 SL1 DOPT 5 20 7 28 8 12 SL2 DOPT 5 20 7 28 8 12 SL3 DOPT 5 20 7 29 8 12 SL4 DOPT 5 20 7 29 8 12 SL5 DOPT 5 20 7 29 8 12 SLIB data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 SLIB compiling 4 14 space requirements BMC Software DB2 objects ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 space requirements distribution data sets ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 SPLAN DOPT 8 12 SPP DOPT 5 20 7 29 SQL Explorer client installation 9 2 DASD MANAGER PLUS interface 3 11 interacting with DASD MANAGER PLUS 3 11 post installation tasks 4 22 SSID DOPT 5 20 6 20 7 29 8 12 SSID installation considerations 1 16 multiple options module 3 17 Multiple SSID 1 17 product restrictions 1 17 single options module 3 17 BMC Software Inc Confidential and Proprietary Information stamp VOLSER on distribution tape 2 13 s
18. At least one character in the CPU model number specified in the batch JCL is invalid Only hexadecimal characters 0 to 9 and A to F are allowed in the model number System Action The password is not processed User Response Correct the model number and resubmit the job See Control Statements and Keywords on page A 29 for assistance with syntax BMC89059E SERIAL NUMBER CONTAINS INVALID CHARACTERS Explanation At least one character in the CPU serial number specified in the batch JCL is invalid Only hexadecimal characters 0 to 9 and A to F are allowed in the serial number System Action The password is not processed User Response Correct the serial number and resubmit the job See Control Statements and Keywords on page A 29 for assistance with syntax BMC89060E THIS PASSWORD REQUIRES NEWCPUID KEYWORD FOR THE CPU ID TO BE ADDED Explanation The Add password being processed requires specification of the NEWCPUID keyword and none was specified System Action The password is not processed User Response Specify the NEWCPUID keyword on your input control statement See Control Statements and Keywords on page A 29 for assistance with syntax BMC89061E THIS PASSWORD REQUIRES OLDCPUID KEYWORD FOR THE CPU ID TO BE DELETED Explanation The Delete password being processed requires specification of the OLDCPUID keyword and none was specified System Action The password is not processed
19. BMC Software Inc Confidential and Proprietary Information 9 20 Administrative Products for DB2 Installation Guide Appendix A BMC Software Product Authorization This appendix presents the following topics OVEIVIEW sorta iii rien Seis a eee ta A 2 Product Authorization Tables 0 0 0 0 cee eee ee eee A 3 Problem Regarding Product Authorization Table Installation A 3 Product Authorization Passwords 0 0 0 c eee ee eee eee A 4 Permanent Passwords 0 0c e cece eee eee eee A 4 Temporary Passwords 00 cece eee eee eee A 5 How to Apply Passwords 0 0 eee eee A 5 How Products Are Licensed 0 0 0 eee eee eee eee A 5 Product Trials and Permanent Licensing A 6 CPU Upgrades ns ito ancy idee An Wea oa oe eae ME A 6 CPU Fallures 0 ieri aria eee Bae dl de A 6 Product Maintenance or Version Upgrades A 8 How to Obtain Passwords 0 0 0 cee eee eee eee A 9 CPU Information oenen ee ety ia A EAA A 10 Online Product Authorization 0 0 0 0 cece eee eee eee A 10 Processing a Permanent Password LL A 11 Adding Authorization for a Processor 0 005 A 13 Deleting Authorization for a Processor A 15 Replacing Authorization for a Processor A 17 Modifying Authorization for an Existing Processor A 19 Resetting Authorization for all Processors
20. BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 23 Displaying Product Authorization Displaying Product Authorization Summary Use the Product Authorization Display panel to display the current authorization for a product Step 1 On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 2 Step 2 At Product load library type a fully qualified data set name Step 3 Press Enter to display the Product Authorization Display panel Figure A 12 See Additional Information on page A 25 for descriptions of the fields on this panel Step 4 When you finish reviewing the panel press F3 to exit the Product Authorization utility and return to the previous menu or panel Figure A 12 Product Authorization Display Panel SECEPTBL SECEPTBL Product Authorization Display ROW 1 TO 1 OF 1 Press Enter to continue Load Library secs a 6 ea Gea eo oh TBMG PRODUCT LOAD Product code te 4 e wu e 6 e St Let Oe Ser La de SS DOM Last changed mm dd yy hh mm 11 19 96 10 11 Last changed by RDHDXJ3 Grace period ends mm dd yyyy 1 04 29 1999 Temporary expiration date mm dd yyyy 05 10 1999 Licensed Processors Product Maximum License Serial Model Version Significant Number of Expiration Number Number Code Digits Tier Processors Date 77403 3090 62 4 018 ALL NONE 10309 9021 D5 4 018 ALL 12 1999 KKKKKKKKKKKKKKKKKK
21. Chapter 3 Performing Additional Installation Tasks 3 11 Interacting with Other BMC Software Products Pointing the SQL Explorer Synonyms to the DASD MANAGER PLUS Tables Table 3 5 shows the SQL Explorer synonyms that are used to access the DASD MANAGER PLUS tables in the Migrate Statistics function when BMCSTATS is the source of the data You must not change the synonym names The default naming standard for the tables assumes that yy is the version and release number of the DASD MANAGER PLUS product These table names are the default names as shipped and may have changed when DASD MANAGER PLUS was installed Table 3 5 SQL Explorer Synonyms Synonym DASD MANAGER PLUS Table BMCPSS_SCOLDIST BMCASUyy Vyy RS_COLDIST BMCPSS_SCOLDISTSTA BMCASUyy Vyy RS_COLDISTSTAT BMCPSS_SCOLSTATS BMCASUyy Vyy _RS_COLSTATS BMCPSS_SCOLUMNS BMCASUyy Vyy _RS_COLUMNS BMCPSS_SINDEXES BMCASUyy Vyy_RS_INDEXES BMCPSS_ STABLES BMCASUyy Vyy_RS_ TABLES BMCPSS_STABLESPACE BMCASUyy Vyy_RS_ TABLESPACE Examine these synonyms and verify that the table names are correct If your current SQL Explorer synonyms do not point to the correct DASD MANAGER PLUS tables complete the following steps to point the synonyms to the correct tables 1 Drop the seven SQL Explorer synonyms 2 Recreate new SQL Explorer synonyms by using the same synonym names but pointing to the correct DASD MANAGER PLUS table names The synonym qualifier must be the same one that w
22. Confidential and Proprietary Information xxiv Administrative Products for DB2 Installation Guide e automatic selection of the CATALOG MANAGER to BMC Utilities interface when UTILITY MANAGER and CATALOG MANAGER are selected to be installed at the same time e modification of the Catalog Indirection installation panel to include only those products that use this process This installation guide provides documentation for the following products e ALTER for DB2 version 5 4 04 e CATALOG MANAGER for DB2 version 5 4 05 e CHANGE MANAGER for DB2 version 5 4 04 e CM PILOT for DB2 version 5 4 04 e DASD MANAGER PLUS for DB2 version 5 4 04 e PATROL DB Alter for DB2 version 3 1 02 e PATROL DB Change Manager for DB2 for OS 390 version 3 1 02 e SQL Explorer for DB2 version 3 1 01 Version 1 5 30 December 15 1999 This installation guide provides support for the BMC Software Install System Enhancements for version 1 5 30 of the Install System include e the inclusion of 198ssid in the HLQ CNTL library to enable you to remove DB2 structures from a previous installation e the ability to unload a Japanese language version of the SQL Explorer double byte character set rules e the use of the F4 key or the CKPANELS command to display the percentage of the installation that is complete and the number of panels that remain e the modification of the TIS and SAT tape labels to make them more readable and useful This installation guide
23. For information on collection nicknames as well as default options refer to the following sections BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 3 Installation Considerations Collection Nicknames You can assign a meaningful nickname to the collection name This nickname provides CATALOG MANAGER users with easy to remember names of collections Table 6 2 shows an example of collection names that are on the test system DB2T that access indirect copies of production systems DB2P1 and DB2P2 and the corresponding nicknames that could be used Table 6 2 Examples of CATALOG MANAGER Collection Nicknames Collection Name Collection Nickname ACT621_1_1_MAIN DB2P11 ACT621_ _ 2 MAIN DB2P2 The nickname can be up to 13 characters long and cannot contain any blanks Default Options Processing Unlike the other Administrative Products for DB2 CATALOG MANAGER is designed to use a single default options DOPTs module for both direct and indirect access To implement a single DOPTs module the installation dialog must process the CATALOG MANAGER DOPTs module differently than the DOPTs module of the other Administrative Products The differences are described as follows e During catalog indirection installation the installation dialog prompts you for the creator of the CATALOG MANAGER indirect synonyms for the indirect collection ID and for the name of the direct
24. Inc Confidential and Proprietary Information 1 6 Administrative Products for DB2 Installation Guide Estimated Space Requirements CHANGE MANAGER Space Estimates Table 1 5 and Table 1 6 provide space estimates for CHANGE MANAGER objects and distribution data sets Table 1 5 Space Estimates for CHANGE MANAGER Objects Primary Secondary Estimated Estimated Object Quantity Quantity Tracks Tracks Default KB KB 3380 3390 table space 28000 4480 700 584 index space 6480 2760 162 135 Note Space estimates for the CM PILOT component of CHANGE MANAGER are included in Table 1 5 Table 1 6 Space Estimates for CHANGE MANAGER Disiribution Data Sets Estimated Estimated Distribution Data Set HLQ CNTL HLQ LOAD HLQ CLIST HLQ PLIB HLQ SLIB HLQ MLIB HLQ DBRM HLQ TLIB HLQ MSGS HLQ SCRIPT HLQ MSGTEXT BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 7 Estimated Space Requirements DASD MANAGER PLUS Space Estimates Table 1 7 and Table 1 8 provide space estimates for DASD MANAGER PLUS objects and distribution data sets Table 1 7 Space Estimates for DASD MANAGER PLUS Objects Primary Secondary Estimated Estimated Object Quantity Quantity Tracks Tracks Default KB KB 3380 3390 table space 51840 15840 1296 1080 index space 18000 9000 450 375 Table 1 8 Space Estimates fo
25. User Response Verify that the data set name for the correct product load library was specified The product load library should be a partitioned data set If the data set is not partitioned check to ensure that the product was correctly installed Retry the action If failure persists contact BMC Software Product Support for assistance THIS TEMPORARY AUTHORIZATION PASSWORD CONTAINS AN EXPIRATION DATE THAT HAS ALREADY EXPIRED Explanation To be valid the expiration date for the temporary password must be equal to or greater than the current date System Action The password is not processed User Response Contact your BMC Software sales representative THE PRODUCT AUTHORIZATION TABLE IS FULL NO NEW CPU IDS CAN BE ADDED Explanation The maximum number of CPUs has been stored in this product authorization table System Action The password is not processed User Response If some CPUs in the table are no longer being used they can be deleted to make room for this CPU Contact your BMC Software sales representative to obtain a Delete password If no CPUs can be deleted call BMC Software Product Support for assistance BMC Software Inc Confidential and Proprietary Information B 14 Administrative Products for DB2 Installation Guide Error Messages BMC89118E TEMPORARY AUTHORIZATION PASSWORD DOES NOT CORRESPOND TO THE CURRENT BMC PRODUCT Explanation The temporary authorization in your product authorization library
26. X04 UH9 KNG JKE New serial number 10293 New model number 9672 for example 9021 9121 3090 Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 2 At New serial number type the serial number of the processor for which you are adding authorization BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 13 Adding Authorization for a Processor Step3 At New model number type the model number of the processor for which you are adding authorization and press Enter A pop up message on the Product Authorization Primary Menu explains that the product authorization table was modified successfully Figure A 3 Figure A 3 Product Authorization ADD Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options Process password Requires product load library and password Display product authorization Requires product load library only Display current processor information Help about Exit Additional information Product load library BMC PRODUCT LOAD Authorization password BMC89127I PROCESSOR WAS SUCCESSFULLY ADDED TO THE PRODUCT AUTHORIZATION TABLE YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON SERIAL NUMBER 10293 MODEL NUMBER 9672 PRESS ENTER TO CONTINUE Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cance
27. Y Use BMCSTATS N Use RUNSTATS X Do not generate statistics Specifies whether to use the BMC Software UNLOAD PLUS utility product in place of ALTER UNLOAD Y or N Indicates the size of the buffer pool for user indexes Valid values include BPO through BP49 Indicates the size of the buffer pool for user data Valid values include e BPO through BP49 e BP8KO through BP8K9 e BPIGKO through BP16K9 e BP32K BP32KI through BP32K9 The DDL audit logging indicator If you have CATALOG MANAGER installed an entry of Y causes Execution to log executed DDL statements in the CATALOG MANAGER DDL Audit Log Y or N BMC Software Inc Confidential and Proprietary Information 5 14 Administrative Products for DB2 Installation Guide CATRECOV N CCSID E Default Option Descriptions The Drop Recovery indicator This parameter is useful only if you have CATALOG MANAGER installed Type Y if you want execution to save information in the CATALOG MANAGER drop recovery log about objects that are being dropped ALTER or CHANGE MANAGER logs the information that is required for recovering any object that you drop You must then use CATALOG MANAGER to recover the objects See the CATALOG MANAGER for DB2 Reference Manual for information about Drop Recovery Provides the default encoding scheme for databases created using ALTER A ASCII E EBCDIC COPYDD01 R COPYDD02 N REC VDD01 N REC VDD02 N DASDMAN Y DATACLAS N DATE amp SYSDAT
28. amp amp OBNOD FF F FF F F FF F F FF F F FF F F FF F F FF FF F F FF F FF FF F F FF F F FF F F FF F F KF OF BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Default Option Descriptions Figure 8 1 RECVSS 2 RECVMAX RECVMAXU TAP TAP TAP DPN CAT CAT JCL PN E1 CART E2 TAPE E3 TAPE AM DPDELOAD AUDIT N R RECOV DB2I TATAUT DGDEF N DGLIM 0 N O PLAN ASU PLAN ASU PLAN ASU PLAN PLAN PLAN PLAN ASU ASU ASU ASU CLEAN N R 613 613 613 613 613 613 613 EVT 3380 R DC DD DJ DS DX DZ DR DASD MANAGER PLUS Default Options Listing Part 2 of 2 FROWN KnNnGQDOAUWAAN NO OCATION EPP AEX613DM EAP AEX613DA EIP DCIINSTL DLHO BMCADMN V613 D61 ISPTLIB BMCADMN V613 D61 TLIB END LKED SYSIN DD R F FF F O O F F O F F O F F FF F F FF F F a O F NAME ASUDOPD1 R Note The R in the variable syntax indicates that the value specified will refresh the existing value of the variable in the user s ISPF profile data set if the timestamp of the DOPTS is later than that in the user s ISPF profile member Default Option Descriptions This section describes the DOPTs listed in Figure 8 1 on page 8 8 In some cases the default value for the option is listed CATAUDIT N The DDL
29. e change data structures using an existing Work ID e migrate data structures using an existing Work ID e receive data structure changes strong sender e receive data structure changes strong receiver e receive DDL to create data structures e create a full recovery baseline e recover data structures with current data e recover data structures with old data BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 3 Overview The dialog for two of the Scripts helps you create SQL like data manipulation language DML statements to change update and delete capabilities and to migrate data structures You can also modify the DML statements in an ISPF edit session provided by CM P Using DML gives you functions similar to the CHANGE MANAGER Specification component except you can change or migrate multiple data structures in a single DML statement Three of the Scripts use triggers which are conditions that result in the remaining Script steps being executed if the trigger condition is true For the Compare trigger you specify the trigger in the form of a comparison For the DML triggers you specify the triggers in the WHERE clause of the DML statement The information that you provide through the CM PILOT dialog is stored in a Task ID which is a unit of work with a unique identifier CM PILOT provides the dialog for the creation and maintenance tasks that are associated with Task IDs Yo
30. installation During the subsequent Multiple SSID installation process the Install System replaces the special identifier with the correct SSID when it generates the installation batch jobs Note Ifthe DB2 subsystems differ in characteristics that are outside the scope of the Multiple SSID installation process you must perform a standard SSID installation for each subsystem using a new installation user profile Installation Data Sets The Install System creates the following data sets prior to creating the data sets for the BMC Software products e HLQ INSTALL library e HLQ ANSTALL LOAD load library e User named output JCL data set Note You can create as many user named output JCL data sets as you want by rerunning the Install System BMC Software Inc Confidential and Proprietary Information 1 18 Administrative Products for DB2 Installation Guide Installation User Profile Installation User Profile The Install System saves the installation options in a user profile The member name of the user profile is xxxxPROF where xxxx is the profile ID The default profile ID is DCI so the default member name is DCIPROF The Install System saves the installation profile in the following locations e the ISPF profile data set ISPPROF that is associated with your user ID e the output JCL data set that you specify in the User Options panel to contain the installation batch jobs e the HLQ INSTALL library that you create when y
31. synonyms by using the same synonym names but with the correct table names 3 Rebind all ALTER ALU or CHANGE MANAGER ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Provided that ALTER or CHANGE MANAGER still exists in toleration mode use the fallback procedures described for toleration mode and remove the product in exploitation mode Any data that you added while you were in exploitation mode will not be available in toleration mode 3 35 Maintaining BMC Software Administrative Products Table 3 17 If You Are using ALTER or CHANGE MANAGER 6 1C or later installed on DB2 Version 4 using CATALOG MANAGER 5 3 or 5 4 Then Migrate the DB2 catalog 2 Ifthe Distributed Data Facility DDF is installed for CHANGE MANAGER drop the current synonyms to the old communication database tables Then recreate the synonyms by using the same synonym names but with the new catalog table names For an example refer to the ALUINIT5 or ACMINIT5 member in the HLQ JCL library 3 Rebind all ALTER ALU or CHANGE MANAGER ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Then you will be operating in toleration mode Migrating DB2 Version 4 to Version 5 Part 2 of 5 To Fall Back Then 1 Check your synonyms to
32. to access the SYSIBM SYSTRIGGERS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether all users or just users with DB2 SYSADM authority can terminate utilities Y Only users with DB2 SYSADM authority can terminate utilities N Any user can terminate the utility The ARCHIVE device type The size of the ARCHIVE primary space The size of the ARCHIVE secondary space UADSP amp amp PREFIX amp amp SSID The prefix to be used with the last qualifier of ARCHIVE data sets BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 21 Default Option Descriptions UBSTP The DASD MANAGER PLUS load library If you are installing DASD MANAGER PLUS together with CATALOG MANAGER type the name of the DASD MANAGER PLUS load library Otherwise comment out the library name Note These parameters must match the load library and options module name that is used when installing DASD MANAGER PLUS See also the description for BOPTS UCDSP amp amp PREFIX amp amp SID amp amp OBNOD UCOMD UCSTP UDEVT SYSDA UDSTP UESTP UJC4 UJC5 UKSTP The prefix to be used with the last qualifier of SYSCOnnn data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space n
33. 05 14 02 181 181 SIO5UNLD 01 00 99 02 05 14 02 494 494 SI10VSAM 01 00 99 02 05 14 02 306 306 SI30DOPT 00 99 02 05 14 02 230 230 SI35BNDI JO 99 02 05 14 02 41 41 staomsr v 00 99 02 05 14 03 186 186 SI55ICPY 01 00 99 02 05 14 04 121 LZ SI65MIG o1 00 99 02 05 14 04 82 82 SI66MIG YO 99 02 05 14 04 108 108 SI67COPY DO 99 02 05 14 05 115 ELS son 01 00 99 02 05 14 05 90 90 I97DOC 01 00 99 02 05 14 05 14 14 I98DROP 01 00 99 02 05 14 06 203 203 SI99DLTE 01 00 99 02 05 14 06 109 109 Cancelling the Installation At times it is necessary to cancel the installation process and revert to the previous level of a product or a product tape set You should ensure that a complete backup of your current system is available prior to beginning your installation Reverting to Conditions Prior to a Tape Installation If you used new plan names table names and repository names during a single tape or merged tape installation then you can easily revert to the product level that was in place prior to the new installation Modify the newly generated JCLs to refer to the previous product libraries To start those products that have an ISPF or a graphical user interface you can then invoke the previous CLISTs or desktop shortcuts BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 27 Where to Go From Here Reverting to the Prior Version of an Individual Product Some products have interdepende
34. 2 DASD Allocations for ESD Images DASD Type Primary Allocation Secondary Allocation 3380 27 cylinders 2 cylinders 3390 24 cylinders 2 cylinders The data set should have the following attributes e a fixed binary record format RECFM F B e a logical record length of 80 columns LRECL 8 0 e a block size of 3120 bytes BLKSIZE 3120 BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 3 Processing an ESD Image To Process the ESD Image Step 1 Use your site s file transfer protocol FTP procedure to transfer the ESD image to the data set that was Just allocated on the mainframe using a binary transfer scheme You can also use an internet browser to copy files to your site then upload the files to the mainframe If you are not familiar with FTP procedures or if you need assistance transferring the file to the mainframe contact your site s MVS system programmer or technical support Step 2 Edit the mainframe data set as follows 2 A Edit the job card to comply with your site s requirements using all uppercase letters 2 B To specify a high level qualifier HLQ prefix for the expanded data set other than your user ID remove the comment marker from the PROFILE PREFIX statement and specify a prefix Only a single node prefix or high level qualifier is allowed The prefix appends to the HLQ for the expanded data set and you ca
35. 22 6 21 7 31 8 13 TAPE3 DOPT 5 22 6 21 7 31 8 13 TCP IP configuration 4 23 temporary expiration date A 25 temporary passwords A 5 JCL for batch A 28 message A 23 processing online A 23 TIMEPARM DOPT 5 22 7 31 8 14 TLIB data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 trials A 2 A 6 TRIGGER DOPT 6 21 troubleshooting client installation 9 12 TRS DOPT 6 21 TSO Commands Utility panel 2 11 TSOSX DOPT 5 22 7 31 typographical conventions xix U UADEV DOPT 6 21 UADPR DOPT 6 21 UADSE DOPT 6 21 UADSP DOPT 6 21 UBSTP DOPT 6 22 UCDSP DOPT 6 22 BMC Software Inc Confidential and Proprietary Information COMD DOPT 6 22 JCSTP DOPT 6 22 JDEVT DOPT 6 22 JDSTP DOPT 6 22 JESTP DOPT 6 22 JC1 DOPT 6 22 JC2 DOPT 6 22 JC3 DOPT 6 22 JC4 DOPT 6 22 JJC5 DOPT 6 22 JKSTP DOPT 6 22 JLL1 DOPT 6 23 JLSTP DOPT 6 23 uninstalling client 9 15 from a command line interface 9 16 silently 9 16 UNLDCOLL DOPT 5 22 7 31 UNLDEMPT DOPT 5 23 7 31 unlicensed CPU executing a product A 5 unloading the Install System from tape 2 6 unsuccessful refresh 3 13 updating product authorization tables A 7 UPDSTATS DOPT 5 23 7 31 upgrading to a new version product authorization A 8 upgrading shared components 3 4 PLAN DOPT 6 23 JPSTP DOPT 6 23 JRDSP DOPT 6 23 RSTP DOPT 6 23 SCPR DOPT 6 23 SCSE DOPT 6 23 SDEV DOPT 6 23 JSED REUSED 2 11 ser options defining 2 22 SERAUT DOPT 6 23 JSERNAM DOPT 6 23 sin
36. 37 Maintaining BMC Software Administrative Products Table 3 17 If You Are using DASD MANAGER PLUS 6 1 using PATROL DB Alter or PATROL DB Change Manager server 2 2 04 through 3 1 02 initially installed on a DB2 Version 4 subsystem Then 1 Migrate the DB2 catalog 2 Run HLQ CNTL UPGRD4 5 Then you will be operating in exploitation mode 1 Migrate the DB2 catalog 2 Ifthe Distributed Data Facility DDF is installed drop the current synonyms to the old communication database tables Then recreate the synonyms by using the same synonym names but with the new catalog table names For an example refer to the ALUINIT5 or ACMINIT5 member in the HLQ JCL library 3 Rebind all PATROL DB Alter ALU or PATROL DB Change Manager ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Then you will be operating in toleration mode As an alternative to toleration mode you can perform a Full installation of ALTER or CHANGE MANAGER 6 2D Then you will be operating in exploitation mode Migrating DB2 Version 4 to Version 5 Part 4 of 5 To Fall Back Then 1 Check your synonyms to make sure that they point to the correct table names 2 If the synonyms do not point to the correct names drop the current synonyms Recreate the synonyms by using the same synonym names but with the correct table
37. 5 DASD MANAGER PLUS Plans LL 8 5 DASD MANAGER PLUS Execution Plans 8 6 Interacting with Other BMC Software Products 8 7 Default Option Listing DOPTS LL 8 7 Default Option Descriptions 0 0 ce eee eee eee 8 9 Post Installation Considerations 0 0 00 e eee eee eee ee 8 14 Chapter 9 Installing the Client for ALTER and CHANGE MANAGER OVEIVICW ici Sek eaa he EE ea EAE Boa ian 9 2 Prer quisites 2 iu bese geld Se Vibe Se eee RL GE ae 9 2 Domestic and International Supported Environments 9 2 Installing the Client 9 3 Setting up the Client sugo an Gages Rees 9 3 Verifying Server Networking 0 0 0c cece ee eee eee 9 4 Selecting the Type of Installation 9 5 Installing a Client to Run Locally 0 0 0 0 00 eee eee 9 6 Installing the Client on a Network Drive 004 9 8 Installing a Client Command Line Interface 9 9 Installing the Client Using Distribution Software 9 11 Verifying Installed Files 9 12 Troubleshooting the Client Installation 9 12 Maintaining the Client 9 13 Adding a Product 9 14 BMC Software Inc Confidential and Proprietary Information viii Administrative Products for DB2 Installation Guide Uninstalling a Client GUI LL 9 15 Uninstalling a Client Command Line Interface 9 16 Reinstalling a Product 9 17 S
38. 5 5 ALvrmcDS 5 5 ALvrmcDA Analysis plan 5 5 ALvrmcDE Environment plan 5 5 ALvrmcDF Front End plan 5 4 ALvrmcDI Import plan 5 5 ALvrmcDS Specification plan 5 5 AMS DOPT 5 12 7 19 ANP DOPT 5 12 7 19 AOPTS DOPT 6 11 ARCHPPREF DOPT 5 12 7 19 ARCHPS DOPT 5 12 7 19 ARCHSS DOPT 5 12 7 19 ARCHUNIT DOPT 5 12 7 19 ASUDOPT DOPT 5 13 7 19 ASUvrmDC DB2 Catalog Update plan 8 5 ASUvrmDD Object Definition plan 8 5 ASUvrmDJ BMCTRIG Utility Job Generation plan 8 5 ASUvrmDR Report Display plan 8 5 ASUvrmDS Statistics Collection plan 8 6 ASUvrmDX Cross Reference Utility Access plan 8 6 ASUvrmDZ Browse Statistics plan 8 6 ATTN DOPT 5 13 7 19 AUDIT DOPT 6 11 AUTHSW DOPT 5 13 7 19 AUXRELS DOPT 6 11 B backing up 2 6 BASDIAG DOPT 7 20 BASE DOPT 7 20 batch product authorization A 27 control statements and keywords A 29 return codes A 30 sample JCL A 28 BDSN DOPT 6 12 bind 2 24 binding packages and plans 4 17 BLDBS DOPT 5 13 7 20 BLDCU DOPT 5 14 7 20 BLRPPREF DOPT 7 20 BLRPPS DOPT 7 20 BLRPSS DOPT 7 20 BLRPUNIT DOPT 7 20 BMC Software Utilities ALTLIB command 4 4 interacting with ALTER 3 6 BMC Software Inc Confidential and Proprietary Information Index interacting with CATALOG MANAGER 3 7 interacting with CHANGE MANAGER 3 6 interacting with DASD MANAGER PLUS 3 9 8 7 BMCADMFI CLIST 4 21 BMCADMEF 2 CLIST 4 21 BMCAKMEG 4 27 BMCCHECK DOPT 5 14 7 21 BMCCOPY DOPT 5 14 7 21 BMCDB2 C
39. 7 Installing CHANGE MANAGER see the description for Chapter 6 In addition this chapter explains how to use the product s Compare component to perform a catalog to catalog comparison Chapter 8 Installing DASD MANAGER PLUS Chapter 9 Installing the Client for ALTER and CHANGE MANAGER see the description for Chapter 6 provides information about installing configuring and starting the client for ALTER and CHANGE MANAGER Appendix A BMC Software Product Authorization Appendix B BMC Software Product Authorization Messages describes the licensing of BMC Software products The Product Authorization utility from BMC Software enables online or batch authorization from the Install System tapes explains the product authorization messages that the Install System may generate Related Documentation BMC Software products are supported by several types of documentation e online and printed books e online Help e release notes and other notices In addition to this book and the online Help you can find useful information in the publications that are listed in the following table As Online and Printed Books explains these publications are available on request from BMC Software BMC Software Inc Confidential and Proprietary Information xvi Administrative Products for DB2 Installation Guide Category Product use Document Administrative Products fo
40. 9 Merging Data Sets from Multiple Tapes 1 9 Understanding Checkpoints LL 1 9 Installation Modes oroen ccce erupe cee eee eee nee 1 10 International Language Support LL 1 10 Installation Paths iis Lesa ia eae Ra ee 1 10 Determining Product Status 1 11 Determining Version Release and Maintenance Levels 1 12 Determining Installation Paths 0 0 0 0005 1 13 Pull Installation ech sna ie ia thane Ro eae ees 1 14 Maintenance Installation LL 1 14 SSID Installation LL 1 15 Multiple SSID Installation 1 17 Installation Data Sets 1 18 Installation User Profile ioner denea a 1 19 Searching for the Installation Profile 02 1 19 Reusing the User Profile L LL 1 19 Installation Default Options 1 20 Rules for Running Multiple Product Releases in a Single Subsystem 1 21 Product Naming Conventions LL 1 22 BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 1 Overview Overview This chapter describes the Administrative Products for DB2 distribution tapes and the installation requirements for the products on the tapes You install BMC Software products on MVS by using an Interactive System Productivity Facility ISPF application called the Install System This chapter provides an overview of the Install System and describes the types of installations that you can perform using t
41. A MU OPTS DOPRP ARU OPTS DOPUP ADU OPTS DOPVP AFR OPTS DPLAN The DB2 subsystem location name Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSDBAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Indicates if DB2 subsystem character strings can contain either a mixture of SBCS and DBCS data or SBCS data only Y SBCS and DBCS data N SBCS data only Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSDBRM DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies the name of the COPY PLUS product s DOPTs module that CATALOG MANAGER uses to interact with COPY PLUS This parameter is used only if COPY PLUS is installed Specifies the name of the BMC Software CHECK PLUS for DB2 product s DOPTs module that CATALOG MANAGER uses to interact with CHECK PLUS This parameter is used only if CHECK PLUS is installed Specifies the name of the BMC Software LOADPLUS for DB2 product s DOPTs module that CATALOG MANAGER uses to interact with LOADPLUS This parameter is used only if LOADPLUS is installed Specifies the name of the BMC Software REORG PLUS for DB2 product s DOPTs module that CATALOG MANAGER uses to interact with REORG PLUS This parameter is us
42. ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID For PATROL DB Alter ALU and PATROL DB Change Manager ACM rebind all PATROL DB Alter or PATROL DB Change Manager packages and plans for the previous version by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID As an alternative you can perform a Full installation of ALTER or CHANGE Provided that ALTER CHANGE MANAGER PATROL DB Alter or MANAGER 6 2E Then you will be operating in exploitation mode PATROL DB Change Manager still exists in toleration mode use the fallback procedures described for toleration mode and remove the product in exploitation mode Any data that you added while you were in exploitation mode will not be available in toleration mode using ALTER or 1 Migrate the DB2 catalog Rebind all ALTER ALU or CHANGE CHANGE f MANAGER ACM packages and plans MANAGER 6 1D or ec Bening all ALTER ALU or CHANGE for the previous version by using prdssidP later installed on MANAGER ACM packages and bind packages and prdssidB bind DB2 Version 5 plans by using prdssidP bind plans where prd is the product code and packages and prdssidB bind plans ssid is the subsystem ID where prd is the product code and ssid is the subsystem ID Then you will be operating in toleration mode
43. BDSN 6 12 BOPTS 6 12 CATOP 6 12 CHECKDE 6 12 CHECKS 6 12 CMAX 6 12 CMAXU 6 12 COLAUTH 6 12 COLDISS 6 13 COLDIST 6 12 COLSTAT 6 13 COLUMNS 6 13 COMD 6 13 CONSTDE 6 13 COPY 6 13 CRS 6 13 CUP 6 13 DATABAS 6 13 DATATYP 6 13 DB2CT 6 13 DB2LO 6 14 DBAUTH 6 14 DBCS 6 14 DBRM 6 14 DOPCP 6 14 DOPKP 6 14 DOPLP 6 14 DOPRP 6 14 DOPUP 6 14 DOPVP 6 14 DPLAN 6 14 DPT 6 15 DRO 6 15 EDSN 6 15 EPLAN 6 15 ESC 6 15 FIELDS 6 15 FOREIGN 6 15 GRPAT 6 15 HDAL 6 15 HDIX 6 15 HDPL 6 15 HDSY 6 15 HDTB 6 15 HDTS 6 15 HDVW 6 15 HPLAN 6 16 HRS 6 16 ICCOL 6 16 ICSYC 6 16 INDEXES 6 16 INDEXPA 6 16 INDEXST 6 16 IPNAMES 6 16 JDSN 6 16 KEYS 6 16 KPLAN 6 16 LDSN 6 17 LOBSTAT 6 17 LOCATIO 6 17 LPLAN 6 17 LULIST 6 17 LUMODES 6 17 LUNAMES 6 17 MAX 6 17 MODESEL 6 17 MPLAN 6 17 BMC Software Inc Confidential and Proprietary Information NOWRK 6 17 PACKAGE 6 18 PACKAUT 6 18 PACKDEP 6 18 PACKLIS 6 18 PACKSTM 6 18 PARMS 6 18 PDSN 6 18 PKSYSTE 6 18 PLAN 6 19 PLANAUT 6 19 PLANDEP 6 19 PLP 6 19 PLSYSTE 6 19 PROCEDU 6 19 RCCOL 6 19 RELS 6 19 RESAUTH 6 19 RMAX 6 19 RMAXU 6 19 ROUTINA 6 20 ROUTINE 6 20 SCHEMAA 6 20 SDSN 6 20 SSID 6 20 STMT 6 20 STOGROU 6 20 STRINGS 6 20 SYNONYM 6 20 SZDEV 6 20 TABAUTH 6 20 TABLEPA 6 21 TABLES 6 21 TABLESP 6 21 TABSTAT 6 21 TAPEI 6 21 TAPE2 6 21 TAPE3 6 21 TRIGGER 6 21 TRS 6 21 JADEV 6 21 JADPR 6 21 ADSE 6 21 ADSP 6 21 BSTP 6 22 CDSP 6 22 JCOMD 6 22 CSTP 6 22 4
44. BMC Software Inc Confidential and Proprietary Information CHANGE MANAGER 7 9 DASD MANAGER PLUS 8 5 naming conventions 3 23 platforms supported 9 2 PLIB data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 PLP DOPT 6 19 PLSYSTE DOPT 6 19 post installation tasks ALTER 4 3 ALTER GUI 4 22 CATALOG MANAGER 4 3 CHANGE MANAGER 4 3 CHANGE MANAGER GUI 4 22 DASD MANAGER PLUS 4 3 MVS Server 4 22 SQL Explorer 4 22 prdDOPDI installation default modules 3 16 prerequisites client installation 9 2 PROCEDU DOPT 6 19 product authorization ADD message A 14 ADD panel A 13 applying maintenance A 8 authorization tables A 3 batch method A 27 batch control statements A 29 batch return codes A 30 CPU failures A 6 CPU information A 10 CPU properties A 25 CPU upgrades A 6 DELETE message A 16 DELETE panel A 15 displaying current authorization A 24 displaying current processor A 26 licensing A 5 LINKLST library A 7 messages B 2 MODIFY message A 21 MODIFY panel A 20 obtaining passwords A 5 online method A 10 overview A 2 processing permanent passwords A 11 16 Administrative Products for DB2 Installation Guide processing temporary passwords A 23 REPLACE message A 18 REPLACE panel A 17 RESET message A 22 RESET password A 7 trials A 6 unlicensed processor A 5 updating authorization tables A 7 Product Authorization Display panel A 24 product authorization tables A 3 copying A 8 naming convention A 3 Product A
45. CHANGE MANAGER e for sites that use Single Point Entry for remote access to other non TSO ISPF environments the addition of the input variable BASE SSID to the BMCDB2PR panel for DB2 Version 4 and later for ALTER CHANGE MANAGER and DASD MANAGER PLUS e the ability to install the BMC Software UTILITY MANAGER for DB2 product from the Install System Product Selection panel e the ability to use the BMC Software COPY PLUS product to update the DASD MANAGER PLUS statistics tables e the ability to specify the name of the foreground started procedure by setting the FOREGROUND STARTEDPROC parameter in the INIFACV member in the HLO CNTL data set e the ability to limit each user to open only the spool output that is owned by the user by using the JSI SPOOLBYOWNER parameter in the INI ACV member in the HLQ CNTL data set e the removal of the prompt for the JES release number during the installation of the products e the addition of the BPOOLIX BPOOLTS JDSNBG and REBLD parameters to the default options module for ALTER and CHANGE MANAGER e the addition of the LOCATION parameter to the default options module for DASD MANAGER PLUS BMC Software Inc Confidential and Proprietary Information Summary of Changes xxiii e the modification of the RECVPREF and SYSCPREF parameters in the default options module for ALTER CHANGE MANAGER and DASD MANAGER PLUS e the modification of the IXTYPE parameter in the default options module for ALTER an
46. CPLDIAG DOPT 7 23 CPLWDSN DOPT 7 23 CPU failures product license A 6 information product license A 10 properties licensed processors A 25 upgrades A 6 CRS DOPT 6 13 CUP DOPT 6 13 Current Processor Information panel A 26 custom installation 1 10 D DASD MANAGER PLUS BMC Software Utilities interface 3 9 controlling access 8 5 default option descriptions 8 9 default option listing 8 7 DOPTs 8 7 Execution plans 8 6 installation considerations 8 3 installation defaults 8 3 interacting with BMC Software utilities 8 7 interacting with SQL Explorer 3 11 overview 8 2 plans 8 5 post installation tasks 4 3 product description 8 2 QMF report feature 8 4 space requirements 1 8 DASD MANAGER PLUS data sets CLIST 1 8 CNTL 1 8 DBRM 1 8 LOAD 1 8 Index 9 MLIB 1 8 MSGS 1 8 PLIB 1 8 QMFFORM 1 8 QMFPROC 1 8 QMFQRY 1 8 SLIB 1 8 TLIB 1 8 DASD MANAGER PLUS DOPTs BMC Software Inc Confidential and Proprietary Information 10 CATAUDIT 8 9 CATRECOV 8 10 CPLAN 8 10 DATE 8 10 DB2CAT 8 10 DLHQ 8 10 DPLAN 8 10 DPNAM 8 10 EAP 8 10 EIP 8 10 EPP 8 10 GDGDEF 8 10 GDGLIM 8 10 ISPTLIB 8 10 JC1 8 11 JC2 8 11 JC3 8 11 JC4 8 11 JCS 8 11 JCLCLEAN 8 10 JDSNE 8 11 JPLAN 8 11 LOCATION 8 11 OPNDB2ID 8 11 PRODUCT 8 11 RECVMAX 8 11 RECVMAXU 8 11 RECVPREF 8 11 RECVPS 8 12 RECVSS 8 12 RECVUNIT 8 12 RPLAN 8 12 SLI 8 12 SL2 8 12 SL3 8 12 SL4 8 12 SLS 8 12 SPLAN 8 12 SSID 8 12 Administrative Products for DB2
47. CPU configuration Note You do not need to apply passwords or update CPU authorization when you install product maintenance or version upgrades Passwords can be processed in either of the following ways e as part of an online procedure e ina batch interface that uses a job that is supplied on the product distribution tape This appendix describes the process that you use to apply passwords and to reconfigure your CPU either permanently or temporarily If you have additional authorization questions or concerns about the Product Authorization utility contact your BMC Software sales representative BMC Software Inc Confidential and Proprietary Information A 2 Administrative Products for DB2 Installation Guide Product Authorization Tables Product Authorization Tables When you apply passwords the BMC Software Product Authorization utility builds or updates product authorization tables The utility uses passwords to create entries in the tables that define the authorization for the product and to validate software licenses The types of product authorization tables are as follows e The Product Authorization utility builds or updates a permanent product authorization table when you install or apply a permanent password The permanent table controls which CPUs are licensed to run the product based on the serial number the model number and the submodel number of the unit e The Product Authorization utility builds or update
48. Creator Name can be any name Run all of the installation jobs prior to I65MIG I66MIG and 167COPY Do not run I65MIG I66MIG and I67COPY To Build Valid Data Migration Jobs Step 1 Perform Step 1 through Step 5 of the procedure Generating Installation JCL on page 2 22 to install ALTER and to build the valid I65MIG and I66MIG data migration jobs 1 A From the Install System Previous Release of product panel select the current installed release level for ALTER 1 B From the Install System ALTER Object Storage Verification panel perform the following actions 1 Type the Database Name and the Creator Name that you used in Step 1 during the CHANGE MANAGER installation 2 Type to Select to migrate data from ALTER v r BMC Software Inc Confidential and Proprietary Information 3 28 Administrative Products for DB2 Installation Guide Migrating Data From ALTER to CHANGE MANAGER 1 C From the Install System ALTER Migration Table Verification panel type the Creator Name for your existing ALTER tables Step 2 Run only the I65MIG and I66MIG installation jobs To Complete the Migration Run the 167COPY installation job that was created when you installed CHANGE MANAGER To Fall Back to ALTER Run the I98DROP and I99DLTE installation jobs that were created when you installed CHANGE MANAGER Warning Any data that you added while you had CHANGE MANAGER installed will be lost when you run the I98DROP and I9
49. ISPF interface considerations BMCDB2 CLIST 4 4 BMCDB2PR panel 4 4 catalog indirection 4 8 ISPF profile 1 19 ISPPROF 1 19 ISPSLIB DOPT 5 17 7 25 ISPTLIB DOPT 8 10 IVP 4 20 4 45 IXTYPE DOPT 5 17 7 25 J JC1 DOPT 5 17 7 25 8 11 JC2 DOPT 5 17 7 25 8 11 JC3 DOPT 5 17 7 25 8 11 JC4 DOPT 5 17 7 25 8 11 JC5 DOPT 5 17 7 25 8 11 JCL for batch product authorization A 28 generating JCL for generation data groups GDGs 4 16 BMC Software Inc Confidential and Proprietary Information generating JCL for JES3 environment 4 15 generating JCL region statements 4 14 generating product JCL 4 14 JCLCLEAN DOPT 5 18 7 25 8 10 JDSN DOPT 5 18 6 16 7 25 JDSNB DOPT 7 25 JDSNBG DOPT 5 18 7 26 JDSNBR DOPT 7 26 JDSNC DOPT 7 26 JDSNCPL DOPT 7 26 JDSNE DOPT 5 18 7 26 8 11 JDSNI DOPT 7 26 JES3 environment generating JCL 4 15 JPLAN DOPT 8 11 JSI JES Interface installing 5 7 7 13 K KEYS DOPT 6 16 keywords batch product authorization A 29 KPLAN DOPT 6 16 L LDSN DOPT 6 17 licensing products A 5 LIST function batch authorization A 29 LNKLST library product authorization A 7 LOAD data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 LOBSTAT DOPTS 6 17 LOCATIO DOPT 6 17 LOCATION DOPT 5 18 7 26 8 11 LOCK DOPT 5 18 7 26 LOG DOPT 5 18 7 26 LPLAN DOPT 6 17 LULIST DOPT 6 17 LUMODES DOPT 6 17 LUNAMES DOPT 6 17 Main Menu options 2 14 14 Administrative Products
50. Install System offers two installation modes for most products e Quick installation limits the number of panels that are shown for most products to the common installation panels and the synonym and default processing options DOPTs panels These panels use the default values that BMC Software provides The Quick option does not allow you to migrate from an earlier version of a product e Custom installation displays all of the option panels for each product in addition to the common installation panels This option allows you the most flexibility in setting up the components of the products from file and database names to file sizes and product execution parameters Note The Quick option is not available for all products Refer to the appropriate product chapter for information about the installation options that are available for a specific product International Language Support The Install System automatically invokes international language support if the terminal type is 32xxKN The terminal type is set from the ISPF main menu For this terminal type the Install System also displays the installation panels in uppercase letters Installation Paths The installation path that you select depends on whether you are installing a product for the first time or a new version of an existing product To help you choose an installation path for each product that you plan to install review the information in the following sections BMC
51. JSIDLL 000007 MSGKSDS DD 000008 BMCIPROF DD 000009 JZSJES DD 000010 SYSTCPD DD 000011 SBISCRC DD 000012 SYSUDUMP DD 000013 SYSPRINT DD 000014 STDOUT DD 000015 SYSTERM DD 000016 STDERR DD 000017 SYSOUT DD 000018 DISP SHR DSN BMCADMN V621 D62 LOAD DISP SHR DSN SYS2 DB2V61M DSNLOAD DISP SHR DSN BMCADMN V621 D62 LOAD DISP SHR DSN BMCADMN V621 D62 ACVMSGS DISP SHR DSN BMCADMN V621 D62 CNTL INI ACV SYSOUT Q INTRDR INTERNAL READER DISP SHR DSN TCPIP TCPIP DATA DUMMY SYSOUT amp OUT SYSOUT amp OUT DEBUG MSGS SYSOUT amp OUT DEBUG MSGS SYSOUT amp OUT ERROR MSGS SYSOUT amp OUT ERROR MSGS SYSOUT amp OUT ERROR MSGS PE AE ACHE RK kK Kk kK kk KK kK RK AA KKK BOTTOM OF DATA FARA A AAA AAA kkk kkk kkk kkk kkk kk 3 A 3 B 3 C In the steplib of the PATROLDB started task specify the load libraries that you referenced in the INIHACV file Note The steplib must point to only APF authorized loadlibs Copy PATROLDB into a system proclib data set where it can be started as a started task For more information refer to the IBM 05 390 eNetwork Communications Server IP Planning and Migration Guide Define the proclib name to RACF as a started task BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Configuring TCP IP 3 D Start the PATROLDB member to activate the MVS Server For a list of available MVS console
52. MSAUL100 in Figure 4 21 on page 4 37 Type the network name This network is the same network as the VTAM where the LU Alias resides Deselect the Enable Automatic Partnering option Select the Member of Default Outgoing Local APPC LU Pool option Step 3 Define a remote APPC LU to the SNA Gateway Server by performing the following actions at the SNA Gateway Server console 3 A 3 B 3 C 3 D In the Servers and Connections window select the connection From the Edit menu choose Insert Select APPC REMOTE Specify the following APPC REMOTE properties 1 Type the LU Alias and LU Name These properties are the same as those in the MVS Server ACVLUO1 in Figure 4 21 on page 4 37 Type the network name This property is the name of the VTAM where the MVS Server resides Select the Supports Parallel Sessions option Deselect the Enable Automatic Partnering option BMC Software Inc Confidential and Proprietary Information 4 38 Administrative Products for DB2 Installation Guide Setting Up the SNA Gateway Server 3 E To partner the local and remote LU select Partners from the APPC REMOTE properties 1 Select Modes and create a logon mode with the same name and characteristics as those used by the Database Administration MVS Server which is APPCPCLM in the previous example Use the same RU size as the one that was defined for the mainframe logon mode Note To allow subtasking or foreground pr
53. Processor Information Summary Use the Current Processor Information panel to display information about the processor that you are currently using Step 1 On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 3 Step 2 Press Enter to display the Current Processor Information panel Figure A 13 Step3 When you finish reviewing the panel press F3 to exit the Product Authorization utility and return to the previous menu or panel See Additional Information on page A 27 for more an explanation of the information that is displayed on this panel Figure A 13 Current Processor Information Panel SECEPCPU SECEPCPU Current Processor Information Command gt For the MVS system on which this application is currently executing Serial number Model number Version code 06 Number of available processors Press Enter to continue Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel BMC Software Inc Confidential and Proprietary Information A 26 Administrative Products for DB2 Installation Guide Batch Product Authorization Additional Information This panel displays the CPU serial and model numbers for the processor on which TSO is currently running It also displays the version code of the processor The version code is the hardware representation of the submodel for example the 942 in ES 9000 942 or the 600 for a 3090 600 processor If you experience problems
54. SYS1 DSNEXIT The optional first STEPLIB library for DB2 load modules This library is concatenated to the library that keyword SL1 specifies BMC Software Inc Confidential and Proprietary Information 7 28 Administrative Products for DB2 Installation Guide Default Option Descriptions SL3 SYS1 DSNLOAD The optional second STEPLIB library for DB2 load modules This library is concatenated to the library that keywords SL1 and SL2 specify SL4 SYSLOTHER LOADLIB1 Optional additional STEPLIB libraries SL5 SYS1 OTHER LOADLIB2 SPP CMvrmcDS SSID DB2 STATS S STOPCOMM N STORCLAS N SWPS 10 SWSS 2 SWU SYSDA SYNCPNT parm Optional additional STEPLIB libraries Defines the Specification plan name Identifies the DB2 subsystem ID SSID The SSID must match the SSID command in the worklist This parameter is required Indicates what type of statistics should be generated DB2 Version 5 1 or later The DOPTs parameters are defined as follows S Standalone The worklist generates either a BMCS or RNST command in the worklist U Utility The worklist combines statistics with a utility Reorg Copy Load whenever possible X No statistics are generated For DB2 Version 5 1 and later indicates whether an AT COMMIT generates in a worklist when a STOP is created Indicates whether support for the STORCLAS parameter is required for VCAT defined DB2 objects Y or N Defines
55. Software Inc Confidential and Proprietary Information 1 10 Administrative Products for DB2 Installation Guide Installation Paths Determining Product Status To determine the status of each product that you plan to install review the requirements that are described in the product specific chapters of this book and answer the following questions e Are you installing the product for the first time e Are you installing a new version release or maintenance level for a product that is currently installed on your system e Are you planning to run this product version concurrently with previous versions or releases For products with DB2 specific requirements answer the following questions e Are you planning to use existing BMC Software product tables created during a previous installation e Are you propagating the product across multiple DB2 subsystems e Are you planning to share product libraries between DB2 subsystems e Are you planning to install the DB2 products in a data sharing environment Sysplex Consider a data sharing environment as one DB2 subsystem since only one catalog exists Note To enable access to all of the data sharing members you must edit the BMCDB2 CLIST Refer to Performing the Post Installation Tasks for Administrative Products on page 4 3 After you determine the product status new or existing use Table 1 10 on page 13 to help you select an installation path BMC Software In
56. The DATA PACKER for DB2 plan If installed CATALOG MANAGER can use the AMEND and TRIAL command features The load module name for the BMC Software DATA PACKER product Defines the Execution Authorization plan name which determines if a user is authorized to run Execution Defines the Installation plan Defines the Execution primary plan name Indicates whether JCLGEN creates the base of the Generation Data Group GDG data set Y or N Specifies the number of GDG data sets that are allowed GDGLIM contains the value of the LIMIT parm Valid values are from 0 through 255 If GDGLIM is set to 0 then GDGDEF N The fully qualified data set name for the ISPF TLIB This value is used during batch JCL generation Enables you to generate a job step that automatically deletes many of the permanent also known as non temporary data sets that the Execution component creates These data sets are created during worklist processing and have a disposition NEW CATLG CATLG The automatic delete step is only performed if the condition code that any previous job step returns is four or less Y or N BMC Software Inc Confidential and Proprietary Information 8 10 Administrative Products for DB2 Installation Guide Default Option Descriptions JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 JC3 NOTIFY amp amp USERID JC4 JC5 The defa
57. The prefix that is used with the last qualifier of SYSCOnnn data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied The primary space allocation in cylinders for SYSCOnnn data sets The secondary space allocation in cylinders for SYSRCOnnn data sets The default UNIT for creating SYSCOnnn data sets The SYSREC threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSREC secondary or alternate unit that is used for any overflow SYSRPREF amp amp PREFIX amp amp WKID SYSRPS 10 SYSRSS 2 SYSRUNIT SYSDA SYSTYPE S SZDEVT 3380 The prefix that is used with the last qualifier of SYSREnnn data sets The primary space allocation in cylinders for SYSREnnn data sets The secondary space allocation in cylinders for SYSREnnn data sets The default UNIT for creating SYSREnnn data sets Indicates if DB2 Subsystem character strings can contain a mixture of SBCS and DBCS data M mixed S single byte only The device type for data set sizing for JCLGEN Valid values are 3380 and 3390 TAPE1 CART TAPE2 TAPE TAPE3 TAPE Defines the valid installation tape unit names for your site BMC Software Inc Con
58. User Response Specify the OLDCPUID keyword on your input control statement See Control Statements and Keywords on page A 29 for assistance with syntax BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 9 Error Messages BMC89062E BMC89063E BMC89064W BMC890651 BMC89069E PASSWORD TO UPDATE AN EXISTING CPU ID ENTRY REQUIRES OLDCPUID KEYWORD Explanation The Update password being processed requires specification of the OLDCPUID keyword and none was specified System Action The password is not processed User Response Specify the OLDCPUID keyword on your input control statement See Control Statements and Keywords on page A 29 for assistance with syntax THIS PASSWORD REQUIRES NEWCPUID AND OLDCPUID KEYWORDS Explanation The Replace password being processed requires specification of the NEWCPUID and OLDCPUID keywords and neither was specified System Action The password is not processed User Response Specify the NEWCPUID and OLDCPUID keywords on your input control statement See Control Statements and Keywords on page A 29 for assistance with syntax ERRORS CAUSED TERMINATION SOME OR ALL REQUESTS DID NOT COMPLETE SUCCESSFULLY Explanation The input data contains one or more errors System Action Processing terminates at the point of the error User Response Examine the input control statements for err
59. action is required When time is available more investigation is needed All messages with a severity code E are sent to the system console Some messages with a severity code A or are also sent to the system console Message Explanations The following error messages can be issued by the Product Authorization utility BMC89000A PRODUCT LOAD LIBRARY IS A REQUIRED FIELD Explanation The product load library must be specified System Action The action fails User Response Enter the data set name for the product load library and retry the action BMC89001A PASSWORD IS A REQUIRED FIELD Explanation The action that you requested requires a password to be specified System Action The action fails User Response Enter the password and retry the action If you do not have a password contact your BMC Software sales representative to acquire one BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 3 Error Messages B 4 BMC89002E BMC89003A BMC89004E BMC89005E BMC89006A PASSWORD MAY NOT CONTAIN BLANK CHARACTERS Explanation A blank is not a valid password character Valid characters are A to Z excluding J and O 0 to 9 and Note Some nondomestic keyboards do not have the at sign For this reason the asterisk has been designated as a synonym for These two characters and can be used interchange
60. amp amp F C amp amp PREF I amp amp PREF B amp amp PREF BR amp amp P SYSOUT E SYSOUT IAG SYSOUT IAG SYSOUT IAG SYSOUT DIAG SYSOUT REFIX BASE IX COM IX IM IX BASEL INI INI EFIX ANALYSIS amp amp WO amp amp PREFIX EXEC amp amp WORKI PREFIX JCLGEN amp amp WO PARE CMPJCL PORT amp amp WOR E amp amp WORKID E BL REID VII Dit RKID pore te RID FP RPTJCL r DSN amp amp PR IAG SYSOUT DIT N R COV N R W bic UNIT SYSDA PS 1 0 SS 2 MAX MAXU UNIT SYSDA PS 10 SS 2 MAX MAXU LRP LRP LRP ECV UNIT SYSDA PS 10 SS 2 ECV ECV ECV RCH RCH RCH ee GI Q lt UNIT SYSDA PS 10 SS 2 MAX MAXU UNIT SYSDA PS 10 REF amp amp PREFIX PREF amp amp PREFIX PREF amp amp PREFIX PREF amp amp PREFIX PREF amp amp USERID amp amp SSID amp amp SSID amp amp SSID amp amp SSID Use SSID Administrative Products for DB2 Installation Guide PL amp amp PREFIX TASKID amp amp TASKID 7 EFIX amp amp SSID amp amp TASKID amp amp WORKID8 amp amp OBNOD amp amp WORKID8 amp amp OBNOD FF F FF F FF FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F KF F BM
61. amp amp PGMR wrong JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR correct Considerations for SAS C For those products that require SAS C transient libraries the Install System optionally unloads version 6 5 of the SAS C transient library during the unload process If you choose not to unload the SAS C library you must ensure that the SASIC transient library version 6 5 or later exists in the link list BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 17 Running the Install System If you choose to unload the SAS C transient library the Install System unloads a copy of the library into one or both of the following locations e the load library that is designated for your BMC Software products e anew or existing file to be concatenated in your JCL as a STEPLIB EDM products only BMC Software Inc Confidential and Proprietary Information 2 18 Administrative Products for DB2 Installation Guide Specifying User Options Specifying User Options Summary The Install System lets you specify user options for each installation session The options that you specify determine how the Install System runs and where it stores the installation JCL The options remain in effect until you change them Before You Begin Before you specify the user options you must complete the following tasks e Unload the Install System as instructed
62. amp amp TSNAM Gl user options amp PREFIX amp SSID amp DBNAME amp TSNAME Example 2 DOPTs amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR user options amp USERID amp JOBCHAR JOB ACCT amp PGMR BMC Software Inc Confidential and Proprietary Information 2 16 Administrative Products for DB2 Installation Guide Running the Install System Common Assembly Errors for DOPTs All DOPTs assembly jobs should be completed with a successful return code of zero If you get assembly errors compare your DOPTs listing with one that the installation process generated Some common errors are as follows e missing comma delimiter after keyword value For each keyword value except the last a comma delimiter is needed For example SSID DB2P R wrong SSID DB2P R correct e missing continuation character in column 72 For each keyword value except the last a character such as an asterisk is required in column 72 e incorrect symbolic variable substitution The macro tries to resolve all symbolic variables Double the ampersand amp on all symbolic variables For example JCLDSN amp PREFIX amp SSID amp DBNAME amp TSNAME wrong JCLDSN amp amp PREFIX amp amp SSID amp amp DBNAME amp amp TSNAME correct e missing or unbalanced single quotation marks For example JC1 amp amp USERID amp amp JOBCHAR JOB ACCT
63. are authorized to Administration which issues a product run a licensed product password after processing the license agreement You stop using an permanent removes a designated CPU from BMC Software sales authorized CPU the list of CPUs that are representative or Contracts authorized to run a licensed Administration product You upgrade to a new permanent authorizes the transfer of a BMC Software sales CPU license from one CPU to another representative or Contracts Administration You want to run the permanent adds a designated CPU to the list BMC Software Contracts product on an of CPUs that are authorized to Administration which issues a additional CPU run a licensed product password after processing the license agreement The authorized CPU is temporary temporarily bypasses BMC Software sales not available because authorization checking and representative Contracts of an emergency allows you to run the product on Administration or Product such as hardware any CPU for a limited time Support failure The grace period has permanent resets the grace period BMC Software sales been triggered and needs to be reset representative or Contracts Administration BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 9 Online Product Authorization CPU Information When you request a permanent product license from BMC Software you must furnis
64. authorizations e executes BMC Software and DB2 utilities e builds and issues DB2 commands e logs user actions for an audit trail e converts DBRM plans to use packages e converts packages back to DBRM plans e lists EXPLAIN command information for SQL tuning e searches local and remote DB2 subsystem catalogs by using specific search criteria to limit the retrieved object list You do not need a thorough knowledge of DB2 structures or SQL syntax because CATALOG MANAGER constructs the necessary SQL statements from your input and selections and also maintains the database structures You choose when and how to execute the SQL statements You can also store frequently used SQL statements for future use For information about CATALOG MANAGER read the CATALOG MANAGER for DB2 User Guide You can install the UTILITY MANAGER product when you install CATALOG MANAGER For information about configuring UTILITY MANAGER refer to the UTILITY MANAGER for DB2 Getting Started manual BMC Software Inc Confidential and Proprietary Information 6 2 Administrative Products for DB2 Installation Guide Installation Considerations Installation Considerations When you use the Install System to install the Administrative Products the installation process generates a customized installation data set This data set contains customized jobs that are created to install these products into your specific DB2 environment One of these jobs establishes the de
65. authorizations and supports a large number of data type conversions BMC Software Inc Confidential and Proprietary Information 7 2 Administrative Products for DB2 Installation Guide Overview CHANGE MANAGER is able to use the BMC Software LOADPLUS UNLOAD PLUS CHECK PLUS REORG PLUS RECOVER PLUS and COPY PLUS utilities to speed up the execution of structure changes and migrations Refer to Installation Considerations on page 7 5 for specific considerations and requirements for this product For information about CHANGE MANAGER read the ALTER and CHANGE MANAGER for DB2 User Guide CM PILOT Component Predefined Scripts The CM PILOT CM P component of CHANGE MANAGER allows you to automate DB2 change management tasks that are normally performed through the CHANGE MANAGER Front End With CMP you do not need to decide which CHANGE MANAGER Front End panels are required for your task and in what sequence you need to complete them CM PILOT guides you with its ISPF dialog The CM PILOT dialog is based on predefined steps called Scripts Each Script contains ordered steps that prompt you for only the information that is required to perform the change management task You also have the capability to modify various settings in each Script CM PILOT contains the following scripts e change data structures using a Compare trigger e change data structures using a DML trigger e migrate data structures using a DML trigger
66. bind packages and ACT ssidB bind plans where ssid is the subsystem ID Then you will be operating in toleration mode Rebind all CATALOG MANAGER packages and plans by using ACT ssidP bind packages and ACT ssidB bind plans where ssid is the subsystem ID using CATALOG MANAGER 6 1 or later 1 Migrate the DB2 catalog 2 Run HLQ CNTL UPGRD5 6 Then you will be operating in exploitation mode Rebind all CATALOG MANAGER packages and plans by using ACT ssidP bind packages and ACT ssidB bind plans where ssid is the subsystem ID using DASD MANAGER PLUS at a version earlier than 5 4 04 Migrate the DB2 catalog and perform a Full installation of DASD MANAGER PLUS 6 1 Then you will be operating in exploitation mode 1 Provided that the previous version of DASD MANAGER PLUS still exists remove the product in toleration mode 2 Rebind all DASD MANAGER PLUS packages and plans for the previous version by using ASUssidP bind packages and ASUssidB bind plans where ssid is the subsystem ID Any data that you added while you were in exploitation mode will not be available 3 32 Administrative Products for DB2 Installation Guide BMC Software Inc Confidential and Proprietary Information Table 3 15 If You Are using DASD MANAGER PLUS 5 4 04 using DASD MANAGER PLUS 6 1 using catalog indirection and ALTER CHANGE MANAGER PATROL DB Alter or PATROL DB Chan
67. cases installation of the Acrobat Reader and downloading the online books is an optional part of the product installation process For information about downloading the free reader from the Web go to the Adobe Systems site at http www adobe com To view any online book that BMC Software offers visit the support page of the BMC Software Web site at http www bmc com support html Log on and select a product to access the related documentation To log on first time users can request a user name and password by registering at the support page or by contacting a BMC Software sales representative BMC Software Inc Confidential and Proprietary Information About This Book xvii To Request Additional Printed Books BMC Software provides printed books with your product order To request additional books go to http www bmc com support html Online Help The Product Name include online Help In the Product Name ISPF interface you can access Help by pressing F1 from any ISPF panel Note The messages that Product Name generate are available in an MVS data set that is downloaded during installation For each message the data set includes an explanation and suggests a user response The MVS data set is called HLO MSGS where HLQ is the high level qualifier that is specified during installation The BMCMSG CLIST can be used to view the messages Release Notes and Other Notices Printed release notes accompany each BMC Software pro
68. code to the ALTER components Pre Image Copy Indicates whether an image copy should be taken of each table space before a database is dropped a table is dropped or the table space is dropped or reorganized Y or N BMC Software Inc Confidential and Proprietary Information 5 18 Administrative Products for DB2 Installation Guide Default Option Descriptions PRODUCT PRODUCT NAME REBLD I RECOV I RECVMAX RECVMAXU Defines the product name For example PRODUCT ALTER For DB2 Version 6 and later specifies whether to use the rebuild utility from IBM or BMC Software or no rebuild utility If REBLD N eligible indexes will not be created with DEFER YES If a non unique index is being dropped or created in a worklist and its parent table is not being dropped or created in the worklist then the index will be created with DEFER YES if REBLD I or REBLD B The DOPTs parameters are defined as follows B BMCRECOVER I IBMREBUILD N NO REBUILD For DB2 Version 5 and earlier specifies whether to use the recover utility from IBM or BMC Software or no recover utility If RECOVEN eligible indexes will not be created with DEFER YES If a non unique index is being dropped or created in a worklist and its parent table is not being dropped or created in the worklist then the index will be created with DEFER YES if RECOV I or RECOV B The DOPTs parameters are defined as follows B BMCRECOVER I IBMRECOVER N NO RECOVER T
69. coded on the correct macro listing keyword in the DOPTs assembly member 2 Verify that the DOPTs assembly completed successfully with a return code of 0 3 Verify that the assembled DOPTs member is the same DOPTs member that the Administrative Products use To verify type ENVI on the command line within the product Compare the listed DOPTs module name with the name of the DOPTs module that you assembled and link edited 4 Verify that the DOPTs module assembly is updating the correct load library The SYSLMOD ddname statement should reference the load library where the Administrative Products reside BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 13 Refreshing Default Options Unlike the other DOPTs parameters the plan names are used directly by the product If you must specify different plan name values for each subsystem you need multiple DOPTs modules For additional information about setting the products options see the chapters that address specific products Setting User Options Using DOPTs The purpose of the DOPTs module is to establish installation wide default values You can change many of these values on an individual basis using each product s user options Unlike DOPTs user options are saved and maintained in a user s ISPF profile data set under the name xxxxPROF where xxxx is the ISPF application ID under which the product is runni
70. copy operations Do not include copy operations but do start objects in copy pending status with ACCESS FORCE 7x ZK Indicates whether to use the BMC Software LOADPLUS utility for loads in place of the IBM LOAD utility Y or N Indicates whether to use the BMC Software BMCSTATS utility for updating statistics in the DB2 catalog in place of the IBM RUNSTATS utility DB2 Version 4 1 or earlier The DOPTs parameters are defined as follows Y Use BMCSTATS N Use RUNSTATS X Do not generate statistics Specifies whether to use the BMC Software UNLOAD PLUS utility in place of ALTER UNLOAD Y or N Indicates the size of the buffer pool for user indexes Valid values include BPO through BP49 Indicates the size of the buffer pool for user data Valid values include e BPO through BP49 e BP8KO through BP8K9 e BPIGKO through BP16K9 e BP32K BP32KI through BP32K9 The default name for the Baseline Report diagnostic output data set BRPTDSN amp amp PREFIX BASELINE REPORT CATAUDIT N The default name for the Baseline Report data set name The DDL audit logging indicator If you have CATALOG MANAGER installed an entry of Y causes Execution to log executed DDL statements in the CATALOG MANAGER DDL Audit Log Y or N BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 21 Default Option Descriptions CATRECOV N CCSID E The Drop Recovery indicator This parameter
71. currently in use The Install System creates a new set of BMC Software product libraries to support the new release e Do not copy the load modules to the APF library that is currently in use e Use the Custom installation mode e Use a DB2 synonym qualifier for the product that is different from the qualifier currently in use e Use naming conventions that are different from the conventions currently in use for plans and collection IDs e Ifyou do not want to share the existing DB2 objects with the new release of the products use DBNAME and CREATOR names that are different from other BMC Software objects The Install System generates a new ISPF interface to access the newly installed set of products You must continue to use the old ISPF interface to access the older set of products BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 21 Product Naming Conventions Product Naming Conventions 1 22 The Administrative Products use a new set of DB2 structures for each new release Most of the BMC Software Utility products and Backup and Recovery products use the same set of DB2 structures from one release to the next You are prompted during the installation for the names of the existing DB2 structures When you install new releases over existing releases a consistent naming convention is important Some sites use their own naming conventions during the installation Because th
72. data rows Figure 4 6 CATALOG MANAGER CONNECT Command Servers PROD SSID S SERVER NAME SSID COLL_ID NICKNAME l ACT AAAA S BBBB BBBB BBB_COLCT AAAABBBB i ACT AAAA S CCCC CCCC CCCC_COLCT AAAACCCC BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 7 Enabling the Product CLISTs e Ifyou used the Multiple subsystem ID SSID installation path the CATALOG MANAGER server entries that were added by the Multiple SSID installation will be commented out in the BMCDB2 CLIST as shown in Figure 4 7 Follow the instructions in the comments to enable the servers to be listed on the CONNECT command panel Figure 4 7 BMCDB2 CLIST for Multiple SSID Installation Ke SSS o RI SRE IO Rg IR IES OIE RR ORES IR ERS SKS ORE PRR GROLIER Fg RR IE n INSERTED FROM MSSID INSTALL TO USE UALLY UPDATE SERVER DATA ROWS BELOW AND UNCOMMENT BY REMOVING COLUMN ONE ASTERISKS PROD SSI ER NAME SSID COLL_ID NICKNAME i ACT S DBBA LCTvrm_D_MAIN DBBFDBBA y ACT S DBDB LCTvrm_D_MAIN DBBFDBDB ui ACT S DBDA LCTvrm_D_MAIN DBBFDBDA a ACT S DBBA LCTvrm_D_MAIN DBBFDBBA i ACT S DBDB LCTvrm_D_MAIN DBBFDBDB ta ACT S DBDA LCTvrm_D_MAIN DBBFDBDA n Note Before you remove the comment you will need to update the values for the Server Name Server SSID and the Server Nickname For additional examples refer
73. delete the utility ID manually in the BMCUTIL and BMCSYNC tables before starting over ALTER and CHANGE MANAGER use the following synonyms e BMC_UTILITY for the BMCUTIL table e BMC_UTIL_SYNC and BMC_UTIL_SYNC2 for the BMCSYNC table BMC Software Inc Confidential and Proprietary Information 3 6 Administrative Products for DB2 Installation Guide Interacting with Other BMC Software Products Update your product s synonyms if e your current synonyms do not point to the correct tables e ALTER or CHANGE MANAGER accesses the utility tables during batch processing To update the synonyms complete the following steps 1 Drop the current utility synonyms for ALTER or CHANGE MANAGER 2 Create the new ALTER or CHANGE MANAGER utility synonyms by using the same synonym names but with the correct table names 3 Bind the package AEXEUTID into the main collection ID for ALTER or CHANGE MANAGER The HLQ INSTALL member DCI AEXU provides an example of a worklist If the utilities are installed in a different load library complete the following steps 1 Find the member in the HLQ CNTL library that has the same name as the DOPTs module 2 Update the first available steplib option SL1 SL2 and so on in the ALTER or CHANGE MANAGER DOPTs member to use the different utilities load library For a description of the steplib options see the following chapters e Chapter 5 Installing ALTER e Chapter 7 Installing CHANGE M
74. dialog panels Commands are entered on the ISPF command line e HELP or F1 displays the Help panel for the current dialog panel END or F3 saves changes and returns to the Install System Main Menu e CKPANELS or F4 displays the percentage of the installation that is complete and the number of panels that remain BMC Software Inc Confidential and Proprietary Information 2 14 Administrative Products for DB2 Installation Guide Running the Install System e CANCEL or F12 saves any changes and returns to the previous panel e Enter accepts the defaults or changes and continues to the next panel Note The F4 key is assigned to the percentage complete function only if you have installed using version 1 5 30 or later of the Install System and you are using a new profile ID The following function keys are available to help you move through the Install System Help panels e 3 exits the Help panel and returns to the current dialog panel e F10 or F12 returns to the previous page of a multiple page help panel e Enter or F11 continues to the next page of a multiple page help panel Data Set Names The Install System uses ISPF conventions when processing data set names When you specify a data set name the Install System determines whether the TSO E PROFILE NOPREFIX option is in use If it is in use the Install System does not append a prefix to the data set name The maximum length for data set names is 44 characters including the
75. do not have MVS ESA and TSO E 2 1 or later follow the directions in BMCDB2CI for updating the BMCDB2 CLIST If you install CATALOG MANAGER follow the instructions for modification of the CATALOG MANAGER plan name Because the BMCDB2 CLIST uses the ISPF LIBDEF facility to allocate all necessary ISPF data sets you may not need to modify your TSO logon procedure Step 3 Enable BMCDB2 CLIST to use different libraries for an SSID If your installation has more than one version of DB2 the Administrative Products must have separate libraries for each version Use the following scenarios as examples for editing the BMCDB2 CLIST e In this scenario CHANGE MANAGER is installed on SSID DB31 The product libraries have a high level qualifier of BMC DB31 During the installation JCL and the BMCDB2 CLIST are generated into BMCDB2 CLIST Figure 4 9 Adding CHANGE MANAGER to Subsystem DB31 DATA PROD SSID D I DOPT PLAN APPL COLL_ID I NICKNAME ACM DB31 D ACMDOPD1 CMvrmBDF ACMA LIB SSID Data Set Name bi EXIT DB31 SYS3 DBAP DSNEXIT LOAD DB31 SYS2 DB2V31M DSNLOAD BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks BMC DB31 JCL The table in Figure 4 9 is added to the bottom of the 4 9 Enabling the Product CLISTs e In this scenario CHANGE MANAGER is installed on SSID DB41 The product libraries have a hig
76. end of the book Chapter Appendix Number and Title Description Chapter 1 Preparing for Installation describes the Administrative Products distribution tapes and the installation requirements for the products on the tapes This chapter also describes the Install System Chapter 2 Using the Install System explains how to unload the Install System e start and run the Install System handle special case installations BMC Software Inc Confidential and Proprietary Information About This Book XV Chapter Appendix Number and Title Chapter 3 Performing Additional Installation Tasks Chapter 4 Performing Post Installation Tasks Description discusses how to migrate to a new version of DB2 upgrade from ALTER to CHANGE MANAGER use catalog indirection with the BMC Software Administrative Products explains what you should do after installing particular BMC Software products Chapter 5 Installing ALTER Chapter 6 Installing CATALOG MANAGER explains the prerequisites and installation considerations that you should review before you install this product The chapter describes each default option and shows a sample listing for the default option module In addition this chapter discusses upgrading from ALTER to CHANGE MANAGER explains the prerequisites and installation considerations that you should review before you install this product Chapter
77. for DB2 Installation Guide Administrative Products Tapes TIS Tape The TIS tape supports DB2 Version 6 1 The TIS tape contains the following products e ALTER for DB2 e CATALOG MANAGER for DB2 e CHANGE MANAGER for DB2 e DASD MANAGER PLUS for DB2 e UTILITY MANAGER for DB2 SAT Tape The SAT tape supports DB2 Versions 4 1 and 5 1 The SAT tape contains the following products e ALTER for DB2 e CATALOG MANAGER for DB2 e CHANGE MANAGER for DB2 e DASD MANAGER PLUS for DB2 e UTILITY MANAGER for DB2 Installation Requirements The requirements for using the tape set for the BMC Software Administrative Products are as follows e IBM DATABASE 2 version 4 1 or later e TSO E version 1 4 or later e ISPF PDF version 3 1 or later e DB2 authorization of SYSADM to execute the generated jobs e product LOAD libraries must be APF authorized e CATALOG MANAGER at least 4 MB for each user who signs on e DASD MANAGER PLUS IBM GDDM with the Presentation Graphics Feature PGF to use the DASD MANAGER PLUS graphics option e client for ALTER and CHANGE MANAGER IBM TCP IP for OS 390 version 3 1 or later if TCP IP is used BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 3 Estimated Space Requirements e client for ALTER and CHANGE MANAGER IBM APPC MVS for MVS version 4 3 or later if APPC SNA is used e IEBCOPY job to copy all load modules to a single APF library optional
78. for DB2 Installation Guide maintaining clients 9 13 Maintenance installation initial 1 15 overview 1 14 subsequent 1 15 maintenance level determining 1 12 maintenance installing product authorization A 8 marketing solution 1 2 MAX DOPT 6 17 MERGE function considerations 2 7 Install System 2 7 merging tapes 1 9 messages ADD authorization A 14 DELETE authorization A 16 error messages and explanations B 3 errors copying authorization tables A 8 format B 2 help 4 13 MODIFY authorization A 21 online MVS data set xviii product authorization B 2 REPLACE authorization A 18 RESET authorization A 22 severity codes B 3 temporary password A 23 MGMTCLAS DOPT 5 18 7 27 Microsoft SMS product installing the client 9 11 migrating DB2 Version 4 to Version 5 3 35 DB2 Version 5 to Version 6 3 30 MLIB data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 MODESEL DOPT 6 17 MODIFY Authorization for an Existing Processor panel A 20 MODIFY authorization message A 21 MPLAN DOPT 6 17 MSGS data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 BMC Software Inc Confidential and Proprietary Information DASD MANAGER PLUS 1 8 MSGTEXT data set ALTER 1 5 CHANGE MANAGER 1 7 multiple options module 3 17 Multiple SSID installation considerations 1 17 description and use 1 17 name propagation 1 18 selecting option from dialog 1 17 MVS commands 4 28 MVS Server configuring APPC SNA 4 27 configuring T
79. generates the SQL TABLE statement next STEPLIB DD The table table _ name is not available The instructions that you give to the software are called commands In this message the variable file_name represents the file that caused the error gt To enable incremental backups type y and press Enter at the next prompt GUI menu sequence Choose File gt Open BMC Software Inc Confidential and Proprietary Information About This Book xix This book uses the following types of special text Note Notes contain important information that you should consider Warning Warnings alert you to situations that could cause problems such as loss of data if you do not follow instructions carefully Tip Tips contain useful information that may improve product performance or that may make procedures easier to follow Syntax Statements Syntax statements appear in Courier The following example shows a sample syntax statement COMMAND KEYWORD1 KEYWORD2 KEYWORD3 KEYWORD4 YES NO file name The following table explains conventions for syntax statements and provides examples ltem Example Items in italic type represent variables that you dtsbackup control directory must replace with a name or value Use an underscore for variables with more than one word Brackets indicate a group of options You can table_name column_name field choose at least one of the items in the
80. group but none of them is required Do not type the brackets when you enter the option A comma means that you can choose one or more of the listed options You must use a comma to separate the options if you choose more than one option Braces enclose a list of required items You must DBD_name table_name enter at least one of the items Do not type the braces when you enter the item A vertical bar means that you can choose only commit cancel one of the listed items In the example you would choose either commit or cancel An ellipsis indicates that you can repeat the column_name previous item or items as many times as necessary BMC Software Inc Confidential and Proprietary Information XX Administrative Products for DB2 Installation Guide Summary of Changes The summary of changes includes enhancements to the installation application that is used to install BMC Software Administrative Products It also includes any major changes to the documentation The changes are listed by product version and release date Version 1 7 30 March 30 2001 This installation guide provides support for the BMC Software Install System for the ISPF products and for the graphical user interface GUI client CD Enhancements for version 1 7 30 include e ability to add products that are not included on the TIS or SAT tapes to the BMCDB2PR panel e addition of values for default processing options for the BMC Sof
81. is used REORG PLUS LOADPLUS or COPY PLUS can update the DASD MANAGER PLUS statistics tables to update statistical information Table 3 3 shows the synonyms that the REORG PLUS and LOADPLUS utilities use to reference the corresponding tables for DASD MANAGER PLUS Table 3 3 DASD MANAGER PLUS Table Synonyms for REORG PLUS and LOADPLUS Synonym DASD MANAGER PLUS Table prdvr_RS_TABLSPACE BMCASUyy Vyy_RS_TABLESPACE prdvr_RS_TABLEPART BMCASUyy Vyy_RS_TABLEPART prdvr_RS_TABLES BMCASUyy Vyy_RS_TABLES prdvr_RS_INDEXES BMCASUyy Vyy_RS_INDEXES prdvr_RS_INDEXPART BMCASUyy Vyy_RS_INDEXPART Table 3 4 shows the synonyms that the COPY PLUS utility uses to reference the corresponding tables for DASD MANAGER PLUS Table 3 4 DASD MANAGER PLUS Table Synonyms for COPY PLUS Synonym DASD MANAGER PLUS Table BMCACP_BMCXTBSP BMCASUyy Vyy_RS_ TABLESPACE BMCACP_BMCXTBPT BMCASUyy Vyy_RS_TABLEPART BMCACP_BMCXTBLS BMCASUyy Vyy_RS_ TABLES BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 9 Interacting with Other BMC Software Products The variables in Table 3 3 and Table 3 4 are defined as follows e prdis the product code ARU for REORG PLUS or AMU for LOADPLUS e vristhe version and release installed for REORG PLUS and LOADPLUS e yy is the version and release number of your current DASD MANAGER PLUS product These table names are the default names as sh
82. is useful only if you have CATALOG MANAGER installed Type Y if you want execution to save information in the CATALOG MANAGER drop recovery log about objects that are being dropped ALTER or CHANGE MANAGER logs the information that is required for recovering any object that you drop You must then use CATALOG MANAGER to recover the objects See the CATALOG MANAGER for DB2 Reference Manual for information about Drop Recovery Provides the default encoding scheme for databases created using CHANGE MANAGER A ASCII E EBCDIC CDLDSN amp amp PREFIX amp amp SSID CDL CDL CDLPS 15 Defines the default data set name for generated Change Definition Language CDL statements Defines the default value for the primary space allocation of the CDL data set CDLRDSN amp amp PREFIX COMPARE REPORT CDLSS 5 CDLU SYSDA CMP CMyrmcDC CMPDIAG SYSOUT Defines the default data set name for the CDL Report data set Defines the default value for the secondary space allocation of the CDL data set Defines the default unit for the CDL data set Defines the Compare plan name Defines the default value for the Compare diagnostic output data set COPYDD01 R COPYDD02 N REC VDD01 N REC VDD02 N Defines image copies for the DB2 Copy and the BMC Software COPY PLUS and LOADPLUS utilities The DOPTs parameters are defined as follows N no C copy R register and copy BMC Software Inc Confidential and Proprietary Informa
83. names 3 Rebind all DASD MANAGER PLUS packages and plans by using ASUssidP bind packages and ASUssidB bind plans where ssid is the subsystem ID 1 Check your synonyms to make sure that they point to the correct table names 2 If the synonyms do not point to the correct names drop the current synonyms Recreate the synonyms by using the same synonym names but with the correct table names 3 Rebind all PATROL DB Alter ALU or PATROL DB Change Manager ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Provided that PATROL DB Alter or PATROL DB Change Manager still exists in toleration mode use the fallback procedures described for toleration mode to remove the products in exploitation mode Any data that you added while you were in exploitation mode will not be available in toleration mode 3 38 Administrative Products for DB2 Installation Guide BMC Software Inc Confidential and Proprietary Information Table 3 17 If You Are using catalog indirection and ALTER CHANGE Maintaining BMC Software Administrative Products Then 1 Perform a Full installation of ALTER or CHANGE MANAGER 6 2D Then you will be operating in exploitation mode Migrating DB2 Version 4 to Version 5 Part 5 of 5 To Fall Back Then 1 Provided that the previous indirection still exists remove the indirect cop
84. normally would for the installation type that you want to perform Step 2 Select the new products that you want to install Step3 Clear the selection for those products that are already installed Note The disk space requirements listed in this chapter are for an initial installation Disk space requirements for additional products are reduced by the amount of disk space that you used for the initial installation BMC Software Inc Confidential and Proprietary Information 9 14 Administrative Products for DB2 Installation Guide Uninstalling a Client GUI Uninstalling a Client GUI Summary Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 This procedure describes how to uninstall one or more of the Database Administration products When you uninstall a product all installed product files are deleted but any saved work files remain From Windows click the Start button Choose Settings gt Control Panel Double click the Add Remove Programs icon Select the PATROL Database Administration Client OS390 Click the Add Remove button Click OK BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 15 Uninstalling a Client Command Line Interface Uninstalling a Client Command Line Interface Summary This procedure describes how to uninstall a client by using the command line interface From a command prompt run the command line
85. of N generates a worklist STOP command that allows you to complete the DELETEs and DEFINEs before the CREATEs that are located later in the worklist Y or N ANP CMvrmeDA Defines the Analysis plan name ARCHPPREF amp amp USERID amp amp SSID The high level qualifier or prefix for data sets that is used for a BMC Software utility archive ARCHPS 10 The primary space allocation in cylinders for BMC Software utility archive data sets ARCHSS 2 The secondary space allocation in cylinders for BMC Software utility archive data sets ARCHUNIT SYSDA The default UNIT that is used for BMC Software utility archive data sets ASUDOPT ASUDOPDI The name of the DASD MANAGER PLUS product s DOPTs module that the GUI for CHANGE MANAGER will use to interact with DASD MANAGER PLUS This parameter is used only if DASD MANAGER PLUS is installed ATTN Y Allows you to press the ATTENTION key to interrupt processing when ATTN Y This option allows you to stop processing for example when building a Mixed List in ALTER or CHANGE MANAGER Y or N AUTHSW N Controls the method of authorization ID switching that Analysis uses If you specify AUTHSW Y AUTH commands are used in the worklist to switch the authorization ID for subsequent SQL statements and reBINDs In this mode you can add SETS commands to the worklist for setting the authorization ID with SET CURRENT SQLID statements If you specify AUTHSW N SETS commands are generated for switchi
86. output JCL data set in the ISPF command shell with the following command ex HLO JCL BMCDB2 e Ifthe BMCDB2 CLIST is copied to a CLIST library that is normally allocated to your TSO session invoke BMCDB2 implicitly with SBMCDB2 Step 2 Ifthe BMCDB2 CLIST supports multiple SSIDs in the BMCDB2PR panel type in the DB2 SSID field On the BMCDB2P2 panel type S to select an SSID from the list of available SSIDs The SSID you selected appears in the DB2 SSID field of the BMCDB2PR panel Step3 If you edited your BMCDB2 CLIST to use a generated permanent ISPF table for the control table or if you modified the control table that was previously generated type GENERATE on the command line BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 19 Verifying the Installation of the Administrative Products Verifying the Installation of the Administrative Products Summary Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 This section describes the steps that you must complete to verify that the Administrative Products that have an ISPF interface have been installed correctly Invoke the BMCDB2 CLIST Verify that all the products appear on the BMCDB2PR panel that is displayed Type CONTAB on the command line On the BMCDB2TB panel verify that the correct partitioned data set PDS and member name are displayed in the library in which the BMCDB2 CLIST is loca
87. privileges of the person who is listing the table Specifies the name of the CATALOG MANAGER command module See job xnnCOMD in the output JCL file Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCOPY DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether issuing the SET PROFILE and SET PROFILE OFF commands requires SYSADM System Administrator authority Y or N The conditional uppercase indicator Y Translate delimited identifiers to uppercase N Do not translate delimited identifiers to uppercase Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSDATABASE DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSDATATYPES DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table The VSAM CATALOG alias that contains the data sets of the DB2 catalog BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 13 Default Option Descriptions DB2LO DBAUTH STATIC DBCS N DBRM STATIC DOPCP ACP OPTS DOPKP ACK OPTS DOPLP
88. product 9 14 Administrative Assistant for DB2 1 2 ADSN DOPT 6 11 AEXvrmAA Execution Monitor Entry plan 5 6 AEXvrmAM Execution Monitor plan 5 6 AEXvrmDA Execution Monitor Entry plan 8 6 AEXvrmDM Execution Monitor plan 8 6 AEXvrmHA Execution Monitor Entry plan 7 12 BMC Software Inc Confidential and Proprietary Information AEXvrmHM Execution Monitor plan 7 12 ALLC DOPT 6 11 ALLOC DOPT 5 12 7 18 ALTER BMC Software Utilities interface 3 6 client installation 9 2 controlling access 5 4 default option descriptions 5 12 default option listing 5 8 DOPTs 5 8 Execution plans 5 6 installation considerations 5 3 installation defaults 5 3 migrating data to CHANGE MANAGER 3 28 object security 5 7 overview 5 2 plans 5 4 post installation tasks 4 3 product description 5 2 space requirements 1 5 upgrading to CHANGE MANAGER 3 27 5 4 ALTER data sets CLIST 1 5 CNTL 1 5 DBRM 1 5 LOAD 1 5 MLIB 1 5 MSGS 1 5 MSGTEXT 1 5 PLIB 1 5 SCRIPT 1 5 SLIB 1 5 Index 1 TLIB 1 5 ALTER DOPTs BMC Software Inc Confidential and Proprietary Information 2 ACTDOPT 5 12 ACVPLAN 5 12 ALLOC 5 12 AMS 5 12 ANP 5 12 ARCHPPREF 5 12 ARCHPS 5 12 ARCHSS 5 12 ARCHUNIT 5 12 ASUDOPT 5 13 ATTN 5 13 AUTHSW 5 13 BLDBS 5 13 BLDCU 5 14 BMCCHECK 5 14 BMCCOPY 5 14 BMCLOAD 5 14 BMCSTATS 5 14 BMCUNLD 5 14 BPOOLIX 5 14 BPOOLTS 5 14 CATAUDIT 5 14 CATRECOV 5 15 CCSID 5 15 COPYDD01 5 15 COPYDD02 5 15 DASDMAN 5 15 DATACLAS 5 15 DATE 5 15 DB2CA
89. product is not yet running there How Products Are Licensed You must use the Product Authorization utility in the following situations e for product trials and permanent licensing e when upgrading to a new CPU e when an authorized CPU fails Note Although you do not need the Product Authorization utility for product maintenance and version upgrades you must consider certain issues that are associated with these upgrades See Product Maintenance or Version Upgrades on page A 8 for more information BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 5 How Products Are Licensed Product Trials and Permanent Licensing During a trial period for a BMC Software product you can install and use the product on any CPU by using a temporary password that you obtained from your BMC Software sales representative When you finish the trial and want to obtain a product license the following rules apply e You must purchase a product license for each CPU on which you will run the product e BMC Software Contracts Administration issues a permanent password for each combination of CPU and licensed product e To enable a product on a CPU you must add the permanent password that is issued for that CPU You do not need to reinstall and retest the product e You can install multiple passwords in the same product library This capability lets you use the same load library to run
90. provides documentation for the following products e ALTER for DB2 version 5 4 04 e CATALOG MANAGER for DB2 version 5 4 05 e CHANGE MANAGER for DB2 version 5 4 04 e CM PILOT for DB2 version 5 4 04 e DASD MANAGER PLUS for DB2 version 5 4 04 e PATROL DB Alter for DB2 version 3 1 02 e PATROL DB Change Manager for DB2 for OS 390 version 3 1 02 e SQL Explorer for DB2 version 2 2 07A BMC Software Inc Confidential and Proprietary Information Summary of Changes XXV Version 1 5 20 July 30 1999 This installation guide provides support for the BMC Software Install System Enhancements for version 1 5 20 of the Install System include the modification of I40INST to automatically copy the BMCMSG CLIST to HLQ CLIST e the ability to list the subsystem IDs SSIDs that are supported by the BMCDB2 CLIST This installation guide provides documentation for the following products e ALTER for DB2 version 5 4 04 e CATALOG MANAGER for DB2 version 5 4 04 e CHANGE MANAGER for DB2 version 5 4 04 e CM PILOT for DB2 version 5 4 04 e DASD MANAGER PLUS for DB2 version 5 4 04 e PATROL DB Alter for DB2 version 3 0 02 e PATROL DB Change Manager for DB2 for OS 390 version 3 0 02 e SQL Explorer for DB2 version 2 2 07A Version 1 5 10 April 30 1999 This installation guide provides support for the BMC Software Install System Enhancements for version 1 5 10 of the Install System include e the ability to copy an installat
91. same directory as the current version or as the earlier version you must first exit the Setup program and uninstall the client On the Select Components dialog box select the products to install 5 A Ensure that the Space Required does not exceed the Space Available If it does exceed the space available click Disk Space and select a new drive that contains the appropriate amount of space The new drive location appears in the Destination Location 5 B Click Next to continue BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Installing a Client to Run Locally Step6 On the Select Program Folder dialog box accept the program folder name type in a new folder name or select a folder name from the list Then click Next Step 7 When the Start Copying Files dialog box appears verify that the displayed installation options are correct Click Next to begin the installation or click Back to change the installation options Step 8 When the installation is complete click Finish Where to Go From Here The next task is to start and configure the client See Starting and Configuring the Client on page 9 18 BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 7 Installing the Client on a Network Drive Installing the Client on a Network Drive Summary Step 1 Step 2 Step 3
92. server uses for initialization The variables that define the JSI JES interface in the INI file are JSI JESSSID JES2 JES2 subsystem name JISI USISSID JSI1 JSI JES subsystem name JISI DLL 00 JSI JES main Load module ID JSI SPOOLBYOWNER 0 Restrict spool access by owner Default Option Listing DOPTs 7 14 This section provides an example of the default options DOPTs module listing for CHANGE MANAGER see Figure 7 1 on page 7 15 The DOPTs listing is created by the Install System and resides in xnnDOPT The DOPTs listing also resides in HLQ CNTL with the same member name as the DOPTs BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Default Option Listing DOPTs Figure 7 1 CHANGE MANAGER Default Options Listing Part 1 of 4 KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK MODULE ACMDOPD1 FUNCTION CHANGE MANAGER for DB2 COPYRIGHT COPYRIGHT BMC SOFTWARE INC 2000 LEVEL RELEASE 6 2 September 2000 FUNCTIONS DEFINE THE DEFAULT PROFILE VARIABLES KAKKKAKKKAKAKKKAKAKKAKAKKAAKAAKAKAKAKAKAAKAAAKAKAKAKAAKAAAKAKAAKAAKAKAAAKAKAKAKAAKAAAKAKAAAKAAKAAKAKAAAKAKAAKAKAAAAAAAKAA ACMDOPTS CSECT ACMDOPTS RMODE 24 ACMDOPTS AMODE 24 ACMDOPTS SALUDOPT PRODUCT CHANGE MANAG DATE amp SYSDATC PC ACM VRM 621E R SSID DBDB R DB2CAT DBDBCAT R EURO N R
93. size of the SYSREC primary space The size of the SYSREC secondary space The name of the SYSREC device type The size of the sort work primary space The size of the sort work secondary space BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 23 Default Option Descriptions USWVL UUSTP UVDEV SYSDA UVDPR 10 UVDSE 2 UVSTP UWFPR 10 UWFSE 2 UWFUN SYSDA UWFVL UWLPR 10 UWLSE 2 UWLUN SYSDA UWLVL UXSTP VIEWDEP STATIC The name of the work log volume The name of the UNLOAD PLUS product s load library The recovery device type The size of the recovery primary space UVDSP amp amp PREFIX amp amp SSID amp KOBNOD The prefix to be used with the last qualifier of RECVnnn data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied The size of the recovery secondary space The name of the RECOVER PLUS product s load library The size of the work file primary space The size of the work file secondary space The name of the work file device type The name of the work file volume The size of the work log primary space The size of the work log secondary space The name of the work log device type The name of the work log volume The name of the library where the Executio
94. task will be operating Currently support for JES3 is not provided The installer needs to provide the following information e The name of the JES2 macro library data set for that release typically this name is SYS1 HASPSRC e The MVS subsystem name that JES2 is using on that system and with which this particular MVS server task will communicate default of JES2 is provided The information that is required can be obtained from your local MVS or JES system programmer e An MVS subsystem name which the JSI JES Interface will use This name should be limited to four characters and reflect the name of the JSI interface that will be used by that particular server started task Note Each MVS server started task should have a unique JSI subsystem name default of JSI1 is provided No MVS system configuration changes are required for this parameter definition BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 7 Default Option Listing DOPTs Once these parameters have been determined the installation process builds an installation job This job may assemble a JES Offset module for the specified SP level of JES2 that is using the specified macro library if necessary This JES Offset module is then linked into the main JSI JES interface load module The installation also updates the MVS Server started task JCL and the server INI file with the subsystem names for both JES2 and the JSI interfa
95. that is shared by any of the Administrative Products When you are completing a Maintenance installation you must bind each product to the new level of the components if the products are using the same APF authorized load library Note To share the same APF authorized load library the products must be at the same version and release levels For example you have ALTER version 5 4 04 and DASD MANAGER PLUS version 5 4 04 installed and you are using the same APF authorized load library If you want to upgrade to version 6 1 01 for ALTER only you need to bind DASD MANAGER PLUS to the new JCL Generation and Execution Monitor components Note If you do not properly bind all Administrative Products that share the common components any attempts to generate JCL or to run worklists can cause SQLCODES 805 and 818 The product that has not been bound or upgraded will not run You do not have to bind a product separately to the shared components if the following conditions exist e You are using the same APF authorized load library and you are upgrading all of your products which are at the same version and release level at the same time The binds will be done during the upgrade e You are using separate APF authorized load libraries for your products BMC Software Inc Confidential and Proprietary Information 3 4 Administrative Products for DB2 Installation Guide Upgrading Shared Components Table 3 2 shows which server and
96. the distribution tape Note This procedure unloads only those files that you use during the installation process It does not unload any product files from the tape Before you unload the Install System from the distribution tape you should review the release notes technical bulletins and flashes that are included with the product These notices contain additional information about the products on the tape including information that may have been added after this book was published At times it is necessary to cancel the installation process and revert to the previous level of a product or a product tape set To ensure that you can revert to conditions prior to this installation you should back up your current version before you begin the installation process e Copy and save your current installation and product libraries Depending upon the products that you have installed these libraries may include LOAD DBRM PLIB MLIB SLIB TLIB INSTALL CLIST CNTL JCL and MSGS e When you install BMC Software recommends that you use unique plan names table names repository names and qualifier names To Unload the Install System Step 1 Create a batch job similar to the one shown in Figure 2 1 on page 2 7 as follows 1 4 Create a job step to unload File 1 into a data set with the low level qualifier INSTALL for example BMC INSTALL 1 B Create a job step to unload File 2 into the load library that the Install System w
97. the job that unloads the load library from the tape 3 E Return to Step 1 of this procedure and start the Install System again BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Starting the Install System The Install System displays the Main Menu see Figure 2 4 from which you can set user options for the installation process and generate batch jobs for the product installation If the tape set has additional options they are listed on the Main Menu also Refer to Chapter 1 Preparing for Installation for information about the contents of the distribution tape Figure 2 4 Install System Main Menu Install System Version 1 7 31 Main Menu Welcome to the BMC Install System Select an option number then press Enter to continue _ 0 User Options Specify User Parameters for Installation 1 Product Install Specify a Product Installation Path 2 BMC Authorization Maintain Product Passwords 3 What s New Install changes for this release 4 Additional Options Install Catalog Indirection ALTER Upgrade Copyright and Demo C 1997 2001 BMC Software Inc as an unpublished licensed work All rights reserved DB2 and IBM are registered trademarks of International Business Machines Corp Command gt F1 HELP F2 SPLIT F3 EXIT F9 SWAP F12 CANCEL If a Problem Occurs The distribution tape VOLSER is recorded in File 1 on the
98. the same synonym names but with the correct table names 3 Rebind all CATALOG MANAGER packages and plans by using ACTssidP bind packages and ACTssidB bind plans where ssid is the subsystem ID 3 36 Administrative Products for DB2 Installation Guide BMC Software Inc Confidential and Proprietary Information Table 3 17 If You Are using CATALOG MANAGER 6 1 or later Maintaining BMC Software Administrative Products Then 1 Migrate the DB2 catalog 2 Run HLQ CNTL UPGRD4 5 Then you will be operating in exploitation Migrating DB2 Version 4 to Version 5 Part 3 of 5 To Fall Back Then 1 Check your synonyms to make sure that they point to the correct table names ASUssidP bind packages and ASUssiaB bind plans where ssid is the subsystem ID Then you will be operating in exploitation mode BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks mode 2 Ifthe synonyms do not point to the correct names drop the current synonyms Then recreate the synonyms by using the same synonym names but with the correct table names 3 Rebind all CATALOG MANAGER packages and plans by using ACTssidP bind packages and ACT ssidB bind plans where ssid is the subsystem ID using DASD 1 Migrate the DB2 catalog 1 Check your synonyms to make sure ea PLUS 2 Ifthe Distributed Data Facility DDF is that they point to the
99. to CHANGE MANAGER and to migrate your existing data from ALTER to CHANGE MANAGER see Migrating Data From ALTER to CHANGE MANAGER on page 3 28 Controlling Access Plans are provided with ALTER that access Specification Analysis and Execution You can control access to each of these components by controlling the authorization that is granted to each of these plans Plan names vary depending on the version and release of the product that you are using ALTER and CHANGE MANAGER plan names have the format ppvrmcyz where pp is the product code vrm is the version release and maintenance level c is the DB2 level B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later y is the access type and z is the plan function Note The c character in the syntax ppvrmcyz is only used when defining plans for ALTER and CHANGE MANAGER versions 5 2 or later Earlier versions use the syntax prdvrmyz Execution component plan names have the format prdvrmnn where prd is the product code vrm is the version release and maintenance level and nn is a unique plan identifier The default plans that are shipped with this release follow along with their default plan names ALTER Specification and Analysis Plans The following plans are used by the Specification Import and Analysis components ALvrmcDF Front End Plan This plan controls access to the ALTER interface Authority to u
100. to the comment block that is located at the bottom of the BMCDB2 CLIST Customizing the Generated ISPF Interface for Catalog Indirection The BMCDB2 CLIST and the BMCDB2PR panel may need slight customization before you run the Administrative Products with catalog indirection Specifically you should add Indirect to the BMCDB2PR panel in HLQ INSTALL JCL as shown below to display the Indirect option in the BMCDB2PR panel DB2 Catalog Access _Z Direct Indirect You should also make the changes shown in Figure 4 8 to make the INDIRECT option valid Figure 4 8 BMCDB2PR Panel ver amp catopt nb list DIRECT INDIRECT Uncomment this line et ee ee ef ver Scatopt nb list DIRECT Comment out this line 4 8 BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Member BMCDB2CTI is generated to support catalog indirection This Enabling the Product CLISTs member contains logic for the DOPTs module allocation for indirect access When you use BMCDB2CI to update the BMCDB2 CLIST consider the following e If you have MVS ESA and TSO E 2 1 or later the Install System automatically updates the BMCDB2 CLIST with BMCDB2CI The Install System searches both the JCL output file and the installation file to apply the updates wherever a copy of BMCDB2 is found The Install System prompts you for the location of the BMCDB2 CLIST e Ifyou
101. who is listing the table BMC Software Inc Confidential and Proprietary Information 6 20 Administrative Products for DB2 Installation Guide TABLEPA STATIC TABLES STATIC TABLESP STATIC TABSTAT STATIC Default Option Descriptions Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSTABLEPART DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSTABLES DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSTABLESPACE DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSTABSTATS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table TAPE1 CART TAPE2 TAPE TAPE3 TAPE TRIGGER STATIC TRS N UADEV SYSDA UADPR 10 UADSE 2 Defines the valid installation tape unit names for your site Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL
102. with Other BMC Software Products Update your synonyms if e your current synonyms do not point to the correct tables e DASD MANAGER PLUS accesses the utility tables during batch processing To update your synonyms complete the following steps 1 Drop the current utility synonyms for DASD MANAGER PLUS 2 Create the new DASD MANAGER PLUS utility synonyms by using the same synonym names but with the correct table names 3 Bind the package AEXEUTID into the main collection ID for DASD MANAGER PLUS The HLQ INSTALL member DCI AEXU provides an example of a worklist If the utilities are installed in a different load library complete the following steps 1 Find the member in the HLQ CNTL library that has the same name as the DOPTs module 2 Update the first available steplib option SL1 SL2 and so on in the DASD MANAGER PLUS DOPTs member to use the different utilities load library For a description of the steplib options see Chapter 8 Installing DASD MANAGER PLUS 3 Add any additional load libraries to SLIB member AJXSTEPU SQL Explorer with DASD MANAGER PLUS If you plan to use the SQL Explorer function of migrating statistics from the DASD MANAGER PLUS statistics tables and you did not establish a connection between the products during the installation process you must point the PATROL SQL Explorer synonyms to the correct DASD MANAGER PLUS tables BMC Software Inc Confidential and Proprietary Information
103. you are not installing the same version and release level of CHANGE MANAGER on the remote subsystem as you have installed on the local subsystem perform the following steps 1 Install the compare components that are required for the catalog to catalog Compare feature on the remote subsystem A Edit the ACMC2CO member in the HLO CNTL data set B Follow the instructions in the member The member contains data definition language DDL for execution at the remote subsystem via DB2I SPUFI 2 Bind the packages and the plan that are needed for the remote subsystem A Edit the ACMC2CB member in the HOL CNTL data set B Follow the instructions in the member C Follow the instructions in ACMC2CG to grant execute on the collection IDs Note Collection IDs and the compare plan name must be identical on both DB2 subsystems If the remote subsystem has a version of DB2 that is different from the version of DB2 that is installed on the local subsystem use the following steps as an example for implementing the catalog to catalog Compare feature 1 On the subsystem that has DB2 Version 4 install CHANGE MANAGER version vrmC with DDF active The variable vrm indicates the version release and maintenance level Use the collection ID ACMvrmC_D_MAIN and the compare plan name CMvrmCDC 2 On the subsystem that has DB2 Version 5 install CHANGE MANAGER version vrmD with DDF active Use the collection ID ACMvrmD_D_MAIN and the compar
104. you specified the Review Variables user option see page 2 19 the Install System displays a series of panels that summarizes the values that you specified for the installation parameters You can change most of the values shown by typing over them Step5 Generate the batch jobs to install the products 5 A Inthe JCL Generation Option panel specify one of the following options e Specify 1 to generate installation batch jobs in the data set that you specified in Specifying User Options on page 2 19 This option generates all of the batch jobs that will unload the product libraries from tape and install the MVS components Warning If installation batch jobs already exist in the specified data set they are overwritten e Specify 2 to skip batch job generation and display the next panel No installation batch jobs are created e Specify 3 to generate installation batch jobs and a template for multiple SSID installations If you plan to install products on several DB2 subsystems consider using the Multiple SSID installation path for the additional subsystems For more information see SSID Installation on page 1 15 and Multiple SSID Installation on page 1 17 5 B Press Enter to start processing the batch jobs If you chose to generate the batch jobs the Install System creates the batch job streams that are used for product installation The job streams contain batch jobs and BMC Software worklists which are used b
105. you want to use to log in to the DB2 subsystem for this connection TSO User ID RDACRJ lt Back Cancel Step 2 Configure OS 390 e Ifyou are using OS 390 release 2 5 or later and IBM TCP IP version 3 4 or later the owner of the started procedure that is the user ID that is accessing TCP IP must define an OMVS segment in Resource Access Control Facility RACF or in another security package to operate the MVS Server Refer to the IBM OS 390 eNetwork Communications Server IP Planning and Migration Guide for more information BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 25 Configuring TCP IP 4 26 e Ifyou are using OS 390 release 2 4 or earlier set the MVSTCP HPNS variable found in the Server INI file to MVSTCP HPNS 0 A zero value indicates that the TCP IP API will not be defined as High Performance Native Sockets HPNS Step3 Activate the MVS Server The PATROLDB member shown in Figure 4 16 is the started task that enables the MVS Server to communicate with DB2 Figure 4 16 ISPF Edit Panel EDIT BMCADMN V621 D62 CNTL PATROLDB 01 00 COLUMNS 001 072 COMMAND gt SCROLL gt CSR TKK RK kK Kk kk KK kK RK RRR KKK TOP OF DATA RARA AAA AAA AAA AAA k kkk kkk kkk k k 000001 PATROLDB PROC OUT X 000002 000003 PATROLDB EXEC PGM XAMSERV PARM 1 0 0 0 MVSDB2 1 REGION 0M 000004 STEPLIB DD 000005 DD 000006
106. your BMC Software Technical Support Analyst may need this information Note Version code X FF indicates that MVS is running as a VM guest This X FF is not the real processor version code To determine the real version code run the LIST option of the Batch Product Authorization utility from an APF authorized library See Table A 6 Control Statement Keywords on page 29 for more information This panel also displays the number of processors that are online to the current operating system This information may apply to your BMC Software License Agreement Note The information that is displayed on this panel might not refer to a computer on which you are licensed to run a BMC Software product For example if you log on to TSO on SYSA but run your BMC Software product on SYSB your product authorization entries might refer to SYSB Batch Product Authorization This section describes the batch interface that is used for product authorization To use the online interface see Online Product Authorization on page A 10 Using the batch interface you can perform the following tasks e process a password e obtain current product authorization and processor information Running Batch Product Authorization Figure A 14 on page A 28 is a sample JCL script for running batch product authorization See Additional Information on page A 28 for descriptions of the information in the JCL script You can find product specific JCL
107. 1 D61 LOA USDEV SYSDA USWVL USWPR 10 USWSE 2 UDEVT SYSDA USRUN SYSDA UWFUN SYSDA UWFVL UWFPR 10 UWFSE 2 UWLUN SYSDA UWLVL UWLPR 10 UWLSE 2 UCDSP amp amp PREFIX amp amp SSID amp amp OBNOD USCPR 10 USCSE 2 URDSP amp amp PREFIX SYSREC USRPR 10 CATALOG MANAGER Default Options Listing Part 2 of 5 amp amp PGMR 1 1 FF F FF F FF FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F KF F BMC Software Inc Confidential and Proprietary Information Default Option Listing DOPTs Figure 6 1 RSE 2 BESS Sissa WLDSN SYSOUT AOPTS ALUDOPD1 R BOPTS ASUDOPD1 R TAPE1 CART TAPE2 TAPE TAPE3 TAPE Ss gt Q To Z D D aT e SES E E E lt lt gt gt si x di Il 2 gt Xx D NOWRK Y DOPCP ACPSOPTS DOPRP ARUSOPTS DOPVP AFRSOPTS LP AMUSOPTS UP ADUSOPTS DOPKP ACKSOPTS SACTSQLD IPNAMES STATIC LOCATIO STATIC LULIST STATIC LUMODES STATIC LUNAMES STATIC M EL STATIC AUXRELS STATIC E C O UO zal n Ti HECKS STATIC HECKDE STATIC COLAUTH STATIC COLDIST STATIC COLDISS STATIC COLSTAT STATIC COLUMNS STATIC CONSTDE STATIC COPY STATIC DATABAS STATIC DATATYP STATIC DBAUTH STATIC BMC Software Inc Confidential and Proprietary Informat
108. 19 Use the Install System to specify environment and See Generating Installation JCL on page 2 22 product options and to generate installation batch jobs for each product that you install Run the installation batch jobs to install the products See the product chapters in this book and create any DB2 objects that are required for the products BMC Software Inc Confidential and Proprietary Information 2 2 Administrative Products for DB2 Installation Guide Processing an ESD Image Processing an ESD Image Summary To install the data sets from an Electronic Software Distribution ESD image you must copy the image to the mainframe and expand the data sets Use the following procedure to accomplish this task This procedure does not describe how to acquire an ESD image from BMC Software For information about receiving your software electronically contact your BMC Software sales representative Before You Begin At the BMC software download site review the documents README HTML and ESD_MODULES pdf to identify the files that you need If you are installing more than one product modules and data sets that are common among products need only be transferred once Note Many products have only one required image while others have several Before you can process the ESD image on your mainframe you must allocate a sequential data set on your direct access storage device DASD as shown in Table 2 2 Table 2
109. 2 User Guide For a sample compile JCL refer to the HLO CNTL member AJXCOMPS Generating JCL Region Statements The EXEC REGION parameter is set by default to REGION 0M in the AJX USRV member that resides in the SLIB If you do not change the IBM supplied default limits in the IEALIMIT or IEFUSI exit routine modules this parameter requests that the job step get all of the available storage above and below the 16 MB line If the IBM defaults have been changed you should also change the REGION 0M parameter in the AJX USRV member by finding the variable REGION and changing 0M After you edit the member compile it BMC Software Inc Confidential and Proprietary Information 4 14 Administrative Products for DB2 Installation Guide Compiling SLIBs Generating JCL for JES3 Environments Users encounter a problem on systems using JES3 when the users attempt to close a data set through a subtask other than the subtask that opened the data set This action can result in a 1FB ABEND You can circumvent this problem by uncommenting the AJXJJES3 Y statement in the AJX USRV member that resides in the SLIB After you edit the member compile it Generating JCL for Generation Data Groups Refer to the comments in the SLIB member AJX DSNS for GDG examples of making global changes After you edit the member compile it BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 15 Assembling
110. 2 product The CHANGE MANAGER product provides management of application data structure definitions and application data over multiple DB2 subsystems It is a comprehensive tool for managing complex environments in which users can design multiple data structures install them on multiple DB2 subsystems vary the structures at each DB2 location to meet local requirements and implement version upgrades over the life of the application CHANGE MANAGER provides the following major functions e changes data structures e copies data structures within the same DB2 subsystem e migrates data structures e migrates changes that are made to data structures e undoes changes that are made to data structures e recovers structures and data to a prior state e records changes that are made to data structures e interacts with data modeling CASE tools e feeds back changes that are made at the receiving DB2 subsystem to the sending DB2 subsystem CHANGE MANAGER provides full management support for the same set of data structures as the ALTER product e storage group e database e table space e table e check constraint DB2 Version 4 1 and later e foreign key e index e view e trigger DB2 Version 6 1 and later e alias e synonym When you use CHANGE MANAGER to specify any of these objects for change CHANGE MANAGER automatically propagates the change as needed for any dependent objects CHANGE MANAGER restores all data dependencies and
111. 5 JDSNBG 7 26 JDSNBR 7 26 JDSNC 7 26 JDSNCPL 7 26 JDSNE 7 26 JDSNI 7 26 LOCATION 7 26 LOCK 7 26 LOG 7 26 MGMTCLAS 7 27 PC 7 27 PIC 7 27 PRODUCT 7 27 REBLD 7 27 Index 7 RECOV 7 27 RECVDDOI 7 22 RECVDD02 7 22 RECVMAX 7 27 RECVMAXU 7 27 RECVPREF 7 28 RECVPS 7 28 RECVSS 7 28 RECVUNIT 7 28 REORG 7 28 RPTPL 7 28 SDSN 7 28 SDSNE 7 28 SEQI 7 28 SLI 7 28 SL2 7 28 SL3 7 29 SL4 7 29 SL5 7 29 SPP 7 29 SSID 7 29 STATS 7 29 STOPCOMM 7 29 STORCLAS 7 29 SWPS 7 29 SWSS 7 29 SWU 7 29 SYNCPNT 7 29 SYSCMAX 7 30 SYSCMAXU 7 30 SYSCPREF 7 30 SYSCPS 7 30 SYSCSS 7 30 SYSCUNIT 7 30 SYSRMAX 7 30 SYSRMAXU 7 30 SYSRPREF 7 30 SYSRPS 7 30 SYSRSS 7 30 SYSRUNIT 7 30 SYSTYPE 7 30 SZDEVT 7 30 TABLEACC 7 30 TABLEALL 7 31 TAPEI 7 31 TAPE2 7 31 TAPE3 7 31 TIMEPARM 7 31 BMC Software Inc Confidential and Proprietary Information TSOSX 7 31 UNLDCOLL 7 31 UNLDEMPT 7 31 UPDSTATS 7 31 UTILCOPY 7 31 VRM 7 31 VVALPROP 7 31 WDC 7 32 WDSN 7 32 WLPS 7 32 WLSS 7 32 WLU 7 32 WMC 7 32 WPS 7 32 WSC 7 32 WSS 7 32 WU 7 32 CHANGE MANAGER GUI installing JSI JES interface 7 13 post installation tasks 4 22 CHANGE MANAGER plans ACVvrmDM 7 10 AEXvrmHA 7 12 AEXvrmHM 7 12 MvrmcDA 7 11 MyrmcDI 7 11 MvrmeDR 7 11 CMvrmcDS 7 11 characters in passwords A 4 CHECKDE DOPT 6 12 checkpoints 1 9 CHECKS DOPT 6 12 clients configuring 9 18 files installed on 9 12 installation requirements 9 3 installing 9 6 9 9 mainta
112. 6 7 The DOPTs listing is created by the Install System and resides in xnnDOPT The DOPTs listing also resides in HLQ CNTL with the same member name as the DOPTs BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Default Option Listing DOPTs Figure 6 1 CATALOG MANAGER Default Options Listing Part 1 of 5 KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKK MODULE NAME ACTDOPD1 FUNCTION CATALOG MANAGER DEFAULT PROFILE MODULE COPYRIGHT COPYRIGHT BMC SOFTWARE INC 2000 LEVEL RELEASE 6 2 September 2000 FUNCTIONS DEFINE THE DEFAULT PROFILE VARIABLES KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK SECTIONS ACTDOPTS CSECT KKKKAKKAKKAKKAKAKKKAKKAKKAKKAKAKKAKKAKAKKAAKKAAKAKAKAKAKAAKAKAAKAKAKKAKKAAKAKAAKAKAAKAKAKAKAKAKAAKAKAAK ACTDOPTS CSECT SACTDOPT SSID DBDB R GRPAT B2LO PT R Scatter UP Y RS N R RS N R RS N R RO O UDIT Y ALLC N DBCS N R PLP 55 AX 300 MPLAN ACT621DM LPLAN ACT621DL PLAN ACT621DU PLAN ACT621DK H PUQHTAHUSD PLAN ACT621D PLAN ACT621D PLAN RCCOL ACT621_D_ MAIN DB2CT DBDBCAT R TCEOLS TESYVO CATOP Y SZDEV 3380 R PDSN amp amp ZUSE
113. 7 Default Option Descriptions PACKAGE STATIC PACKAUT STATIC PACKDEP STATIC PACKLIS STATIC PACKSTM STATIC PARMS STATIC Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPACKAGE DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPACKAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPACKDEP DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPACKLIST DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPACKSTMT DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPARMS DB
114. 7 18 DASD MANAGER PLUS 8 9 default option listing ALTER 5 8 CATALOG MANAGER 6 6 CHANGE MANAGER 7 14 DASD MANAGER PLUS 8 7 default options DOPTs description 1 20 refreshing 3 13 default options processing CATALOG MANAGER 6 4 BMC Software Inc Confidential and Proprietary Information DEFERUIX DOPT 5 16 7 23 defining user options for installation 2 22 DELETE Authorization for a Processor panel A 15 DISCARDS DOPT 5 16 7 24 displaying current processor A 26 distributed systems software installing the client 9 11 distribution data sets ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 distribution tape Administrative Products 1 2 distribution tape space requirements ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 distribution tape unloading 2 6 DLHQ DOPT 8 10 document conventions xix documentation online xvii online help xviii printed xviii DOPCP DOPT 6 14 DOPKP DOPT 6 14 DOPLP DOPT 6 14 DOPRP DOPT 6 14 DOPTs ALTER 5 8 CATALOG MANAGER 6 6 CHANGE MANAGER 7 14 DASD MANAGER PLUS 8 7 installation default options 1 20 DOPUP DOPT 6 14 DOPVP DOPT 6 14 DPLAN DOPT 6 14 8 10 DPNAM DOPT 8 10 DPT DOPT 6 15 DRO DOPT 6 15 dropping DB2 structures 2 24 DSN3 ATH member 4 44 DSN3SATH member 4 44 Dynamic SQL GRANT 3 20 Index 11 E EAP DOPT 5 16 7 24 8 10 EDSN DOPT 6 15 EIP DOPT 5 16 7 24 8 10 electronic documentation online help xviii Electronic Software Distributio
115. 9 CATALOG MANAGER Default Options Listing Part 1 of 5 6 7 CHANGE MANAGER Default Options Listing Part 1 of 4 7 15 DASD MANAGER PLUS Default Options Listing Part 1 of 2 8 8 Modifying the PDB_Install ini File Client Installation 9 9 Product Authorization Primary Menu SECEPPRI A 11 BMC Software Inc Confidential and Proprietary Information Figures x xii Figure A 2 Figure A 3 Figure A 4 Figure A 5 Figure A 6 Figure A 7 Figure A 8 Figure A 9 Figure A 10 Figure A 11 Figure A 12 Figure A 13 Figure A 14 ADD Authorization for a Processor Panel SECEPADD A 13 Product Authorization ADD Message 0 000005 A 14 DELETE Authorization for a Processor Panel SECEPDEL A 15 Product Authorization DELETE Message 04 A 16 REPLACE Authorization for a Processor Panel SECEPREP A 17 Product Authorization REPLACE Message 2 4 5 A 18 MODIFY Authorization for an Existing Processor Panel SECEPUPD A 20 Product Authorization MODIFY Message 204 5 A 21 Product Authorization RESET Message A 22 Product Authorization Temporary Password Message A 23 Product Authorization Display Panel SECEPTBL A 24 Current Processor Information Panel SECEPCPU A 26 Sample JCL for Running Batch Product Authorization A 28 BMC Software Inc Confid
116. 9 5 Installing the Client Using Distribution Software on page 9 11 Installing a Client to Run Locally Installing a Client to Run Locally 9 6 Summary Step 1 Step 2 Step 3 Step 4 Step 5 This procedure enables you to install the client on your hard drive to run locally This procedure uses D for the CD ROM drive If your machine uses a different letter substitute the correct drive letter Insert the Database Administration product s CD into the client s CD ROM drive The Database Administration product s Setup program launches automatically Read the Welcome page and click Next to continue Note Use the Next and Back buttons to navigate through the Setup program To go back and undo a selection click Back To continue click Next On the User Information dialog box enter your name and company name and then click Next On the Choose Destination Location dialog box review the installation destination location If you prefer a different location click Browse and select an appropriate location To accept the default location click Next Note If you have a current version of the Database Administration products installed or if you have a version of the products that is earlier than the current version and you choose to install the products in the same directory a warning is displayed Choose another location in which to install the products If you want to install the products in the
117. 9DLTE installation jobs BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 29 Maintaining BMC Software Administrative Products Maintaining BMC Software Administrative Products The tables in this section provide guidelines that help you to maintain BMC Software Administrative Products when you migrate between the following versions of DB2 e version 5 to version 6 e version 4 to version 5 Migrating from DB2 Version 5 to Version 6 To maintain BMC Software Administrative Products when you migrate to DB2 Version 6 or when you fall back to DB2 Version 5 use the guidelines in Table 3 15 Table 3 15 Migrating DB2 Version 5 to Version 6 Part 1 of 4 If You Are Then To Fall Back Then using ALTER or Perform a Full installation of ALTER or 1 Provided that the previous version of CHANGE CHANGE MANAGER 6 2E Then you will ALTER CHANGE MANAGER MANAGER 5 4 03 be operating in exploitation mode PATROL DB Alter or PATROL or earlier or using DB Change Manager still exists PATROL DB Alter remove the product in exploitation or PATROL mode DB Change i Manager server 2 For ALTER ALU or CHANGE 3 0 01 or earlier MANAGER ACM rebind all packages and plans for the previous version by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Any data that you added while you were in exploitation mode will not be av
118. ABLE Explanation This CPU is already authorized for this product System Action The password is not processed User Response Determine whether the CPU ID is correct You may need to display current processor information see page A 26 BMC Software Inc Confidential and Proprietary Information B 12 Administrative Products for DB2 Installation Guide Error Messages BMC89108W PRODUCT IS NOT AUTHORIZED TO EXECUTE PLEASE ENTER BMC SUPPLIED PASSWORDS Explanation There are no authorized CPUs in the product load library System Action The product does not run User Response Use a password to add an entry for the correct processor to the product load library BMC891101 PRODUCT AUTHORIZATION TABLE WAS SUCCESSFULLY BUILT UPDATED YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON ANY PROCESSOR UNTIL lt mm dd yyyy gt PRESS ENTER TO CONTINUE Explanation The product authorization table has been modified to allow execution of this product temporarily until the indicated date System Action None User Response None Information only If you have a permanent license for this product contact your BMC Software sales representative to obtain a permanent license password BMC89111E RC lt n gt WHILE ATTEMPTING TO DECODE THE EXPIRATION DATE Explanation The Product Authorization utility was unable to decode the expiration date because of an internal error System Action The action fails or the batch job terminates Us
119. AKAAKAKAKAKAAAK MODULE NAME ACTDOPD1 DESCRIP NAME CATALOG MANAGER DEFAULT PROFILE OPTIONS ENTRY INFORMATION THIS MODULE CONTAINS NO EXECUTABLE CODE F KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK END BMC Software Inc Confidential and Proprietary Information 6 10 Administrative Products for DB2 Installation Guide Default Option Descriptions Figure 6 1 CATALOG MANAGER Default Options Listing Part 5 of 5 LKED SYSIN DD NAME ACTDOPD1 R Note The R in the variable syntax indicates that the value specified will refresh the existing value of the variable in the user s ISPF profile data set every time that a user starts the product Default Option Descriptions This section describes the DOPTs listed in Figure 6 1 on page 6 7 In some cases the default value for the option is listed ADSN amp amp ZUSER BMCCAT ARCHIVE ALLC N AOPTS ALUDOPD1 AUDIT Y AUXRELS STATIC The name of the data set where you want to store archived log entries CATALOG MANAGER dynamically allocates the log entries the first time that they are used See the CATALOG MANAGER for DB2 User Guide for details about log maintenance When allocating this data set use these parameters DCB LRECL 2044 BLKSIZE 2048 RECFM VB Note In many installation sites allocation of data sets is controlled by user written or third party routines If allocat
120. ANAGER 3 Add any additional load libraries to SLIB member AJXSTEPU CATALOG MANAGER CATALOG MANAGER can interact with the BMCUTIL BMCHIST and BMCSYNC tables to provide BMC Software utility control status and history information History information is not provided for the BMC Software RECOVER PLUS for DB2 product CATALOG MANAGER uses the following synonyms e BMC_UTILITY for the BMCUTIL table e REORG HISTORY for the BMCHIST table e BMC_UTIL_SYNC and BMC_UTIL_SYNC2 for the BMCSYNC table BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 7 Interacting with Other BMC Software Products CATALOG MANAGER assumes that all BMC Software Utilities products share these tables You should examine these synonyms and verify that the table names are correct Update your synonyms if e your current synonyms do not point to the correct tables e CATALOG MANAGER accesses the utility tables during batch processing To update the synonyms complete the following steps 1 Drop the CATALOG MANAGER utility synonyms 2 Create new CATALOG MANAGER utility synonyms by using the same synonym names but with the correct table names 3 Bind the packages ACTCSQRH ACTDDQRH and ACTCSQBU into the main collection ID for CATALOG MANAGER 4 Bind the CATALOG MANAGER BMC Software Utility History Plan BMC Software specifies this plan as ACTvrmDH where vrm is the version release
121. Administrative Products for DB2 Installation Guide Administrative Assistant for DB2 ALTER for DB2 CATALOG MANAGER for DB2 CHANGE MANAGER for DB2 DASD MANAGER PLUS for DB2 UTILITY MANAGER for DB2 Version 1 7 31 May 11 2001 lt bmosoftvare Copyright 1988 2001 BMC Software Inc as an unpublished work All rights reserved BMC Software the BMC Software logos and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software Inc IBM and DB2 are registered trademarks of International Business Machines Corp All other registered trademarks or trademarks belong to their respective companies Restricted Rights Legend U S GOVERNMENT RESTRICTED RIGHTS UNPUBLISHED RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES Use duplication or disclosure by the U S Government is subject to restrictions set forth in FAR Section 52 227 14 Alt II g 3 FAR Section 52 227 19 DFARS 252 227 7014 b or DFARS 227 7202 as amended from time to time Send any contract notices to Contractor Manufacturer BMC Software Inc 2101 CityWest Blvd Houston TX 77042 2827 USA Contacting BMC Software You can access the BMC Software Web site at http www bmc com From this Web site you can obtain general information about the company its products special events and career opportunities For a complete list of all BMC Software offices and locations go to http www bmc com corporate of
122. BMCDB2 CLIST and BMCDB2PR panel are generated using only the options for the last product that was installed Therefore you may not be able to access the previously installed product unless you manually edit the BMCDB2 CLIST Use the following scenarios as examples for editing the BMCDB2 CLIST Note If you are planning to execute multiple copies of the BMCDB2 CLIST you may need to change the ISPF application ID that the CLIST allocates so that each SSID user profile is unique across all BMCDB2 CLISTs Otherwise changing user options in one SSID might also change the same user options for a different SSID Refer to Avoiding User Options Overlay on page 3 15 for more information BMC Software Inc Confidential and Proprietary Information 4 4 Administrative Products for DB2 Installation Guide If you have multiple versions of the products installed and the version and Enabling the Product CLISTs release numbers of the products on one subsystem are later than the version and release numbers of the products on another subsystem use the CLIST for the later version and release of the products For example if you installed version 5 4 of the products on subsystem DBDA and you installed version 6 1 of the products on subsystem DBDB and you want to use one CLIST use the CLIST for the version 6 1 products on DBDB If you copy the BMCDB2 CLIST from the HLQ JCL library to a CLIST library that is normally allocated to your TSO sessi
123. C Defines image copies for the DB2 Copy and the BMC Software COPY PLUS and LOADPLUS utilities The DOPTs parameters are defined as follows N no C copy R register and copy These DOPTs control the input keywords to Analysis as follows e Local copy parameters parms for the COPYDDN keyword can be COPY01 and COPY02 separated by commas or blanks e Remote copy parameters parms for the COPYDDN keyword can be RECVOI and RECV02 separated by commas or blanks Indicates whether version 5 1 or later of the BMC Software DASD MANAGER PLUS product is installed Y or N ALTER and CHANGE MANAGER select DB2 catalog statistics for space estimation When DASDMAN Y any statistics from the BMCSTATS tables will be merged Indicates whether support for the DATACLAS parameter is required for VCAT defined DB2 objects Y or N This parameter is used only if you have ASMA90 as your assembler DB2CAT or DB2CT DBDBCAT The VSAM CATALOG alias that contains the data sets of the DB2 catalog DBRM1 DBRM2 DBRM3 Names the three default DBRM libraries BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 15 Default Option Descriptions DBRMLIB N DEFERUIX N DISCARDS nnnn EAP AEXvrmAA EIP DCIINSTL ENVP ALvrmcDE EPP AEXvrmAM EURO N Includes the LIBRARY parameter on the BIND statement for plans and packages Y or N Note A disadvantage to adding the LIBRARY parameter to the BIND
124. C Software Inc Confidential and Proprietary Information Figure 7 1 RCHSS 2 EQI 050 YNCPNT 00 MS Y ALLOC N STORCLAS N DATACLAS N MGMTCLAS N JCLCLEAN N AUTHSW N R GLID DASDMAN Y R CCSID E R IXTYPE 2 R VVALPROP N R POOLTS BP0 POOLIX BP0 OCK X A S S A MCCOPY N R MCCHECK N R MCLOAD N R BLDCU N R BLDBS N R UTILCOPY N R MCUNLD N R EORG N R EBLD I R NLDCOLL N ZDEVT 3380 R TATS S R PDSTATS C ABLEALL B B D BMCSTATS N R B B B a NAHAHnHNAADY HSMVOL LOCATION TAPE1 CART TAPE2 TAPE TAPE3 TAPE ATTN Y ENVP CM62 FEP CM6211 SPP CM6211 fan al J zj Gl Gl BMC Software Inc Confidential and Proprietary Information ISCARDS 0000 R Default Option Listing DOPTs CHANGE MANAGER Default Options Listing Part 3 of 4 Chapter 7 Installing CHANGE MANAGER FF F FF F F FF F F FF F F FF F F FF F F FF F F F FF F F FF F F FF F F FF FF F FF F F F FF F F FF F F FF F KF F 7 17 Default Option Descriptions Figure 7 1 CHANGE MANAGER Default Options Listing Part 4 of 4 ANE P 621E IMP p 621EDI CMP CM621EDC BASE CM621EDB c DA c RPTPL CM621EDR A A EPP AEX621HM EAP AEX621HA EIP DCIINSTL ASUDOPT ASUDOPD1 ACTDOPT ACTDOPD1 ACVPLAN ACV621DM DEFERUIX N XX F F
125. COLL_ID NICK NAME ACM DB31 D ACMDOPD1 CMvrmBDF ACMA i ACM DB41 D ACMDOPD1 CMvrmCDF ACMB K SSID Data Set Name LIB EXIT LOAD EXIT LOAD HLO DB31 DB31 DB41 DB41 DB41 SYS3 SYS25 SYS3 SYS 2 Step 4 DBAP DSNEXIT DB2V31M DSNLOAD DB41 DSNEXIT DB2V41M DSNLOAD F BMC DB41 After you complete your changes end the edit session Customize the BMCDB2 CLIST for CATALOG MANAGER Catalog Browser is a subset of CATALOG MANAGER functionality that provides access to the BMC Software UTILITY MANAGER for DB2 product for users who do not have a CATALOG MANAGER license UTILITY MANAGER supports utility processing for the BMC Software REORG PLUS for DB2 and the BMC Software COPY PLUS for DB2 products and requires the installation of these products If you install UTILITY MANAGER with CATALOG MANAGER and you choose not to apply a password for CATALOG MANAGER when you perform the installation you will receive the functionality of the BMC Software Catalog Browser interface only To obtain the full functionality of CATALOG MANAGER you will need to perform the following steps 1 Apply a password for CATALOG MANAGER 2 Edit the call to ACTEMAIN in your BMCDB2 CLIST and change the M B parameter to M BC The M parameter determines the password that is checked and the menu that is displayed BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Inst
126. CP IP 4 23 DB2 secondary authorizations 4 44 defining 9 18 installation verification 4 45 post installation tasks 4 22 setting up 4 28 setting up the SNA Gateway Server 4 37 verifying the host code page 4 43 verifying the network 9 4 N naming conventions 3 23 collection names 3 25 collection nicknames 3 26 options module 3 23 plan names 3 23 product 1 22 product authorization tables A 3 synonym qualifier 3 23 network drive copying an installation image to 9 8 NOWRK DOPT 6 17 O object security ALTER 5 7 CHANGE MANAGER 7 13 objects space requirements ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 Index 15 DASD MANAGER PLUS 1 8 online documentation xviii help xviii product authorization A 10 OPNDB2ID DOPT 8 11 options module multiple 3 17 naming conventions 3 23 prdDOPDI 3 16 single 3 17 OS 390 configuring 4 25 overview ALTER 5 2 CATALOG MANAGER 6 2 CHANGE MANAGER 7 2 DASD MANAGER PLUS 8 2 P PACKAGE DOPT 6 18 packages and plans binding 4 17 PACKAUT DOPT 6 18 PACKDEP DOPT 6 18 PACKLIS DOPT 6 18 PACKSTM DOPT 6 18 PARMS DOPT 6 18 passwords applying A 5 functions A 4 permanent A 4 temporary A 5 PC DOPT 5 18 7 27 PDSN DOPT 6 18 performance BMCDB2 CLIST 4 5 4 19 permanent password functions A 4 JCL for batch A 28 processing online A 11 PIC DOPT 5 18 7 27 PKSYSTE DOPT 6 18 PLAN DOPT 6 19 PLANAUT DOPT 6 19 PLANDEP DOPT 6 19 plans ALTER 5 4 CATALOG MANAGER 6 5
127. CTU 3 8 DCI AEXU 3 7 3 11 DCI ASUC 3 10 DCI ASUL 3 10 DCI ASUR 3 10 DCI PSSD 3 12 hosts defining 9 18 HPLAN DOPT 6 16 HRS DOPT 6 16 HSMVOL DOPT 5 17 7 25 ICCOL DOPT 6 16 ICSYC DOPT 6 16 IMP DOPT 5 17 7 25 IMPDIAG DOPT 7 25 index space 12 Administrative Products for DB2 Installation Guide ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 INDEXES DOPT 6 16 INDEXPA DOPT 6 16 INDEXST 6 16 INDEXST DOPT 6 16 INFOBMC command 7 6 INI ACV example 4 23 Install System generating JCL 2 22 international language support 1 10 migrating DB2 objects 2 26 running 2 14 specifying user options 2 19 starting 2 10 unloading 2 6 user options 2 22 installation adding a product 9 14 backing out 2 27 cancelling 2 6 2 27 checkpoints 1 9 client 9 5 client files 9 12 custom 1 10 data sets 1 18 default options DOPTs 1 20 Full 1 14 image copying 9 8 JCL 2 22 Maintenance 1 14 modes 1 10 multiple products 3 2 Multiple SSID 1 17 multiple tapes 1 9 paths 1 10 prerequisites 9 2 quick 1 10 requirements 1 3 requirements client 9 3 resuming 1 9 silent clients 9 9 SSID 1 15 starting over 1 9 tasks 2 2 troubleshooting client 9 12 BMC Software Inc Confidential and Proprietary Information types 9 5 uninstalling client 9 15 uninstalling client silently 9 16 user profile 1 19 verification procedure 4 20 4 45 verifying 4 20 4 45 installation considerations ALT
128. Chapter 8 Installing DASD MANAGER PLUS 8 1 Overview Overview This chapter provides information about how to prepare to install the BMC Software DASD MANAGER PLUS for DB2 product The DASD MANAGER PLUS product is a comprehensive database management tool that supports DB2 Version 3 1 and later DASD MANAGER PLUS e gathers stores and analyzes statistics in a production environment e monitors changes in the database e automates utility execution based on the condition of the data e estimates space requirements e features support for DB2 Version 5 1 e produces numerous analytical and statistical reports on DB2 objects DASD MANAGER PLUS gathers and analyzes statistics with BMCSTATS which collects all the statistics collected by RUNSTATS and STOSPACE plus many others that can be helpful in administering a database The statistics that BMCSTATS collects are maintained in a historical database in which each entry is time stamped The historical database makes possible trend analysis of DB2 object activity If installed the LOADPLUS or REORG PLUS utilities can also provide statistics to the BMCSTATS database DASD MANAGER PLUS automates utility execution through BMCTRIG an analysis tool that examines the BMCSTATS database for almost two dozen exception conditions such as number of extents When conditions reach or exceed the trigger values that you specify DASD MANAGER PLUS can automatically build and submit the appropriate utility jo
129. D installation process duplicates the installation of the selected products for each additional DB2 subsystem This duplication involves assembling default options creating tables and synonyms and binding plans on the additional DB2 subsystems All of the considerations that apply to the SSID installation path also apply to the Multiple SSID installation path See Considerations on page 1 16 BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 17 Installation Data Sets Name Propagation In addition subsystem characteristics must be similar for all of the DB2 subsystems in the multiple SSID model Installation parameters for subsequent subsystems cannot differ significantly from the initial installation process However the following installation information can differ between subsystems e job card information e library name for the generated batch jobs e DB2 LOAD and EXIT library names e authorized program facility APF library name e DOPTs names only for BMC Software administrative products e STOGROUP names e VSAM catalog VCAT names including VCAT volume and DASD type You can easily propagate the names for multiple subsystem installations if the name or part of the name differs only by the DB2 SSID To propagate a name that includes the SSID substitute the special identifier for that part of the name that represents the SSID during the initial Full or SSID
130. DBRMLIB DD statement in these members 3 Submit the BIND jobs 4 Repeat for the next product if applicable Interacting with Other BMC Software Products If you have any of the BMC Software Utilities products or the Backup and Recovery products the Install System enables all the Administrative Products to interact with those products The following sections provide additional steps you must follow to allow the products to interact with each other Note If you merged the different product tapes during the unload of the Install System and you associated the products on the Install System Product to Product Interface Panel the Install System performs these additional steps for you If you are installing products from different distribution tapes without merging the tapes be sure to install the Utilities products and the Backup and Recovery products before you install the Administrative Products ALTER and CHANGE MANAGER ALTER and CHANGE MANAGER can interact with the BMC Software Utilities BMCUTIL and BMCSYNC tables to provide STARTOVER capability For example while you are performing a reorganization by using the BMC Software REORG PLUS utility from the CHANGE MANAGER product you receive an error and the utility stops running You can request a STARTOVER that deletes the utility ID in the BMCUTIL and BMCSYNC tables before proceeding with the reorganization If the CHANGE MANAGER synonyms do not point to the correct tables you must
131. Defines the default secondary space allocation in cylinders for RECVnnn recovery data sets Defines the default unit that is used for creating RECVnnn recovery data sets Indicates whether to generate reorganizations in worklists for operations which require reorganizing table spaces and indexes Changes to attributes such as PRIQTY SECQTY PCTFREE FREEPAGE and VOLUME for VCAT defined partitions can cause placement of reorganization commands in the worklist If reorganizations are to be generated this option also indicates whether to use the BMC Software REORG PLUS product in place of the IBM REORG utility B Generate BMC reorganizations in worklists I Generate IBM reorganizations in worklists N Do not generate reorganizations in worklists default The name of the CHANGE MANAGER plan that is used to generate reports The default data set for diagnostic messages for Analysis This option may be a sequential data set the keyword SYSOUT or TERM terminal If you use SYSOUT the diagnostic messages are written to the JES SPOOL If you use TERM the diagnostic messages are written to your terminal The default data set for diagnostic messages for Execution This option may be a sequential data set or the keyword SYSOUT If you use SYSOUT the diagnostic messages are written to the JES SPOOL Defines the sequence number increment for worklists and CDL files The STEPLIB library that contains the BMC Software load modules SL2
132. ER 5 3 CATALOG MANAGER 6 3 CHANGE MANAGER 7 5 DASD MANAGER PLUS 8 3 installation default modules multiple 3 16 3 17 prdDOPDI1 3 16 single 3 16 3 17 installation default options xnnDOPT member 1 20 HLQ JCL 1 20 refreshing 3 13 installation defaults ALTER 5 3 CATALOG MANAGER 6 3 CHANGE MANAGER 7 5 DASD MANAGER PLUS 8 3 installation modes custom 1 10 quick 1 10 installation path determining maintenance level 1 12 determining path 1 12 determining product status 1 11 determining release level 1 12 determining version level 1 12 Full installation 1 14 initial Maintenance 1 15 Maintenance installation 1 14 Multiple SSID 1 17 SSID Installation 1 15 subsequent Maintenance 1 15 installation user profile HLQ INSTALL 1 19 HLQ JCL 1 19 ISPF profile data set 1 19 ISPPROF 1 19 output JCL data set 1 19 reusing 1 19 searching for 1 19 XXXXPROF 1 19 Index 13 installation space requirements ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 installing clients from a command line interface 9 9 locally 9 6 silently 9 9 installing maintenance product authorization A 8 interaction ALTER with BMC Software Utilities 3 6 BMC Software Utilities with DASD MANAGER PLUS 3 9 CATALOG MANAGER with BMC Software Utilities 3 7 CHANGE MANAGER with BMC Software Utilities 3 6 DASD MANAGER PLUS with BMC Software Utilities 3 9 SQL Explorer with DASD MANAGER PLUS 3 11 international language support 1 10 IPNAMES DOPT 6 16
133. Enabling the Product CLISTs Enabling the Product CLISTs Summary This section describes the steps that you must perform to enable the product CLISTs Step 1 Make the product CLISTs available for execution Administrative Products are shipped with CLISTs From the Install System dialog you were prompted to indicate whether to use the ALTLIB command to make these CLISTs available for execution If you decided not to use the ALTLIB command copy the CLISTs from the HLQ CLIST library to a library in your SYSPROC concatenation or add the HLQ CLIST library to your SYSPROC concatenation BMC Software products that are installed with different high level qualifiers that is products that are installed individually and that may reside in different libraries can be accessed from a single BMC Software supplied ISPF interface The Administrative Products for DB2 require you to integrate their ISPF dialog into your ISPF system The Install System generates a BMC Software supplied ISPF interface based on the options and products that you specify during installation The Install System then generates a CLIST BMCDB2 and a panel BMCDB2PR This CLIST and panel are generated in the HLQ JCL library If you want to invoke the BMCDB2 CLIST implicitly copy the CLIST to a CLIST library that is normally allocated to your TSO session Step 2 Edit the BMCDB2 CLIST If you install the products individually using the same installation data set the
134. F F FF F KF F END LKED SYSIN DD NAME ACMDOPD1 R _ Note The R in the variable syntax indicates that the value specified will refresh the existing value of the variable in the user s ISPF profile data set if the timestamp of the DOPTS is later than that in the user s ISPF profile member Default Option Descriptions This section describes the DOPTs listed in Figure 7 1 on page 7 15 In some cases the default value for the option is listed ACTDOPT ACTDOPD1 The name of the CATALOG MANAGER product s DOPTs module that the GUI for CHANGE MANAGER will use to interact with CATALOG MANAGER This parameter is used only if CATALOG MANAGER is installed ACVPLAN ACVyrmDM The main DB2 plan for the GUI for CHANGE MANAGER ALLOC N The allocation units to use for data sets that are managed by System Managed Storage SMS If the AMS is set to Y then this option determines how ALTER and CHANGE MANAGER allocate space for VCAT defined DB2 objects that SMS manages The DOPTs parameters are as follows C cylinders K kilobytes M megabytes BMC Software Inc Confidential and Proprietary Information 7 18 Administrative Products for DB2 Installation Guide Default Option Descriptions N SMS not in use default T tracks AMS Y Controls whether Analysis will by default generate AMS statements IDCAMS DELETE and CREATE in the worklist You can use the INCLUDE AMS keyword to override this value An entry
135. F profile data set has at least one free directory block If you do not have at least one free directory block the PROFILE NOT LOADED message or an ISPF STOW error message is displayed and the Install System dialog panel terminates e Run the IBM RUNSTATS utility on the DB2 catalog BMC Software Administrative Products use Structured Query Language SQL to access the DB2 catalog If you run the RUNSTATS utility up to date statistics are available to the DB2 Optimizer when it determines access paths that could improve performance e The Install System uses the ZUSER symbolic to create temporary data sets for the installation process and to identify the installer in the comments of the installation JCL If you prefer to use ZPREFIX instead of ZUSER you must edit member HLO INSTALL DCIC0000 In member DCIC0000 find the keyword UNCOMMENT and follow the instructions that are provided in the member e Ifyou are using the Full installation path for a product specify a synonym qualifier to own all of the product s synonyms Each BMC Software product that accesses DB2 tables uses its own set of synonym names to access its own DB2 tables and the DB2 catalog tables These synonyms are created by the Install System The Install System online dialog panel prompts you to specify synonym qualifiers BMC Software Inc Confidential and Proprietary Information 2 10 Administrative Products for DB2 Installation Guide To Start the Ins
136. FERUIX N Names the three default DBRM libraries Includes the LIBRARY parameter on the BIND statement for plans and packages Y or N Note A disadvantage to adding the LIBRARY parameter to the BIND PLAN command is that the order of the libraries on the BIND could be incorrect If some DBRMs are present in multiple libraries ALTER and CHANGE MANAGER cannot guarantee that the concatenation will result in every DBRM coming from the correct library For DB2 Version 5 and later enables ALTER and CHANGE MANAGER to create unique indexes with the DEFER YES parameter Y or N BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 23 Default Option Descriptions DISCARDS nnnn EAP AEXvrmHA EIP DCIINSTL ENVP CMvrmcDE EPP AEXvrmHM EURO N FEP CMvrmcDF GLID id Used by ALTER and CHANGE MANAGER to specify the number of discard data sets to allow The parameter nnnn specifies the number of discards in a range from 0 to 9999 DISCARDS 0 means that no maximum number of discards exists If the DISCARDS option is set to 1 the product will generate one SYSDISC file for the entire run and DISCARDS 1 is generated as a LOAD parameter This action will cause the load utility to terminate with a return code of 8 if any records must be discarded If the DISCARDS option is set to anything other than 1 a different discard file will be generated for each LOAD and DISCARDS n will be gener
137. From Here 2 28 BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 1 Getting Started Getting Started Table 2 1 lists the tasks that you must perform to install BMC Software products Complete the tasks in the order that they are presented using the References column to direct you to the location of the task instructions Table 2 1 Getting Started with the Install System References Perform preinstallation tasks These tasks include See Chapter 3 Performing Additional Installation gathering the information that you need to Tasks configure the products that you choose to install See the product chapters in this book backing up your current system See Install System for MVS Related Products ensuring that everything on your system is ready Helpful Tips accessible from the Web at for the new products http www bmc com support html If you receive your software electronically you must See Processing an ESD Image on page 2 3 process the Electronic Software Distribution ESD image If you receive your software on a distribution tape you See Unloading the Install System on page 2 6 must unload the Install System application from that tape Run the Install System CLIST to start the Install See Starting the Install System on page 2 10 System Specify your user options for the Install System See Specifying User Options on page 2
138. HANGE MANAGER Execution Plans The following plans are used by the Execution component AEXvrmHA Execution Monitor Entry Authorization EXECUTE authority on this plan allows users to execute a worklist You should therefore carefully consider who receives authorization to use this plan AEXvrmHM Execution Monitor This plan does not control who has authorization to execute a worklist It does however provide users with the ability to attach to DB2 with alternate authorization IDs for the AUTH commands Since this plan does not affect who can run Execution you may grant PUBLIC authority to this plan The Execution plan contains some packages that use dynamic SQL Some of these packages will cause long running SQL and may need to be added to your RLST The packages are described as follows e AEXAUNLD is the package that does the unload of data from tables e AEXSQLIO is the package that does all worklist SQL commands including deletions before a data only migration LOAD e AEXESTDL is the package that does some of the restart logic before the restart of a LOAD including the deleting of previously loaded rows By restricting authorization to run the Execution plans you can control what change and migrate functions users can perform Giving wide access to Specification and Analysis while controlling access to the Execution Monitor Entry lets your users run CHANGE MANAGER for training purposes or use it as a system diction
139. How Products Are Licensed Product Maintenance or Version Upgrades A 8 Installing a new maintenance level or upgrading the version or release level of a product has no effect on product authorization No new passwords are required However you must ensure that your authorization tables reside in the new production libraries If you install products in a test environment before moving them to production the product authorization tables must also reside in the test libraries If you try to run the product on a different CPU that CPU must also be licensed Copy the product authorization tables from the old library to the new library that contains the products new maintenance or upgrade To copy the tables from the old library to the new library use the job prdCPUID where the variable prd is the three character product code Although the product authorization tables typically reside in the product s load library these tables are not load modules If you are running ISPF 4 2 or later you may not be able to copy these tables by using the ISPF Move Copy utility option 3 3 You could receive a STOW error or one or more of the following error messages H INTIFIED BY EW2515W 4731 DIRECTORY ENTRY FOR prdTBL3n I DDNAME ISPddname IS NOT MARKED AS LOAD MODULE HO Ti TEW2522E 470E MEMBER praTBL3n IDENTIFIED BY DDNAM ISPddname IS NOT A LOAD MODULE INVALID RECORD TYP T GI Q
140. IAL NUMBER lt nnnnn gt MODEL NUMBER lt mmmm gt PRESS ENTER TO CONTINUE Explanation The Replace password has been processed The CPU with the serial and model numbers indicated is now authorized to use this product System Action None User Response None Information only BMC89130I PROCESSOR SERIAL NUMBER lt nnnnn gt MODEL NUMBER lt mmmm gt WAS SUCCESSFULLY MODIFIED IN THE PRODUCT AUTHORIZATION TABLE PRESS ENTER TO CONTINUE Explanation The Modify password has been processed The product authorization table has been modified for the CPU with the serial and model numbers indicated System Action None User Response None Information only BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 17 Error Messages BMC Software Inc Confidential and Proprietary Information B 18 Administrative Products for DB2 Installation Guide Index Symbols I98DROP 2 24 xnnBNDI 2 26 xnnCOPY 2 26 xnnDOPT 3 16 xnnINST 2 26 xnnMIG 2 26 A ACTDOPT DOPT 5 12 7 18 ACTvrmDE Data Editor plan 6 5 ACTvrmDH Utility Status Display plan 6 5 ACTvrmDK Command Generation and Execution plan 6 5 ACTvrmDL Log Table maintenance plan 6 6 ACTvrmDM Display DB2 Catalog plan 6 6 ACTvrmDU Grant Authorities plan 6 6 ACVPLAN DOPT 5 12 7 18 ACVvrmDM Display Catalog plan 5 5 7 10 ADD Authorization for a Processor panel A 13 authorization message A 14 adding a
141. ID TO A NEW TABLE BUT SERIAL NUMBER AND MODEL NUMBER WERE NOT SPECIFIED Explanation The CPU serial number and the model number are required before the password can be processed System Action The password is not processed User Response Add the CPU ID and the model number and resubmit the job BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 15 Error Messages BMC89123E BMC89124E BMC89125E BMC89126E PERMANENT PRODUCT AUTHORIZATION TABLE IS INVALID PLEASE CONTACT BMC PRODUCT SUPPORT Explanation An error invalidated the product authorization table The table must be rebuilt System Action All functions are suppressed User Response Contact BMC Software Product Support for assistance TEMPORARY PRODUCT AUTHORIZATION TABLE IS INVALID PLEASE CONTACT BMC PRODUCT SUPPORT Explanation An error invalidated the product authorization table The table must be rebuilt System Action All functions are suppressed User Response Contact BMC Software Product Support for assistance THIS PASSWORD IS NO LONGER VALID IT CANNOT BE USED TO ACTIVATE OR CHANGE YOUR PRODUCT LICENSE PLEASE CONTACT YOUR BMC SALES REPRESENTATIVE Explanation The password has expired System Action The password is not processed User Response Contact your BMC Software sales representative or BMC Software Product Support for assistance I O ERROR WHILE ATTEMPTI
142. Installation Considerations CM PILOT provides diagnostic output that contains information from the processing of the CM PILOT worklist If the Task ID contains DML an informative DML report is included in the diagnostic output If you are using DML and want to evaluate impacts to data structures before actually executing the steps in a Script you can optionally produce a DML trial report The CM PILOT worklist will then contain only the necessary commands to analyze the DML and produce the report Installation Considerations When you use the Install System to install the Administrative Products for DB2 the installation process generates a customized installation data set This data set contains customized jobs that are created to install these products into your specific DB2 environment One of these jobs is used to establish the default processing option values The job name begins with a character followed by a three character identifier that varies depending on which Install System installation path that you used The last four characters are always DOPT The xnnDOPT member of the installation data set contains an assembly language program with an options macro call that establishes the default processing values You can tailor the installation of the product including changing plan names by editing the default values in the xnnDOPT member Installation Defaults During installation you can specify names for options modules
143. Installation Guide STATAUTH 8 12 SWPS 8 12 SWSS 8 12 SWU 8 12 SYSCMAX 8 13 SYSCMAXU 8 13 SYSCPREF 8 13 SYSCPS 8 13 SYSCSS 8 13 SYSCUNIT 8 13 SYSRMAX 8 13 SYSRMAXU 8 13 SYSRPREF 8 13 SYSRPS 8 13 SYSRSS 8 13 SYSRUNIT 8 13 SYSTYPE 8 13 SZDEVT 8 13 TAPE 8 13 TAPE2 8 13 TAPE3 8 13 TIMEPARM 8 14 WDC 8 14 WDSN 8 14 WMC 8 14 WPS 8 14 WSC 8 14 WSS 8 14 WU 8 14 XPLAN 8 14 ZPLAN 8 14 DASD MANAGER PLUS plans AEXvrmDA 8 6 AEXvrmDM 8 6 ASUvrmDC 8 5 ASUvrmDD 8 5 ASUvrmDJ 8 5 ASUvrmDR 8 5 ASUvrmDS 8 6 ASUvrmDX 8 6 ASUvrmDZ 8 6 DASDMAN DOPT 5 15 7 23 data sets ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 installation 1 18 DATABAS DOPT 6 13 DATACLAS DOPT 5 15 7 23 data sharing members 4 7 DATATYP DOPT 6 13 DATE DOPT 5 15 7 23 8 10 DB2 migrating to Version 5 3 35 migrating to Version 6 3 30 secondary authorizations for MVS Server 4 44 DB2 structures dropping 2 24 DB2CAT DOPT 5 15 7 23 8 10 DB2CT DOPT 5 15 6 13 7 23 DB2LO DOPT 6 14 DBAUTH DOPT 6 14 DBCS DOPT 6 14 DBRM data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 DBRM DOPT 6 14 DBRMI DOPT 5 15 7 23 DBRM2 DOPT 5 15 7 23 DBRM3 DOPT 5 15 7 23 DBRMLIB DOPT 5 16 7 23 DCB attributes authorization table library A 7 DCI ACTU 3 8 DCI AEXU 3 7 3 11 DCI ASUC 3 10 DCI ASUL 3 10 DCI ASUR 3 10 DCI PSSD 3 12 default option descriptions ALTER 5 12 CATALOG MANAGER 6 11 CHANGE MANAGER
144. KKKKKKKKKKKKK Bottom of data KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel BMC Software Inc Confidential and Proprietary Information A 24 Administrative Products for DB2 Installation Guide Displaying Product Authorization Additional Information Table A 5 describes the information that the Product Authorization Display panel provides Table A 5 Field Descriptions for the Product Authorization Display Panel Field Description Load library name of the product s load library Product code code that BMC Software assigns to the product Last changed mm dd yy hh mm Last changed by Grace period ends mm dd yyyy Temporary expiration date mm dd yyyy date and time that the product authorization tables were last modified The variables are as follows mm represents the month in the range 01 12 e ddrepresents the day in the range 01 31 e yy represents the year in the range 00 99 e hh represents the hour in the range 00 23 e mm represents minutes in the range 00 59 user ID or job that requested the modification date when the grace period if triggered will end The variables are as follows e mm represents the month in the range 01 12 e ddrepresents the day in the range 01 31 e yyyy represents the year in the range 0001 9999 Note This line appears only if the failure mode is phased and the grace period
145. KKKKKKKKKKKKKKKAKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK MODULE UNCTION OPYRIGHT EVEL E C I F Xx F F F x ASU 8 8 UNCTIONS KKKKKKKKKKKKKKKKKK DOPTS SALUDOPT PRODUCT DASD MANAGER ASUDOPD1 DASD DEFAULT OPTIONS COPYRIGHT BMC SOFTWARE INC 2001 RELEASE 6 1 March 2001 DEFINE THE DEFAULT PROFILE VARIABL DATE amp SYSDATC SSID DBDB R DB2CAT DBDBCAT R SYSTYPE S L2 L4 te Los iy JC1 amp amp USERID amp amp JOBCHAR JOB ACCT JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 SL1 BMCADMN V613 SL2 SYS3 DBDB DSN SL3 SYS2 DB2V61M SL4 S T GI wn KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK D61 LOAD R EXIT R DSNLOAD R amp amp PGMR JC3 NOTIFY amp amp USERID dC4 tft JC5 WDSN amp amp PREFIX amp amp SSID amp amp WKID WU SYSDA WPS 10 WSS 2 WDC WSC WMC JDSNE amp amp PREFIX EXEC amp amp WKID SWU SYSDA SWPS 10 SWSS 2 SYSRPREF amp amp PREFIX amp amp WKID SYSRUNIT SYSDA SYSRPS 10 SYSRSS 2 SYSRMAX SYSRMAXU SYSCPREF amp amp PREFIX amp amp SSID amp amp OBNOD SYSCUNIT SYSDA SYSCPS 10 SYSCSS 2 SYSCMAX SYSCMAXU RECVUNIT SYSDA RECVPS 10 RECVPREF amp amp PREFIX amp amp SSID
146. KKKKKKKKKKKKKKKKKKKKKKKKKK APPCPCLM MODEENT LOGMODE APPCPCLM i RUSIZES X 8787 SRCVPAC X 00 SSNDPAC X 01 KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKKKKKK TITLE APPCHOST KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE AS LU 6 2 DEVICES FOR HOST TARGET IN THIS EXAMPLE RU SIZE OF 4096 IS USED KKKKKKKKKKKK APPCHOST MODEENT LOGMODE APPCHOST RUSIZES X 8989 SRCVPAC X 00 SSNDPAC X 01 MODEEND END Step 2 Define the local LU to VTAM A VTAM application APPL definition statement in SYS1 VTAMLST OF ACTING KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK defines an APPC MVS local LU to VTAM This definition must be made by the person who is responsible for implementing VTAM network changes for the MVS system BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 31 Setting Up the MVS Server 4 32 Step 3 The APPL statement e names the local LU e identifies the local LU as a type 6 2 e sets the default parameters for the LU e specifies the name of the logon mode table that contains the logon modes that the LU uses To ensure the use of subtasking verify the VTAM LU definition DSESLM 10 The number 10 represents the number 16 in hex
147. L To enable the SEARCH command to work on the copy of the catalog that catalog indirection uses either run GRANT SELECT ON TABLE statements or bind with Dynamic Rules BIND on the main plan Considerations for Using Views of the Catalog To control access to sensitive information in your catalog tables you must design a view or a set of views on your system catalog that achieves the control that you need To define the view that a particular catalog indirection access method uses you must edit the CREATE VIEW statements in the BMCCVIEW member that the Install System generated You must also add to the BMCCVIEW member the DML search criteria that limits access to selected rows of the catalog When a user attempts to access catalog information that a view filters out an SQL error occurs Also you must manage the authorizations to the groups of users who are allowed to access the DB2 catalog through a view or views Implementing Catalog Indirection Implementing catalog indirection e uses existing product libraries e allows use of your own VSAM data sets which requires Custom mode e optionally creates a copy of the DB2 catalog using the CREATE LIKE DDL syntax e optionally creates views of the DB2 catalog BMC Software Inc Confidential and Proprietary Information 3 20 Administrative Products for DB2 Installation Guide Using Catalog Indirection Catalog indirection is divided into two tasks e installation e maintenance
148. LIST 3 3 3 14 3 15 3 16 3 22 4 4 BMCDB2C variable 4 5 BMCDB2P variable 4 5 BMCDB2T variable 4 6 Catalog Browser 4 11 CONTAB command 4 20 GENERATE variable 4 5 4 19 GENTABLE variable 4 5 performance 4 5 4 19 MCDB2C variable 4 5 MCDB2P variable 4 5 MCDB2P2 panel 4 5 4 19 MCDB2PR panel 4 4 SSID list 4 19 BMCDB2T variable 4 6 BMCDB2TB panel 4 5 4 20 BMCLOAD DOPT 5 14 7 21 B B B B B B MCMSG CLIST 4 13 4 20 MCSTATS DOPT 5 14 7 21 BMCUNLD DOPT 5 14 7 21 BOPTS DOPT 6 12 BPOOLIX DOPT 5 14 7 21 BPOOLTS DOPT 5 14 7 21 BRPTDIAG DOPT 7 21 BRPTDSN DOPT 7 21 C Catalog Browser 4 11 catalog indirection GRANT 3 20 ISPF interface considerations 4 8 overview 3 17 CATALOG MANAGER BMC Software Utilities interface 3 7 catalog indirection considerations 3 22 6 3 collection nicknames 3 26 6 4 BMC Software Inc Confidential and Proprietary Information 4 Administrative Products for DB2 Installation Guide controlling access 6 5 default option descriptions 6 11 default option listing 6 6 default options processing 6 4 DOPTs 6 6 installation considerations 6 3 installation defaults 6 3 menu parameter 4 11 overview 6 2 plans 6 5 post installation tasks 4 3 product description 6 2 space requirements 1 6 CATALOG MANAGER data sets CLIST 1 6 CNTL 1 6 DBRM 1 6 LOAD 1 6 MLIB 1 6 MSGS 1 6 PLIB 1 6 SLIB 1 6 TLIB 1 6 CATALOG MANAGER DOPTs ADSN 6 11 ALLC 6 11 AOPTS 6 11 AUDIT 6 11 AUXRELS 6 11
149. LL represents an older release of the install library and BMC latest INSTALL represents the most recent release of the install library Step 3 Run the job to unload the installation libraries into File 1 and File 2 Step 4 Ifyou list the BMC Software products in the link list check the concatenation of the data set with the most recent release of the SAS C library Ensure that the most current library is concatenated before any data sets that contain older SAS C releases This process is especially important if you use products from other vendors who also distribute the SAS C transient library BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 9 Starting the Install System Starting the Install System Summary After you unload File 1 and File 2 from the distribution tape you must run a CLIST to access the Install System You can run the CLIST from the TSO Commands Utility panel This panel is displayed if you choose the Command option from the ISPF PDF Primary Option menu You can also run the CLIST from any ISPF command line Note In this procedure the variable HLQ is the high level qualifier that you assigned to the INSTALL data set when you unloaded the tape Before You Begin Before you start the Install System complete the following tasks e Unload the Install System as instructed in Unloading the Install System on page 2 6 e Verify that the installer s ISP
150. LOG MANAGER Collection Nicknames 6 4 CHANGE MANAGER Installation Default Values 7 5 DASD MANAGER PLUS Installation Default Values 8 3 System Software Requirements 9 2 Client Installation Options 9 5 Client Installation Directories 9 12 Permanent Password Functions A 4 Password ScenarioS 0 cece eee nen eens A 9 Product Authorization Work Sheet 000 eee eee eee A 10 Product Authorization Primary Menu Options A 12 Field Descriptions for the Product Authorization Display Panel A 25 Control Statement Keywords 0 0 c eee eee eee ee A 29 Message Severity Codes B 3 BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide About This Book This book contains detailed information about the Administrative Products for DB2 It is intended for use by the system programmer or database administrator DBA who will install the following BMC Software products from the Administrative Products for DB2 distribution tapes or CD e ALTER e CATALOG MANAGER e CHANGE MANAGER e DASD MANAGER PLUS e UTILITY MANAGER To use this book you should be familiar with DB2 Multiple Virtual Storage MVS systems Job control language JCL and the Interactive System Productivity Facility ISPF How This Book Is Organized This book is organized as follows In addition an index appears at the
151. LOG N SL1 BMCADMN V621 D61 LOAD R Gi bi bd DO DO F HF peli e pes SL2 SYS3 DBDB DSNEXIT R SL3 SYS2 DB2V61M DSNLOAD R SLAS t Ships T t ISPSLIB BMCADMIN V621 D61 SLIB R TSOSX N JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 JC3 NOTIFY amp amp USERID JC4 JC5 DBRM1 DBRM2 DBRM3 DBRMLIB N WU SYSDA WPS 10 WSS 2 WDC WSC WMC SWU SYSDA SWPS 10 SWSS 2 WDSN amp amp PREFIX amp amp SSID amp amp WORKID WLU SYSDA WLPS 15 FF F F FF F FF FF F F FF F F FF F F FF F F FF FF F F FF F F FF F F FF F F FF F F KF OF BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 9 Default Option Listing DOPTs Figure 5 1 ALTER Default Options Listing Part 2 of 3 WLSS 5 JDSN amp amp PREFIX ANALYSIS amp amp WORKID JDSNE amp amp PREFIX EXEC amp amp WORKID JDSNBG amp amp PREFIX JCLGEN amp amp WORKID SDSN SYSOUT SDSNE SYSOUT CATAUDIT N R CATRECOV N R SYSRPREF amp amp PREFIX amp amp SSID amp amp WORKID8 SYSRUNIT SYSDA SYSRPS 10 SYSRSS 2 SYSRMAX SYSRMAXU SYSCPREF amp amp PREFIX amp amp SSID amp amp OBNOD SYSCUNIT SYSDA SYSCPS 10 SYSCSS 2 SYSCMAX SY
152. MANAGER use synonyms that point either to a copy of the DB 2 catalog or to user created views of the catalog BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 17 Using Catalog Indirection Catalog indirection applies only to catalog queries Any action that changes information in the catalog must operate on the actual catalog not the catalog s copy or view For example when you issue a command through CATALOG MANAGER to update the catalog the action affects the actual catalog In contrast the ALTER and CHANGE MANAGER Analysis programs can use either the actual catalog or catalog indirection when creating worklists However the Execution Monitor in ALTER and CHANGE MANAGER always runs a worklist against the actual catalog Note Successful implementation of catalog indirection requires an in depth understanding of the DB2 environment and its catalog structure and experience in maintaining DB2 applications Each method of implementing catalog indirection should be managed as if it were a DB2 application General points about catalog indirection are as follows e The synonyms that reference the DB2 catalog are hard coded in the Administrative Products You direct the synonyms to the catalog copy or views during installation by providing information on the Install System panels e When you install Administrative Products with the Install System the product is set up
153. MC Software Inc Confidential and Proprietary Information 9 4 Administrative Products for DB2 Installation Guide Selecting the Type of Installation Verifying Server Networking To meet the specific needs of your site you can select from the types of client installations that are shown in Table 9 2 Table 9 2 Client Installation Options Installation Option install to a local hard drive copy the installation image to a network drive and then install the client to the local hard drive silent installation from a command prompt Description and Benefit installs the specified products to a local hard drive After the products are installed you can remove the CD from the CD ROM drive copies an image of the installation from the CD to a resource from which other users can install the client to their local hard drive installs the client from a command prompt with minimal user interaction See Section Installing a Client to Run Locally on page 9 6 Installing the Client on a Network Drive on page 9 8 Installing a Client to Run Locally on page 9 6 Installing a Client Command Line Interface on page 9 9 install using distribution software installs the client to every workstation to which you have access without the need to leave your computer BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER
154. MCDB2 CLIST DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME ALU xxxx D ALUDOPD1 ALvrmDDF ALU ASU xxxx D ASUDOPD1 ASUvrmDC ASU ACT xxxx D ACTDOPD1 ACTvrmDM ACT ACTvrm_D_MAIN DBBF ACM xxxx D ACMDOPD1 CMvrmEDF ACM BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 15 Refreshing Default Options In the sample shown in Figure 3 1 the variable xxxx is the SSID name and is a unique one byte character such as A for the first SSID B for the second SSID C for the third and so on Catalog Indirection Default Options When accessing the DB2 catalog with catalog indirection the BMCDB2 CLIST allocates an indirect DOPTs module This indirect DOPTs module must have a different name than the direct DOPTs module that was previously built The exception is CATALOG MANAGER which uses a single DOPTs module for both direct and indirect access For more information about catalog indirection refer to Using Catalog Indirection on page 3 17 Single and Multiple Installation Default Modules The module prdDOPD1 where prd is the product code establishes default processing options for a particular product You can generate one DOPTs module for all of a product s SSIDs to share or you can generate customized DOPTs modules for each SSID Because you can override many of the default processing option parameters for Admini
155. MS Y Controls whether Analysis will by default generate AMS statements IDCAMS DELETE and CREATE in the worklist You can use the INCLUDE AMS keyword to override this value An entry of N generates a worklist STOP command that allows you to complete the DELETEs and DEFINEs before the CREATEs that are located later in the worklist Y or N ANP ALyrmcDA Defines the Analysis plan name ARCHPPREF amp amp USERID amp amp SSID The high level qualifier or prefix for data sets that is used for a BMC Software utility archive ARCHPS 10 The primary space allocation in cylinders for BMC Software utility archive data sets ARCHSS 2 The secondary space allocation in cylinders for BMC Software utility archive data sets ARCHUNIT SYSDA The default UNIT that is used for BMC Software utility archive data sets BMC Software Inc Confidential and Proprietary Information 5 12 Administrative Products for DB2 Installation Guide ASUDOPT ASUDOPDI1 ATTN Y AUTHSW N BLDBS N Default Option Descriptions The name of the DASD MANAGER PLUS product s DOPTs module that the GUI for ALTER will use to interact with DASD MANAGER PLUS This parameter is used only if DASD MANAGER PLUS is installed Allows you to press the ATTENTION key to interrupt processing when ATTN Y This option allows you to stop processing for example when building a Mixed List in ALTER or CHANGE MANAGER Y or N Controls the method of authorization ID switching th
156. NAGER e the compilation of the Skeleton Library SLIB members that are customized during the installation for the JCL Generation component e the process for upgrading from ALTER to CHANGE MANAGER e the removal of unnecessary icons from the PATROL DB Admin Client program group for the GUI clients This installation guide provides documentation for the following products e ALTER for DB2 version 6 2 01 e CATALOG MANAGER for DB2 version 6 2 01 e CHANGE MANAGER for DB2 version 6 2 01 e DASD MANAGER PLUS for DB2 version 6 1 02 e SQL Explorer for DB2 version 3 1 03 e UTILITY MANAGER for DB2 version 1 2 BMC Software Inc Confidential and Proprietary Information xxii Administrative Products for DB2 Installation Guide Version 1 6 50 and Version 1 6 10 Controlled Availability May 31 2000 This installation guide provides support for the BMC Software Install System Enhancements for version 1 6 50 and 1 6 10 of the Install System include e support forall DB2 Version 6 tables and indexes for Catalog Indirection for the BMC Software ALTER for DB2 CHANGE MANAGER for DB2 and CATALOG MANAGER for DB2 products e the integration of the functionality of the BMC Software CM PILOT for DB2 product into CHANGE MANAGER e the integration of the functionality of the BMC Software PATROL DB Alter for DB2 product into ALTER e the integration of the functionality of the BMC Software PATROL DB Change Manager for DB2 product into
157. NG TO WRITE PRODUCT AUTHORIZATION TABLE DDNAME SYSLIB Explanation A write error occurred System Action All functions are suppressed User Response Verify that the data set name is correct and that the data set is partitioned If you are unable to resolve the problem contact BMC Software Product Support for assistance BMC Software Inc Confidential and Proprietary Information B 16 Administrative Products for DB2 Installation Guide Error Messages BMC89127I PROCESSOR WAS SUCCESSFULLY ADDED TO THE PRODUCT AUTHORIZATION TABLE YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON SERIAL NUMBER lt nnnnn gt MODEL NUMBER lt mmmm gt PRESS ENTER TO CONTINUE Explanation The Add password has been processed The product authorization table was modified to allow operation of this product on the CPU with the serial number and model numbers indicated System Action None User Response None Information only BMC891281 PROCESSOR SERIAL NUMBER lt nnnnn gt MODEL NUMBER lt mmmm WAS SUCCESSFULLY DELETED FROM THE PRODUCT AUTHORIZATION TABLE PRESS ENTER TO CONTINUE Explanation The Delete password has been processed This product can no longer be executed on the CPU with the serial and model numbers indicated in the message System Action None User Response None Information only BMC891291 PROCESSOR WAS SUCCESSFULLY REPLACED IN THE PRODUCT AUTHORIZATION TABLE YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON SER
158. Name BMCASUvr Creator Name BMCASUvr Collection Name ASUvrm_D_MAIN Implementing the QMF Report Feature If you want to use the QMF Report feature that is included with DASD MANAGER PLUS you will need to perform two additional steps to complete the installation You perform these steps outside the Install System dialog 1 Build views for the DASD MANAGER PLUS QMF reports To build the necessary views for the DASD MANAGER PLUS QMF reports supplied with DASD MANAGER PLUS invoke SPUFI and specify the HLQ CNTL data set and member ASURVIEW Note If you are installing DASD MANAGER PLUS on multiple DB2 subsystems execute this SPUFI job for each DB2 SSID where the DASD MANAGER PLUS QMF reports will be used 2 Import the DASD MANAGER PLUS QMF Reports into QMF e Edit all members of the HLO QMFPROC data set Change HLQ to the high level qualifier for DASD MANAGER PLUS data sets at your installation Change U to the user ID of the person who is running the QMF install e From QMF execute the following IMPORT PROC FROM HLO OMFPROC M LOADPROC Note The data set name should be typed in uppercase capital letters The IMPORT command can be executed either from the first panel of QMF or from the Query panel 3 Run the procedure by pressing F2 or by entering the RUN command This action IMPORTs all of the BMC Software supplied DASD MANAGER PLUS QMF reports BMC Software Inc Confidential and Proprieta
159. PLAN command is that the order of the libraries on the BIND could be incorrect If some DBRMs are present in multiple libraries ALTER and CHANGE MANAGER cannot guarantee that the concatenation will result in every DBRM coming from the correct library For DB2 Version 5 and later enables ALTER and CHANGE MANAGER to create unique indexes with the DEFER YES parameter Y or N Used by ALTER and CHANGE MANAGER to specify the number of discard data sets to allow The parameter nnnn specifies the number of discards in a range from 0 to 9999 DISCARDS 0 means that no maximum number of discards exists If the DISCARDS option is set to 1 the product will generate one SYSDISC file for the entire run and DISCARDS 1 is generated as a LOAD parameter This action will cause the load utility to terminate with a return code of 8 if any records must be discarded If the DISCARDS option is set to anything other than 1 a different discard file will be generated for each LOAD and DISCARDS n will be generated as a LOAD parameter for each LOAD step where n is the maximum number of discards This action will cause the load to terminate if the discard maximum is reached If fewer records are discarded the discard file will contain them and execution will proceed to the next step in the worklist Defines the Execution Authorization plan name which determines if a user is authorized to run Execution Defines the Installation plan name Defines the Env
160. Products for DB2 Installation Guide Determining Installation Paths Installation Paths Use Table 1 10 to determine the best installation path for the products that you plan to install Table 1 10 Selecting an Installation Path Product Installation Description Condition or Requirement Path Reference Never You are installing a BMC Software product Full See Full Installation on installed for the first time initial installation page 1 14 You completed the initial installation and subsystem ID See SSID Installation on now want to install the product on other SSID page 1 15 DB2 subsystems You want to share the or For Multiple SSID product libraries that were created during Multiple SSID installations see Multiple the initial installation SSID Installation on page 1 17 You completed the initial installation and Full See Full Installation on now want to install the product on other page 1 14 DB2 subsystems However you do not want to share the product libraries that were created during the initial installation Previously You are installing a new version or new Full See Full Installation on installed release of a BMC Software product for the page 1 14 first time initial installation You are installing maintenance updates and want to overlay your existing installation Maintenance See Maintenance Installation on page 1 14 You are installing mai
161. Proprietary Information Chapter 4 Performing Post Installation Tasks 4 39 Setting Up the SNA Gateway Server 5 C Select Users and Groups 5 D Double click the group Everyone 5 E Add the previously defined Local LU alias and Remote LU alias MSAUL100 and ACVLU01 respectively in Figure 4 21 on page 4 37 Step6 Specify the SNA Gateway Server Control Point Name by performing the following actions at the SNA Gateway Server console 6 A Select the SNA Gateway Server Admin Icon 6 B In the Servers and Connections window select the server 6 C From the Services menu choose Properties 6 D In the Server Properties dialog box specify the following items 1 Enter the Network Name This name is the same as the VTAM where the MVS Server resides 2 Enter the Control Point Name This name is the same as the CPNAME parameter for the PU definition in VTAM AUS3 in Figure 4 21 on page 4 37 See Step 1 on page 4 37 Where to Go from Here After you set up the MVS Server and the SNA Gateway Server you set up the client For more information see Setting Up the Client on page 4 41 BMC Software Inc Confidential and Proprietary Information 4 40 Administrative Products for DB2 Installation Guide Setting Up the Client Setting Up the Client Summary The third task in the APPC configuration process requires you to set up the client for the Database Administration products Before You Begin Before you set up the c
162. Provided that ALTER CHANGE MANAGER PATROL DB Alter or PATROL DB Change Manager still exists in toleration mode use the fallback procedures described for toleration mode and remove the product in exploitation mode Any data that you added while you were in exploitation mode will not be available in toleration mode As an alternative you can perform a Full installation of ALTER or CHANGE MANAGER 6 2E Then you will be operating in exploitation mode BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 31 Maintaining BMC Software Administrative Products Table 3 15 Migrating DB2 Version 5 to Version 6 Part 3 of 4 If You Are Then To Fall Back Then using CATALOG Migrate the DB2 catalog and perform a 1 Provided that the previous version of MANAGER at a Full installation of CATALOG MANAGER CATALOG MANAGER still exists version earlier than 5 4 04 6 2 Then you will be operating in exploitation mode remove the product in exploitation mode 2 Rebind all CATALOG MANAGER packages and plans for the previous version by using ACTssidP bind packages and ACTssidB bind plans where ssid is the subsystem ID Any data that you added while you were in exploitation mode will not be available in toleration mode using CATALOG MANAGER 5 4 04 or 5 4 05 Migrate the DB2 catalog 2 Rebind all CATALOG MANAGER packages and plans by using ACTssidP
163. R BMCCAT PRINT WDSN amp amp ZUSER BMCCAT WORK XDSN amp amp ZUSER BMCCAT SQLX SDSN amp amp ZUSER BMCCAT SQLS EDSN amp amp ZUSER BMCCAT SQLE DRG la O j J W po SE E a OP F F O F F O F F O F F O F F F F F F O F F FF F F O F KF F Es BY ie W po BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 7 Default Option Listing DOPTs Figure 6 1 6 8 DSN DSN DSN Cj Q UCOM DTS DTB HDAL DIX DSY HDVW DPL amp amp ZUSER BMCCAT ARCHIVE amp amp ZUSER BMCCAT SOL amp amp ZUSER BMCCAT UTILITY D Y Y N y N Y N UJC1 amp amp US OMD ACTCOMND Administrative Products for DB2 Installation Guide ERID ERID amp amp JOBCHAR JOB UJC2 CLASS A MSGCLASS X MSGL UJC3 NOTIFY amp amp USI A BDSN BMCADMN V621 D61 DBRM L ACCT EVEL UIC4 UIJC5 ULL1 SYS3 DBDB DSNEXIT ULL2 SYS2 DB2V61M DSNLOAD UBSTP BMCADMN V621 D61 LOA UCSTP BMCUTIL V62 LOAD URSTP BMCUTIL V62 LOAD UDSTP BMCUTIL V62 LOAD UESTP BMCUTIL V62 LOAD UKSTP BMCUTIL V62 LOAD UXSTP BMCADMN V621 D61 LOA UVSTP BMCUTIL V62 LOAD ULSTP BMCUTIL V62 LOAD UUSTP BMCUTIL V62 LOAD UPSTP BMCADMN V62
164. S Server on page 4 28 To Set Up the SNA Gateway Server Step 1 Define the APPC LU to VTAM To define the APPC LU in a VTAM major node you can define an LU with LOCADDR set to 0 and a LOGMODE parameter that supports APPC For the PU macro add the CPNAME parameter and set it equal to the Control Point Name value for the SNA Gateway Server see Step 6 on page 4 40 The example in Figure 4 21 defines an APPC LU named MSAUL 100 In this example the MVS VTAM system programmer has created a VTAM logon mode table called ACVAPPC with an APPC capable logon mode entry called APPCPCLM Figure 4 21 Sample APPC LU Definition for an SNA Gateway Server MSAUP100 PU ADDR 04 CPNAME AUS3 DLOGMOD N32702 PUTYPE 2 MAXDATA 1024 MAXOUT 7 MAXPATH 1 IDBLK 05D IDNUM B0927 x MM PI KM MK DI MSAUL100 LU LOCADDR 0 ISTATUS ACTIVE MODETAB ACVAPPC DLOGMOD APPCPCLM BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 37 Setting Up the SNA Gateway Server Step 2 Define a local APPC LU to the SNA Gateway Server by performing the following actions at the SNA Gateway Server console 2 A 2 B 2 C 2 D In the Servers and Connections window select the server From the Edit menu choose Insert Select APPC LOCAL Specify the following APPC LOCAL properties 1 Type the LU Alias and LU Name These properties are the same as those in the VTAM major node
165. SCMAXU ECVPREF amp amp PREFIX amp amp SSID amp amp OBNOD ECVUNIT SYSDA ECVPS 10 ECVSS 2 ECVMAX ECVMAXU RCHPREF amp amp USERID amp amp SSID RCHUNIT SYSDA RCHPS 10 RCHSS 2 EOI 050 PNT 00 S Y ALLOC N STORCLAS N DATACLAS N MGMTCLAS N JCLCLEAN N AUTHSW N R GLID DASDMAN Y R CCSID E R IXTYPE 2 R VVALPROP N R BPOOLTS BP0 BPOOLIX BP0 LOCK X DISCARDS 0000 R BMCSTATS N R BMCCOPY N R R R R R R R Posi tone Gey eee Z Q SR SE OP F O F UO FF F F FF F F FF F F FF F F ae O F F O aaae F F FF F a F F OO O F F O F F O F Oa O F KF F BMC Software Inc Confidential and Proprietary Information 5 10 Administrative Products for DB2 Installation Guide Figure 5 1 ALTER Default Options Listing Part 3 of 3 END LKED SYSIN DD NAME ALUDOPDI BMCCHECK N R BMCLOAD N R BLDCU N R BLDBS N R UTILCOPY N R UNLD N R RG N R LD I R DCOLL N EVT 3380 R TATS S R PDSTATS C R BLEALL N DEMPT Y STOPCOMM N R TABLEACC DDO1 R COPYDD02 N DDO1 N ECVDD02 N HSMVOL LOCATION TAPE1 CART TAPE2 TAPE TAPE3 TAPE ATTN Y ENVP AL621EDE FEP AL621EDF SPP AL621EDS A I S Q O amp amp Zi bo A D po T r eee ae iw Hi E zZ po 1 Il lt vol r 1 7 CT
166. SNA Gateway Server and setting up the client BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 27 Setting Up the MVS Server Setting Up the MVS Server Summary Before You Begin The first task in the APPC configuration process requires you to set up the MVS Server The MVS Server uses the APPC MVS Server Facilities introduced in MVS ESA SP 4 3 0 In this section the term APPC MVS is used to represent the APPC MVS Server Facility and the term server refers to the MVS Server The server selects inbound conversations on the basis of the named application TP name its location in the network and the LU name e The TP name is a 1 to 64 character name describing the server s address space Inbound requests are directed to this location The TP name may be the started task name or job name of the server s address space e The logical unit LU name is a unique name defined to the VTAM network for the server application After APPC MVS receives a client request for a conversation APPC MVS checks whether any address space has registered to serve the request If so APPC MVS assigns the request to an allocation queue The server can then select the request from the queue for processing When the server selects the request from the queue it receives the conversation ID and a conversation with the client begins Because APPC MVS requires the server to register and unr
167. SRPREF amp amp PREFIX amp amp SSID amp amp WORKID8 SYSRPS 10 SYSRSS 2 SYSRUNIT SYSDA SYSTYPE S SZDEVT 3380 TABLEACC Y TABLEALL N Defines the default SYSREC data set prefix Defines the default SYSREC primary space allocation Defines the default SYSREC secondary space allocation Defines the default SYSREC unit Defines the installation s character set M mixed S single byte only The device type for data set sizing for JCLGEN Valid values are 3380 and 3390 The default is 3380 For DB2 Version 5 1 and later indicates whether all tables remain accessible during execution Y or N For DB2 Version 5 1 and later specifies the STATS utility to gather information for all columns of tables N Do not include the TABLE ALL parameter on stand alone stats runs Y Include the TABLE ALL parameter on stand alone stats runs TAPE1 CART TAPE2 TAPE TAPE3 TAPE TIMEPARM TSOSX N UNLDCOLL N Defines the valid installation tape unit names for your site Indicates the TIME limit in minutes for each step in a batch job stream Specifies whether your site uses the TSO Submit exit to supply the job statements at submit time Y or N Explicit column list that is required on all BMC Software UNLOAD PLUS unloads Y or N BMC Software Inc Confidential and Proprietary Information 5 22 Administrative Products for DB2 Installation Guide UNLDEMPT Y UPDSTATS C UTILCOPY N VVALPROP N VRM vrmmd
168. SSID amp amp OBNOD Defines the default prefix high level qualifier that is used for the RECVnnn recovery data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied BMC Software Inc Confidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 11 Default Option Descriptions RECVPS 10 Defines the default primary space allocation in cylinders for RECVnnn recovery data sets RECVSS 2 Defines the default secondary space allocation in cylinders for RECVnnn recovery data sets RECVUNIT SYSDA Defines the default unit that is used for creating RECVnnn recovery data sets RPLAN ASUvrmDR The name of the DASD MANAGER PLUS plan that is used for displaying online reports SL1 The STEPLIB library that contains the BMC Software load modules You can place DASD MANAGER PLUS load modules in the same library as DB2 Keywords SL1 SL2 and SL3 indicate from what libraries DASD MANAGER PLUS should load DB2 load modules SL2 SYS1 DSNEXIT The optional first STEPLIB library for DB2 load modules This library is concatenated to the library that keyword SL1 specifies SL3 SYS1 DSNLOAD The optional second STEPLIB library for DB2 load modules This library is concatenated to the library that keywords SL1 and SL2 specify SL4 SYS1 OTHER LOADLIB1 Optional addit
169. System uses a lt C I Parm indicator to mark values that must be different from the direct access specification When you see this indicator supply unique names Creating Collection Names for Multiple Indirect Catalogs With CATALOG MANAGER 3 4 or later you can have more than one indirect catalog Each indirect catalog requires a unique collection name Also you can assign a collection name alias See Chapter 6 Installing CATALOG MANAGER for information about implementing catalog indirection with this product BMC Software Inc Confidential and Proprietary Information 3 22 Administrative Products for DB2 Installation Guide Naming Conventions Post Installation Considerations for Catalog Indirection After installation refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for catalog indirection Naming Conventions The following sections provide naming conventions Synonym Qualifier The synonym qualifiers have the following conventions e prdvrmy all products with the exception of ALTER and CHANGE MANAGER 5 2 or later e prdvrmcy ALTER and CHANGE MANAGER 5 2 or later Table 3 6 indicates what the variables represent and Table 3 7 shows examples of the synonym qualifiers Table 3 6 Synonym Qualifier Variables Variable Represents prd product code vrm version release maintenance level c indicates the exploited DB2 v
170. T 5 15 DB2CT 5 15 DBRMI 5 15 DBRM2 5 15 DBRM3 5 15 DBRMLIB 5 16 DEFERUIX 5 16 DISCARDS 5 16 EAP 5 16 EIP 5 16 ENVP 5 16 EPP 5 16 EURO 5 16 FEP 5 17 GLID 5 17 HSMVOL 5 17 IMP 5 17 Administrative Products for DB2 Installation Guide ISPSLIB 5 17 IXTYPE 5 17 JC1 5 17 JC2 5 17 JC3 5 17 JC4 5 17 JC5 5 17 JCLCLEAN 5 18 JDSN 5 18 JDSNBG 5 18 JDSNE 5 18 LOCATION 5 18 LOCK 5 18 LOG 5 18 MGMTCLAS 5 18 PC 5 18 PIC 5 18 PRODUCT 5 19 REBLD 5 19 RECOV 5 19 RECVDD01 5 15 RECVDD02 5 15 RECVMAX 5 19 RECVMAXU 5 19 RECVPREF 5 19 RECVPS 5 19 RECVSS 5 19 RECVUNIT 5 20 REORG 5 20 SDSN 5 20 SDSNE 5 20 SEQI 5 20 SL1 5 20 SL2 5 20 SL3 5 20 SL4 5 20 SLS 5 20 SPP 5 20 SSID 5 20 STATS 5 21 STOPCOMM 5 21 STORCLAS 5 21 SWPS 5 21 SWSS 5 21 SWU 5 21 SYNCPNT 5 21 SYSCMAX 5 21 SYSCMAXU 5 21 SYSCPREF 5 21 SYSCPS 5 21 SYSCSS 5 21 SYSCUNIT 5 22 SYSRMAX 5 22 SYSRMAXU 5 22 SYSRPREF 5 22 SYSRPS 5 22 SYSRSS 5 22 SYSRUNIT 5 22 SYSTYPE 5 22 SZDEVT 5 22 TABLEACC 5 22 TABLEALL 5 22 TAPEI 5 22 TAPE2 5 22 TAPE3 5 22 TIMEPARM 5 22 TSOSX 5 22 UNLDCOLL 5 22 UNLDEMPT 5 23 UPDSTATS 5 23 UTILCOPY 5 23 VRM 5 23 VVALPROP 5 23 WDC 5 23 WDSN 5 23 WLPS 5 23 WLSS 5 23 WLU 5 23 WMC 5 24 WPS 5 24 WSC 5 24 WSS 5 24 WU 5 24 ALTER GUI installing JSI JES interface 5 7 post installation tasks 4 22 ALTER plans ACVvrmDM 5 5 AEXvrmAA 5 6 AEXvrmAM 5 6 ALvrmcDA 5 5 ALvrmcDE 5 5 ALvrmcDF 5 4 ALvrmcDI
171. T AND RERUN THE JOB Explanation The first character of the product code is invalid System Action The password is not processed User Response Correct the first character of the product code in the PARM field on the JCL EXEC statement See Control Statements and Keywords on page A 29 for assistance with syntax THE PASSWORD MUST BE FORMATTED AS PSWD PPP PPP PPP PPP OR PSWD PPPPPPPPPPPP OR PPP PPP PPP PPP Explanation The password in the batch JCL has been specified incorrectly The password can be specified as 12 consecutive characters without spaces or as four sets of three characters with each set separated by a comma or a blank space System Action The password is not processed User Response Correct the password and resubmit the job See Control Statements and Keywords on page A 29 for assistance with syntax OPEN FAILURE FOR DDNAME SYSIN Explanation The Product Authorization utility batch program was unable to open the data set specified by the SYSIN DD statement System Action The batch program terminates User Response Correct the data set name specified on the SYSIN DD statement and resubmit the job See Control Statements and Keywords on page A 29 for assistance with syntax BMC Software Inc Confidential and Proprietary Information B 8 Administrative Products for DB2 Installation Guide Error Messages BMC89058E MODEL NUMBER CONTAINS INVALID CHARACTERS Explanation
172. TH STATIC The name of the SQL Explorer summary listing The DB2 subsystem ID The SSID must match the SSID command in the worklist This parameter is required Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSSTMT DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSSTOGROUP DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSSTRINGS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSSYNONYMS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The device type for data set sizing for JCLGEN Valid values are 3380 and 3390 The default is 3380 Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSTABAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person
173. Table 4 5 Installation Parameters Parameter Description Symbolic Destination Name required provides the CPI C Symbolic Destination Name that was defined in the SNA Gateway Server to describe the MVS Server application This parameter must match the exact name that is used in the SNA Gateway Server setup LU Name optional describes the APPC LU name to be used when establishing the conversation with the MVS Server This value should be specified as a fully qualified SNA LU name A qualified LU name consists of the network name separated from the logical unit name by a period with each name not exceeding 8 characters MODE Name optional allows an overriding specification to the operating mode table entry for the connection to the MVS Server TP Name optional allows an overriding specification to the teleprocessing program name that is associated with the connection that identifies the MVS Server Note Use of the LU name MODE name or TP name parameter allows overrides to the client s CPI C Symbolic Destination Name table entry When all the parameters are used together the CPI C Symbolic Destination Name table that is referenced is bypassed Where to Go from Here After you configure the APPC SNA communication protocol you verify the setting for your host code page For more information see Confirming the Host Code Page for the MVS Server on page 4 43 BMC Software Inc Confidential and Propri
174. a product on multiple CPUs or to install a product at a central site and run it at remote sites CPU Upgrades When you upgrade to a new CPU you must obtain a new permanent password for each product that you want to use on that CPU When you install the new password the old entry in the authorization table for the product is replaced The new table entry defines the authorization for the product CPU Failures If a hardware failure or a disaster recovery situation prevents the use of a licensed CPU BMC Software can provide a temporary license that lets the product run on a backup CPU for a limited time Before the temporary license expires you must acquire a permanent license for the new CPU or you must resume using the original CPU At the end of the grace period you can no longer run the affected product on the temporary CPU If this situation occurs you must obtain a new password to reset the grace period BMC Software Inc Confidential and Proprietary Information A 6 Administrative Products for DB2 Installation Guide How Products Are Licensed Updating Product Authorization Tables To trigger the grace period the license validation process must update the authorization tables If the product load library must be WRITE protected problems could occur with updates To avoid problems you can place the authorization tables in another data set and concatenate that data set to the product load library The concatenated author
175. able 4 2 Fast Path Navigation Commands Product Command ALTER BMCALTER CATALOG MANAGER BMCCAT CHANGE MANAGER BMCCHG DASD MANAGER PLUS BMCDASD For example if you are currently using DASD MANAGER PLUS and want to view an object description in CATALOG MANAGER enter BMCCAT on the DASD MANAGER PLUS Command line When you initiate Fast Path Navigation the main menu for the requested product is displayed In this case the DASD MANAGER PLUS session is temporarily suspended and then resumed when you exit CATALOG MANAGER To use Fast Path Navigation you must install the products by using the Install System and use the BMCDB2 CLIST during product invocation The distributed CLISTs BMCADMFI and BMCADMP2 must be in a data set that is in either the ALTLIB list of the BMCDB2 CLIST or your SYSPROC concatenation Also the product to which you are switching must be installed and reside in the same set of libraries as the product from which you are switching Note You cannot use Fast Path Navigation to access a product that is currently suspended For example if you switch from ALTER to DASD MANAGER PLUS you cannot use fast path to return to ALTER because it is currently suspended Instead you have to exit the DASD MANAGER PLUS session to resume the ALTER session BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 21 Performing the Post Installation Tasks for the MVS Server Perfor
176. ably when typing passwords System Action The action fails User Response Correct the password and retry the action SERIAL NUMBER IS A REQUIRED FIELD Explanation A valid CPU serial number has not been specified Valid CPU serial numbers consist of five hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Supply a valid CPU serial number and retry the action SERIAL NUMBER FIELD CONTAINS INVALID CHARACTERS Explanation The specified CPU serial number contains invalid characters Valid CPU serial numbers consist of five hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Supply a valid CPU serial number and retry the action SERIAL NUMBER MAY NOT CONTAIN BLANK CHARACTERS Explanation The specified CPU serial number contains a blank character and is invalid Valid CPU serial numbers consist of five hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Supply a valid CPU serial number and retry the action MODEL NUMBER IS A REQUIRED FIELD Explanation A valid CPU model number has not been specified Valid CPU model numbers consist of four hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Supply a valid CPU model number and retry the action BMC Software Inc Confidenti
177. ackages and Plans for Shared Components 4 17 Verifying the Product Authorization 00 5 4 18 Invoking the BMCDB2 CLIST 0000 4 19 Verifying the Installation of the Administrative Products 4 20 Using Fast Path Navigation LL 4 21 Performing the Post Installation Tasks for the MVS Server 4 22 Configuring TCP IP LL 4 23 Configuring APPC SNA 4 27 Setting Up the MVS Server 4 28 Setting Up the SNA Gateway Server 4 37 Setting Up the Chient enia e a LA 4 41 Confirming the Host Code Page for the MVS Server 4 43 Enabling the Use of Secondary Authorization IDs 4 44 Verifying the Installation of the MVS Server 4 45 Installing ALTER QVEDVICW eea ne a E e pi ia 5 2 Installation Considerations LL 5 3 Installation Defaults LL 5 3 Upgrading ALTER to CHANGE MANAGER 5 4 Controlling ACCESS os sirio ai eli atone ane oda 5 4 ALTER Specification and Analysis Plans 5 4 ALTER Execution Plans 5 6 ALTER Object Security 5 7 JSI JES Interface Installation 5 7 Default Option Listing DOPTS 0 0 0 0 eee eee 5 8 Default Option Descriptions 0 0 0 cece eee eee 5 12 Post Installation Considerations 0 00 e eee eee een ee 5 24 Installing CATALOG MANAGER OVErvieWes sities E a oth aloe a beh a Bact een etal nite eal eae 6 2 Installatio
178. adecimal numbering Figure 4 18 shows a sample local LU definition to VTAM Figure 4 18 Sample Local LU Definition for VTAM ACVLU01 APPL ACBNAME ACVLUO1 PPC YES C UTOSES 0 C DRAINL NALLOW C D APPCPCLM C INWNL 5 C INWNR 5 C RESPL NALLOW C ESLIM 10 C D D R ie O Q zZ O n ENT 19 C ETAB ACVAPPC C SESS YES C ECACPT CONV C RBEXIT YES C PACING 1 Bd Ped dd gt SUVUN Note A sample local LU definition exists in member APPLACVI of the HLQ CNTL data set You must make this LU active to VTAM before you add the LU to APPC MVS Define the local LU to APPC MVS To define a local LU as a server to APPC MVS update the APPCPMxx configuration member in SYS1 PARMLIB by adding an LUADD statement for the LU of the server The configuration member names the LUs and respective administrative VSAM KSDS The person who is responsible for updating the MVS system or VTAM network definition files must make this update BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Setting Up the MVS Server The LU that is defined for the server does not have a TP Profile data set nor does it require the use of a site information table However a reference to the system level TP Profile data set that accesses only the database token from that TP Profile data set is required Thus an entry for the server is not
179. age owner DYNAMIC uses the privileges of the person who is listing the table The Data Facility Storage Management Subsystem DFSMS or SMS data class name used at data set allocation time to define the allocation attributes of the data set A data class name is not required even for SMS data sets WDC will appear as DATACLAS in the JCL for workfiles WDSN amp amp ZUSER BMCCAT WORK WLDSN SYSOUT WMC WSC The default worklist data set name for a new Work ID CATALOG MANAGER dynamically allocates the name the first time that it is used This data set name can be overridden on the Analysis Interface panel This data set can be either a sequential file or a partitioned data set PDS The name of the worklog data set Note In many installation sites allocation of data sets is controlled by user written or third party routines If allocation fails you should use alternate means such as ISPF to allocate the data sets The SMS management class name used at data set allocation time to define the migration retention and backup requirements of the data set WMC will appear as MGMTCLAS in the JCL for workfiles The SMS storage class name used at data set allocation time to define processing requirements of the data set WSC will appear as STORCLAS in the JCL for non tape work files XDSN amp amp ZUSER BMCCAT SQLX The name of the SQL Explorer report BMC Software Inc Confidential and Proprietary Information
180. ailable in toleration mode 3 For PATROL DB Alter ALU or PATROL DB Change Manager ACM rebind all packages and plans for the previous version by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Any data that you added while you were in exploitation mode will not be available in toleration mode BMC Software Inc Confidential and Proprietary Information 3 30 Administrative Products for DB2 Installation Guide Maintaining BMC Software Administrative Products Table 3 15 Migrating DB2 Version 5 to Version 6 Part 2 of 4 If You Are using ALTER or CHANGE MANAGER 5 4 04D installed on DB2 Version 5 or using PATROL DB Alter or PATROL DB Change Manager server 3 0 02 through 3 1 02 installed on DB2 Version 5 Then Migrate the DB2 catalog 2 Rebind all ALTER ALU or CHANGE MANAGER ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID 3 For PATROL DB Alter ALU and PATROL DB Change Manager ACM rebind all PATROL DB Alter or PATROL DB Change Manager packages and plans for the previous version by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Then you will be operating in toleration mode To Fall Back Then 1 Rebind all ALTER ALU or CHANGE MANAGER
181. al Tasks for Installation Table 3 1 lists the tasks you may want to perform when you install BMC Software products Table 3 1 Task Use the Install System to install BMC Software products at different times Additional Tasks for Installation Reference See Installing Products at Different Times on page 3 2 Upgrade components that are shared by the Administrative Products Administrative Products to interact with the BMC Software Utility and Backup and Recovery products See Upgrading Shared Components on page 3 4 See Interacting with Other BMC Software Products on page 3 6 Use the Install System to allow the Reset the option values in the user profiles indirection See Refreshing Default Options on page 3 13 Use the Install System to install catalog See Using Catalog Indirection on page 3 17 Upgrade ALTER to CHANGE MANAGER at the same or higher maintenance level Products when you migrate between See Migrating Data From ALTER to CHANGE MANAGER on page 3 28 Maintain BMC Software Administrative See Maintaining BMC Software Administrative Products on page 3 30 versions of DB2 When you complete the installation refer to Chapter 4 Performing Post Installation Tasks to perform post installation tasks Installing Products at Different Times The Install System allows you to install multiple products simultaneous
182. al and Proprietary Information Administrative Products for DB2 Installation Guide Error Messages BMC89007E MODEL NUMBER FIELD CONTAINS INVALID CHARACTERS Explanation The specified CPU model number contains invalid characters Valid CPU model numbers consist of four hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Supply a valid CPU model number and retry the action BMC89008E MODEL NUMBER MAY NOT CONTAIN BLANK CHARACTERS Explanation The specified CPU model number contains a blank Valid CPU model numbers consist of four hexadecimal digits No blanks or special characters are allowed System Action The action fails User Response Correct the model number and retry the action BMC89009E DATA SET NAME IS INVALID Explanation The specified data set name is invalid The data set does not exist or it is not cataloged System Action The action fails User Response Correct the data set name and retry the action BMC89010A OPTION IS A REQUIRED FIELD VALID VALUES ARE 1 2 3 4 OR 5 Explanation No menu option has been specified System Action All functions are suppressed User Response Type a valid option number in the selection field and retry the action BMC89011E INVALID OPTION PLEASE ENTER 1 2 3 4 OR 5 Explanation The specified option is invalid System Action All functions are suppressed User Response Type a valid option number in
183. allation Guide Maintaining BMC Software Administrative Products Migrating from DB2 Version 4 to Version 5 To maintain BMC Software Administrative Products when you migrate to DB2 Version 5 or when you fall back to DB2 Version 4 use the guidelines in Table 3 17 Table 3 17 Migrating DB2 Version 4 to Version 5 Part 1 of 5 If You Are Then To Fall Back Then using ALTER or Migrate the DB2 catalog 1 Check your synonyms to make sure CNACERSgCOr 2 Ifthe Distributed Data Facility DDF is that they point to the correct table 5 4C installed on DB2 Version 4 installed for CHANGE MANAGER drop the current synonyms to the old communication database tables Then recreate the synonyms by using the same synonym names but with the new catalog table names For an example refer to the ACMINIT5 member in the HLQ JCL library 3 Rebind all ALTER ALU or CHANGE MANAGER ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID Then you will be operating in toleration mode As an alternative you can perform a Full installation of ALTER or CHANGE MANAGER 6 2D Then you will be operating in exploitation mode BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks names 2 If the synonyms do not point to the correct names drop the current synonyms Then recreate the
184. allation Tasks 4 11 Enabling the Product CLISTs You can optionally cause CATALOG MANAGER to display a custom initial entry panel by adding one or both of the following e Catalog Manager Profile Name is a 1 18 character name for a set of common custom features for a CATALOG MANAGER Session The profile name is passed to the product via the calling CLIST BMCDB2 Upon product entry CATALOG MANAGER reads the profile and brings up the primary menu command table and initial list filtering as defined for the session profile See the CATALOG MANAGER for DB2 Reference Manual for information about how to create a session profile The profile name is passed as a parameter from the invoking CLIST to the CATALOG MANAGER product module ACTEMAIN The syntax for this name is PR profile name e Catalog Manager Initial Command is a 1 48 character command that is passed to the product from the invoking CLIST BMCDB2 This command causes the product s initial entry panel to vary depending on which command is passed for example DB M causes CATALOG MANAGER to first display a list of all the databases that start with the letter M The initial command is passed as a parameter from the invoking CLIST to the CATALOG MANAGER product module ACTEMAIN The syntax for thiscommand isC initial command To add the Profile Name the Initial Command or both you must edit the invoking CLIST To do so enter the CLIST and find the lines shown in Fig
185. allocation Defines the Import plan name This value is used by the GUI for ALTER for JCL generation For DB2 Versions 4 and 5 the default Index type that ALTER and CHANGE MANAGER use when no type is specified on a create index command 1 Type 1 index 2 Type 2 index DB2 Version 4 and later JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 JC3 NOTIFY amp amp USERID JC4 JC5 Defines the jobcard that the Front End uses when it generates JCL Symbolic variables can be used and are described in the Symbolic Variable appendix of the respective products reference manuals BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 17 Default Option Descriptions JCLCLEAN N Enables you to generate a job step that automatically deletes many of the permanent also known as non temporary data sets that the Execution component creates These data sets are created during worklist processing and have a disposition NEW CATLG CATLG The automatic delete step is only performed if the condition code that is returned from any previous job step is four or less Y or N JDSN amp amp PREFIX ANALYSIS amp amp WORKID Defines the default data set name that is used for Analysis JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a part
186. ame Sets the Baseline plan name Determines whether the BMC Software LOADPLUS utility updates catalog Statistics for the BMCSTATS utility tables during loads for DB2 Version 4 1 or earlier Y or N Determines whether the BMC Software LOADPLUS utility updates statistics in the DB2 catalog during loads for DB2 Version 4 1 or earlier Y or N BLRPPREF amp amp PREFIX amp amp SSID amp amp WORKID8 BLRPPS 10 BLRPSS 2 BLRPUNIT SYSDA Defines the high level qualifier or prefix that is used for data sets containing data stored for a baseline recovery point Defines the primary space allocation in cylinders for baseline recovery point data sets Defines the secondary space allocation in cylinders for baseline recovery point data sets Defines the unit that is used for baseline recovery point data sets BMC Software Inc Confidential and Proprietary Information 7 20 Administrative Products for DB2 Installation Guide BMCCHECK N BMCCOPY N BMCLOAD N BMCSTATS N BMCUNLD N BPOOLIX BP0 BPOOLTS BP0 BRPTDIAG SYSOUT Default Option Descriptions Specifies whether to use the BMC Software CHECK PLUS utility in place of the IBM CHECK DATA utility for checking referential constraint violations in DB2 table spaces Y or N Specifies whether to use the BMC Software COPY PLUS utility in place of the IBM COPY utility The DOPTs parameters are defined as follows Use BMCCOPY Use IBMCOPY Do not include
187. ame depending on the type of object that is being copied optional The user command table The name of the COPY PLUS product s load library If you are installing COPY PLUS together with CATALOG MANAGER type the name of the COPY PLUS load library Otherwise comment out the library name The name of the copy device type The DATA PACKER load library If you are installing DATA PACKER together with CATALOG MANAGER type the name of the DATA PACKER load library Otherwise comment out the library name The DATA PACKER EDITPROC load library UJC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR UJC2 CLASS A MSGCLASS X MSGLEVEL 1 1 UJC3 NOTIFY amp amp USERID Five default job statements for your installation Set unused statements to comments or null The CHECK PLUS product s load library If you are installing CHECK PLUS together with CATALOG MANAGER type the name of its load library Otherwise comment out the library name BMC Software Inc Confidential and Proprietary Information 6 22 Administrative Products for DB2 Installation Guide Default Option Descriptions ULL1 SYS1 DSNEXIT ULL2 SYS1 DSNLOAD ULSTP UPLAN ACTyrmDU UPSTP Load library DD statements for DB2 utility execution Most installations require only ULLI If your installation uses two load libraries type the name of the second library in ULL2 Otherwise leave ULL2 set to null If your ins
188. amp PREFIX TASKID amp amp TASKID The default data set name where the CM PILOT component places the generated Execution JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The CM PILOT component automatically uses the TASK ID as the member name JDSNE amp amp PREFIX EXEC amp amp WORKID Defines the default data set name that is used for Execution JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The product automatically uses the Work ID as the member name JDSNI amp amp PREFIX IMPORT amp amp WORKID Defines the default data set name that is used for Import JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The product automatically uses the Work ID as the member name JDSNBR amp amp PREFIX BASELINE BLRPTJCL The default data set name where the product places the generated Baseline Report JCL This data set can be either a sequential or partitioned data set LOCATION The local subsystem location If you are using Single Point Entry the parameter is set to SPE METHOD LOCK X Controls the SQL LOCK TABLE statements that are issued by the Execution component for ALTER unloads The LOCK parameter does not apply to the BMC Software UNLOAD PLUS prod
189. ample logon mode table that IBM supplies Alternatively you can use an existing logon mode table containing the entry that the server uses APPCPCLM BMC Software Inc Confidential and Proprietary Information 4 30 Administrative Products for DB2 Installation Guide Setting Up the MVS Server KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKKKKKKKK OF ACTING Figure 4 17 Sample Logon Mode Definition LOGMODES MODETAB EJECT KKEKKKKKKKKKKKKKEKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK TITLE SNASVCMG KKKKKKKKKKKK LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE AS LU 6 2 DEVICES REQUIRED FOR LU MANAGEMENT KKKKKKKKKKKK SNASVCMG MOD KKKKKKKKKKKKKK KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKKKKKK EENT LOGMODE SNASVCMG FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X DOB1 RUSIZES X 8585 ENCR B 0000 PSERVIC X 060200000000000000000300 KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKAKKKKKKKK TITLE APPCPCLM KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE OF ACTING AS LU 6 2 DEVICES FOR PC TARGET IN THIS EXAMPLE THE DEFAULT RU SIZE FOR OS 2 1024 IS USED KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
190. an perform Giving wide access to Specification and Analysis while controlling access to the Execution Monitor Entry lets your users run ALTER for training purposes or use it as a system dictionary Further control over the Execution component s authorization switching function is provided by the Execution Security Exit BMC Software Inc Confidential and Proprietary Information 5 6 Administrative Products for DB2 Installation Guide JSI JES Interface Installation ALTER Object Security The security features of ALTER provide you with the ability to restrict access to ALTER Work IDs and to separate projects that access the same set of tables The ability to maintain the security features is restricted to users who have been granted SELECT and UPDATE authority on the security table as follows tbcreator Vvr_CM_SECURITY The variable tbcreator is the ALTER creator ID that is specified at installation and the variable vr is the version and release of ALTER Install System GRANTS are only executed on plans and collections The Install System does not execute grants on tables If you want non S YSADM users to be Security Administrators execute the necessary GRANT SELECT and UPDATE statements JSI JES Interface Installation The JSI JES Interface installation consists of several installation options These options help to define the interface to the MVS Server started task for the specific MVS and JES2 environment in which the server
191. anagement support for the following DB2 data structures e storage group e database e table space e table e check constraint DB2 Version 4 1 or later e foreign key e index e view e trigger DB2 Version 6 1 or later e alias e synonym When you use ALTER to specify any of these objects for change ALTER automatically propagates the change as needed for any dependent objects ALTER restores all data dependencies and authorizations and supports a large number of data type conversions ALTER is able to use the BMC Software LOADPLUS UNLOAD PLUS REORG PLUS CHECK PLUS RECOVER PLUS and COPY PLUS utilities to speed up the execution of structure changes and migrations In addition ALTER can be upgraded to the CHANGE MANAGER product easily For information about ALTER read the ALTER and CHANGE MANAGER for DB2 User Guide BMC Software Inc Confidential and Proprietary Information 5 2 Administrative Products for DB2 Installation Guide Installation Considerations Installation Considerations When you use the Install System to install the Administrative Products for DB2 the installation process generates a customized installation data set This data set contains customized jobs that are created to install these products into your specific DB2 environment One of these jobs establishes the default processing option values The job name begins with a character followed by a three character identifier that varies de
192. and maintenance level Use the existing plan bind source to create this plan then change the name 5 Edit the member in the HLQ CNTL library that has the same name as the DOPTs module Change HPLAN to the plan that was created in Step 4 Submit the job to reassemble the DOPTs module The HLQ INSTALL member DCI ACTU provides an example of a worklist If the utilities are installed in a different load library complete the following steps 1 Find the member in the HLQ CNTL library that has the same name as the DOPTs module 2 Update the CATALOG MANAGER DOPTs values for UCSTP UDSTP UESTP UKSTP ULSTP URSTP UUSTP and UVSTP to use the different utilities load library For a description of these DOPTs options see Chapter 6 Installing CATALOG MANAGER 3 Add any additional load libraries to SLIB member AJXSTEPU BMC Software Inc Confidential and Proprietary Information 3 8 Administrative Products for DB2 Installation Guide Interacting with Other BMC Software Products DASD MANAGER PLUS If you plan to use DASD MANAGER PLUS with the BMC Software REORG PLUS LOADPLUS or COPY PLUS for DB2 products and you did not merge the products during the unload of the Install System you must point the utility synonyms to the correct DASD MANAGER PLUS tables and point the DASD MANAGER PLUS synonyms to the appropriate utility tables Pointing the Utility Synonyms to the DASD MANAGER PLUS Tables If the BMCSTATS runtime option
193. arious DB2 versions To Remove Old DB2 Structures The installation procedure generates JCL member I98DROP You can use this member to drop DB2 structures that are created during installation or that become obsolete as a result of subsequent installations This capability is useful if you cancel restart or upgrade an installation BMC Software Inc Confidential and Proprietary Information 2 24 Administrative Products for DB2 Installation Guide Generating Installation JCL Beginning with version 1 5 30 the Install System renames a copy of I98DROP to 198ssid where ssid is the four character DB2 subsystem ID that is associated with the installation The Install System then places 198ssid into the HLQ CNTL library In future installations those that use Install System version 1 5 31 or later you can easily remove DB2 structures from an earlier installation by submitting the 198ssid job in the HLO CNTL library that is associated with the earlier installation BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 25 Migrating DB2 Objects Between Releases Migrating DB2 Objects Between Releases Summary When you install a new release you can copy data from an old release to the new release using identical DB2 object names for example database and table names To use existing DB2 object names for a new release follow the procedure below and refer to the example job listing
194. ary Further control over the Execution component s authorization switching function is provided by the Execution Security Exit BMC Software Inc Confidential and Proprietary Information 7 12 Administrative Products for DB2 Installation Guide JSI JES Interface Installation CHANGE MANAGER Object Security The security features of CHANGE MANAGER provide you with the ability to restrict access to CHANGE MANAGER objects Work IDs baseline profiles and migrate profiles and to separate projects that access the same set of tables The ability to maintain the security features is restricted to users who have been granted SELECT and UPDATE authority on the security table as follows tbcreator Vvr_CM_SECURITY The variable tbcreator is the CHANGE MANAGER creator ID that is specified at installation and the variable vr is the version and release of CHANGE MANAGER Install System GRANTS are only executed on plans and collections The Install System does not execute GRANTs on tables If you want non SYSADM users to be Security Administrators execute the necessary GRANT SELECT and UPDATE statements JSI JES Interface Installation The JSI JES Interface installation consists of several installation options These options help to define the interface to the MVS Server started task for the specific MVS and JES2 environment in which the server task will be operating Currently support for JES3 is not provided The installer needs to pr
195. ary Password 0 00000 e eee eee A 23 Displaying Product Authorization 2 0005 A 24 Displaying Current Processor Information A 26 Batch Product Authorization LL A 27 Running Batch Product Authorization 04 A 27 Control Statements and Keywords 0000 0008 A 29 Return Cod s o neniet Hee Sega Pan cane hee dee See bees A 30 Appendix B BMC Software Product Authorization Messages Error MeSsa ges canal ae Be te Sate a Rass ileal va eyelet es B 2 Message Format i siii ad aw epa a Se ae B 2 Message Severity Codes 0 0 0 cee cece eee nee B 3 Message Explanations 0 0 cece eee eee eee B 3 Index BMC Software Inc Confidential and Proprietary Information Contents ix X Administrative Products for DB2 Installation Guide BMC Software Inc Confidential and Proprietary Information Figures Figure 2 1 Figure 2 2 Figure 2 3 Figure 2 4 Figure 2 5 Figure 3 1 Figure 4 1 Figure 4 2 Figure 4 3 Figure 4 4 Figure 4 5 Figure 4 6 Figure 4 7 Figure 4 8 Figure 4 9 Figure 4 10 Figure 4 11 Figure 4 12 Figure 4 13 Figure 4 14 Figure 4 15 Figure 4 16 Figure 4 17 Figure 4 18 Figure 4 19 Figure 4 20 Figure 4 21 Figure 5 1 Figure 6 1 Figure 7 1 Figure 8 1 Figure 9 1 Figure A 1 Unload Job for the Install System 2 7 Unload Job for the Install System Using Merge 2 8 Install System Load Library Specifica
196. as used to perform the BINDS for the SQL Explorer installation The HLQ INSTALL member DCI PSSD provides examples of a worklist BMC Software Inc Confidential and Proprietary Information 3 12 Administrative Products for DB2 Installation Guide Refreshing Default Options Refreshing Default Options If you need to reset the values in user profiles the BMC Software Administrative Products provide a refresh feature This feature modifies one or more option values for all of the product s users To refresh an option value in all existing user profiles enclose the option value in parentheses and include R after the value inside the parentheses as in the following example SSID DB2J R This example refreshes the default subsystem ID for all of the product s users Note Do not drop either the continuation comma after the closing parenthesis or the continuation character in column 72 For products other than CATALOG MANAGER the R in the variable syntax indicates that the value specified will refresh the existing value of the variable in the user s ISPF profile data set if the timestamp of the DOPTS is later than that in the user s ISPF profile member However the user can change the override value in the user profile In CATALOG MANAGER the refresh occurs every time that a user starts the product If your user options do not successfully refresh complete the following steps 1 Verify that the refresh option is
197. at Analysis uses If you specify AUTHSW Y AUTH commands are used in the worklist to switch the authorization ID for subsequent SQL statements and reBINDs In this mode you can add SETS commands to the worklist for setting the authorization ID with SET CURRENT SQLID statements If you specify AUTHSW N SETS commands are generated for switching the authorization ID and AUTH commands are not allowed If you specify AUTHSW B both AUTH and SETS commands are used AUTH commands are generated to set the original CREATEDBY values SETS commands are generated to set new OWNER values for all objects The B option also causes authorization ID switching before CREATE TABLE and CREATE INDEX statements which is not done under either of the other options When the AUTHSW keyword is used in the ALUIN input stream it is equivalent to AUTHSW Y in the DOPTs module Note Do not use the AUTHSW keyword in the following situations e If AUTHSWEN is in the DOPTs module e Ifyou are using a global authorization ID GLID Note If your site does not use DB2 secondary AUTHIDs set AUTHSW Y Otherwise set AUTHSWEN If you require that the CREATEDBY field in the DB2 catalog remain unchanged after updates then set AUTHSW B Warning Setting AUTHSW B is not recommended because of a potential security exposure This exposure exists because the DB2 catalog does not accurately reflect the primary authorization ID of the creator of the objects If you mus
198. at the variables represent and Table 3 11 shows examples of plan names Table 3 10 Plan Name Variables Variable Represents prd or pp product code vrm version release maintenance level c indicates the exploited DB2 version B 3 1 C 4 1 D 5 1 and E 6 1 or later access type D direct l indirect plans function Note The access type for CATALOG MANAGER 3 3 or later must be direct D CATALOG MANAGER 3 3 or later is designed to use a single DOPTs module for both direct and indirect access Because the plan names are communicated to the products through the DOPTs module CATALOG MANAGER is the only Administrative Product that requires only a single set of plans for both direct access and indirect access Table 3 11 Examples of Plan Names Example Description AL621EDF ALTER 6 2 01 DB2 Version 6 direct access Front End plan AL621EIF ALTER 6 2 01 DB2 Version 6 indirect access Front End plan ASU613DD DASD MANAGER PLUS 6 1 03 direct access Object Definition plan Collection Names Collection names have the following conventions e prdvrmc_y_MAIN ALTER and CHANGE MANAGER e prdvrm_y_ _MAIN CATALOG MANAGER e prdvrm_y_ MAIN DASD MANAGER PLUS BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 25 Naming Conventions Table 3 12 indicates what the variables represent and Table 3 13 shows examples of collection names
199. ated as a LOAD parameter for each LOAD step where n is the maximum number of discards This action will cause the load to terminate if the discard maximum is reached If fewer records are discarded the discard file will contain them and execution will proceed to the next step in the worklist Defines the Execution Authorization plan name which determines if a user is authorized to run Execution Defines the Installation plan name Defines the Environment plan name which is used to display ALTER and CHANGE MANAGER environment information Defines the Execution primary plan name Instructs ALTER CHANGE MANAGER and DASD MANAGER PLUS to expect numbers in the European format comma used for the decimal point and to create output in European decimal format Y or N This parameter is particularly important when ALTER or CHANGE MANAGER parses index LIMITKEY values that are separated by commas If the EURO keyword is present ALTER or CHANGE MANAGER requires delimiting commas to be followed by blanks Note The Import Specification Baseline and Compare components use the value for EURO from the DOPTs module but do not support use of the EURO keyword in the ALUIN parameter input data stream Defines the Front End plan name Defines a global authorization ID GLID This authorization ID is used instead of the authorization ID of the person who submits the Analysis job The worklist begins with a GLID command that switches authoriza
200. atic SQL or dynamic SQL to access the SYSIBM SYSCOLDIST DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table BMC Software Inc Confidential and Proprietary Information 6 12 Administrative Products for DB2 Installation Guide COLDISS STATIC COLSTAT STATIC COLUMNS STATIC CONSTDE STATIC COMD ACTCOMND COPY STATIC CRS N CUP Y DATABAS STATIC DATATYP STATIC DB2CT DBDBCAT Default Option Descriptions Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCOLDISTSTATS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCOLSTATS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCOLUMNS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCONSTDEP DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the
201. audit logging indicator If you have CATALOG MANAGER installed an entry of Y causes Execution to log executed DDL statements in the CATALOG MANAGER DDL Audit Log Y or N BMC Software Inc Confidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 9 Default Option Descriptions CATRECOV N CPLAN ASUvrmDC DATE amp SYSDATC DB2CAT DBDBCAT DLHQ HLQ DPLAN ASUvrnDD DPNAM DPDELOAD EAP AEXvrmDA EIP DCIINSTL EPP AEXvrmDM GDGDEF N GDGLIM 0 ISPTLIB HLQ TLIB JCLCLEAN N The Drop Recovery indicator This parameter is useful only if you have CATALOG MANAGER installed Type Y if you want execution to save information in the CATALOG MANAGER drop recovery log about objects being dropped ALTER or CHANGE MANAGER logs the information required for recovering any object that you drop You must then use CATALOG MANAGER to recover the objects See the CATALOG MANAGER for DB2 Reference Manual for information about Drop Recovery The name of the DASD MANAGER PLUS plan that is used to control DB2 catalog updates This parameter is used only if you have ASMA90 as your assembler The VSAM CATALOG alias that contains the data sets of the DB2 catalog The DASD MANAGER PLUS high level qualifier that is used to derive DASD MANAGER PLUS ISPF data set names that are dynamically allocated during batch TSO simulation in DASD MANAGER PLUS For example if DLHQ BMC ADMIN then ISPTLIB BMC ADMIN TLIB
202. b to correct the condition BMCTRIG lets you generate worklist JCL or standard JCL with its flexibility familiarity and easy restarts The Space Estimation function simulates changes to the database so that you can predict the effect of changes to such things as page size segment size primary and secondary allocations number of rows index type and average row length DASD MANAGER PLUS exploits the advantages of DB2 Version 4 1 and later e type 2 indexes e data sharing across DB2 subsystems e partition independence for DB2 utilities e faster LOAD REORG and RUNSTATS e online REORG e improved queries BMC Software Inc Confidential and Proprietary Information 8 2 Administrative Products for DB2 Installation Guide Installation Considerations e large table spaces e new version 4 and version 5 parameters for BMC Software utilities DB2 utilities and DB2 commands This product provides both analytical and statistical reports The reports provide comprehensive information about space allocation reorganization image copies table spaces indexes tables and storage groups DASD MANAGER PLUS also provides customizable reports that help you to monitor trends in space utilization and to maintain Work IDs For information about DASD MANAGER PLUS read the DASD MANAGER PLUS for DB2 User Guide Installation Considerations When you use the Install System to install the Administrative Products for DB2 the installation proc
203. ble The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPLANDEP DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The number of print lines per page for the PRINT commands Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPLSYSTEM DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPROCEDURES DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table RCCOL ACTvrm_D_MAIN RELS STATIC RESAUTH STATIC RMAX RMAXU CATALOG MANAGER collection ID for direct catalog access Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSRELS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSRESAUTH DB catalog table The default STATIC uses the privileges of t
204. c Confidential and Proprietary Information 1 14 Administrative Products for DB2 Installation Guide Installation Paths Use the Maintenance installation path when the maintenance level for a product changes for example from version 3 3 00 to version 3 3 0 Note The Maintenance installation does not provide DB2 object creation for products that require this feature You must use the Full installation path to create DB2 objects If the DB2 structures are changed you must perform a Full installation to migrate your data from a previous release The Maintenance installation consists of the following paths e initial Maintenance installation e subsequent Maintenance installation which must share product libraries Initial Maintenance Installation Use the initial Maintenance installation path to apply a maintenance update for the first time Select this option to unload the distribution tape create a new set of product libraries or overlay existing libraries generate new default options and bind plans and packages when applicable Subsequent Maintenance Installation Use the subsequent Maintenance installation path to apply maintenance to other installation sites that share the product libraries that were created during the initial maintenance application If the subsequent installation sites do not share product libraries you must use the initial Maintenance installation path A subsequent Maintenance installation does not unl
205. c Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 11 Installation Paths Determining Version Release and Maintenance Levels You must determine whether the distribution tape contains a new version a new release or maintenance for each product that you plan to install The format of the version or release number on the tape label is as follows date VR MM The variables shown in the format are as follows e date represents the product date in the form mm dd yyyy e V represents the version number e R represents the release number e MM represents the maintenance level Determine the version release and maintenance levels of your currently installed products and compare that information with the levels on the distribution tape s external label Table 1 9 shows examples of changes in product status You can quickly determine whether the distribution tape contains a new version a new release or maintenance Table 1 9 Changes in Product Status Product Status VRMM new version installed level 3 2 03 distribution tape 4 0 01 new release installed level 3 2 03 distribution tape 3 3 00 maintenance level installed level 3 2 03 distribution tape 3 2 04 Note Some new versions and releases contain data structure changes for the BMC Software databases and thus require a Full Installation BMC Software Inc Confidential and Proprietary Information 1 12 Administrative
206. catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table PDSN amp amp ZUSER BMCCAT PRINT PKSYSTE STATIC The name of the print output data set CATALOG MANAGER dynamically allocates this data set the first time that it is used When allocating this data set use these parameters DCB LRECL 133 BLKSIZE 1330 RECFM FBA Note In many installations allocation of data sets is controlled by user written or third party routines If allocation fails you should use alternate means such as ISPF to perform the allocations Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPKSYSTEM DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table BMC Software Inc Confidential and Proprietary Information 6 18 Administrative Products for DB2 Installation Guide PLAN STATIC PLANAUT STATIC PLANDEP STATIC PLP 55 PLSYSTE STATIC PROCEDU STATIC Default Option Descriptions Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPLAN DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSPLANAUTH DB catalog ta
207. ccess to the Analysis component to analyze changes and generate a worklist Note however that you cannot make actual changes to DB2 objects and data by creating a worklist The Specification and Analysis plans provide a way for you to request and analyze changes For this reason you can usually place minimum restrictions on the Specification and Analysis programs CMvrmcDB Baseline Plan This plan provides you with the ability to establish and delete baselines Since baselines especially full recovery baselines contain critical information that is used for database recovery you should restrict access to this plan to informed users CMvrmcDC Compare Plan Access to this plan provides users with the ability to compare data structure definitions Since no DB2 data structures are modified you can usually grant wide access to this plan CMvrmcDR Report Plan Access to this plan provides users with the ability to create baseline reports You can grant wide access to this plan BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 11 Controlling Access CMvrmcDE Environment Plan Access to this plan allows users to invoke the ENVI command to review their system environment Since this plan is not accessed outside of the other CHANGE MANAGER components you can usually grant PUBLIC access to this plan This plan does not control the use of the ENVI keyword with batch components C
208. ce The MVS Server INI file is a PDS member that contains various parameters that the server uses for initialization The variables that define the JSI JES interface in the INI file are JSI JESSSID JES2 JES2 subsystem name JISI USISSID JSI1 JSI JES subsystem name JISI DLL 00 JSI JES main Load module ID JSI SPOOLBYOWNER 0 Restrict spool access by owner Default Option Listing DOPTs 5 8 This section provides an example of the default options DOPTs module listing for ALTER see Figure 5 1 on page 5 9 The DOPTs listing is created by the Install System and resides in xnnDOPT The DOPTs listing also resides in HLO CNTL with the same member name as the DOPTs BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Default Option Listing DOPTs Figure 5 1 ALTER Default Options Listing Part 1 of 3 KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK MODULE ALUDOPD1 FUNCTION ALTER for DB2 COPYRIGHT COPYRIGHT BMC SOFTWARE INC 2000 LEVEL RELEASE 6 2 September 2000 FUNCTIONS DEFINE THE DEFAULT PROFILE VARIABLES KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK DOPTS CSECT LUDOPTS RMODE 24 LUDOPTS AMODE 24 LUDOPTS SALUDOPT PRODUCT ALTER DATE amp SYSDATC PC ALU VRM 621E R SSID DBDB R DB2CAT DBDBCAT R EURO N R SYSTYPE S PIC N
209. cess the SYSIBM LOCATIONS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The name of the CATALOG MANAGER logs maintenance plan Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM LULIST DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM LUMODES DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM LUNAMES DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The maximum number of lines to generate in a list Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM MODESELECT DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The name of the CATALOG MANAGER main plan Overrides a blank NOWORKDDN parameter for REORG PLUS Y or N BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 1
210. client versions are equivalent to specific mainframe product versions Table 3 2 Version Equivalents for the Mainframe Server and Client Product Mainframe Version Server Version Client Version ALTER 6 2 01 6 2 01 6 2 01 6 1 02 6 1 02 6 1 02 6 1 01 6 1 01 6 1 01 5 4 04 3 1 02 3 1 02 5 4 04 3 0 02 3 0 01 5 4 03 3 0 01 3 0 01 5 4 02 2 2 08 2 2 06 5 4 01 2 2 07 2 2 06 CHANGE MANAGER 6 2 01 6 2 01 6 2 01 6 1 02 6 1 02 6 1 02 6 1 01 6 1 01 6 1 01 5 4 04 3 1 02 3 1 02 5 4 04 3 0 02 3 0 01 5 4 03 3 0 01 3 0 01 5 4 02 2 2 08 2 2 06 5 4 01 2 2 07 2 2 06 To bind a product to the shared components follow these steps 1 Edit the product s BIND packages and plans which are in the HLO CNTL data set The member names are as follows prdssidP prdssidB prdssidZ package BIND jobs plan BIND jobs including CATALOG MANAGER plan BIND jobs for indirection package and plan BIND jobs for indirection except CATALOG MANAGER plan BIND jobs The variable prd is the product code and ssid is the subsystem ID The product codes are as follows ALU for ALTER ACT for CATALOG MANAGER e ACM for CHANGE MANAGER e ASU for DASD MANAGER PLUS BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 5 Interacting with Other BMC Software Products 2 Concatenate the new HLQ DBRM library ahead of the old HLO DBRM library in the
211. condary Authorization IDs 4 44 Verifying the Installation of the MVS Server 4 45 BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 1 Performance Considerations Performance Considerations DB2 Version 4 and later allows indexes on the catalog To improve performance BMC Software recommends that you create indexes on the following DB2 catalog tables e SYSIBM SYSCOLAUTH e SYSIBM SYSDBRM e SYSIBM SYSFIELDS e SYSIBM SYSFOREIGNKEYS e SYSIBM SYSRELS e SYSIBM SYSSTMT e SYSIBM SYSSYNONYMS e SYSIBM SYSTABAUTH e SYSIBM SYSTABLES e SYSIBM SYSVIEWDEP Depending on the functionality used in a product you may be able to create several other indexes that improve the performance of the product Refer to HLQ CNTL DCIDB2IX for details on creating these indexes You can implement the desired indexes by reading the comments in this member For indexes used with catalog indirection refer to HLO CNTL DCIDB2ZX Adding Products to the BMCDB2PR Panel The Tools Install System enables you to add products that are not included on the TIS or SAT tapes to the BMCDB2PR panel The following BMC Software products can be added to the BMCDB2PR panel ACTIVITY MONITOR for DB2 DOM e APPTUNE for DB2 ASQ e CHANGE ACCUMULATION PLUS ACA e COORDINATED RECOVERY MANAGER CRR e COPY PLUS for DB2 ACP EXTENDED BUFFER MANAGER XBM e Log Mas
212. correct table installed drop the current synonyms names to the old communication database 2 If the synonyms do not point to the tables Then recreate the synonyms correct names drop the current by using the same synonym names synonyms Then recreate the but with the new catalog table names synonyms by using the same For an example refer to the ASUINIT5 synonym names but with the correct member in the HLQ JCL library table names 3 Rebind all DASD MANAGER PLUS 3 Rebind all DASD MANAGER PLUS packages and plans by using packages and plans by using ASUssidP bind packages and ASUssidP bind packages and ASUssidB bind plans where ssid is ASUssidB bind plans where ssid is the subsystem ID the subsystem ID Then you will be operating in toleration mode using DASD 1 Migrate the DB2 catalog 1 Check your synonyms to make sure aa PLUS 2 Modify the ASUDB25E worklist that they point to the correct table member in the HLQ JCL library names 3 Execute the worklist using a modified 2 f the synonyms do not point to the copy of the I40INST job that the correct names drop the current INSTALL job dialog generated synonyms Recreate the synonyms by f using the same synonym names but 4 dale all 3 Sti PLUS with the correct table names ackages and plans by usin 2 y 9 3 Rebind all DASD MANAGER PLUS packages and plans by using ASUssidP bind packages and ASUssidB bind plans where ssid is the subsystem ID 3
213. d CHANGE MANAGER e the modification of the UCDSP and UVDSP parameters in the default options module for CATALOG MANAGER e the ability to type the codes I or D on the BMCDB2PR panel to indicate Indirect or Direct catalog access e the addition of the What s New option to the Install System Main Menu e the combination of the ALTER and PATROL DB Alter for DB2 chapters and the combination of the CHANGE MANAGER and PATROL DB Change Manager for DB2 for OS 390 chapters in this installation guide This installation guide provides documentation for the following products e ALTER for DB2 version 6 1 02 e CATALOG MANAGER for DB2 version 6 1 02 e CHANGE MANAGER for DB2 version 6 1 02 e DASD MANAGER PLUS for DB2 version 6 1 01 e SQL Explorer for DB2 version 3 1 03 e UTILITY MANAGER for DB2 version 1 2 Version 1 6 01 February 29 2000 This installation guide provides support for the BMC Software Install System Enhancements for version 1 6 01 of the Install System include e the ability to connect to another DB2 subsystem from your current SQL Explorer session through the DB2 Distributed Data Facility DDF e anew input variable in the BMCDB2PR panel for sites that use Single Point Entry e reminders for the mask variable on installation panels for sites that use Single Point Entry e anew interface between SQL Explorer and DASD MANAGER PLUS to migrate or copy statistics from BMCSTATS to the DB2 catalog BMC Software Inc
214. distribution tape During installation the Install System displays the VOLSER Verify that the VOLSER corresponds with the label on the distribution tape If the VOLSERs differ you may be invoking the wrong installation CLIST See Unloading the Install System on page 2 6 for more information BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 13 Running the Install System Running the Install System The Install System guides you through installation procedures and decisions Use the dialog panels to generate installation batch jobs for the products that you choose to install Main Menu Options on the Main Menu correspond to the list of tasks that you usually perform the first time that you install a BMC Software product The menu options are as follows e User Options e Product Installation e BMC Software Authorization If the tape set has additional options they are also listed on the Main Menu Refer to Chapter 1 Preparing for Installation for information about the contents of the distribution tape Keys and Commands The Install System panels provide messages at the bottom to indicate which function keys are active By default the active function keys are not displayed To display the active keys type the ISPF command PFSHOW on the command line and press Enter The following commands and function keys are available to help you move through the Install System
215. ds on page A 29 for assistance with syntax BMC89051E UNRECOGNIZABLE OR INCOMPLETE PARAMETER ON THE CURRENT INPUT CONTROL STATEMENT Explanation A parameter on the input control statement is incorrect System Action The password is not processed User Response Correct the parameter and retry the action See Control Statements and Keywords on page A 29 for assistance with syntax BMC89052E MODEL NUMBER CANNOT BE LONGER THAN FOUR CHARACTERS Explanation A CPU model number of more than four characters was specified in the batch JCL CPU model numbers cannot be longer than four characters System Action The password is not processed User Response Correct the model number and retry the action See Control Statements and Keywords on page A 29 for assistance with syntax BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 7 Error Messages BMC89053E BMC89054E BMC89055E BMC89057E SERIAL NUMBER MUST BE 5 HEXADECIMAL CHARACTERS WITH DELIMITING HYPHEN Explanation The CPU serial number must be followed by a delimiting hyphen System Action The password is not processed User Response Insert a hyphen between the serial number and the model number and retry the action See Control Statements and Keywords on page A 29 for assistance with syntax THE FIRST CHARACTER OF THE BMC PRODUCT CODE CANNOT BE A NUMBER PLEASE CORREC
216. duct Release notes provide current information such as e updates to the installation instructions e last minute product information In addition BMC Software sometimes provides updated product information between releases in the form of a flash or a technical bulletin for example The latest versions of the release notes and other notices are available on the Web at http www bmc com support html BMC Software Inc Confidential and Proprietary Information xvili Administrative Products for DB2 Installation Guide Conventions This section provides examples of the conventions used in this book and explains how to read syntax statements General Conventions This book uses the following general conventions Item information that you are instructed to type specific standard keyboard key names Example Type SEARCH DB in the designated field Press Enter field names text on a panel directories file names Web addresses Type the appropriate entry in the Command field The BMC Software home page is at http www bmc com nonspecific key names option names Use the HELP function key KEEPDICTIONARY option MVS calls commands control statements keywords parameters reserved words code examples syntax statements system messages screen text emphasized words new terms variables single step procedures Use the SEARCH command to find a particular object The product
217. e CPU in the product authorization table with another CPU This process allows the new CPU to run the product in place of the old CPU Step 1 Access the REPLACE Authorization for a Processor panel as follows 1 A On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 1 B At Product load library type a fully qualified data set name and press Tab 1 C At Authorization password type your permanent password and press Enter The REPLACE Authorization for a Processor panel is displayed Figure A 6 shows a sample Figure A 6 REPLACE Authorization for a Processor Panel SECEPREP SECEPREP REPLACE Authorization for a Processor Command gt Supply information for all input fields Then press Enter Authorization password 4XY YAL AMB 48S Old serial number 10293 Old model number 9672 for example 9021 9121 3090 New serial number 10293 New model number 9652 for example 9021 9121 3090 Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 2 At Old serial number type the serial number of the processor to be replaced BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 17 Replacing Authorization for a Processor A 18 Step3 At Old model number type the model number of the processor to be replaced Step4 At New serial number type the serial number of the processor that will replace t
218. e action specifying the proper numbers If the numbers are correct contact BMC Software Product Support for assistance If the batch program was used verify that the three character product code specified in the PARM statement is correct If the product code is correct but the job still fails contact BMC Software Product Support for assistance PASSWORD IS INCORRECT PLEASE VERIFY AND RE ENTER THE PASSWORD Explanation The specified password is not correct System Action The password is rejected User Response Verify that the password and the product code have been specified correctly and retry the action If the password continues to be rejected contact BMC Software Product Support for assistance COULD NOT FIND THE EXISTING CPU ID ENTRY THAT WAS TO BE DELETED Explanation An attempt was made to delete an entry in the product authorization table but the entry could not be found This error usually indicates that the wrong product library was specified System Action No changes are made to the product authorization table User Response Verify that the correct product load library is specified and retry the action You can view entries in the product authorization table by selecting the Display product authorization option from the Product Authorization Primary Menu see page A 11 or by submitting the product authorization batch program with the LIST option see page A 29 ATTEMPTING TO ADD A CPU ID THAT IS ALREADY IN THE T
219. e installation batch jobs You change only those parameters that are different on each DB2 subsystem The Install System generates installation batch jobs for the specified subsystem but it does not unload data sets from the distribution tape Instead the Install System uses the data sets that were unloaded during the Full installation to install the software on the specified DB2 subsystem Consider the following requirements before you choose the SSID installation path For a subsequent installation on a different DB2 subsystem that does not meet these requirements use the Full installation path again e You can use the SSID installation path only after you complete a Full installation of the selected product e The SSID installation path applies only to those products that can share BMC Software product libraries e The DB2 subsystem that you choose during an SSID installation must have the same version of DB2 as the Full installation of the selected product e Edit your output JCL data set name in the User Options panel before you perform a subsequent SSID installation Note For ALTER and CHANGE MANAGER the SSID installation must be the same version of DB2 as the Full installation Each of these products must also have separate product libraries for each version of DB2 BMC Software Inc Confidential and Proprietary Information 1 16 Administrative Products for DB2 Installation Guide Installation Paths Product Restrictio
220. e plan name CMvrmDDC BMC Software Inc Confidential and Proprietary Information 7 8 Administrative Products for DB2 Installation Guide Controlling Access 3 On the subsystem that has DB2 Version 5 install the DB2 Version 4 compare components that are required for the catalog to catalog Compare feature A Customize the ACMC2CO ACMC2CB and ACMC2CG members of the HLQ CNTL data set using the JCL for DB2 Version 4 for CHANGE MANAGER B In the ACMC2CB member bind the packages using the DB2 Version 4 level DBRMLIB into a collection ID that matches the ID used on DB2 Version 4 ACMvrmC_D_MAIN The plan name in the ACMC2CB member must match the plan name CMvrmCDC that was used on the DB2 Version 4 subsystem Note On DB2 Version 5 the collection ID and the plan name must differ from those used for the exploitation version of CHANGE MANAGER 4 Execute the catalog to catalog Compare feature from the DB2 Version 4 subsystem to the DB2 Version 5 subsystem so that the DB2 Version 4 load library collection ID packages and plan are used Note The Compare or Compare fields can be set to local or remote See the ALTER and CHANGE MANAGER for DB2 User Guide for an example of the steps that are required to run a catalog to catalog comparison Controlling Access Maintaining security over the components of CHANGE MANAGER is an important consideration Executing a worklist usually changes the definitions of your DB2 object
221. e recover utility from IBM or BMC Software or no recover utility If RECOVEN eligible indexes will not be created with DEFER YES If a non unique index is being dropped or created in a worklist and its parent table is not being dropped or created in the worklist then the index will be created with DEFER YES if RECOV I or RECOV B The DOPTs parameters are defined as follows B BMCRECOVER I IBMRECOVER N NO RECOVER The offsite copy threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The offsite copy secondary or alternate unit that is used for any overflow BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 27 Default Option Descriptions RECVPREF amp amp PREFIX amp amp SSID amp amp OBNOD RECVPS 10 RECVSS 2 RECVUNIT SYSDA REORG N RPTPL CMyrmcDR SDSN SYSOUT SDSNE SYSOUT SEQI 050 SL1 HLO LOAD Defines the default prefix high level qualifier that is used for the RECVnnn recovery data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied Defines the default primary space allocation in cylinders for RECVnnn recovery data sets
222. ecification Install System Load Library Specification Command gt Enter the Install System LOAD Library name File 2 on the Product Tape Note that this is not a product LOAD library It is a LOAD library used to run the installation dialog If the LOADLIB is valid press Enter to continue LOADLIB Name BMC DCI INSTALL LOAD Note If you have not unloaded the Install LOADLIB enter Y below After the unload completes successfully restart the Install To generate a batch job to unload File 2 type Y N F1 HELP F2 SPLIT F3 END F4 RETURN F5 RFIND F 6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 LEFT F11 RIGHT F12 RETRIEVE Step 2 Inthe LOADLIB Name field type the name of the Install System load library File 2 of the distribution tape If you unloaded File 2 as instructed on page 2 6 this is the name of the load library as specified in the job that you used to unload the Install System from the distribution tape Step 3 If you followed the unload procedure on page 2 6 or if you have already completed Steps 3 A through 3 E specify N in the next field and press Enter If you did not unload File 2 as instructed on page 2 6 complete the following steps 3 A Type Y in the selection field and press Enter 3 B Type the appropriate job card tape and load library information in the Unload LOADLIB panel and press Enter to generate the JCL 3 C Review the JCL member UNLOAD and edit it as necessary 3 D Run
223. ected products e the ISPF panels and table that correspond to the product CLISTs e most of the CLISTs that are used to run the selected products Some products do not require CLISTs in the installation JCL Warning The default is the HLO JCL data set If you enter an existing data set name the Install System warns you that it will overwrite existing JCL in that data set The installer may need to review the user named output JCL data set periodically to customize a product remove the installation or accommodate the request of a BMC Software technical support representative on a support call You should have one output JCL data set for each type of installation If you overwrite an output JCL data set you remove a helpful audit trail Specify the output JCL VOLSER or Storage Management System SMS parameters Specify a user profile ID for the installation user profile The Install System uses the ID that you specify and the suffix PROF to form the profile member name The default value of the profile ID is DCI and the ID can be up to four characters long The Install System stores the profile in the following locations e the output JCL data set that you specified in Step 3 e the ISPF profile data set ISPPROF that is associated with your user ID e the HLQ INSTALL library that you created when you unloaded the Install System from the tape The installation user profile contains the settings for the installation variables For m
224. ed only if REORG PLUS is installed Specifies the name of the BMC Software UNLOAD PLUS for DB2 product s DOPTs module that CATALOG MANAGER uses to interact with UNLOAD PLUS This parameter is used only if UNLOAD PLUS is installed Specifies the name of the BMC Software RECOVER PLUS for DB2 product s DOPTs module that CATALOG MANAGER uses to interact with RECOVER PLUS This parameter is used only if RECOVER PLUS is installed The DATA PACKER for DB2 plan If installed CATALOG MANAGER can use the AMEND and TRIAL command features BMC Software Inc Confidential and Proprietary Information 6 14 Administrative Products for DB2 Installation Guide DPT DRO O Default Option Descriptions The decimal point character for CATALOG MANAGER must be a comma or a period The Drop Recovery option M mandatory 0 optional N not used EDSN amp amp ZUSER BMCCAT SQLE EPLAN ACTvrnDE ESC FIELDS STATIC FOREIGN STATIC GRPAT HDAL N HDIX Y HDSY N HDTB Y HDTS Y HDVW Y HDPL N The name of the SQL Explorer product s errors listing The name of the plan that enables access to the data editing and browsing functions The SQL string delimiter This must be an apostrophe or a quotation mark You must select the one that matches the way your DB2 system was generated The character that you do not select becomes the SQL escape character Specifies whether CATALOG MANAGER uses static SQL o
225. efore you contact BMC Software have the following information available so that a technical support analyst can begin working on your problem immediately e product information product name product version release number license number and password trial or permanent e Operating system and environment information machine type operating system type version and service pack or program temporary fix PTF system hardware configuration serial numbers related software database application and communication including type version and service pack or PTF e sequence of events leading to the problem e commands and options that you used e messages received and the time and date that you received them product error messages messages from the operating system such as file system full messages from related software iv Administrative Products for DB2 Installation Guide Contents About THIS BOOK 5 65 ici ee i pile aa XV Summary oLGhanges uit idee eil tu Veen xxi Chapter 1 Preparing for Installation Overview cirio einer ii SO eae eS eee ia 1 2 Distribution Methods 0 ccc eee eens 1 2 Administrative Products Tapes 0 0 cece eee eee ee ene 1 2 TIS Tape ceee tenit iatea blebs A a i aai E nd ube 1 3 SAT Tape coi no ted wie ire ia 1 3 Installation Requirements 0 0 0 cece cece ee eee 1 3 Authorization to Run the Installation Batch Jobs
226. egister for services the server must be shut down in an orderly way to be unregistered as an APPC MVS Server Cancelling the server is not recommended You can use an MVS console STOP command P to stop the server Alternatively you can use an MVS modify STOP command F to shutdown the server task in an orderly fashion For a list of available MVS console commands see Table 4 3 on page 4 29 BMC Software Inc Confidential and Proprietary Information 4 28 Administrative Products for DB2 Installation Guide Table 4 3 MVS Commands S jobname Setting Up the MVS Server MVS Commands Description starts the job or task named by the jobname parameter P jobname F jobname DRAIN F jobname LIST stops the job or started task named by the jobname parameter toggles the DRAIN status flag When DRAIN is enabled new clients are prevented from attaching to the server and the server automatically shuts down when all active tasks are complete lists active tasks that are running in the server F jobname STATUS F jobname STOP displays the current status information for the server stops the job or started task named by the jobname parameter F jobname TERM xxx terminates the task where xxx is the key The key is found by issuing the LIST command F jobname TRACE toggles the Global Trace variable F jobname TRCAGENT F jobname TRCSERV toggles the Trace Agent variable to
227. ential and Proprietary Information Administrative Products for DB2 Installation Guide Tables Table 1 1 Table 1 2 Table 1 3 Table 1 4 Table 1 5 Table 1 6 Table 1 7 Table 1 8 Table 1 9 Table 1 10 Table 2 1 Table 2 2 Table 2 3 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 3 10 Table 3 11 Table 3 12 Table 3 13 Table 3 14 Table 3 15 Table 3 16 Table 3 17 Table 3 18 Table 4 1 Table 4 2 Space Estimates for ALTER Objects 1 5 Space Estimates for ALTER Distribution Data Sets 1 5 Space Estimates for CATALOG MANAGER Objects 1 6 Space Estimates for CATALOG MANAGER Distribution Data Sets 1 6 Space Estimates for CHANGE MANAGER Objects 1 7 Space Estimates for CHANGE MANAGER Distribution Data Sets 1 7 Space Estimates for DASD MANAGER PLUS Objects 1 8 Space Estimates for DASD MANAGER PLUS Distribution Data Sets 1 8 Changes in Product Status 1 12 Selecting an Installation Path 1 13 Getting Started with the Install System 00 2 2 DASD Allocations for ESD Images 2 3 Using Double Characters LL 2 16 Additional Tasks for Installation 3 2 Version Equivalents for the Mainframe Server and Client 3 5 DASD MANAGER PLUS Table Synonyms for REORG PLUS and LOADPLUS 3 9 DASD MANAGER PLUS Table Synonyms for COPY PLUS 3 9 SQL Explorer Synonyms LL
228. eport Display This plan controls access to the display of reports Any user needing to report events and exceptions online should be authorized to use this plan BMC Software Inc Confidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 5 Controlling Access ASUvrmDS Statistics Collection This plan controls access to statistics collection Any user needing to run BMCSTATS should be authorized to use this plan ASUvrmDX Cross Reference Utility Access This plan controls access to the Cross Reference Utility Any user needing to use this utility should be authorized to use this plan ASUvrmDZ Browse DASD MANAGER PLUS Database Statistics This plan controls access to the Browse function which displays statistics from the DASD MANAGER PLUS databases Any user needing to display statistics online should be authorized to use this plan You can place minimum restriction on the online programs to allow a user to define objects and to specify and analyze changes By restricting authorization to run the Execution plans see next section you can control which users can actually execute changes Giving wide access to the online programs but controlling access to the Execution Monitor lets your users run DASD MANAGER PLUS for training purposes or use it as a system dictionary DASD MANAGER PLUS Execution Plans The following plans are used by the Execution component AEXvrmDA Execution Monitor Entry A
229. er Response Note the return code and contact BMC Software Product Support for assistance BMC89112W THERE ARE NO ENTRIES FOR LICENSED PROCESSORS Explanation There are no authorized CPUs in the product load library System Action The product does not execute User Response Use a password to add an entry for the correct processor to the product load library BMC89113E DATA SET DOES NOT EXIST OR IS NOT CATALOGED Explanation The specified load library cannot be found System Action The action fails or the batch job terminates User Response Correct the data set name for the product load library or catalog the data set and retry the action BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 13 Error Messages BMC89114E BMC89115E BMC89116E BMC89117E OBTAIN ERROR DATA SET MAY BE ARCHIVED Explanation The specified load library cannot be found and might be archived System Action The action fails or the batch job terminates User Response Verify the data set name for the product load library or restore the data set and retry the action DATA SET IS NOT A VALID LOAD LIBRARY Explanation The specified load library is not a partitioned data set The product authorization interface and Product Authorization utility expect the product load library to be a partitioned data set System Action The action fails or the batch utility job terminates
230. ers must match the load library and options module name that is used when installing DASD MANAGER PLUS See also the description for UBSTP Specifies whether to perform the install SYSADM check when CATALOG MANAGER is initialized Y or N Selecting Y starts a DB2 trace Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCHECKDEP DB catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCHECKS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table The SYSCOPY threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 SYSCMAX is used with JCLGEN only not with the BMC Software COPY PLUS product s dynamic allocation The SYSCOPY secondary or alternate unit that is used for any overflow Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSCOLAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses st
231. ersion B 3 1 C 4 1 D 5 1 and E 6 1 or later y access type D direct l indirect Table 3 7 Examples of Synonym Qualifiers Example besoripioo ALU621DD ALTER 6 2 01 DB2 Version 6 direct access ALU621DI ALTER 6 2 01 DB2 Version 6 indirect access ACT621D CATALOG MANAGER 6 2 01 direct access BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 23 Naming Conventions Options Module The DOPTs module has the following convention prdDOPyz Table 3 8 indicates what the variables represent and Table 3 9 shows examples of DOPTs modules Table 3 8 DOPTs Module Variables Variable Represents access type D direct l indirect Note The access type for CATALOG MANAGER 3 3 or later must be direct D CATALOG MANAGER 3 3 or later is the only Administrative Product that uses a single DOPTs module for both direct access and indirect access Table 3 9 Examples of DOPTs Modules Example Description ALUDOPDT ALTER direct access test subsystem ALUDOPIT ALTER indirect access test subsystem Plan Names Plan names have the following convention e prdvrmyz all products with the exception of ALTER and CHANGE MANAGER 5 2 or later e ppvrmcyz ALTER and CHANGE MANAGER 5 2 or later BMC Software Inc Confidential and Proprietary Information 3 24 Administrative Products for DB2 Installation Guide Naming Conventions Table 3 10 indicates wh
232. ese naming conventions may not incorporate the version and release level of the BMC Software products the object names in the new release may become identical to those in the old release You can install a new release and then copy the data from the old release to the new release using identical DB2 object names for example database and table names See Migrating DB2 Objects Between Releases on page 2 26 for detailed steps BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Chapter 2 Using the Install System This chapter presents the following topics Getting Started ict ce taws toute wie nee hoe ee Se a 2 2 Processing an ESD Image 0 0 2c eee ee eee 2 3 Unloading the Install System 2 6 Starting the Install System 2 10 Running the Install System 2 14 Main M nu piloni be ge cab esse gee a ein 2 14 Keys and Commands 0 0 0 cece eee eee eee 2 14 Data Set Names saes iii SP od EL 2 15 Symbolic Variables 0 0 0 eee eee eee 2 15 Considerations for SAS C LL 2 17 Specifying User Options 0 0 0 0 cece ee eee ee eee 2 19 Generating Installation JCL LL 2 22 Migrating DB2 Objects Between Releases 2 26 Cancelling the Installation LL 2 27 Reverting to Conditions Prior to a Tape Installation 2 27 Reverting to the Prior Version of an Individual Product 2 28 Where to Go
233. esetting Authorization for all Processors Resetting Authorization for all Processors A 22 Summary Use the Product Authorization Primary Menu to reset a global property applying to all CPU IDs of the authorization table Step 1 On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 Step 2 At Product load library type a fully qualified data set name and press Tab Step3 At Authorization password type your permanent password and press Enter A pop up message explains that the product authorization table was updated successfully Figure A 10 Figure A 10 Product Authorization RESET Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options 1 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about ba 2 EXIE Additional information Product load library BMC PRODUCT LOAD Authorization password BMC89029I PRODUCT AUTHORIZATION TABLE WAS Fl Help SUCCESSFULLY UPDATED PRESS ENTER TO CONTINUE F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 4 Press F3 to exit the Product Authorization utility and return to the previous menu or panel BMC Software Inc Confidential and Proprietary Information Administra
234. ess generates a customized installation data set This data set contains customized jobs that are created to install these products into your specific DB2 environment One of these jobs is used to establish the default processing option values The job name begins with a character followed by a three character identifier that varies depending on which Install System installation path that you used The last four characters are always DOPT The xnnDOPT member of the installation data set contains an assembly language program with an options macro call that establishes the default processing values You can tailor the installation of the product including changing plan names by editing the default values in the xnnDOPT member Installation Defaults During installation you can specify names for options modules synonym qualifiers database names creator names and collection names The default values for these names are listed in Table 8 1 In these default values v indicates the version r indicates the release and m indicates the maintenance level Table 8 1 DASD MANAGER PLUS Installation Default Values Part 1 of 2 Default Options Module ASUDOPD1 Synonym Qualifier ASUvrmD BMC Software Inc Confidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 3 Installation Considerations Table 8 1 DASD MANAGER PLUS Installation Default Values Part 2 of 2 Installation Default Value Database
235. etary Information 4 42 Administrative Products for DB2 Installation Guide Confirming the Host Code Page for the MVS Server Confirming the Host Code Page for the MVS Server Summary This section describes the steps that you must perform to verify the setting for your Host Code Page The Host Code Page setting specifies the table that the application uses to map the EBCDIC codes on the server to the appropriate single byte ASCII codes on the PC during the transfer of data Step 1 Edit the INI ACV file Step 2 Set the value of the sbiDBS CP variable in the INIHACV file to one of the Host Code Page values in Table 4 6 Note The default value for the sbiDBS CP variable is CP037 Table 4 6 Code Page Values Host Code Page Value Language CP037 English US CP273 Austrian or German CP277 Danish or Norwegian CP278 Finnish or Swedish CP280 Italian CP284 Spanish CP285 English England CP297 French CP500 International Step 3 Start PATROLDB to activate the MVS Server Where to Go from Here After you confirm the host code page you determine whether to enable the use of secondary authorization IDs for each client For more information see Enabling the Use of Secondary Authorization IDs on page 4 44 BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 43 Enabling the Use of Secondary Authorization IDs Enabling the Use of Secondary Authorizati
236. fault processing option values The job name begins with a character followed by a three character identifier that varies depending on which Install System installation path that you used The last four characters are always DOPT The xnnDOPT member of the installation data set contains an assembly language program with an options macro call that establishes the default processing values You can tailor the installation of the product including changing plan names by editing the default values in the xnnDOPT member Installation Defaults During installation you can specify names for options modules synonym qualifiers command modules database names creator names and collection names The default values for these names are listed in Table 6 1 In these default values v indicates the version r indicates the release and m indicates the maintenance level Table 6 1 CATALOG MANAGER Installation Default Values Value ACTDOPD1 ACTvrmD ACTCOMND BMCACT vr BMCACT vr ACTvrm_D_MAIN Installation Default Default Options Module Synonym Qualifier Command Module Database Name Creator Name Collection Name Implementing Catalog Indirection Catalog indirection is an optional method of implementing and maintaining the Administrative Products To implement catalog indirection see Implementing Catalog Indirection on page 3 20 For information on collection names see Collection Names on page 3 25
237. fices html USA and Canada Outside USA and Canada Address BMC Software Inc Telephone 01 713 918 8800 2101 CityWest Blvd Houston TX 77042 2827 Fax 01 713 918 8000 Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000 Customer Support You can obtain technical support by using Response Online comprehensive information from the Web or Response On Demand To expedite your inquiry please see Before Contacting BMC Software below Response Online You can obtain technical support from BMC Software 24 hours a day seven days a week by accessing the technical support Web site at http www bmc com support html From this site you can e read overviews about support services and programs that BMC Software offers e find the most current information about BMC Software products e search a database for problems similar to yours and possible solutions e order or download product documentation e report a problem or ask a question e subscribe to receive e mail notices when new product versions are released e find worldwide BMC Software support center locations and contact information including e mail addresses fax numbers and telephone numbers Response On Demand In the USA and Canada if you need technical support and do not have access to the Web call 800 537 1813 Outside the USA and Canada please contact your local support center or your local sales office for assistance Before Contacting BMC Software B
238. fidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 13 Post Installation Considerations TIMEPARM WDC Indicates the TIME limit in minutes for each step in a batch job stream The Data Facility Storage Management Subsystem DFSMS or SMS data class name used at data set allocation time to define the allocation attributes of the data set A data class name is not required even for SMS data sets WDC will appear as DATACLAS in the JCL for workfiles WDSN amp amp PREFIX amp amp SSID amp amp WKID WMC WPS 10 WSC WSS 2 WU SYSDA XPLAN ASUvrmDX ZPLAN ASUvrmDZ The default worklist data set name for a new Work ID This data set can be either a sequential file or a partitioned data set PDS Note In many installations allocation of data sets is controlled by user written or third party routines If allocation fails you should use alternate means such as ISPF to perform the allocations The SMS management class name used at data set allocation time to define the migration retention and backup requirements of the data set WMC will appear as MGMTCLAS in the JCL for workfiles Defines the default work primary space allocation in cylinders for work data sets that include Analysis and Execution diagnostics The SMS storage class name used at data set allocation time to define processing requirements of the data set WSC will appear as STORCLAS in the JCL fo
239. g symbols in passwords A 4 SRPR DOPT 6 23 JSRSE DOPT 6 23 SRUN DOPT 6 23 SWPR DOPT 6 23 SWSE DOPT 6 23 SWVL DOPT 6 24 JTILCOPY DOPT 5 23 7 31 JTILITY MANAGER 4 11 JUSTP DOPT 6 24 JVDEV DOPT 6 24 4 4 4 cocecte eee aia ees 4 4 Gases aaqeaqaqaeaaqaqaGgea 4 4 C accdcd e GE Index 19 IVDPR DOPT 6 24 XPLAN DOPT 8 14 IVDSE DOPT 6 24 IVDSP DOPT 6 24 JVSTP DOPT 6 24 Z JWEPR DOPT 6 24 JWESE DOPT 6 24 ZPLAN DOPT 8 14 JWFUN DOPT 6 24 WEVL DOPT 6 24 JWLPR DOPT 6 24 JWLSE DOPT 6 24 WLUN DOPT 6 24 JWLVL DOPT 6 24 IXSTP DOPT 6 24 4 4 GEG ae eC dee Eee V verifying installation 4 20 4 45 version level determining 1 12 version upgrades product authorization A 8 VIEWDEP DOPT 6 24 VIEWS DOPT 6 25 VMAX DOPT 6 25 VMAXU DOPT 6 25 VOLSER number verifying 2 13 VOLUMES DOPT 6 25 VRM DOPT 5 23 7 31 VRMM 1 12 VVALPROP DOPT 5 23 7 31 W WDC DOPT 5 23 6 25 7 32 8 14 WDSN DOPT 5 23 6 25 7 32 8 14 WLDSN DOPT 6 25 WLPS DOPT 5 23 7 32 WLSS DOPT 5 23 7 32 WLU DOPT 5 23 7 32 WMC DOPT 5 24 6 25 7 32 8 14 WPS DOPT 5 24 7 32 8 14 WSC DOPT 5 24 6 25 7 32 8 14 WSS DOPT 5 24 7 32 8 14 WU DOPT 5 24 7 32 8 14 X XDSN DOPT 6 25 BMC Software Inc Confidential and Proprietary Information 20 Administrative Products for DB2 Installation Guide Notes 100037827
240. ge Manager in toleration mode using catalog indirection and CATALOG MANAGER 6 1 or later Maintaining BMC Software Administrative Products Then Migrate the DB2 catalog 2 Modify the ASUDB26E worklist member in the HLQ JCL library 3 Execute the worklist using a modified copy of the I40INST job that the JCL job dialog generated 4 Rebind all DASD MANAGER PLUS packages and plans by using ASUssidP bind packages and ASUssidB bind plans where ssid is the subsystem ID Then you will be operating in toleration mode 1 Migrate the DB2 catalog 2 Run HLQ CNTL UPGRD5 6 Then you will be operating in exploitation mode 1 Perform a Full installation of ALTER or CHANGE MANAGER 6 2E Then you will be operating in exploitation mode 2 Reinstall catalog indirection Reinstall catalog indirection Migrating DB2 Version 5 to Version 6 Part 4 of 4 To Fall Back Then Rebind all DASD MANAGER PLUS packages and plans by using ASUssidP bind packages and ASUssidB bind plans where ssid is the subsystem ID Rebind all DASD MANAGER PLUS packages and plans by using ASUssidP bind packages and ASUssiaB bind plans where ssid is the subsystem ID 1 Provided that the previous indirection still exists remove the indirect copy or view in exploitation mode 2 Provided that ALTER CHANGE MANAGER PATROL DB Alter or PATROL DB Change Manager still exists in toleration mode use the fallbac
241. ge 3 4 BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 17 Verifying the Product Authorization Verifying the Product Authorization Summary All BMC Software products require Product Authorization before you can use them This section describes how you can authorize your products You can enter your BMC Software Authorization passwords when you install the Administrative Products If you are a licensed user and have already received and entered the permanent BMC Software Authorization passwords ensure that the appropriate authorization modules are saved and copied to the new load library after you execute the Full or Maintenance installation The authorization modules are created when the password is added Alternatively you can use the BMC Software Product Authorization utility to apply passwords and to change your CPU configuration To use the Product Authorization utility refer to Appendix A BMC Software Product Authorization BMC Software Inc Confidential and Proprietary Information 4 18 Administrative Products for DB2 Installation Guide Invoking the BMCDB2 CLIST Invoking the BMCDB2 CLIST Summary This section describes the steps that you must complete to invoke the CLIST Step 1 Invoke the BMCDB2 CLIST by using one of the following e Ifyou specify your high level qualifier with JCL as the low level node invoke BMCDB2 directly from your
242. ggles the Trace Server variable Note For detailed information about establishing a server with APPC MVS refer to the MVS ESA Planning APPC Management Reference Manual To Set Up the MVS Server Step 1 Define an APPC logon mode in the VTAM logon mode table A logon mode is a set of parameters that determine the characteristics of the communication session between the client and the server The person who is responsible for setting up the MVS system s network definitions defines the logon mode Typically this person is familiar with making the network definitions available to VTAM An installation can create several logon mode tables that contain varying communication characteristics for the MVS VTAM network The logon mode tables are assembled and link edited to SYS1 VTAMLIB All the modes that the server LU uses should be contained in the table and specified in the server s LU APPL definition statement BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 29 Setting Up the MVS Server Figure 4 17 on page 4 31 shows a sample logon mode table that contains three logon modes including the required SNASVCMG entry In the sample LU definition the specified logon mode table was assembled and linked as ACVAPPC Note This example is available in SYS1 SAMPLIB in member ATBLMODE It can be assembled and linked using member ATBLJOB The server can use the s
243. h information about the affected CPUs For each product that you license use the work sheet in Table A 3 to record the CPU information and the passwords that you receive from BMC Software The first line of the table provides a sample entry for a 9X2 with three processors and a CPU ID of 10309 9021 DA Note CPU information is not needed for temporary passwords Table A 3 Product Authorization Work Sheet Version CPU Serial CPU Type Code Permanent Password 10309 123 456 789 ABC For information about determining your CPU ID see Displaying Current Processor Information on page A 26 or use the LIST option of Batch Product Authorization see page A 29 Online Product Authorization This section describes the online interface that is used for product authorization To apply passwords using the batch interface see Batch Product Authorization on page A 27 BMC Software Inc Confidential and Proprietary Information A 10 Administrative Products for DB2 Installation Guide Online Product Authorization Processing a Permanent Password Use the Product Authorization Primary Menu Figure A 1 to process passwords You can also obtain pertinent information about the current processor and the authorization for that processor Figure A 1 Product Authorization Primary Menu SECEPPRI SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an opt
244. h level qualifier of BMC DB41 During the installation JCL and the BMCDB2 CLIST are generated into BMC DB41 JCL The table shown in Figure 4 10 is added to the bottom of the BMCDB2 CLIST Figure 4 10 Adding CHANGE MANAGER to Subsystem DB41 DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME i a ACM DB41 D ACMDOPD1 CMvrmCDF ACMB X LIB SSID Data Set Name EXIT DB41 SYS3 DB41 DSNEXIT Li LOAD DB41 SYS2 DB2V41M DSNLOAD e Ifthe BMCDB2 CLIST in BMC DB31 JCL is used to invoke CHANGE MANAGER for both SSIDs you must add the lines in Figure 4 11 to the control table Figure 4 11 Running DB41 Administrative Products from the DB31 BMCDB2 CLIST DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME hi ACM DB41 D ACMDOPD1 CMvrmCDF ACMB LIB SSID Data Set Name EXIT DB41 SYS3 DB41 DSNEXIT LOAD DB41 SYS2 DB2V41M DSNLOAD x HLO DB41 BMC DB41 a The HLQ in Figure 4 11 tells the BMCDB2 CLIST to use BMC DB41 as the high level qualifier for products that are installed on SSID DB41 Figure 4 12 on page 4 11 shows the updated table at the bottom of BMC DB31 JCL BMCDB2 BMC Software Inc Confidential and Proprietary Information 4 10 Administrative Products for DB2 Installation Guide Enabling the Product CLISTs Figure 4 12 Updated BMCDB2 CLIST DATA PROD SSID D I DOPT PLAN APPL
245. has been triggered The grace period can be triggered when you run a permanently licensed product on an unlicensed processor You should apply a RESET password to reset the grace period Contact your BMC Software sales representative for assistance date on which you will no longer be allowed to bypass the CPU ID check or trial the product The variables are as follows e mm represents the month in the range 01 12 ddrepresents the day in the range 01 31 e yyyy represents the year in the range 0001 9999 Note If this expiration date has not yet been reached you can run this product on any processor On the date shown either your trial period will end or if you have licensed the product you will be able to run the product only on an authorized processors Licensed processors list of properties for each licensed CPU The Version Code column reflects the hardware representation of the submodel Significant Digits refers to the number of significant digits for the serial number The expiration date indicates the month and year through which you are licensed for the specific processor In most cases this value is NONE Most of the remaining processor information is provided for reference in case you need to contact BMC Software Product Support BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 25 Displaying Current Processor Information Displaying Current
246. he BMC Software products on a single subsystem All products allow you to choose a Full installation path This installation path has the following characteristics e creates new product libraries and DB2 objects e allows an interface with other BMC Software products e allows data migration from a previous release when you specify the Custom installation mode e allows you to retain BMC Software security authorization from a previous release e allows use of your own VSAM data sets when supported by the selected product and when you specify the Custom installation mode Note ALTER and CHANGE MANAGER are the only products that must have separate libraries for each DB2 version on which they are installed Maintenance Installation Use the Maintenance installation path to install a maintenance update of BMC Software products To use the Maintenance installation path you must have an installed version of the product Warning The Maintenance installation path can overlay existing DB2 plans and packages If you do not change the DB2 plan name you can lose access to your currently installed products To avoid this problem specify a new DB2 plan name for the Maintenance installation This installation path has the following characteristics e optionally creates new product libraries e allows data migration from a previous release e allows you to retain BMC Software security authorization from a previous release BMC Software In
247. he COPY REPLACE option in the JCL that you use to unload the tape When you use a merged data set with the Install System the installation panels list all of the tape volume serial numbers VOLSERs and products that are available in the merged data set For more information about merging distribution tapes see Unloading the Install System on page 2 6 Understanding Checkpoints The amount of time that is required to install BMC Software products depends on several factors including the number of products that you install the installation path that you choose for each product and the complexity of each product By taking checkpoints at predetermined points the Install System enables you to interrupt the installation at any time When you resume the installation process the Install System displays a list of the checkpoints that were taken before the interruption The Install System also saves the options that you specified before the interruption to an ISPF profile For more information about the ISPF profile data set see Installation User Profile on page 1 19 If the Install System is unable to perform the save no checkpoints will exist You can return to any checkpoint or begin the installation again which removes all checkpoints that were taken in the previous session BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 9 Installation Paths Installation Modes The
248. he offsite copy threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The offsite copy secondary or alternate unit that is used for any overflow RECVPREF amp amp PREFIX amp amp SSID amp amp OBNOD RECVPS 10 RECVSS 2 Defines the default prefix high level qualifier that is used for the RECVnnn recovery data sets The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied Defines the default primary space allocation in cylinders for REC Vann recovery data sets Defines the default secondary space allocation in cylinders for RECVnnn recovery data sets BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 19 Default Option Descriptions RECVUNIT SYSDA Defines the default unit that is used for creating RECVnnn recovery data sets REORG N Indicates whether to generate reorganizations in worklists for operations which require reorganizing table spaces and indexes Changes to attributes such as PRIQTY SECQTY PCTFREE FREEPAGE and VOLUME for VCAT defined partitions can cause placement of reorganization commands in the worklist If reorganizations are to be generated this option als
249. he old processor Step 5 At New model number type the model number of the processor that will replace the old processor and press Enter A pop up message on the Product Authorization Primary Menu explains that the product authorization table was updated successfully replacing the old processor with the new processor Figure A 7 Figure A 7 Product Authorization REPLACE Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options _ 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about bi BX Additional information Product load library BMC PRODUCT LOAD Authorization password Fl Help BMC89129I PROCESSOR WAS SUCCESSFULLY REPLACED IN THE PRODUCT AUTHORIZATION TABLE YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON SERIAL NUMBER 10293 MODEL NUMBER 9652 PRESS ENTER TO F2 Split F3 Ex CONTINUE Step 6 Press F3 to exit the Product Authorization utility and return to the previous menu or panel BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Modifying Authorization for an Existing Processor Modifying Authorization for an Existing Processor Summary Use the MODIFY Authorizatio
250. he package owner DYNAMIC uses the privileges of the person who is listing the table The SYSREC threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSREC secondary or alternate unit that is used for any overflow BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 19 Default Option Descriptions ROUTINA STATIC ROUTINE STATIC SCHEMAA STATIC Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSROUTINEAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSROUTINES DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSSCHEMAAUTH DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table SDSN amp amp ZUSER BMCCAT SQLS SSID DB2 STMT STATIC STOGROU STATIC STRINGS STATIC SYNONYM STATIC SZDEV 3380 TABAU
251. his application For information about installing the products on the Administrative Products for DB2 CD see Chapter 9 Installing the Client for ALTER and CHANGE MANAGER Distribution Methods BMC Software distributes products in the following ways e on hard media such as a tape or CD e electronically either by file transfer protocol FTP or from the BMC Software Web site http www bmc com The following sections describe the contents of the distribution tape If you request electronic distribution the distribution package is an Electronic Software Distribution ESD image The image compresses the product data sets into one or more sequential data sets Installing from an ESD image is slightly different than installing from a tape For more information about installing from an ESD image see Processing an ESD Image on page 2 3 Administrative Products Tapes The Administrative Products are distributed on two tapes with the volume prefixes TIS Tools Install System and SAT Second Administrative Tape The products on the tapes are installed by the Install System Note New to the TIS and SAT tapes is the marketing solution called Administrative Assistant for DB2 When you choose Administrative Assistant for DB2 on the Product Selection Menu the ALTER for DB2 and CATALOG MANAGER for DB2 products are automatically installed BMC Software Inc Confidential and Proprietary Information 1 2 Administrative Products
252. his plan This plan does not control the use of the ENVI keyword with batch components BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 5 Controlling Access ALTER Execution Plans The following plans are used by the Execution component AEXvrmAA Execution Monitor Entry Authorization EXECUTE authority on this plan allows users to execute a worklist You should therefore carefully consider who receives authorization to use this plan AEXvrmAM Execution Monitor This plan does not control who has authorization to execute a worklist It does however provide users with the ability to attach to DB2 with alternate authorization IDs for the AUTH commands Because this plan does not affect who can run Execution you may grant PUBLIC authority to this plan The execution plan contains some packages that use dynamic SQL Some of these packages will cause long running SQL and may need to be added to your RLST The packages are described as follows e AEXAUNLD is the package that does the unload of data from tables e AEXSQLIO is the package that does all worklist SQL commands including deletions before a data only migration LOAD e AEXESTDL is the package that does some of the restart logic before the restart of a LOAD including the deleting of previously loaded rows By restricting authorization to run the Execution plans you can control what change and migrate functions users c
253. ibrary to a library in the SYSPROC concatenation If you do not you will not have access to the CLIST unless you explicitly invoke it Note Make sure that the current copy of the BMCMSG CLIST is in the same library as your other CLISTs BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 13 Compiling SLIBs Compiling SLIBs Summary Step 1 Step 2 Step 3 The Administrative Products share a common component called JCL Generation This component generates the JCL that is needed to execute all the batch functions that use ISPF file tailoring You may need to change members of the BMC Software product skeleton library SLIB to generate environment specific JCL This section describes the steps you must perform to edit test and compile the SLIB Edit the appropriate SLIB members in HLQ SLIB to change the way the JCL is generated Note Any customizations that you have made to the SLIB members for a previous release will not be included in your current installation Use JCLGEN to test the changes to the SLIB For more information refer to the ALTER and CHANGE MANAGER for DB2 User Guide the CATALOG MANAGER for DB2 User Guide and the DASD MANAGER PLUS for DB2 User Guide Compile the SLIB members that you edited For more information refer to the ALTER and CHANGE MANAGER for DB2 User Guide the CATALOG MANAGER for DB2 User Guide and the DASD MANAGER PLUS for DB
254. ic delete step is only performed if the condition code that is returned from any previous job step is four or less Y or N JDSN amp amp PREFIX ANALYSIS amp amp WORKID Defines the default data set name that is used for Analysis JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The products automatically use the Work ID as the member name JDSNB amp amp PREFIX BASELINE amp amp WORKID Defines the default data set name that is used for Baseline JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The product automatically uses the Work ID as the member name BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 25 Default Option Descriptions JDSNBG amp amp PREFIX JCLGEN amp amp WORKID For DB2 Version 5 and later defines the default data set name that is used for batch JCL Generation This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The products automatically use the Work ID as the member name JDSNC amp amp PREFIX COMPARE CMPJCL Defines the default data set name that is used for Compare JCL This data set can be either a sequential or partitioned data set JDSNCPL amp
255. ill use for example BMC INSTALL LOAD Note In Figure 2 1 on page 2 7 the variable XXXYMD represents the product tape VOLSER For products that are contained on two tapes use either tape to unload the Install System BMC Software Inc Confidential and Proprietary Information 2 6 Administrative Products for DB2 Installation Guide Unloading the Install System Figure 2 1 Unload Job for the Install System DCIINST JOB ACCOUNT UNLOAD EXEC PGM IEBCOPY SYSPRINT DD SYSOUT SYSUT3 DD UNIT SYSDA SPACE TRK 1 1 SYSUT4 DD UNIT SYSDA SPACE TRK 1 1 DCITINST DD DSN BMC INSTALL DISP OLD VOL SER xxxymd UNIT TAPE LABEL 1 SL EXPDT 98000 DCITLOAD DD DSN BMC INSTALL LOAD DISP OLD VOL SER xxxymd UNIT AFF DCITINST LABEL 2 SL EXPDT 98000 LE DCIINST DD DISP CATLG DELETE DSN your name INSTALL UNIT SYSDA SPACE CYL 40 5 700 DCB RECFM FB LRECL 80 BLKSIZE 6160 DCILOAD DD DISP CATLG DELETE DSN your name INSTALL LOAD UNIT SYSDA SPACE CYL 5 1 40 DCB RECFM U BLKSIZE 23476 SYSIN DD COPY I DCITINST O DCIINST COPY I DCITLOAD O DCILOAD Step 2 To install products from multiple tapes edit the unload job to copy multiple INSTALL data sets into a single data set by using the REPLACE option For each tape to be merged you mu
256. improve the performance of the Administrative Products If you are using DB2 Version 4 or later you can add your own indexes to the copy of the catalog You can also reorganize the tables or table spaces of the catalog copy For information about performance considerations see Performance Considerations on page 4 2 For catalog indirection to be effective you must ensure that the copy of the catalog reflects the status of the actual catalog The degree of accuracy that is required depends on the type of users who are involved and the purpose of their information queries The job that updates the catalog copy temporarily halts all information queries made through the copy Controlling Catalog Access Data centers with highly sensitive information may need to restrict how users access specific tables in the DB2 catalog To restrict catalog access you can implement catalog indirection through one or more user created views that filter out specified columns within the DB2 catalog tables You can allow specific user groups to use the Administrative Products in a limited fashion without compromising the security of the data or data structures that are defined in the catalog tables Considerations for Using a Copy of the Catalog Maintaining a copy of the catalog uses additional DASD space The amount of space that is required equals the size of your DB2 catalog and can vary greatly depending on your DB2 system For example assume that a u
257. in Unloading the Install System on page 2 6 e Start the Install System as instructed in Starting the Install System on page 2 10 To Specify User Options Step 1 From the Install System Main Menu type 0 in the selection field and press Enter Step 2 Select an installation mode by typing 1 for Quick or 2 for Custom e Quick installation limits the number of panels that are shown for most products to the common installation panels and the synonym and DOPTs panels These panels use the default values that BMC Software provides The Quick option does not allow you to migrate from an earlier version of a product e Custom installation displays all of the option panels for each product in addition to the common installation panels This option allows you the most flexibility in setting up the components of the products from file and database names to file sizes and product execution parameters Note The Quick option is not available for all products Refer to the appropriate product chapters for more information about the installation options that are available for specific products BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 19 Specifying User Options Step 3 Step 4 Step 5 Specify an output JCL data set to contain the installation JCL that the Install System generates The output JCL data set contains e all of the jobs that are used to install the sel
258. in Figure 2 5 on page 2 27 Warning Using the same object names between releases is not recommended because it replaces your current DB2 structures To Use Existing DB2 Object Names for a New Release Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 When the Object Storage Verification panel prompts you select the option to migrate data Change the DB2 object names of the BMC Software product to your naming conventions After you generate the installation batch jobs run all of the jobs that are listed before xnnINST Run the first xnnMIG job to unload the data from the current DB2 databases Drop the current DB2 databases for the BMC Software product using I98DROP from the previous install JCL Resume installation with job xnnBNDI to bind the install plan just freed until you get to the first xnnMIG job Run the second xnnMIG job to load the data into the new tables Run the remaining jobs starting with xnnCOPY and ending just before I98DROP Warning Do not run I98DROP or I99DLTE until you are ready to uninstall the product BMC Software Inc Confidential and Proprietary Information 2 26 Administrative Products for DB2 Installation Guide Cancelling the Installation Figure 2 5 Sample Installation Batch Jobs EDIT BMC Vvrm DB2T JCL Row 00001 of 00014 Command gt Scroll gt CSR Name Prompt VV MM Changed Size Init IOODOC 01 00 99 02
259. ing the INI file Figure 4 20 on page 4 34 shows a sample MVS Server configuration file BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 33 Setting Up the MVS Server Figure 4 20 Sample APPC for MVS Configuration File sbiDBS MaxAgents 16 sbiDBS AutoStart 1 sbiDBS Serverl MVSAPPC sbiDBS MAXADDR 16 sbiDBS CP CP500 VSDB2 AccessDriver SBIDB2M VSSPD AccessDriver SBISPDM VSJZS AccessDriver SBIJZSM VSFILE AccessDriver ACVFILM VSAPPC ServerEnabled 1 VSAPPC OperatingMode SERVER VSAPPC LocalMethod MultiplexSVP VSAPPC AccessDriver SBIRTMM VSAPPC ProtocolDriver SBIAPPCM IVSAPPC TPname APPCACVI IVSAPPC MODEname APPCPCLM VSAPPC LUname ACVLUO1 VSAPPC packetsize 8192 VSAPPC receivetimeout 0 VSAPPC transmitttimeout 0 IVSAPPC SASDebug 0 JISI USISSID JSI1 JSI JESSSID JES2 JSI JSIDLL 00 JSI SPOOLBYOWNER 0 FOREGROUND STARTEDPROC BMCAKMF G SCRIPT FIL Eal BMCADMN V621 V62 SCRIPT DOPTS DBAL DIRECT BMCADMN V621 V62 LOAD KGCDOPT Table 4 4 describes some of the important configuration parameters which you may need to modify manually Table 4 4 APPC MVS Configuration Parameter Descriptions Part 1 of 2 AccessDriver name of the RTM driver program The value is SBIRTMM LocalMethod indicates multiplexed service provider The value is MultiplexSVP BMC Software Inc C
260. ining 9 13 platforms supported 9 2 setting up 4 41 starting 9 18 stopping 9 18 uninstalling 9 15 9 16 CLIST data set Administrative Products for DB2 Installation Guide ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 CM PILOT applications 7 4 description 7 3 diagnostics 7 5 predefined scripts 7 3 worklists 7 4 CMAX DOPT 6 12 CMAXU DOPT 6 12 CMP DOPT 7 22 CMPDIAG DOPT 7 22 CMvrmcDA Analysis plan 7 11 CMvrmcDB Baseline plan 7 11 CMvrmeDC Compare plan 7 11 CMvrmcDE Environment plan 7 12 CMvrmcDF Front End plan 7 10 CMvrmcDI Import plan 7 11 CMvrmcDR Report plan 7 11 CMvrmcDS Specification plan 7 11 CNTL data set ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 COLAUTH DOPT 6 12 COLDISS DOPT 6 13 COLDIST DOPT 6 12 collection names 3 23 collection nicknames 3 26 COLSTAT DOPT 6 13 COLUMNS DOPT 6 13 COMD DOPT 6 13 commands 2 14 Compare component 7 6 compiling the SLIB 4 14 configuring clients 9 18 CONNECT command 4 20 CONSTDE DOPT 6 13 CONTAB command 4 20 control statements for batch authorization A 29 controlling access ALTER 5 4 CATALOG MANAGER 6 5 CHANGE MANAGER 7 9 DASD MANAGER PLUS 8 5 BMC Software Inc Confidential and Proprietary Information conventions document xix naming 3 23 syntax statements xx typographical xix COPY DOPT 6 13 COPYDD01 DOPT 5 15 7 22 COPYDD02 DOPT 5 15 7 22 copying the installation image to a network drive 9 8 CPLAN DOPT 8 10
261. inistrative Products for DB2 Installation Guide Upgrading ALTER to CHANGE MANAGER Upgrading ALTER to CHANGE MANAGER To upgrade to CHANGE MANAGER without migrating your existing data in ALTER perform a Full installation of CHANGE MANAGER To upgrade to CHANGE MANAGER and to migrate your existing data from ALTER to CHANGE MANAGER use the following procedure BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 27 Migrating Data From ALTER to CHANGE MANAGER Migrating Data From ALTER to CHANGE MANAGER Summary This task describes how you can migrate data from an existing ALTER product environment to the CHANGE MANAGER product environment To migrate your data from an existing ALTER environment to CHANGE MANAGER you must have ALTER 3 6 or later installed To Install CHANGE MANAGER Step 1 Step 2 Perform Step 1 through Step 6 of the procedure Generating Installation JCL on page 2 22 to install CHANGE MANAGER and to build a valid I67COPY image copy job 1 A From the Install System Previous Release of Product panel select an installed release level for CHANGE MANAGER Note Do not select NONE 1 B From the Install System CHANGE MANAGER Object Storage Verification panel type to Select to migrate data from Change Manager v r 1 C From the Install System CHANGE MANAGER Migration Verification panel remove the asterisk from the Creator Name The
262. installation defaults 7 5 migrating data from ALTER 3 28 object security 7 13 overview 7 2 plans 7 9 post installation tasks 4 3 product description 7 2 space requirements 1 7 Specification and Analysis plans 7 10 upgrading from ALTER 3 27 5 4 CHANGE MANAGER data sets CLIST 1 7 CNTL 1 7 DBRM 1 7 LOAD 1 7 Administrative Products for DB2 Installation Guide MLIB 1 7 MSGS 1 7 MSGTEXT 1 7 PLIB 1 7 SCRIPT 1 7 SLIB 1 7 TLIB 1 7 CHANGE MANAGER DOPTs ACTDOPT 7 18 ACVPLAN 7 18 ALLOC 7 18 AMS 7 19 ANP 7 19 ARCHPPREEF 7 19 ARCHPS 7 19 ARCHSS 7 19 ARCHUNIT 7 19 ASUDOPT 7 19 ATTN 7 19 AUTHSW 7 19 BASDIAG 7 20 BASE 7 20 BLDBS 7 20 BLDCU 7 20 BLRPPREF 7 20 BLRPPS 7 20 BLRPSS 7 20 BLRPUNIT 7 20 BMCCHECK 7 21 BMCCOPY 7 21 BMCLOAD 7 21 BMCSTATS 7 21 BMCUNLD 7 21 BPOOLIX 7 21 BPOOLTS 7 21 BRPTDIAG 7 21 BRPTDSN 7 21 CATAUDIT 7 21 CATRECOV 7 22 CCSID 7 22 CDLDSN 7 22 CDLPS 7 22 CDLRDSN 7 22 CDLSS 7 22 CDLU 7 22 CMP 7 22 CMPDIAG 7 22 COPYDD01 7 22 BMC Software Inc Confidential and Proprietary Information COPYDD02 7 22 CPLDIAG 7 23 CPLWDSN 7 23 DASDMAN 7 23 DATACLAS 7 23 DATE 7 23 DB2CAT 7 23 DB2CT 7 23 DBRMI 7 23 DBRM2 7 23 DBRM3 7 23 DBRMLIB 7 23 DEFERUIX 7 23 DISCARDS 7 24 EAP 7 24 EIP 7 24 ENVP 7 24 EPP 7 24 EURO 7 24 FEP 7 24 GLID 7 24 HSMVOL 7 25 IMP 7 25 IMPDIAG 7 25 ISPSLIB 7 25 IXTYPE 7 25 JC1 7 25 JC2 7 25 JC3 7 25 JC4 7 25 JC5 7 25 JCLCLEAN 7 25 JDSN 7 25 JDSNB 7 2
263. ion amp amp PREFIX amp amp SSID CATALOG MANAGER Default Options Listing Part 3 of 5 P amp amp PREFIX amp amp SSID amp amp OBNOD FF F FF FF F FF FF F F FF F F FF F F F FF F F FF F F FF F F KF F F PAPI PI PI PG pi Pi PI Pi pi pi PI PI I pi pi I DI Chapter 6 Installing CATALOG MANAGER 6 9 Default Option Listing DOPTs Figure 6 1 CATALOG MANAGER Default Options Listing Part 4 of 5 DBRM STATIC FIELDS STATIC FOREIGN STATIC INDEXES STATIC D D INDEXPA STATIC INDEXST STATIC KEYS STATIC LOBSTAT STATIC PACKAGE STATIC PACKAUT STATIC PACKDEP STATIC PACKLIS STATIC PACKSTM STATIC PARMS STATIC PKSYSTE STATIC PLAN STATIC PLANAUT STATIC PLANDEP STATIC PLSYSTE STATIC PROCEDU STATIC RELS STATIC RESAUTH STATIC ROU A STATIC ROU E STATIC SCH STM STO ST Z I 7 I a T N N MAA STATIC STATIC ROU STATIC GS STATIC NYM STATIC TABAUTH STATIC TABLEPA STATIC TABLES STATIC TABLESP STATIC TABSTAT STATIC TRIGGER STATIC USERAUT STATIC VIEWDEP STATIC VIEWS STATIC VOLUMES STATIC USERNAM STATIC vol Z FRI n lt Zz T K KOK K K K K PI K pi pi PI PI Pi pi pi PI Pi pi pi pi PI Pi K PI PI pi pi pi PI Pi pio pi pi PI DG pio DI LTORG ACT SACTDOPT DSECT YES LBL ACT KKKAKKAKKKAKKAKKAKKKAKAKKKAKKAKKAKKAKKAAKKAAKAKAAKAKAKAKAKAKAKAKAKAAKAKAKAKAKAAKKAAKAKAAKAAK
264. ion Type additional information if applicable Then press Enter Options _ 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about 5 Exit Additional information Product load library BMC PRODUCT INSTALL Authorization password Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 11 Online Product Authorization Table A 4 Table A 4 describes each option on the primary menu The following sections of this appendix provide instructions for completing specific tasks such as adding authorization to run the product on a new CPU Product Authorization Primary Menu Options Option 1 Description processes a password that BMC Software Contracts Administration provides to you Use this option to add delete replace modify or reset authorization for a password The Product Authorization utility automatically identifies the type of password and displays the appropriate panel displays a listing of processors that are currently authorized to use the product The listing also displays when the authorization was last modified and by whom and the trial or temporary expiration date displays information about the current processor including the serial nu
265. ion fails you should use alternate means such as the Interactive System Productivity Facility ISPF to perform the allocations Determines whether to display all panel titles column heads field prompts and messages in uppercase characters Y or N If ALTER or CHANGE MANAGER is installed the DOPTs name specified with this parameter is used to run a CATALOG MANAGER worklist using the Execution component and the associated plan names Note See also the description for UXSTP Indicates whether to use audit logging Y or N Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSAUXRELS DB catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 11 Default Option Descriptions BDSN BOPTS ASUDOPD1 CATOP Y CHECKDE STATIC CHECKS STATIC CMAX CMAXU COLAUTH STATIC COLDIST STATIC The DBRM library that CATALOG MANAGER uses when executing the BIND command Indicates whether the DASD MANAGER PLUS product is also installed If DASD MANAGER PLUS is installed the DOPTs name specified with this parameter is used to enable the use of the SPACE and STATS commands in CATALOG MANAGER and to run a CATALOG MANAGER worklist using the Execution component and the associated plan names Note These paramet
266. ion user profile e the integration of the functionality of PATROL DB Voyager into PATROL DB Alter and SQL Explorer The organization of the installation guide particularly the first four chapters has changed significantly for this release Please refer to About This Book for information This installation guide provides documentation for the following products e ALTER for DB2 version 5 4 03 e CATALOG MANAGER for DB2 version 5 4 03 e CHANGE MANAGER for DB2 version 5 4 03 e CM PILOT for DB2 version 5 4 03 e DASD MANAGER PLUS for DB2 version 5 4 03 e PATROL DB Alter for DB2 version 3 0 01 e PATROL DB Change Manager for DB2 for OS 390 version 3 0 01 e SQL Explorer for DB2 version 2 2 07A BMC Software Inc Confidential and Proprietary Information xxvi Administrative Products for DB2 Installation Guide Version 1 4 02 October 30 1998 This installation guide provides support for the BMC Software Install System and documentation for the following products e ALTER for DB2 version 5 4 02 e CATALOG MANAGER for DB2 version 5 4 02 e CHANGE MANAGER for DB2 version 5 4 02 e CM PILOT for DB2 version 5 4 02 e DASD MANAGER PLUS for DB2 version 5 4 02 e PATROL DB Alter for DB2 version 2 2 08 e PATROL DB Change Manager for DB2 for MVS version 2 2 08 e PATROL DB Voyager for DB2 version 2 2 08 e SQL Explorer for DB2 version 2 2 07 Version 1 4 01 July 31 1998 This installation guide provides support for
267. ional STEPLIB libraries SL5 SYS1 OTHER LOADLIB2 Optional additional STEPLIB libraries SPLAN ASUvrmDS The name of the DASD MANAGER PLUS plan that is used for statistics collection SSID DB2 Identifies the DB2 subsystem ID The SSID must match the SSID command in the worklist This parameter is required STATAUTH Y The statistics authorization indicator If the indicator is set to Y the default DASD MANAGER PLUS checks users authorization to run BMCSTATS and requires the same authorization as for RUNSTATS Y or N SWPS 10 The primary space allocation in cylinders for sort work data sets SWSS 2 The secondary space allocation in cylinders for sort work data sets SWU SYSDA Describes the sort work unit BMC Software Inc Confidential and Proprietary Information 8 12 Administrative Products for DB2 Installation Guide SYSCMAX SYSCMAXU Default Option Descriptions The SYSCOPY threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSCMAX parameter is used to generate SYSCOPY DD statements it is not used when COPY PLUS Dynamic Allocation is used The SYSCOPY secondary or alternate unit that is used for any overflow SYSCPREF amp amp PREFIX amp amp SSID amp amp OBNOD SYSCPS 10 SYSCSS 2 SYSCUNIT SYSDA SYSRMAX SYSRMAXU
268. ipped and may have changed when DASD MANAGER PLUS was installed Examine these synonyms and verify that the table names are correct If your current REORG PLUS LOADPLUS or COPY PLUS synonyms do not point to the tables listed in Table 3 3 or Table 3 4 complete the following steps to update them 1 Drop the REORG PLUS LOADPLUS or COPY PLUS synonyms 2 Create the new REORG PLUS LOADPLUS or COPY PLUS synonyms by using the same synonym names but with the correct DASD MANAGER PLUS table names 3 Bind the REORG PLUS LOADPLUS or COPY PLUS BMCSTATS plan BMC Software specifies this plan as ARUTvrmm AMUTvrmm or ACPCvrmm where vrmm is the version release and maintenance level Note If DASD MANAGER PLUS tables are not connected or installed when you install REORG PLUS LOADPLUS or COPY PLUS then the plan binds will complete with RC 4 4 Ifyou want to use DASD MANAGER PLUS with COPY PLUS run the ACPssidC ICOPY installation job The HLO INSTALL member DCIHASUR for REORG PLUS member DCI ASUL for LOADPLUS and member DCIHASUC for COPY PLUS provide examples of a worklist for Step 1 and Step 2 Pointing the DASD MANAGER PLUS Synonyms to the Utility Tables DASD MANAGER PLUS uses the following synonyms e BMC_UTILITY for the BMCUTIL table e BMC_UTIL_SYNC and BMC_UTIL_SYNC2 for the BMCSYNC table BMC Software Inc Confidential and Proprietary Information 3 10 Administrative Products for DB2 Installation Guide Interacting
269. ironment plan name which is used to display ALTER and CHANGE MANAGER environment information Defines the Execution primary plan name Instructs ALTER CHANGE MANAGER and DASD MANAGER PLUS to expect numbers in the European format comma used for the decimal point and to create output in European decimal format Y or N BMC Software Inc Confidential and Proprietary Information 5 16 Administrative Products for DB2 Installation Guide FEP ALvrmcDF GLID id HSMVOL vol IMP ALvrmcDI ISPSLIB IXTYPE 2 Default Option Descriptions This parameter is particularly important when ALTER or CHANGE MANAGER parses index LIMITKEY values that are separated by commas If the EURO keyword is present ALTER or CHANGE MANAGER requires delimiting commas to be followed by blanks Note The Import Specification Baseline and Compare components use the value for EURO from the DOPTs module but do not support use of the EURO keyword in the ALUIN parameter input data stream Defines the Front End plan name Defines a global authorization ID GLID This authorization ID is used instead of the authorization ID of the person who submits the Analysis job The worklist begins with a GLID command that switches authorization to the GLID Specifies the volume ID that indicates an archived data set if you are using a disk management system If this volume ID is encountered ALTER or CHANGE MANAGER uses a template of default values for data set
270. is for a product other than the one that you are attempting to execute System Action The product does not execute User Response Contact BMC Software Product Support for assistance BMC89119E I O ERROR WHILE ATTEMPTING TO READ PRODUCT AUTHORIZATION TABLE DDNAME SYSLIB Explanation The system is unable to read the product authorization table System Action All functions are suppressed User Response After several attempts are made to read the table the table might have to be rebuilt Contact BMC Software Product Support for assistance BMC89120E COULD NOT FIND THE EXISTING CPU ID ENTRY THAT WAS TO BE REPLACED Explanation An attempt was made to apply a Replace password but the CPU to be replaced in the product authorization table cannot be found System Action The password is not processed User Response The old CPU ID or the password was specified incorrectly Correct the specification and retry the action If failure persists contact BMC Software Product Support for assistance BMC89121E PERMANENT PRODUCT AUTHORIZATION TABLE WAS NOT FOUND BUT THE PASSWORD SPECIFIES A DELETE OR REPLACE ACTION Explanation An attempt was made to apply a Delete password or a Replace password but the system cannot locate a product authorization table for this product System Action The password is not processed User Response Contact BMC Software Product Support for assistance BMC89122E ATTEMPTING TO ADD A NEW CPU
271. itioned data set The products automatically use the Work ID as the member name JDSNBG amp amp PREFIX JCLGEN amp amp WORKID For DB2 Version 5 and later defines the default data set name that is used for batch JCL Generation This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The products automatically use the Work ID as the member name JDSNE amp amp PREFIX EXEC amp amp WORKID LOCATION LOCK X LOG N MGMTCLAS N PC ALU PIC N Defines the default data set name that is used for Execution JCL This data set can be either a sequential or partitioned data set Hardcoding a member name is not recommended for a partitioned data set The product automatically uses the Work ID as the member name The local subsystem location If you are using Single Point Entry the parameter is set to SPE METHOD Controls the SQL LOCK TABLE statements that are issued by the Execution component for ALTER unloads The LOCK parameter does not apply to the BMC Software UNLOAD PLUS product S Issue the SQL LOCK TABLE IN SHARE MODE statement x Issue the SQL LOCK TABLE IN EXCLUSIVE MODE statement N Do not issue SQL LOCK TABLE statements Specifies that records be logged during loads that use the IBM LOAD utility Yor N Indicates whether support for the MGMTCLAS parameter is required for VCAT defined DB2 objects Y or N Defines the product
272. ization table library should have the same DCB attributes as the product s load library The RECFM for the table library must be U If you have several BMC Software products you may want to dedicate one library that includes all authorization tables for all products Before updating the library that contains the authorization tables the license validation process determines whether the data set is in LNKLST If the data set is in LNKLST the license validation process does not attempt an update Running a Product on an Unlicensed Processor When you run a product on an unlicensed processor a 15 calendar day grace period can be triggered After this grace period expires the product will not run or will run with diminished functionality Note The product will continue to function normally when run on a licensed CPU even if the grace period has been triggered or has expired To prevent this situation you should obtain a RESET password from BMC Software Contracts Administration If you apply the RESET password before the grace period ends it updates the product authorization table and makes another 15 calendar day grace period available When the grace period is triggered the Product Authorization utility either online or in batch mode and the affected product issue a message that advises you of the expiration date BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 7
273. k procedures described for toleration mode to remove the product in exploitation mode 3 Rebind all indirect packages and plans for the previous version by using prdssidZ bind packages and prdssidB bind plans where ssid is the subsystem ID 1 Provided that the previous indirection still exists remove the indirect copy or view in exploitation mode 2 Provided that CATALOG MANAGER still exists in toleration mode use the fallback procedures described for toleration mode to remove the product in exploitation mode 3 Rebind all indirect packages and plans for the previous version by using prdssidZ bind packages where ssid is the subsystem ID BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 33 Maintaining BMC Software Administrative Products To maintain BMC Software Administrative Products when you create a new DB2 Version 6 catalog use the guidelines in Table 3 16 Table 3 16 Creating a New DB2 Version 6 Catalog If You Are Then using any of the Perform a Full installation of the following Administrative Products Administrative Products e ALTER or CHANGE MANAGER 6 2E exploitation e CATALOG MANAGER 6 2 exploitation e DASD MANAGER PLUS 6 1 exploitation using catalog indirection Install catalog indirection BMC Software Inc Confidential and Proprietary Information 3 34 Administrative Products for DB2 Inst
274. l Step 4 Press F3 to exit the Product Authorization utility and return to the previous menu or panel BMC Software Inc Confidential and Proprietary Information A 14 Administrative Products for DB2 Installation Guide Deleting Authorization for a Processor Deleting Authorization for a Processor Summary Use the DELETE Authorization for a Processor panel to remove a CPU from the product authorization table Step 1 Access the DELETE Authorization for a Processor panel as follows 1 A On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 1 B At Product load library type a fully qualified data set name and press Tab 1 C At Authorization password type your permanent password and press Enter The DELETE Authorization for a Processor panel is displayed Figure A 4 shows a sample Figure A 4 DELETE Authorization for a Processor Panel SECEPDEL SECEPDEL DELETE Authorization for a Processor Command gt Supply information for all input fields Then press Enter Authorization password BFP A M 063 7V Old serial number 10293 Old model number 9672 for example 9021 9121 3090 Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 2 At Old serial number type the serial number of the processor for which you are deleting authorization BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorizatio
275. l catalog indirection 3 39 Post Installation Tasks Post Installation Tasks Once you have verified that an Administrative Product has been installed correctly refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for the BMC Software products that reside on the Administrative Products tape set BMC Software Inc Confidential and Proprietary Information 3 40 Administrative Products for DB2 Installation Guide Chapter 4 Performing Post Installation Tasks This chapter presents the following topics Performance Considerations LL 4 2 Adding Products to the BMCDB2PR Panel 4 2 Performing the Post Installation Tasks for Administrative Products 4 3 Enabling the Product CLISTS LL 4 4 CompilingSEIBS stu pri sro renale 4 14 Assembling the Modifications to the DOPTs 4 16 Binding the Packages and Plans for Shared Components 4 17 Verifying the Product Authorization L LL 4 18 Invoking the BMCDB2 CLIST LL 4 19 Verifying the Installation of the Administrative Products 4 20 Using Fast Path Navigation LL 4 21 Performing the Post Installation Tasks for the MVS Server 4 22 Configuring TCPAP i i e ea 4 23 Configuring APPC SNA eternet oenina i ee eee eee eet ees 4 27 Confirming the Host Code Page for the MVS Server 4 43 Enabling the Use of Se
276. l characters The only special characters permitted are and System Action The password is not processed User Response Correct the password and resubmit the job BMC89102E PASSWORD CONTAINS ILLEGAL CHARACTERS I AND OR O Explanation The password contains one or more of the letters or O These letters are not permitted in passwords System Action The password is not processed User Response Correct the password and resubmit the job BMC89104E PASSWORD DOES NOT MATCH SERIAL NUMBER AND MODEL NUMBER Explanation The specified password is not correct for the specified CPU serial number and model number or if the batch interface was used the product code in the PARM statement is not correct To obtain your CPU serial and model numbers log on to the processor and perform one of the following actions e Select the Display current processor information option from the Product Authorization Primary Menu see page A 11 and submit the product authorization batch program with the LIST option see page A 29 e Issue the MVS operator command D M CPU from the system console BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 11 Error Messages BMC89105E BMC89106E BMC89107E System Action The password is rejected User Response Verify that the specified CPU serial number and model number are correct If the numbers are incorrect retry th
277. l number type the model number of the processor for which you want to modify the authorization and press Enter The properties are modified automatically A pop up message on the Product Authorization Primary Menu explains that the product authorization table was updated successfully Figure A 9 on page A 21 BMC Software Inc Confidential and Proprietary Information A 20 Administrative Products for DB2 Installation Guide Modifying Authorization for an Existing Processor Figure A 9 Product Authorization MODIFY Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options 1 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about 5a Ext Additional information Product load library BMC PRODUCT LOAD Authorization password BMC89130I PROCESSOR SERIAL NUMBER 10293 MODEL NUMBER 9672 WAS SUCCESSFULLY MODIFIED IN THE PRODUCT AUTHORIZATION TABLE PRESS ENTER TO CONTINUE Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 4 Press F3 to exit the Product Authorization utility and return to the previous menu or panel BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 21 R
278. lds Multiple blank spaces are acceptable e To insert comments type an asterisk in column 1 of each line that contains the comment Comments following keywords are not allowed e You cannot specify the LIST keyword on the same line as PSWD NEWCPUID and OLDCPUID Table A 6 describes the control statement keywords Table A 6 Control Statement Keywords Keyword PSWD Data 12 character password formatted as four fields of three characters each separated by either a comma or a blank See sample JCL on page A 28 Twelve continuous characters are also acceptable Explanation Valid characters are alphanumeric excluding letters and O Valid special characters are and You can substitute the asterisk for the at sign when is not available on the keyboard NEWCPUID OLDCPUID LIST BMC Software Inc Confidential and Proprietary Information five digit serial number followed by a hyphen and a four digit model number five digit serial number followed by a hyphen and a four digit model number not applicable Appendix A BMC Software Product Authorization The serial number and model number must be hexadecimal characters separated by a single hyphen The serial number and model number must be hexadecimal characters separated by a single hyphen A report prints showing the contents of the product authorization tables and information about the processor o
279. le release of the Install System Unload Job for the Install System Using Merge JOB ACCOUNT EX DD DD DD DD DD DD DD DD DD EC PGM IEBCOPY SYSOUT UNIT SYS UNIT SYS DA SPACI DA SPACI TRK TRK rp i pie ai 1 1 1 1 DSN BMC earliest INSTALL DISP OLD UNIT TAPE LAB EL 1 SL 1 VOL SER prod_tape 1 EXPDT 98000 DSN BMC latest INSTALL DISP OLD VOL SER prod_tape 2 UNIT AFF DCITINST LABEL 1 SL EXPDT 98000 DSN BMC INSTALL LOAD DISP OLD VOL SER prod_tape 2 T UNIT AFF DCITINST LAB DSN your name EL 2 SL EXPDT 98000 INSTALL Eal DISP CATLG D UNIT SYSDA SPACE DCB RECFM FB LRECL 80 LETE CYL 40 5 700 ETE I DCITINST O DCIINST I DCITINS2 R O DCIINST I DCITLOAD 0 DCILOAD BLKSIZE 6160 DSN your name INSTALL LOAD DISP CATLG DEL UNIT SYSDA SPACE CYL DCB RECFM U BLKSIZE 23476 5 1 40 BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Unloading the Install System Note Bold lines in Figure 2 2 on page 2 8 indicate differences in the unload job when Merge is selected It is critical that the install libraries are unloaded in the order that they were originally released In the example library names BMC earliest INSTA
280. lient be sure that you completed the steps in Setting Up the SNA Gateway Server on page 4 37 To Set Up the Client Step 1 Install the Microsoft SNA Client on the user s PC The client requires the Microsoft Windows 95 98 or Windows NT SNA Client You will need to know about the SNA Gateway Server to supply the SNA Client with information about the particular transport protocol to be used as well as the Domain setting and Primary Server name Step 2 Configure the APPC SNA host To install and configure the client for an SNA host session you must use the host configuration tool Once the client has been installed on the user s PC you must use the session configuration tool to configure a host system and session profile Within the host system configuration section a selection for APPC SNA is provided Several installation parameters are provided to complete the host configuration The CPI C Symbolic Destination Name for APPC services defined previously in the SNA Gateway Server is in most cases the only parameter that is necessary to identify the MVS Server However additional parameters can be used to selectively override the site information table CPI C Symbolic Destination Name table defined on the SNA Gateway Server Table 4 5 on page 4 42 describes these installation parameters BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 41 Setting Up the Client
281. lifiers Default Options and Plan Names When one of the Administrative Products runs it uses its own DOPTs module that was built during installation The BMCDB2 CLIST allocates the DOPTs module name when you start the product When you request indirect access the product allocates a DOPTs module that is different from the direct access options module Contained in this DOPTs module are the plans that are used when certain product functions are executed Note CATALOG MANAGER 3 3 or later uses a single DOPTs module for both direct access and indirect access The BMCDB2 CLIST allocates the same DOPTs module and the same plan for direct access and indirect access The plan that is accessed contains two distinct collection IDs that are used to access direct or indirect catalogs The qualifier of the plan and the packages is used to resolve synonyms that point to either a view of the DB2 catalog or a copy of the DB2 catalog depending on the method of implementation The DOPTs module the plan and collection names and the synonym qualifier are all crucial for the implementation of catalog indirection You should understand their use and interaction before you implement catalog indirection Note To help maintain catalog indirection follow the naming conventions described on page 3 23 Naming conventions enable you to look at the DOPTs module or allocated plan and determine whether indirect access or direct access is being used The Install
282. lows Varies depending on your system Identifies the program SECSEC3B and passes the product code in the PARM field Replace prd with the three character product code Identifies the load library in which SECSEC3B resides This is optional if SECSEC3B resides in LINKLIST or is specified in JOBLIB Identifies the product load library Product authorization tables are stored and updated in this data set Enables the product to issue messages and output from the LIST control statement Identifies the location of the control statements that define the actions the program is to take See the following section Control Statements and Keywords on page A 29 for a description of these control statements BMC Software Inc Confidential and Proprietary Information A 28 Administrative Products for DB2 Installation Guide Control Statements and Keywords Batch Product Authorization Some tasks require different input parameters depending on the type of password that you are installing The sample JCL shown in Figure A 14 on page A 28 shows various tasks that you can perform by using the batch version of product authorization You need to modify the JCL to include only the tasks that you want to perform The following syntax rules apply to the control statements e Control statements can begin in any column e Uppercase letters are required e You must insert at least one blank space between individual keywords and data fie
283. ly However you can install BMC Software products at different times If you install the products at different times and any of the products share the same APF authorized load library you need to bind the products to the shared JCL Generation and Execution Monitor components To bind the products complete the steps in Upgrading Shared Components on page 3 4 BMC Software Inc Confidential and Proprietary Information 3 2 Administrative Products for DB2 Installation Guide Installing Products at Different Times Generating ISPF Interfaces Note This section addresses only those BMC Software products that provide an online dialog The Install System generates an ISPF interface to run many of the BMC Software products The interface consists of a CLIST BMCDB2 a panel BMCDB2PR and an optional table BMCDB2TB You can use this combination without making changes to your TSO logon procedure For new users BMC Software recommends that you use the supplied ISPF interface Full Installation or Initial Maintenance The BMCDB2 CLIST uses the ISPF LIBDEF command to allocate all of the BMC Software product libraries The Install System customizes BMCDB2 and BMCDB2PR to include the data set names that you used during the installation The Install System specifies up to two DB2 load libraries and specifies each product s default options DOPTs module name to support the DB2 subsystem where the product is installed Note You must pe
284. m ID SSID The SSID must match the SSID command in the worklist This parameter is required BMC Software Inc Confidential and Proprietary Information 5 20 Administrative Products for DB2 Installation Guide STATS S STOPCOMM N STORCLAS N SWPS 10 SWSS 2 SWU SYSDA SYNCPNT parm SYSCMAX SYSCMAXU Default Option Descriptions Indicates what type of statistics should be generated DB2 Version 5 1 or later The DOPTs parameters are defined as follows S Standalone The worklist generates either a BMCS or RNST command in the worklist U Utility The worklist combines statistics with a utility Reorg Copy Load whenever possible X No statistics are generated For DB2 Version 5 1 and later indicates whether an AT COMMIT generates in a worklist when a STOP is created Indicates whether support for the STORCLAS parameter is required for VCAT defined DB2 objects Y or N Defines the default primary space allocation for sort work in cylinders Defines the default secondary space allocation for sort work in cylinders Describes the sort work unit Creates additional SYNC commands in a worklist based on the number of SQL commands since the last SYNC command The variable parm specifies the maximum number of SQL commands that can be in the worklist before a SYNC command is created The option also places an additional SYNC command before the next SQL command Valid values for parm are from 0 to 99 A
285. make sure that they point to the correct table names 2 If the synonyms do not point to the correct names drop the current synonyms Then recreate the synonyms by using the same synonym names but with the correct table names 3 Rebind all ALTER ALU or CHANGE MANAGER ACM packages and plans by using prdssidP bind packages and prdssidB bind plans where prd is the product code and ssid is the subsystem ID As an alternative you can perform a Full installation of ALTER or CHANGE MANAGER 6 2D Then you will be operating in exploitation mode 1 Migrate the DB2 catalog 2 Modify the ACTDB25E worklist member in the HLQ JCL library 3 Execute the worklist using a modified copy of the I40INST job that the INSTALL job dialog generated 4 Rebind all CATALOG MANAGER packages and plans by using ACT ssidP bind packages and ACT ssidB bind plans where ssid is the subsystem ID Then you will be operating in exploitation mode Provided that ALTER or CHANGE MANAGER still exists in toleration mode use the fallback procedures described for toleration mode and remove the product in exploitation mode Any data that you added while you were in exploitation mode will not be available in toleration mode 1 Check your synonyms to make sure that they point to the correct table names 2 If the synonyms do not point to the correct names drop the current synonyms Then recreate the synonyms by using
286. mber the model number the version code submodel and the number of available processors displays version copyright and licensing information about the Product Authorization utility exits the Product Authorization utility and returns to the previous menu or panel Note If you select option 1 you must also type the name of the product s load library and the authorization password The utility saves the library name in your ISPF profile and uses that name as the default library The data set name must be fully qualified BMC Software Inc Confidential and Proprietary Information A 12 Administrative Products for DB2 Installation Guide Adding Authorization for a Processor Adding Authorization for a Processor Summary Use the ADD Authorization for a Processor panel to authorize a new CPU to run the product Step 1 Access the ADD Authorization for a Processor panel as follows 1 A On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 1 B At Product load library type a fully qualified data set name and press Tab 1 C At Authorization password type your permanent password and press Enter The ADD Authorization for a Processor panel is displayed Figure A 2 shows a sample Figure A 2 ADD Authorization for a Processor Panel SECEPADD SECEPADD ADD Authorization for a Processor Supply information for all input fields Then press Enter Authorization password
287. me with SYSIBM LOCATIONS Note Names for DDF tables for DB2 Version 5 1 have changed e CHANGE MANAGER needs to be installed on the local and remote DB2 subsystems CHANGE MANAGER can be installed either completely or partially on the remote DB2 subsystem e CHANGE MANAGER must be at the same version release and maintenance level on both DB2 subsystems Implementing the Catalog to Catalog Feature To implement the catalog to catalog Compare feature for local and remote comparisons you must install CHANGE MANAGER compare components on both the local and the remote subsystems Install CHANGE MANAGER on the Local Subsystem with DDF Active When you install CHANGE MANAGER the Install System builds synonyms that access the communications database Install CHANGE Manager on the Remote Subsystem The following list describes the options for installing CHANGE MANAGER e Ifthe remote subsystem has the same version of DB2 that is installed on the local subsystem install the same version and release of CHANGE MANAGER on the remote subsystem and select the DDF option BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 7 Installation Considerations If the same naming convention for the collection IDs and plans is used on both subsystems such as using the defaults from BMC Software for example then the CHANGE MANAGER product s catalog to catalog Compare feature is ready to use If
288. member is the DOPTs file location that the product uses to connect to DB2 The SSID field that is stored in the DOPTs module is the SSID to which the ALTER and CHANGE MANAGER products clients connect This DOPTs module is referenced by a nickname that you specify during the configuration of the client BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Configuring TCP IP The DB2 subsystem name that you specify during the client configuration must be the same as the nickname specified in the INI ACV file Whereas you specify the name of the subsystem with an underscore _ in the INI ACV file you must enter the name in the Connection Wizard screen during the client configuration with a colon In the example in Figure 4 14 on page 4 24 the DOPTs nickname is DB25_DIRECT and it references BMCADMN V621 D62 LOAD ALUDOPD1 The source for the DOPTs module is found in HLQ CNTL member In the example this is member ALUDOPDI Figure 4 15 illustrates that the DOPTs nickname is entered as DB25 DIRECT replacing the underscore _ with a colon when the client is installed on the user s PC Figure 4 15 Connection Wizard Screen Connection Wizard Specify a Database Instance x Specify the name of the DB2 subsystem that you want to connect to TIP Specify the name of your DB2 subsystem DB2 Subsystem DB25 DIRECT Discovery Specify the TSO user ID that
289. ming the Post Installation Tasks for the MVS Server After you install the MVS Server for the Database Administration products you must perform the following tasks e Configure your communication protocol e Confirm the host code page for the server e Enable the use of secondary authorization IDs for each client e Verify the installation If you chose TCP IP as your protocol refer to the section Configuring TCP IP on page 4 23 If you chose APPC SNA refer to Configuring APPC SNA on page 4 27 BMC Software Inc Confidential and Proprietary Information 4 22 Administrative Products for DB2 Installation Guide Configuring TCP IP Configuring TCP IP Summary Step 1 This section describes the steps that you must perform if you select TCP IP as your communication protocol for the MVS Server Edit the INI ACV file The PATROLDB member is the started task that enables the clients to communicate with DB2 PATROLDB uses the initialization file INIHACV to establish the TCP IP address port address as well as the default options DOPTs that the MVS Server uses After you complete the installation the members INI ACV and PATROLDB are placed in the HLQ CNTL data set The INIFACV member contains the TCP IP port number that the MVS Server monitors If an incorrect port number is specified during installation you can edit it manually in INI ACV You do not need to register your port in the TCP IP profile data se
290. modify and stop commands see Table 4 3 on page 4 29 Step 4 Enable foreground processing To enable the option of foreground processing when you run the client follow these steps 4 A Copy BMCAKMEG into a system proclib data set where it can be started as a started task 4 B Define the proclib name to RACF as a started task Note The steplib must point to only APF authorized loadlibs Once foreground processing is enabled you will be prompted to perform a particular function in either foreground mode or batch mode When you indicate foreground mode the server starts the BMCAKMEG task or the task that is specified in the FOREGROUND STARTEDPROC parameter in the INI ACV member and the foreground function is performed Step5 Install the client on the user s PC For information on installing the client refer to Chapter 9 Installing the Client for ALTER and CHANGE MANAGER Where to Go from Here After you configure the TCP IP communication protocol you verify the setting for your host code page For more information see Confirming the Host Code Page for the MVS Server on page 4 43 Configuring APPC SNA During the installation of the MVS Server if you chose a communication protocol of APPC SNA instead of TCP IP you need to follow the instructions in this section Configuring APPC connectivity for use with the MVS Server is a three part process that involves setting up the MVS Server setting up the Microsoft
291. n ESD 1 2 2 3 ENVI command 4 20 environments supported 9 2 ENVP DOPT 5 16 7 24 EPLAN DOPT 6 15 EPP DOPT 5 16 7 24 8 10 error messages product authorization B 2 ESC DOPT 6 15 ESD See Electronic Software Distribution 1 2 2 3 estimated space requirements 1 4 EURO DOPT 5 16 7 24 examples completing the password worksheet A 10 JCL for batch authorization A 28 executing CLISTs 4 4 executing on an unlicensed CPU A 5 expiration dates temporary A 25 F Fast Path Navigation 4 21 FEP DOPT 5 17 7 24 FIELDS DOPT 6 15 files installed on client 9 12 foreground processing 4 39 FOREIGN DOPT 6 15 format of error messages B 2 Full installation 1 14 function keys 2 14 G GDG processing See generation data groups 4 16 GDGDEF DOPT 8 10 GDGLIM DOPT 8 10 GENERATE command 4 6 4 19 GENERATE variable 4 5 4 19 generating JCL BMC Software Inc Confidential and Proprietary Information generation data groups GDGs 4 16 JES3 environment 4 15 product 4 14 region statements 4 14 generation data groups 4 16 GENTABLE variable 4 5 GLID DOPT 5 17 7 24 grace period at temporary password expiration A 6 triggering A 7 group attach name 4 7 GRPAT DOPT 6 15 H HDAL DOPT 6 15 HDIX DOPT 6 15 HDPL DOPT 6 15 HDSY DOPT 6 15 HDTB DOPT 6 15 HDTS DOPT 6 15 HDVW DOPT 6 15 help accessing online help 2 14 configuring the client 9 19 high level qualifier HLQ 1 4 HLQ See high level qualifier 1 4 HLQ INSTALL DCI A
292. n A 15 Deleting Authorization for a Processor A 16 Step3 At Old model number type the model number of the processor for which you are deleting authorization and press Enter A pop up message on the Product Authorization Primary Menu explains that the product authorization table was updated successfully Figure A 5 Figure A 5 Product Authorization DELETE Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options _ 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about ba Exit Additional information Product load library BMC PRODUCT LOAD Authorization password BMC89128I PROCESSOR SERIAL NUMBER 10293 MODEL NUMBER 9672 WAS SUCCESSFULLY DELETED FROM THE PRODUCT AUTHORIZATION TABLE PRESS ENTER TO CONTINUE Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 4 Press F3 to exit the Product Authorization utility and return to the previous menu or panel BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Replacing Authorization for a Processor Replacing Authorization for a Processor Summary Use the REPLACE Authorization for a Processor panel to replace on
293. n Considerations 0 0 0 e cece ee eee nee 6 3 Installation Defaults 0 0 0 ce eee eee 6 3 Implementing Catalog Indirection 000 5 6 3 Controlling ACCESS e orenera sree kge oe e o cece neces 6 5 Default Option Listing DOPTS LL 6 6 BMC Software Inc Confidential and Proprietary Information Contents vii Default Option Descriptions LL 6 11 Post Installation Considerations LL 6 26 Chapter 7 Installing CHANGE MANAGER OVEriIew asia eine 7 2 CM PILOT Component 7 3 Installation Considerations L LL 7 5 Installation Defaults 0 0 LL 7 5 Using INFOBMC in the Compare Component 7 6 Performing a Catalog to Catalog Comparison 7 6 Controlling Access LL 7 9 CHANGE MANAGER Specification and Analysis Plans 7 10 CHANGE MANAGER Execution Plans 04 7 12 CHANGE MANAGER Object Security 7 13 JSI JES Interface Installation LL 7 13 Default Option Listing DOPTs 0 0 0 ce eee eee eee 7 14 Default Option Descriptions LL 7 18 Post Installation Considerations 0 0 0c eee eee eee ee 7 32 Chapter 8 Installing DASD MANAGER PLUS OVERVIEW sited ashi tdi Dita lie hha oie Laas keke ae 8 2 Installation Considerations 0 0 cece eee eee eee 8 3 Installation Defaults 0 0 2 2 eee eee 8 3 Implementing the QMF Report Feature 8 4 Controllimp Access hers iii lol ai 8
294. n component of DASD MANAGER PLUS or ALTER is installed This option applies only if you have DASD MANAGER PLUS or ALTER installed As part of the installation of DASD MANAGER PLUS or ALTER the AEX libraries may have been copied into the DASD MANAGER PLUS or ALTER load libraries Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSVIEWDEP DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table BMC Software Inc Confidential and Proprietary Information 6 24 Administrative Products for DB2 Installation Guide VIEWS STATIC VMAX VMAXU VOLUMES STATIC WDC Default Option Descriptions Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSVIEWS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The offsite copy threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The offsite copy secondary or alternate unit that is used for any overflow Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSVOLUMES DB 2 catalog table The default STATIC uses the privileges of the pack
295. n for an Existing Processor panel to change one or more properties of an existing CPU in the product authorization table These properties include the version code the number of significant digits for the serial number the tier the maximum number of processors and the expiration date for the product license Step 1 Access the MODIFY Authorization for an Existing Processor panel as follows 1 A On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 1 B At Product load library type a fully qualified data set name and press Tab 1 C At Authorization password type your permanent password and press Enter The MODIFY Authorization for an Existing Processor panel is displayed Figure A 8 on page A 20 shows a sample BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 19 Modifying Authorization for an Existing Processor Figure A 8 MODIFY Authorization for an Existing Processor Panel SECEPUPD SECEPUPD MODIFY Authorization for an Existing Processor Command gt Supply information for all input fields Then press Enter Authorization password X3Y 067 006 5U1 Serial number 10293 Model number 9672 for example 9021 9121 3090 Fl Help F2 Split F3 Exit F7 Bkwd F8 Fwd F9 Swap F12 Cancel Step 2 At Serial number type the serial number of the processor for which you want to modify the authorization Step3 At Mode
296. n specify only one qualifier The default HLQ prefix is your user ID Note Keep a record of the HLQ for later use During installation you will identify the HLQ to the Install System 2 C To specify a unit name for the data sets replace the value SYSALLDA with a valid DASD unit name 2 D If you need to specify a volume for the uncompressed data sets add the volume parameter after the unit parameter as in the following statement EXEC DCI prdvrm RECEIVE UNIT SYSALLDA VOL volume_ID where prdvrm indicates the actual product image file release information Warning Do not edit any other part of the job Step 3 Submit the job Note If you have difficulty submitting the job try saving your changes exit the data set and submit the job externally Step 4 Repeat steps 1 through 3 for each ESD file transferred BMC Software Inc Confidential and Proprietary Information 2 4 Administrative Products for DB2 Installation Guide Processing an ESD Image Where to Go from Here After the ESD image has been expanded and separated you are ready to start the Install System For more information see Starting the Install System on page 2 10 BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 5 Unloading the Install System Unloading the Install System Summary Before You Begin Use the following procedure to unload the Install System from
297. n this situation Message Format B 2 All messages produced by this product consist of a message identifier and message text These messages use the following format BMC prefix identifying BMC Software as the owner of the message 89000 five digit number identifying the message A severity code indicating the nature of the message and the level of action required by the user Text actual message text BMC89000A PRODUCT LOAD LIBRARY IS A REQUIRED FIELD Words in the message text that are italicized and enclosed in arrows lt example gt indicate variable text that will be determined when the message is issued Words in the message text that are enclosed in brackets and separated by vertical lines ON OFF indicate actual values one of which will be included at that point in the message BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Error Messages Message Severity Codes Table B 1 lists the severity codes that the Product Authorization utility uses Table B 1 Message Severity Codes Code Meaning A action Immediate action is required E error The function that you requested was not completed information Information only No action is required R reply You must reply to the message before the system can continue S severe A severe error occurred W warning The system is still operating and no immediate
298. n which the job ran A 29 Batch Product Authorization Return Codes You can receive any of the following return codes 0 All requests completed successfully See the SYSPRINT output for messages about each operation 4 A LIST was requested but no tables were in the load library 8 An error prevented completion of all of your requests See the SYSPRINT output for messages about the error and any completed operations BMC Software Inc Confidential and Proprietary Information A 30 Administrative Products for DB2 Installation Guide Appendix B BMC Software Product Authorization Messages This appendix presents the following topics Error Messages lirica sie oh ct hint aon aha Ries Goat AS Rigel Ga lewd B 2 Message Format B 2 Message Severity Codes LL cece ee nee B 3 Message Explanations 0 0 cece cece eee B 3 BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 1 Error Messages Error Messages This section contains the text and explanations for all error messages issued by the ISPF interface and the batch interface of the Product Authorization utility The following information is provided for each message e Explanation explains the reasons why the product issued the message e System Action describes what the product does as a result of encountering the situation e User Response describes what you should do i
299. nabling the Product CLISTs Figure 4 2 Setting the GENTABLE Variable in the BMCDB2 CLIST SET BMCDB2T amp STR BMC DB2ADMN D61 TLIB CONTROL TABLE DATASET SET GENTABLE Y USE GENERATED PERMANENT TABLE Y N FOR CONTROL TABLE After you invoke the BMCDB2 CLIST you must type GENERATE on the command line Refer to the BMCDB2T variable in the BMCDB2 CLIST for the location of the generated ISPF table e To add the CHANGE MANAGER product to the table shown in Figure 4 1 which lists only the DASD MANAGER PLUS product you must add the line shown in Figure 4 3 where vrm is the version release and maintenance level after the line for the ASU product Figure 4 3 Adding CHANGE MANAGER to the Control Table DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME ii p ACM DBAP D ACMDOPD1 CMvrmCDF ACMA x e IfCHANGE MANAGER was installed into a different set of libraries than DASD MANAGER PLUS you must also add the line shown in Figure 4 4 where HLQ is the high level qualifier s of the CHANGE MANAGER libraries to the bottom of the table Figure 4 4 Specifying the Location of CHANGE MANAGER Libraries DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME Di ACM DBAP H HLQ k BMC Software Inc Confidential and Proprietary Information 4 6 Administrative Products for DB2 Installation Guide Figure 4 5 e To enable access t
300. ncies that you must consider before cancelling or backing out of an installation Reverting to the prior version of an individual product may require reverting to the prior version of one or more other products BMC Software recommends that you cancel the entire tape set installation then reinstall only the desired products Where to Go From Here 2 28 After you complete the tasks in this chapter you have completed the primary installation for the BMC Software products that you selected You can now perform additional installation tasks or perform post installation tasks as required for the installed products Task Where to Go perform post installation tasks See Chapter 4 Performing Post Installation Tasks perform an SSID installation for See SSID Installation on an additional DB2 subsystem page 1 15 perform a Multiple SSID See Multiple SSID Installation on installation for several DB2 page 1 17 subsystems BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Chapter 3 Performing Additional Installation Tasks This chapter presents the following topics Performing Additional Tasks for Installation 3 2 Installing Products at Different Times 3 2 Generating ISPF Interfaces 0 0 2 e eee eee eee 3 3 Full Installation or Initial Maintenance 3 3 SSID Installation or Subseq
301. nclude the TABLE ALL parameter on stand alone stats runs Y Include the TABLE ALL parameter on stand alone stats runs TAPE1 CART TAPE2 TAPE TAPE3 TAPE TIMEPARM TSOSX N UNLDCOLL N UNLDEMPT Y UPDSTATS C UTILCOPY N VVALPROP N VRM vrmmd Defines the valid installation tape unit names for your site Indicates the TIME limit in minutes for each step in a batch job stream Specifies whether your site uses the TSO Submit exit to supply the job statements at submit time Y or N Explicit column list that is required on all BMC Software UNLOAD PLUS unloads Y or N For DB2 Version 5 1 and later specifies whether tables that RUNSTATS indicates are empty are unloaded For DB2 Version 5 1 and later specifies which statistics are updated The DOPTs parameters are defined as follows A All The DASD tables and the DB2 Catalog tables are updated BMCSTATS is selected B BMC DASD tables Only the DASD tables are updated BMCSTATS is selected C DB2 Catalog Only the DB2 Catalog tables are updated RUNSTATS is selected Determines whether other utilities or a copy utility creates an image copy during loads Y Image copies are created by utilities other than the copy utilities whenever possible If the utilities cannot create a copy a separate copy step is generated N A separate copy step generates all copies that the specific copy utility takes either the IBM COPY utility or the BMC Software COPY PLUS utility
302. nd maintenance level and nn is a unique plan identifier The default plans that are shipped with this release follow along with their default plan names CHANGE MANAGER Specification and Analysis Plans The following plans are used by the Specification Analysis Compare Import and Baseline components CMvrmcDF Front End Plan This plan controls access to the CHANGE MANAGER interface You can use this plan to create and maintain CHANGE MANAGER objects and to perform other Front End functions ACV vrmDM Display Catalog and SQL Information Access to this plan is required to use the GUI for CHANGE MANAGER This plan displays catalog and SQL generation and execution information BMC Software Inc Confidential and Proprietary Information 7 10 Administrative Products for DB2 Installation Guide Controlling Access CMvrmcDI Import Plan This plan is provided for use by the Import component of CHANGE MANAGER You can use this plan to import changes to the CHANGE MANAGER CD tables CMvrmcDS Specification Plan This plan accesses the Specification component of CHANGE MANAGER You can use this plan to request changes to database objects and data With access to Specification you can also search and review groups of objects Note that while Specification does not allow you to actually perform changes it does allow you to specify changes and to view existing data structures CMvrmcDA Analysis Plan This plan allows you a
303. ng The BMCDB2 CLIST allocates the ISPF application ID based on DB2 subsystem access During a Full installation or an SSID installation the Install System attempts to make each ISPF application ID unique across DB2 subsystems By default the first time that the Install System generates the BMCDB2 CLIST the application ID prdA is allocated where prd is one of the following codes ALU for ALTER e ACM for CHANGE MANAGER e ASU for DASD MANGER PLUS ACT for CATALOG MANAGER Note During the installation if you interface to an existing version of SQL Explorer an application ID of PSS will be added to the CLIST For the second and subsequent installations using SSID Install the Install System attempts to scan the existing BMCDB2 CLIST and to allocate a unique application ID For example if ALTER is initially installed on DB2T the application ID is ALUA If ALTER is installed on DB2P the Install System scans the BMCDB2 CLIST and uses application ID ALUB because ALUA is already in use Refer to Single and Multiple Installation Default Modules on page 3 16 for more information about how to customize the BMCDB2 CLIST BMC Software Inc Confidential and Proprietary Information 3 14 Administrative Products for DB2 Installation Guide Refreshing Default Options When a user accesses an Administrative Product the BMCDB2 CLIST establishes the ISPF application ID and allocates the DOPTs module name The product that
304. ng the authorization ID and AUTH commands are not allowed BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 19 Default Option Descriptions BASDIAG SYSOUT BASE CMvrmcDB BLDBS N BLDCU N If you specify AUTHSW B both AUTH and SETS commands are used AUTH commands are generated to set the original CREATEDBY values SETS commands are generated to set new OWNER values for all objects The B option also causes authorization ID switching before CREATE TABLE and CREATE INDEX statements which is not done under either of the other options When the AUTHSW keyword is used in the ALUIN input stream it is equivalent to AUTHSW Y in the DOPTs module Note Do not use the AUTHSW keyword in the following situations e I AUTHSW N is in the DOPTs module e Ifyou are using a global authorization ID GLID Note If your site does not use DB2 secondary AUTHIDs set AUTHSW Y Otherwise set AUTHSWEN If you require that the CREATEDBY field in the DB2 catalog remain unchanged after updates then set AUTHSW B Warning Setting AUTHSW B is not recommended because of a potential security exposure This exposure exists because the DB2 catalog does not accurately reflect the primary authorization ID of the creator of the objects If you must set AUTHSW B use the sample security exit ALUEUSX1 to avoid the security exposure Sets the default value for the Baseline diagnostic output data set n
305. ng the Install System 2 10 Running the Install System 2 14 Marni Menu ii ened cep eae Sea hee hee bee cies Ws 2 14 Keys and Commands 0 2 e eee eee eee eee ee 2 14 Data Set Names i i ili 2 15 Symbolic Variables ii ra hee a eee 2 15 Considerations for SAS C 2 0 eee 2 17 Specifying User Options 2 19 Generating Installation JCL LL 2 22 Migrating DB2 Objects Between Releases 2 26 Cancelling the Installation 2 27 Reverting to Conditions Prior to a Tape Installation 2 27 Reverting to the Prior Version of an Individual Product 2 28 Where to Go From Here 0 0 0 eee eee eee 2 28 Performing Additional Installation Tasks Performing Additional Tasks for Installation 3 2 Installing Products at Different Times 0 0 000000 3 2 Generating ISPF Interfaces 0 0 0 ee eee eee 3 3 Full Installation or Initial Maintenance 3 3 SSID Installation or Subsequent Maintenance 3 3 Upgrading Shared Components 0 0 000s eee eee eee ee 3 4 Interacting with Other BMC Software Products 3 6 ALTER and CHANGE MANAGER LL 3 6 CATALOG MANAGER orc 0 cece ili iii e na 3 7 DASD MANAGER PLUS 3 9 SQL Explorer with DASD MANAGER PLUS 3 11 Refreshing Default Options LL 3 13 Setting User Options Using DOPTs 0004 3 14 Catalog Indirection Defaul
306. ns Refer to the product specific chapters for detailed information about using the SSID installation path for a particular product The following products do not support the SSID installation path ACTIVITY MONITOR for DB2 e APPTUNE for DB2 e OPERTUNE for MQ e OPERTUNE for DB2 e PACLOG for DB2 COORDINATED RECOVERY MANAGER CRM e EXTENDED BUFFER MANAGER XBM family of products e Cross System Image Manager XIM Multiple SSID Installation The Multiple SSID installation path provides a way for you to use an initial product installation as a model for installations on other DB2 subsystems To enable the Multiple SSID installation path you must complete the following tasks 1 Select either the Full installation path or the SSID installation path e Use the Full installation path to install the selected products on a single DB2 subsystem See Full Installation on page 1 14 e Use the SSID installation path to install the selected products on another DB2 subsystem See SSID Installation on page 1 15 2 At the end of the Full or SSID installation select option 3 in the JCL Generation Options panel This option generates installation batch jobs for the specified DB2 subsystem and builds a multiple SSID JCL model for any additional subsystems When you complete these tasks and return to the Install System Main Menu the Multiple SSID option is displayed as menu option 5 Considerations The SSI
307. ntenance updates Full See Full Installation on but with the following conditions page 1 14 e You do not want to overlay the existing installation You cannot share the product libraries that were created during the initial installation with the maintenance update You completed the initial installation and SSID See SSID Installation on now want to install the product on other or page 1 15 DB2 subsystems You want to share the Multiple SSID For Multiple SSID product libraries that were created during installations see Multiple the initial installation of the product SSID Installation on page 1 17 You completed the initial installation and Full See Full Installation on now want to install the product on other page 1 14 DB2 subsystems However you do not want to share the product libraries that were created during the initial installation You completed the Full Maintenance or Indirection See Using Catalog SSID installation and now want to install Indirection on page 3 17 catalog indirection You have ALTER installed and you want to Upgrade See Migrating Data From upgrade to CHANGE MANAGER at the same or higher maintenance level ALTER to CHANGE MANAGER on page 3 28 BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 13 Installation Paths Full Installation Use the Full installation path to install one or more of t
308. ny SYNC command in the worklist resets the count of SQL commands to zero SYNC commands that this keyword generates are in addition to the SYNC commands that Analysis automatically generates The SYSCOPY threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSCOPY secondary or alternate unit that is used for any overflow SYSCPREF amp amp PREFIX amp amp SSID amp amp OBNOD SYSCPS 10 SYSCSS 2 Defines the default SYSCOPY data set prefix The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves to a table space name or to an index space name depending on the type of object that is being copied Defines the default SYSCOPY primary space allocation Defines the default SYSCOPY secondary space allocation BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 21 Default Option Descriptions SYSCUNIT SYSDA SYSRMAX SYSRMAXU Defines the default SYSCOPY unit The SYSREC threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSREC secondary or alternate unit that is used for any overflow SY
309. o indicates whether to use the BMC Software REORG PLUS product in place of the IBM REORG utility B Generate BMC reorganizations in worklists I Generate IBM reorganizations in worklists N Do not generate reorganizations in worklists default SDSN SYSOUT The default data set for diagnostic messages for Analysis This option may be a sequential data set the keyword SYSOUT or TERM terminal If you use SYSOUT the diagnostic messages are written to the JES SPOOL If you use TERM the diagnostic messages are written to your terminal SDSNE SYSOUT The default data set for diagnostic messages for Execution This option may be a sequential data set or the keyword SYSOUT If you use SYSOUT the diagnostic messages are written to the JES SPOOL SEQI 050 Defines the sequence number increment for worklists and CDL files SL1 HLO LOAD The STEPLIB library that contains the BMC Software load modules SL2 SYS1 DSNEXIT The optional first STEPLIB library for DB2 load modules This library is concatenated to the library that keyword SL1 specifies SL3 SYS1 DSNLOAD The optional second STEPLIB library for DB2 load modules This library is concatenated to the library that keywords SL1 and SL2 specify SL4 SYS1 OTHER LOADLIB1 Optional additional STEPLIB libraries SL5 SYS1 OTHER LOADLIB2 Optional additional STEPLIB libraries SPP ALvrincDS Defines the Specification plan name SSID DB2 Identifies the DB2 subsyste
310. o a table space name or to an index space name depending on the type of object that is being copied Defines the default SYSCOPY primary space allocation Defines the default SYSCOPY secondary space allocation Defines the default SYSCOPY unit The SYSREC threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSREC secondary or alternate unit that is used for any overflow SYSRPREF amp amp PREFIX amp amp SSID amp amp WORKID8 SYSRPS 10 SYSRSS 2 SYSRUNIT SYSDA SYSTYPE S SZDEVT 3380 TABLEACC Y Defines the default SYSREC data set prefix Defines the default SYSREC primary space allocation Defines the default SYSREC secondary space allocation Defines the default SYSREC unit Defines the installation s character set M mixed S single byte only The device type for data set sizing for JCLGEN Valid values are 3380 and 3390 The default is 3380 For DB2 Version 5 1 and later indicates whether all tables remain accessible during execution Y or N BMC Software Inc Confidential and Proprietary Information 7 30 Administrative Products for DB2 Installation Guide TABLEALL N Default Option Descriptions For DB2 Version 5 1 and later specifies the STATS utility to gather information for all columns of tables N Do not i
311. o additional data sharing members or to the group Enabling the Product CLISTs attach name you must duplicate the table rows of the existing subsystem name for each member or group attach name substituting the member or group attach name for the SSID column The example in Figure 4 5 uses the group attach name GRPI Enabling Access to Additional Members DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAM GI ASU DBDB D ASUDOPDI ASUvrmDC ASUS bs ACT DBDB D ACTDOPD1 ACTvrmDM ACT5 ACTvrm_D_MAIN DBDB ACM DBDB D ACMDOPDI CMvrmEDF ACM5 e PSS DBDB D PSSvrmDl PSS5 EXIT DBDB SYS3 DBDB DSNEXIT lo LOAD DBDB SYS2 DB2V62M DSNLOAD HLQ DBDB BMCADMN Vvrm D62 K VCAT DBDB DBDBCAT li DDF DBDB DBDB K ASU GRP1 D ASUDOPDI ASUvrmDC ASUG x ACT GRP1 D ACTDOPD1 ACTvrmDM ACTG ACTvrm D_MAIN DBDB li ACM GRP1 D ACMDOPDI CMvrmEDF ACMG a PSS GRP1 D PSS313D1 PSSG EXIT GRP1 SYS3 DBDB DSNEXIT x LOAD GRP1 SYS2 DB2V62M DSNLOAD HLQ GRP1 BMCADMN Vvrm D62 VCAT GRP1 DBDBCAT io DDF GRP1 DBDB In the example in Figure 4 5 the VCAT keyword is used by CATALOG MANAGER and DASD MANAGER PLUS to indicate the name of a data set that starts with an identifier for the catalog name DBDBCAT e The example in Figure 4 6 shows the data rows servers that can be listed in the CATALOG MANAGER CONNECT command panel To change the servers that the CONNECT command lists you can add delete or modify the
312. oad the distribution tape but it does create new default options files When required by BMC Software products this type of maintenance installation also binds plans and packages Note Edit your output JCL data set name in the User Options panel before you perform a subsequent Maintenance installation SSID Installation The SSID installation path is available for installation of BMC Software products that require you to create a unique set of DB2 objects for each DB2 subsystem This installation path has the following characteristics e uses product libraries that are created during the full installation e allows creation of new DB2 objects BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 15 Installation Paths Considerations e allows an interface with other BMC Software products e allows use of your own VSAM data sets when supported by the selected product and when you specify the Custom installation mode e allows data migration from a previous release when you specify the Custom installation mode If you plan to install products on several subsystems that have similar characteristics you can use the Multiple SSID installation path For more information see Multiple SSID Installation on page 1 17 Since the Install System saves the parameter values that you provide in the first installation the SSID installation path makes it easier and faster to generate th
313. ocessing the logon mode definitions maximum number of sessions must be greater than one 2 Select Add and choose the local LU that you defined in Step 2 and the logon mode entry that you defined in the previous step When you have finished selecting the local partner the LU 6 2 Partner LU screen should contain an entry of 1 Step 4 AddaCPI C symbolic destination to the SNA Gateway Server by performing the following actions at the SNA Gateway Server console 4 A From the Options menu choose CPI C 4 B Select Add and specify the following properties for the symbolic destination 1 Select the symbolic destination name that the PC client will use to access this LU This name can be 1 to 8 characters long Make a note of this CPI C Symbolic Destination Name for later use during the client configuration 2 For the Partner TP Name select Application and enter the TP name of the MVS Server APPCACVI in Figure 4 21 on page 4 37 3 For the Partner L name select Alias and enter the MVS Server LU ACVLUOI in Figure 4 21 on page 4 37 4 For the Mode Name select the logon mode that is defined for the MVS Server APPCPCLM in Figure 4 21 on page 4 37 Step5 Define a default local LU for the SNA Gateway Server by performing the following actions at the SNA Gateway Server console 5 A Select the SNA Gateway Server Admin Icon 5 B In the Servers and Connections window select the server BMC Software Inc Confidential and
314. oftware Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 17 Starting and Configuring the Client Starting and Configuring the Client This section provides information about starting stopping and configuring the client See the online Help for complete instructions about defining hosts and creating subsystem connections Starting the Client To start the client double click the product icon from the PATROL DB Admin Client OS390 program group The PATROL Database Administration window appears To stop the client make the PATROL Database Administration window active Then choose Exit from the File menu Configuring the Client After you install the server and the client you must configure the client before you can use the product Start the client and then perform the following configuration tasks e define hosts or servers A host or server is the OS 390 system that performs the MVS Server operations Each host or server has both an MVS Server and at least one DB2 subsystem installed on it Identifying an available host or server to the client is called defining a host or server You must define at least one host or server to use the Database Administration products You should define a separate host or server for each system that you want to use as a server for the Database Administration products e create subsystem connections When you start a connection yo
315. oftware package at your site making the necessary selections as requested For example using the Microsoft SMS product to distribute the installation you should e create an SMS package by using the setup pdf file included in the directory where you copied the Database Administration product images e schedule an SMS job by using the package that was created using the setup pdf file e ensure that the client receives and runs the package Where to Go from Here After you install the client you can start and configure it See Starting and Configuring the Client on page 9 18 BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 11 Installing the Client Using Distribution Software Verifying Installed Files The directories and files that are listed in Table 9 3 are installed on the client The default is on the C drive During installation you can specify a particular directory to which to install the Database Administration product files By default this directory is Program Files BMC Software PATROL DB Admin Client 0S390 Table 9 3 Client Installation Directories Directories and Files common DB2 OS390 DB2 OS390 bin charmaps Description common files and executables client executables DLLs common executables library files and help files character maps DB2 OS390 bin en_us iso88591 DB2 OS390 bin icons help and mes
316. on you should modify the BMCDB2C variable in the BMCDB2 CLIST Set this variable to the library where the BMCDB2 CLIST was copied Optionally if you copy the BMCDB2PR BMCDB2P2 and BMCDB2TB panels from the HLO JCL library to another library you should modify the BMCDB2P variable in the BMCDB2 CLIST Set this variable to the library where the panels were copied A control table appears at the bottom of the BMCDB2 CLIST as shown in Figure 4 1 Refer to the comments in the BMCDB2 CLIST for the descriptions of the columns and for additional examples Note The data in the control table which begins with the identifier DATA is placed in specific positions and every data row must have an asterisk in column 73 Comment lines contain an asterisk in column 1 The data in the control table is column specific Figure 4 1 BMCDB2 CLIST Control Table DATA PROD SSID D I DOPT PLAN APPL COLL_ID NICKNAME ASU DBAP D ASUDOPD1 ASU611DC ASUA LIB SSID Data Set Name EXIT DBAP SYS3 DBAP DSNEXIT LOAD DBAP SYS2 DB2V31M DSNLOAD e To improve the performance of the invocation of the products from the BMCDB2 CLIST by placing a control table in a permanent ISPF table in the HLQ TLIB data set set the GENTABLE variable in the BMCDB2 CLIST to Y as shown in Figure 4 2 on page 4 6 BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 5 E
317. on IDs Summary This section describes the steps that your DB2 system administrator must perform to enable the use of secondary authorization IDs for the MVS Server The sample connection exit that is supplied by IBM builds a list of secondary authorization IDs that is based on the user ID that is associated with the started task address space As a result this exit does not build the list of secondary authorization IDs for each client as it does for a TSO address space To properly build the list of secondary authorization IDs for each client BMC Software modified the exit The version of the connection exit that is supplied by BMC Software builds a list of secondary authorizations that is based on the user ID that is associated with each client for the MVS Server This sample exit is distributed in the product s HLQ CNTL data set as member DSN3SATH When the modified version of the exit is used the secondary authorizations are dependent on RACF If RACF and the list of groups checking are activated the connection exit sets the list of DB2 secondary authorizations to the list of RACF group names to which the user ID is connected If you are already running a modified connection exit or your site uses a security system other than RACF you should review the sample exit that BMC Software provided and note any modifications Modifications are indicated by BMC34575 after each line of code You can then incorporate these changes into your exi
318. onfidential and Proprietary Information 4 34 Administrative Products for DB2 Installation Guide Setting Up the MVS Server Table 4 4 APPC MVS Configuration Parameter Descriptions Part 2 of 2 Parameter Description LUname the local LU name that has been defined to VTAM for the server MODEname the default Mode Name table entry The entry should match the DLOGMODE parameter of the APPL definition that is used to define the local LU to VTAM OperatingMode indicates operation as an APPC MVS Server The value is SERVER Packetsize size of the data buffer used by the server The default is 8192 ProtocolDriver name of the APPC MVS protocol driver program The value is SBIAPPCM Receivetimeout This parameter is not specified The value is 0 SASDebug flag that disables or enables the SAS C Debugger This flag should be set to 0 ServerEnabled flag that enables or disables the server This flag should be set to 1 TPname the name that is used to describe this server to APPC MVS The Tpname is a 1 to 64 character name that describes the server s address space This name may or may not be the started task name or the job name of the server Transmittimeout This parameter is not specified The value is 0 All APPC MVS parameters have a prefix of MVSAPPC The SBIDBS SERVERI parameter must reflect the type of server that is implemented For APPC MVS the type of server should be MVSAPPC The other
319. options module All other DOPTs module information has been previously gathered BMC Software Inc Confidential and Proprietary Information 6 4 Administrative Products for DB2 Installation Guide Controlling Access e During the batch JCL assembly step the DOPTs module assembly step disassembles the existing DOPTs applies the indirect synonym creator that you specified in the preceding step and reassembles and links the DOPTs module using the same name The step also resolves the indirect collection ID that is located in a subsequent BIND package step Because the installation dialog does not prompt you for this information it must obtain the information from the existing DOPTs module by disassembling it Note If at any time you regenerate the Catalog Indirect JCL for CATALOG MANAGER and then resume the installation at a step later than the DOPTs module assembly step the BINDs for the packages will fail because the value of the indirect collection ID is unresolved You must run the DOPTs assembly step to resolve this value Controlling Access You can restrict access to functions of CATALOG MANAGER through plan authorizations Plan names have the format prdvrmyz where prd is the product code vrm is the version release and maintenance level y is the access type and z is the plan function The following plans are provided with the product ACTvrmDE Data Editor This plan enables access to the data editing and browsing func
320. or ALTER Objects Primary Secondary Estimated Estimated Object Quantity Quantity Tracks Tracks Default KB KB 3380 3390 table space 14560 1160 364 304 index space 2640 1120 66 55 Table 1 2 Space Estimates for ALTER Distribution Data Sets Estimated Estimated Distribution Data Set HLQ CNTL HLQ LOAD HLQ CLIST HLQ PLIB HLQ MLIB HLQ SLIB HLQ DBRM HLQ TLIB HLQ MSGS HLQ SCRIPT HLQ MSGTEXT VB 255 27998 2 1 BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 5 Estimated Space Requirements CATALOG MANAGER Space Estimates Table 1 3 and Table 1 4 provide space estimates for CATALOG MANAGER objects and distribution data sets Table 1 3 Space Estimates for CATALOG MANAGER Objects Primary Secondary Estimated Estimated Object Quantity Quantity Tracks Tracks Default KB KB 3380 3390 table space 8000 2000 200 167 index space 40 40 1 1 Note Space estimates for the UTILITY MANAGER for DB2 product are included in Table 1 3 since the UTILITY MANAGER objects are installed with CATALOG MANAGER For information about UTILITY MANAGER refer to the UTILITY MANAGER for DB2 Getting Started book Table 1 4 Space Estimates for CATALOG MANAGER Distribution Data Sets Estimated Estimated Distribution Data Set HLQ CNTL HLQ LOAD HLQ CLIST HLQ PLIB HLQ MLIB HLQ SLIB HLQ DBRM HLQ TLIB HLQ MSGS BMC Software
321. ore information about how the Install System uses the installation user profile see Installation User Profile on page 1 19 Warning If you use an existing profile you must review the installation parameters carefully Failure to change the required parameters during the new installation procedure can cause severe errors when you submit the installation JCL For example if you do not change a DB2 plan name from a previously specified value you can overwrite a plan that your current installation uses BMC Software Inc Confidential and Proprietary Information 2 20 Administrative Products for DB2 Installation Guide Specifying User Options Step6 Choose to process a profile from a previous installation if necessary If you are unsure of the profile s name or contents this option allows you to browse existing input data sets for an appropriate installation profile and copy the profile to the current installation data set Step 7 Choose Reset if you want to set the installation parameters for the selected products to the initial BMC Software default values The Install System stores the updated values in your installation profile Step 8 Type Y yes or N no to choose whether the Install System displays a series of panels from which you can review the installation variables The Install System displays the review panels before generating the installation JCL You can change most of the values that are shown by typing over
322. ors See Control Statements and Keywords on page A 29 for assistance with syntax If you cannot locate the errors contact BMC Software Product Support for assistance ALL REQUESTS COMPLETED SUCCESSFULLY Explanation All requested functions have been processed System Action The product load library is updated User Response None Information only PERMANENT PRODUCT AUTHORIZATION TABLE S GRACE PERIOD IS INVALID PLEASE CONTACT BMC PRODUCT SUPPORT Explanation An error occurred invalidating the table s grace period The table must be rebuilt System Action All functions are suppressed User Response Contact BMC Software Product Support for assistance BMC Software Inc Confidential and Proprietary Information B 10 Administrative Products for DB2 Installation Guide Error Messages BMC89070E ISPF V3 REQUIRED USE BATCH UPDATE PGM INSTEAD Explanation ISPF version 3 or later is required to run the online customer interface System Action The online customer interface terminates User Response Use the batch update program BMC89100E INTERNAL ERROR RC lt return code gt PLEASE CONTACT BMC PRODUCT SUPPORT Explanation A processing error occurred System Action The function is not performed User Response Note the return code and contact BMC Software Product Support for assistance BMC89101E PASSWORD CONTAINS INVALID CHARACTERS Explanation The password contains one or more invalid specia
323. ot defined 6 MB of free Windows 2000 Drive or higher space in the windows or winnt directory is required Domestic and International Supported Environments The products include domestic and international versions which are categorized as follows e U S English data US7ASCID which is single byte Sorting is based on ASCII code page values e European data support which includes support for extended character sets in any single byte left to right language and support for local date and time formats Note Code page specification is required as part of the server installation For more information refer to Confirming the Host Code Page for the MVS Server on page 4 43 BMC Software Inc Confidential and Proprietary Information 9 2 Administrative Products for DB2 Installation Guide Installing the Client the ability to work with any supported local language in all parts of the product including meta objects such as filter names session names and catalog data support for the creation and management of any persistent object in the user s native language Installing the Client Before you can install the client for any of the products you must have installed and configured the MVS Server For information about the MVS Server refer to Performing the Post Installation Tasks for the MVS Server on page 4 22 Setting up the Client You need the following items to install clients the MVS Serve
324. ou unload the Install System from the tape Searching for the Installation Profile The Install System searches the following data sets in the order shown for the xxxxPROF member 1 the user named output JCL data set 2 the HLO INSTALL data set 3 the ISPF profile data set If the Install System finds the member in one of the first two data sets it copies the member to your ISPF profile data set ISPF can then use the member to retrieve and store the installation parameters Note If the Install System cannot find the profile member it creates a new xxxxPROF member At the end of the installation session the Install System copies this member from the ISPF profile data set to the user named output JCL and HLQ INSTALL data sets If your TSO session terminates abnormally modifications to your profile are not saved Reusing the User Profile You can reuse an installation user profile by starting the Install System with an existing HLQ INSTALL or output JCL data set that contains a xxxxPROF member Reusing the profile gives you access to the installation options that you specified during the previous installation session BMC Software Inc Confidential and Proprietary Information Chapter 1 Preparing for Installation 1 19 Installation Default Options An installation option allows you to browse existing input data sets for an appropriate installation profile and copy the profile to the current installation data set This option i
325. ovide the following information e The name of the JES2 macro library data set for that release typically this name is SYS1 HASPSRC e The MVS subsystem name that JES2 is using on that system and with which this particular MVS server task will communicate default of JES2 is provided The information that is required can be obtained from your local MVS or JES system programmer e An MVS subsystem name which the JSI JES Interface will use This name should be limited to four characters and reflect the name of the JSI interface that will be used by that particular server started task Note Each MVS server started task should have a unique JSI subsystem name default of JSI1 is provided No MVS system configuration changes are required for this parameter definition BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 13 Default Option Listing DOPTs Once these parameters have been determined the installation process builds an installation job This job may assemble a JES Offset module for the specified SP level of JES2 that is using the specified macro library if necessary This JES Offset module is then linked into the main JSI JES interface load module The installation also updates the MVS Server started task JCL and the server INI file with the subsystem names for both JES2 and the JSI interface The MVS Server INI file is a PDS member that contains various parameters that the
326. parameters within the configuration file are not related to APPC MVS so they do not need to be changed Additional Reference Documents The following documents provide additional reference information e MVS ESA Planning APPC Management Reference Manual e MVS ESA Application Development Writing Servers for APPC MVS BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 35 Setting Up the MVS Server e MVS ESA Application Development Writing Transaction Programs for APPC MVS e VTAM Network Implementation Guide Where to Go from Here After you set up the MVS Server you set up the SNA Gateway Server to connect to the MVS Server For more information see Setting Up the SNA Gateway Server on page 4 37 BMC Software Inc Confidential and Proprietary Information 4 36 Administrative Products for DB2 Installation Guide Setting Up the SNA Gateway Server Setting Up the SNA Gateway Server Summary The second task in the APPC configuration process requires you to set up the SNA Gateway Server for connectivity to the MVS Server The MVS Server uses the APPC MVS Server facilities to support an APPC independent LU 6 2 connection to the SNA Gateway Server Several steps are required to configure the SNA Gateway Server to support this APPC connection Before You Begin Before you set up the SNA Gateway Server be sure that you completed the steps in Setting Up the MV
327. pending on which Install System installation path that you used The last four characters are always DOPT The xnnDOPT member of the installation data set contains an assembly language program with an options macro call that establishes the default processing values You can tailor the installation of the product including changing plan names by editing the default values in the xnnDOPT member Installation Defaults During installation you can specify names for options modules synonym qualifiers database names creator names and collection names The default values for these names are listed in Table 5 1 In these default values v indicates the version r indicates the release m indicates the maintenance level and c is a character value indicating the DB2 version where B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later Table 5 1 ALTER Installation Default Values Installation Default Value Default Options Module ALUDOPD1 Synonym Qualifier ALUvrmcD Database Name BMCAL vrc Creator Name BMCAL vre Collection Name ALUvrmc_D_MAIN Server Main Collection Name ACVvrm_D_MAIN BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 3 Controlling Access Upgrading ALTER to CHANGE MANAGER To upgrade to CHANGE MANAGER without migrating your existing data in ALTER perform a Full installation of CHANGE MANAGER To upgrade
328. prefix if one is used Symbolic Variables The Install System frequently uses symbolic variables in data set names data set prefixes and job statement information A symbolic variable is a variable name with an ampersand amp prefix In the Install System most occurrences of symbolic variables are related to keyword values that you specify in the product options While assembling product options macro processing attempts to resolve all symbolic variables in the listing Most of the symbolic variables are resolved when JCL is generated from one of the BMC Software products not during assembly of the default options DOPTs module To prevent errors during DOPTs module assembly the Install System doubles the ampersand for all symbolic variables The double character rule also applies to e single quotation marks within literal values if the literal is enclosed with delimiting single quotation marks e a period if it immediately follows a variable name BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 15 Running the Install System Table 2 3 illustrates the use of double characters Table 2 3 Using Double Characters Variable Result Examples of Symbolic Variables The following examples show symbolic variable specifications in the DOPTs listing and in the user options after DOPTs assembly Example 1 DOPTs amp amp PREFIX amp amp SSID amp amp DBNAME
329. privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSKEYS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The name of the DB2 commands plan BMC Software Inc Confidential and Proprietary Information 6 16 Administrative Products for DB2 Installation Guide Default Option Descriptions LDSN amp amp ZUSER BMCCAT SQL LOBSTAT STATIC LOCATIO STATIC LPLAN ACTvrnDL LULIST STATIC LUMODES STATIC LUNAMES STATIC MAX 300 MODESEL STATIC MPLAN ACTvrnDM NOWRK Y The name of the SQL output data set CATALOG MANAGER dynamically allocates the data set the first time that it is used When allocating this data set use these parameters DCB LRECL 4092 BLKSIZE 4096 RECFM VB Note In many installations allocation of data sets is controlled by user written or third party routines If allocation fails you should use alternate means such as ISPF to perform the allocations Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSLOBSTATS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to ac
330. r CPU allowing the new CPU to run the product in place of the old CPU Modify modifies one or more properties of one CPU that currently exists in the product authorization table Reset modifies the global properties of the product authorization tables BMC Software Inc Confidential and Proprietary Information A 4 Administrative Products for DB2 Installation Guide How to Apply Passwords Temporary Passwords BMC Software issues temporary passwords to customers who are evaluating products on a trial basis or to customers who need to bypass product authorization to run a product temporarily on an unlicensed CPU Temporary passwords have a specific expiration date which is part of the password How to Apply Passwords A password is an activation key for the software license not the software license itself Apply your new passwords as soon as possible after you receive them because temporary passwords have a limited lifespan which is typically 30 days You can apply the new passwords before you completely install the product if you have installed the Product Authorization utility and have downloaded the product load library Also you can apply the passwords even if the product is not yet running on a specific CPU For example if your installation process requires that you install and run the product on a test system before migrating it to the production system you can apply the password for the production system s CPU even though the
331. r DASD MANAGER PLUS Distribution Data Sets Estimated Estimated Distribution Data Set HLQ CNTL HLQ LOAD HLQ CLIST HLQ PLIB HLQ MLIB HLQ SLIB HLQ DBRM HLQ TLIB HLQ MSGS HLQ QMFQRY FB 79 3160 3 3 HLO QMFPROC FB 79 3160 3 3 HLQ QMFFORM V 85 89 15 15 Note The 7LO QMFQRY HLQ QMFPROC and HLO QMFFORM data sets can be edited in the JCL from the IOSUNLD job BMC Software Inc Confidential and Proprietary Information 1 8 Administrative Products for DB2 Installation Guide Understanding the Install System Understanding the Install System The BMC Software Install System is an ISPF application that helps you generate a set of batch jobs in job control language JCL You use the installation batch jobs to unload and install products from a distribution tape The Install System guides you through the installation process allowing you to accept or change defaults along the way You can readily access Help from each panel by pressing F1 You can install multiple BMC Software products on one DB2 system at a time You can request different product installation paths as you go through the installation panels For example you can request a Full installation of one product and a Maintenance installation of another Merging Data Sets from Multiple Tapes You can install products from various BMC Software tapes such as SIS UIS TIS DIS and EDP during a single Install System session You accomplish this by using t
332. r DB2 Messages Manual ALTER and CHANGE MANAGER for DB2 User Guide CATALOG MANAGER for DB2 User Guide Description contains descriptions and responses for the information warning and error messages that the Administrative Products generate explains the objects components commands and keywords for the ALTER and CHANGE MANAGER products explains the concepts and considerations for performing tasks in the CATALOG MANAGER product DASD MANAGER PLUS for DB2 User Guide UTILITY MANAGER for DB2 Getting Started Online and Printed Books explains the features and the functions of the DASD MANAGER PLUS product contains information about installing configuring and using the UTILITY MANAGER product The books that accompany BMC Software products are available in online format and printed format If you are a Windows user you can view online books with Acrobat Reader from Adobe Systems The reader is provided at no cost as explained in To Access Online Books You can also obtain additional printed books from BMC Software as explained in To Request Additional Printed Books To Access Online Books Online books are formatted as Portable Document Format PDF files You can view them print them or copy them to your computer by using Acrobat Reader 3 0 or later You can access online books from the documentation compact disc CD that accompanies your product or from the World Wide Web In some
333. r Guide BMC Software Inc Confidential and Proprietary Information 5 24 Administrative Products for DB2 Installation Guide Chapter 6 Installing CATALOG MANAGER This chapter presents the following topics OVENI EW or i DA RA 6 2 Installation Considerations L LL 6 3 Installation Defaults nonn LL 6 3 Implementing Catalog Indirection LL 6 3 Controlling ACCESS circ ria italia 6 5 Default Option Listing DOPTs LL 6 6 Default Option Descriptions 0 0 0 cece eee eee 6 11 Post Installation Considerations 0 00 cece eee eee 6 26 BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 1 Overview Overview This chapter provides information about how to prepare to install the BMC Software CATALOG MANAGER for DB2 product The CATALOG MANAGER product facilitates the day to day tasks that are associated with DB2 administration CATALOG MANAGER lets you access information in a DB2 catalog by generating a list Then you can initiate an action on one or more objects in the list CATALOG MANAGER provides the following major functions e creates new DB2 objects by using existing objects as a template e drops catalog objects with the option to view a dependency list e logs dropped object structures and their data for recovery purposes e grants revokes and copies authorizations for users or objects e lists revoked dependencies and reassigns
334. r configuration settings sufficient disk space on your client system at least 6 MB of free space in the temp directory which is defined in the autoexec bat file If the TEMP environment variable is not defined ensure that the drive containing your windows directory has at least 6 MB of free space This space is used for the creation of temporary files during the installation process all applications closed down prior to installing the client To ensure that the network is configured properly see Verifying Server Networking on page 9 4 BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 3 Verifying Server Networking Verifying Server Networking Summary This procedure describes how to verify that your network is working properly Step 1 From a DOS prompt enter ipconfig all Windows NT or winipefg all Windows 98 or Windows 2000 Your host name and IP address appear as shown in the following example Windows NT IP Configuration Host Name yourname yourcompany com DHCP Enabled No IP Address 172 18 22 15 Step 2 From a DOS or command prompt enter ping server where server is the location of the MVS Server If the ping returns the message Bad IP address server or Request timed out you can continue with the installation However you must resolve this network problem before you can use the product B
335. r dynamic SQL to access the SYSIBM SYSFIELDS DB2 catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSFOREIGNKEYS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table The group attach name for data sharing in a Sysplex This name is used as the SSID when JCL for utilities is generated Indicates whether to include aliases in the hierarchical describe Y or N Indicates whether to include indexes in the hierarchical describe Y or N Indicates whether to include synonyms in the hierarchical describe Y or N Indicates whether to include tables in the hierarchical describe Y or N Indicates whether to include table spaces in the hierarchical describe Y or N Indicates whether to include views in the hierarchical describe Y or N Indicates whether to include plans in the hierarchical describe Y or N BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 15 Default Option Descriptions HPLAN ACTvrnDH HRS N ICCOL ICSYC The plan for displaying BMC Software utility status Specifies whether all CATALOG MANAGER users can use the HEX command or only those users with DB2 SYSADM authority Y only user
336. r non tape work files Defines the default work secondary space allocation in cylinders for work data sets that include Analysis and Execution diagnostics Defines the default work unit Work data sets include Analysis and Execution diagnostics data sets The name of the DASD MANAGER PLUS plan that is used for cross reference The name of the DASD MANAGER PLUS plan that is used for displaying DASD MANAGER PLUS statistics Post Installation Considerations After installation refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for DASD MANAGER PLUS BMC Software Inc Confidential and Proprietary Information 8 14 Administrative Products for DB2 Installation Guide Chapter 9 Installing the Client for ALTER and CHANGE MANAGER This chapter presents the following topics OVEDVICW i iii lil PRA en BER Sg es 9 2 Prerequisites 0 brani ga etna sad whan oe sta ara 9 2 Domestic and International Supported Environments 9 2 Installing the Client msione ee a aie a bei bleh dade el 9 3 Setting up the Client 0 0 eee ee eee eee 9 3 Verifying Server Networking 9 4 Selecting the Type of Installation 9 5 Installing a Client to Run Locally LL 9 6 Installing the Client on a Network Drive 9 8 Installing a Client Command Line Interface 9 9 Installing the Client Using Distribution Software 9 11 Ve
337. receives control either initializes or refreshes the user s options with the information from the DOPTs module that are allocated by the BMCDB2 CLIST Avoiding User Options Overlay In some situations when you make changes in one environment those changes appear in another environment This situation usually happens when the same ISPF application ID is being established for multiple SSIDs and is probably unacceptable because the user option changes are SSID specific For example if both of the DB2T and DB2P application IDs for ALTER are established as ALUA any user option changes that are made for DB2T are also made for the DB2P user options To avoid accidentally overlaying user options ensure that the ISPF application that is established for each DB2 SSID is unique The Install System attempts to make each application ID unique in a given BMCDB2 CLIST It does not however make each application ID unique across multiple BMCDB2 CLISTs For example if you execute a Full installation for DB2T and a Full installation for DB2P you have two BMCDB2 CLISTs one for each environment The initial ISPF application ID for both SSIDs is xxxA which results in an overlay To correct overlay problems follow these steps for each BMCDB2 CLIST that you are using 1 Edit the BMCDB2 CLIST 2 Proceed to the DATA line 3 For each SSID make sure that the APPLID is unique across all BMCDB2 CLISTs as shown in Figure 3 1 Figure 3 1 Sample B
338. required in the specified TP profile data set but a reference to the system level TP Profile data set is needed as part of the LUADD definition statement The LU application should already be defined and active to VTAM The LU name that is used in the VTAM application definition must match the ACBNAME operand that is used in the LUADD statement Once defined the APPC address space must be started with the appropriate parameters to include the configuration file with the LUADD statement for the server Figure 4 19 shows a sample LUADD statement for defining the local LU to APPC MVS The example can be added to an existing APPCPMxx configuration member or used in a new configuration member Then the example can be dynamically added to the APPC address space using the SET APPC xx MVS command Note The HLQ CNTL data set contains a sample APPCPMxx member Figure 4 19 Sample Local LU Definition for APPC MVS LUADD ACBNAME ACVLUO1 NOSCHED TPDATA SYS1 APPCTP TP LEVEL SYSTEM Step 4 Provide APPC parameters to the server The server requires several parameters that have been defined to APPC MVS and VTAM The values of these parameters are described to the server through an initialization INI file that is specified by the BMCIPROF DD statement in the server JCL The parameters in this file are initialized during the installation of the server If changes to the parameters are required you can modify them by manually edit
339. rform a separate Full installation for every version of DB2 on which the ALTER and CHANGE MANAGER products will run These products require separate libraries for each version of DB2 SSID Installation or Subsequent Maintenance The Install System generates member BMCDB2SS to support the subsequent DB2 subsystems This member contains logic for the DOPTs module allocation When you use this member to update the BMCDB2 CLIST consider the following e If you have MVS ESA and TSO E version 2 1 or later the Install System prompts you for the location of the BMCDB2 CLIST and automatically updates it with the information in the BMCDB2SS e Ifyou do not have MVS ESA and TSO E version 2 1 or later follow the directions in BMCDB2SS for updating the BMCDB2 CLIST If CATALOG MANAGER is being installed follow the instructions for modification of the CATALOG MANAGER plan name BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 3 Upgrading Shared Components Upgrading Shared Components All Administrative Products share the following components e JCL Generation which controls the JCL generation process e Execution Monitor which controls worklist processing by reading and performing worklist commands When you unload Administrative Products from the distribution tape these components are also unloaded The Install System copies these components to an APF authorized load library
340. rifying Installed Files 0 0 0 0 LL 9 12 Troubleshooting the Client Installation 9 12 Maintaining the Client 9 13 Adding a Product ao sir lita laica lea ana wea aes 9 14 Uninstalling a Client GUI LL 9 15 Uninstalling a Client Command Line Interface 9 16 Reinstalling a Product 9 17 Starting and Configuring the Client LL 9 18 Starting the Client 22 0 5 cee ee ee ce ee en eee 9 18 Configuring the Client 0 0 0 cee ee cee eee 9 18 Where to Go From Here i 9 19 BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 1 Overview Overview This chapter provides information about installing configuring and starting the client for ALTER and CHANGE MANAGER The client provides a graphical front end to the MVS Server for the Database Administration products Prerequisites Table 9 1 lists the requirements for the system software that the products support Table 9 1 System Software Requirements Operating Minimum System Hardware Free Disk Space and Product Platforms Requirements Requirements e Windows NT 4 0 64 MB RAM ALTER 71 8 MB with Service e 200 Mhz CHANGE MANAGER 72 0 MB boo si later Pentium 6 MB in the temp directory for appie VGA video at temporary files created during Windows 98 least 600 X 800 installation Second Edition 4x CD ROM If temp is n
341. roblem can be circumvented by specifying a different library to contain the product authorization tables You should allocate a separate PDS or PDS E for the authorization table and specify this PDS or PDS E when installing the password If you have questions about the problem or the work around contact your BMC Software Product Authorization technical support analyst at 800 537 1813 USA or Canada or call your local support center Product Authorization Passwords Valid passwords can include the following characters e the alphanumeric character set excluding the letters J and O to avoid confusion with the numbers one 1 and zero 0 e equal sign at sign and plus sign Note If your keyboard does not have the at sign you can use the asterisk in place of You can use these two characters and interchangeably when typing passwords Permanent Passwords Permanent passwords update a product s permanent authorization table Each permanent password has one of the functions described in Table A 1 When you apply a permanent password the Product Authorization utility automatically recognizes that password s function and prompts you accordingly Table A 1 Permanent Password Functions Function Description Add authorizes one new CPU to run the product Delete removes one CPU from the table preventing that CPU from running the product Replace replaces one CPU in the table with anothe
342. ry Information 8 4 Administrative Products for DB2 Installation Guide Controlling Access Controlling Access You can restrict access to DASD MANAGER PLUS functions by controlling authorization to various plans Plan names have the format prdvrmyz where prd is the product code vrm is the version release and maintenance level y is the access type and z is the plan function Execution component plan names have the format prdvrmnn where prd is the product code vrm is the version release and maintenance level and nn is a unique plan identifier The default plans that are shipped with this release follow along with their default plan names DASD MANAGER PLUS Plans The following plans are used by components of DASD MANAGER PLUS ASUvrmDC DB2 Catalog Update This plan controls access to the operations that update the catalog Only users with authority to change DB2 catalog statistics should be authorized to use this plan ASUvrmDD Object Definition Note This plan is for DASD MANAGER 3 2 only This plan controls access to the user interface for object definition utility generation and statistics display Any user needing to perform online object definition tasks should be authorized to use this plan ASUvrmDJ BMCTRIG Utility Job Generation This plan controls access to utility job generation from BMCTRIG Any user needing to perform online or BMCTRIG JCL generation should be authorized to use this plan ASUvrmDR R
343. s OV CTVACW sect a rama Md A died AIMS bdte DAN 5 2 Installation Considerations 0 00000 cece eee eens 5 3 Installation Defaults 0 0 0 0 000 0 eee eee 5 3 Upgrading ALTER to CHANGE MANAGER 5 4 Controlling Accessu eriat eee ccc cece cee ene 5 4 ALTER Specification and Analysis Plans 5 4 ALTER Execution Plans 5 6 ALTER Object Secufity i bea ie be bbe bu bee 5 7 JSI JES Interface Installation LL 5 7 Default Option Listing DOPTS LL 5 8 Default Option Descriptions LL 5 12 Post Installation Considerations 0 000 cece eee eee ees 5 24 BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 1 Overview Overview This chapter provides information about how to prepare to install the BMC Software ALTER for DB2 product The ALTER product provides both management of application structures within a DB2 subsystem and a means of migrating application structures from one DB2 subsystem to another ALTER performs the following major functions e changes data structures e migrates data structures and their associated data ALTER automates the task of changing data structures It determines the impact of the changes across the DB2 subsystem and prepares the most efficient strategy for implementation ALTER also performs extensive error checking to ensure that the changes are correct before execution ALTER provides full m
344. s DATACLAS in the JCL for workfiles WDSN amp amp PREFIX amp amp SSID amp amp WORKID WLPS 15 WLSS 5 WLU SYSDA Defines the default data set name for a worklist that Analysis generates Defines the default primary space allocation for the worklist in 3120 byte blocks Defines the default secondary space allocation for the worklist in 3120 byte blocks Defines the default worklist unit BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 23 Post Installation Considerations WMC WPS 10 WSC WSS 2 WU SYSDA The SMS management class name used at data set allocation time to define the migration retention and backup requirements of the data set WMC will appear as MGMTCLAS in the JCL for workfiles Defines the default work data set primary space allocation The SMS storage class name used at data set allocation time to define the processing requirements of the data set WSC will appear as STORCLAS in the JCL for non tape workfiles Defines the default secondary space allocation for the work data set Defines the default work data set unit Post Installation Considerations After installation refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for ALTER To perform any additional post installation tasks or to set up ALTER refer to the ALTER and CHANGE MANAGER for DB2 Use
345. s a temporary product authorization table when you apply a temporary password See Product Authorization Passwords on page A 4 for more information about permanent and temporary passwords Product authorization tables are product specific and are identified by the three character product code as in the following examples where the variable prd is the three character product code prdTBL3P permanent prdTBL3T temporary Problem Regarding Product Authorization Table Installation Do not install the Product Authorization tables into load modules that are PDS Es Partition Dataset Extended PDS E files cannot contain load modules and data type objects together in the same file The Product Authorization table is a data file normally stored in the product loadlib Installing Product Authorization tables into load module PDS Es will cause a failure when attempting to apply the password to the product library Detailed Error Message 13 10 20 13 10 21 BMC Software Inc JOB05439 IEC036I 002 CC IGC0005E RDACAL2S SECSEC3B SYSLIB 582B DEVS97 JOB05439 IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE 002 REASON CODE 000000CC Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 3 Product Authorization Passwords Solution This problem will be corrected in a future version of the Product Authorization utility however the p
346. s as they are defined in the DB2 system catalog tables In addition you can also change data when you perform several different kinds of tasks with CHANGE MANAGER This section provides the information that you need to set up proper safeguards for access to the CHANGE MANAGER components BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 9 Controlling Access Plans that are included with CHANGE MANAGER provide access to the Front End Import Specification Analysis Baseline Compare Report Environment and Execution components You can control whether users can access the CHANGE MANAGER interface or each of these components by controlling the authorization that is granted to each of these plans Plan names vary depending on the version and release of the product that you are using ALTER and CHANGE MANAGER plan names have the format ppvrmcyz where pp is the product code vrm is the version release and maintenance level c is the DB2 level B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later y is the access type and z is the plan function Note The c character in the syntax ppvrmcyz is only used when defining plans for ALTER and CHANGE MANAGER versions 5 2 or later Earlier versions use the syntax prdvrmyz Execution component plan names have the format prdvrmnn where prd is the product code vrm is the version release a
347. s must override the options that relate to a specific DB2 subsystem at the beginning of a session for each product These parameters are saved in the user s ISPF profile and are preserved across ISPF sessions The exceptions are the GUI for ALTER and CHANGE MANAGER which use the SSID value in the DOPTs to know to which SSID to connect Multiple Options Modules You can specify separate prdDOPD1 modules for each SSID by using a unique name for each module The Install System panels prompt you for the names and you can assign names that identify the SSIDs on which you are installing the product In most cases only the SSID name will be different for each DOPTs module BMC Software recommends that you include the refresh feature for this option which causes the program to use the SSID from the DOPTs module rather than the SSID that was last saved in your ISPF profile You do not need to specify different plan names or object names for subsequent products or SSID systems When you start the product through the Install System s ISPF interface the unique name of the DOPTs module for each SSID is passed to the product Using Catalog Indirection Catalog indirection is an optional method of implementing and maintaining the Administrative Products As the name implies catalog indirection allows products to access the DB2 catalog indirectly when making information queries To accomplish catalog indirection ALTER CHANGE MANAGER and CATALOG
348. s useful when you are unsure of the profile name or contents If you reuse a profile from a previous installation session you must review the installation options carefully Verify that the values for the options are still valid for the current installation Change any values in order to reflect the new release For example a database name or plan name might change from one release to the next Warning Failure to change the required parameters for the new installation can cause severe errors when you submit the installation JCL For example if you do not change a DB2 plan name from a previously specified value you can overwrite a plan that your current installation uses Installation Default Options After the Install System generates the installation batch jobs the user named output JCL data set contains a member that establishes values for default processing options DOPTs The member name has the format xnnDOPT where the variable xnn is a three character ID that is based on the installation path that you choose for the product Some of the BMC Software products use a text options file while others use an assembled options module The xnnDOPT member contains either logic to copy the option file to the CNTL data set or an assembly language program with an options macro call You can tailor the processing of the product by editing the default values in the xnnDOPT member When the xnnDOPT job is submitted the Install System ac
349. s with DB2 SYSADM authority N all users This DOPT is no longer used The CATALOG MANAGER synonym creator ID that is used when installing catalog indirection for CATALOG MANAGER JDSN amp amp ZUSER BMCCAT UTILITY INDEXES STATIC INDEXPA STATIC INDEXST STATIC IPNAMES STATIC KEYS STATIC KPLAN ACTyrmDK The default data set name that is used for utility JCL This option can be either a sequential or partitioned data set A member name is not allowed for a partitioned data set The product automatically uses the utility name as the default member name Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSINDEXES DB catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSINDEXPART DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSINDEXSTATS DB2 catalog table The default STATIC uses the privileges of the package owner DY NAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSIPNAMES DB2 catalog table The default STATIC uses the
350. sage files icons DB2 OS390 bin iconv DB2 OS390 bin locale code page conversion tables installed locales function and format tables DB2 OS390 config DB2 OS390 work client configuration directory work directory Troubleshooting the Client Installation 9 12 If your client installation stops abnormally you should delete any temporary directories and files that the installation process created before it terminated The installation process creates the following temporary directory and files istmpx dir where x is a number ins0433 mp isz0433 mp If your TEMP environment variable is set you can find these files in the temp directory Otherwise look for them in the windows or winnt directory BMC Software Inc Confidential and Proprietary Information Administrative Products for DB2 Installation Guide Maintaining the Client Maintaining the Client For most installations you can proceed directly to Starting and Configuring the Client on page 9 18 At some point however you may need to upgrade or change the client The following sections discuss e adding a product e uninstalling a client e reinstalling a product BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 13 Adding a Product Adding a Product Summary This task describes how you can add a product Step 1 Run the Setup program as you
351. samples in HLQ CNTL or in the output JCL data set Select the member prdCPUID where the variable prd is the three character product code and then follow the instructions in the comments section of that member BMC Software Inc Confidential and Proprietary Information Appendix A BMC Software Product Authorization A 27 Batch Product Authorization Figure A 14 Sample JCL for Running Batch Product Authorization JJJJJJJJ JOB SECSEC3B EXEC PGM SECSEC3B PARM prd lt lt lt PRODUCT CODE STEPLIB DD DSN BMC INSTALL LOAD DISP SHR SYSLIB DD DSN BMC PRODUCT LOAD DISP SHR lt lt REQUIRED SYSPRINT DD SYSOUT lt lt lt REQUIRED LLX SYSIN DD x PROCESS AN ADD PASSWORD AND LIST RESULTS PSWD AE 82G 91 C7 NEWCPUID 11111 9021 x PROCESS A DELETE PASSWORD AND LIST RESULTS PSWD BE ADO 32 7C OLDCPUID 31091 9121 PROCESS A REPLACE PASSWORD AND LIST RESULTS PSWD ARF 56C 1 C7 OLDCPUID 31001 3390 NEWCPUID 31091 3381 PROCESS A RESET PASSWORD PSWD 123 456 789 ABC PROCESS A TEMPORARY PASSWORD AND LIST RESULTS PSWD AE B32 1C D7 REPORT THE PROCESSOR INFORMATION AND AUTHORIZATION LIST Additional Information JOB EXEC STEPLIB DD SYSLIB DD SYSPRINT DD SYSIN DD Information required for the JCL script are as fol
352. se this plan allows you to create and maintain ALTER objects and perform other Front End functions BMC Software Inc Confidential and Proprietary Information 5 4 Administrative Products for DB2 Installation Guide Controlling Access ACVvrmDM Display Catalog and SQL Information Access to this plan is required to use the GUI for ALTER It displays catalog and SQL generation and execution information ALvrmcDi Import Plan This plan is provided by the Import component of ALTER and allows users to import DDL into the ALTER Change Definition tables ALvrmcDS Specification Plan This plan accesses the Specification component within ALTER This plan provides a way for users to request changes to database objects and data With access to Specification users can also search and review groups of objects ALvrmcDA Analysis Plan This plan allows users access to the Analysis component to analyze changes and to generate a worklist You cannot make actual changes to DB2 objects and data by creating a worklist The Specification and Analysis plans provide a way for users to request and analyze changes For this reason you can usually place minimum restrictions on using Specification and Analysis ALvrmcDE Environment Plan Access to this plan allows users to invoke the ENVI command to review their system environment Since this plan is not accessed outside of the other ALTER components you can usually grant PUBLIC access to t
353. ser uses the Administrative Products to perform an activity that changes information in the DB2 catalog The user then completes a task that performs an information query against the copy of the catalog In this case it may seem that the first activity did not succeed However if you implement catalog indirection only for users who are already restricted to information only queries this problem may not occur For example you could implement catalog indirection for those ALTER users who are not allowed to run the Execution Monitor BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 19 Using Catalog Indirection You need to update the copy of the catalog on a timely basis to keep it accurate Running the copy job does not have a significant impact on catalog contention but does consume other system resources How often you should run the job depends on the amount of catalog change activity in your DB2 system and the type of users who are restricted to accessing a copy A high activity data center may need to run the job several times a day Also the job that updates the catalog copy prevents users from accessing the current copy of the catalog while the job runs This restriction may have an undesirable impact on the Administrative Products if you must run the copy Job during a high activity period The SEARCH command in CATALOG MANAGER uses dynamic structured query language SQ
354. st add the following statements to the unload job e an additional DD statement e an additional SYSIN copy statement When merging product tapes always observe the following guidelines e Ifyou merge tapes with different versions of the Install System copy the oldest release first Then use the COPY REPLACE option to copy the newer releases into the same data set e You cannot merge multiple releases of the same product In other words do not merge two tapes with the same tape code such as SIS BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 7 Unloading the Install System Figure 2 2 DCIINST UNLOAD SYSPRINT SYSUT3 SYSUT4 DCITINST DCITINS2 DCITLOAD DCIINST DCILOAD SYSIN COPY COPY COPY 2 8 e Always use the load library from the latest available release of the Install System The HLQ INSTALL LOAD data set is not merged Note Determine the latest release of the DB2 Common Install System by reviewing the version release level on the physical tape label Alphabetic maintenance levels are more recent than numeric maintenance levels For example version 1 6 A0 is a later release than version 1 6 90 Figure 2 2 shows an example of an unload job that merges data sets from two distribution tapes where prod_tape 2 contains the latest availab
355. sting exit Note If your DB2 subsystems do not share a single HLO SDSNEXIT data set your DB2 system administrator should perform the following steps for each subsystem Step 1 Rename member DSN3 ATH in the HLO SDSNEXIT data set to another name Step 2 Assemble and link member DSN3SATH in the HLQO CNTL data set with the same JCL that is provided for the IBM supplied exit DB2 creates DSN3 ATH Step3 Cycle DB2 Where to Go from Here After you enable the use of secondary authorization IDs you verify the installation For more information see Verifying the Installation of the MVS Server on page 4 45 BMC Software Inc Confidential and Proprietary Information 4 44 Administrative Products for DB2 Installation Guide Verifying the Installation of the MVS Server Verifying the Installation of the MVS Server Summary This section describes the steps that you must perform to verify the installation Step 1 Refer to Starting and Configuring the Client on page 9 18 to start and configure the client Step 2 If necessary follow the procedure in the online Help BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 45 Verifying the Installation of the MVS Server BMC Software Inc Confidential and Proprietary Information 4 46 Administrative Products for DB2 Installation Guide Chapter 5 Installing ALTER This chapter presents the following topic
356. stomer Company Name BMC Customer Start Menu Program Folder PATROL DB Admin Client 05390 Directory Default value is c Program Files BMC Software PATROL DB Admin Client 08390 InstallFolder c pdbclient 6 2 01 Step3 From a command prompt change the current drive and directory to the location at which you copied the client images BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 9 Installing a Client Command Line Interface Step 4 Step 5 Run the command line silent setup command setup s This command accepts the following options setup s m filename s indicates silent and m indicates the specification of a MIF filename The m parameter and filename are optional The MIF file indicates the status of the installation successful or unsuccessful It does not have to currently exist Note The order of these options is important Specifying the m option before the s option will not invoke the MIF file Check the status of the installation to determine if it was successful To do so locate the MIF file in the windows temp or winnt temp directory that you specified in Step 4 Note An unsuccessful installation may be due to a shortage of disk space If you did not specify a MIF file check the pdba_out tre file in the windows or winnt directory for specific warning or error messages associated with the installation
357. strative Products through the ISPF panels you do not need to establish a separate prdDOPD1 module on each DB2 SSID for each product However establishing separate default processing options for each DB2 SSID may be more convenient to minimize key strokes for example The exceptions are the graphical user interface GUI for ALTER and CHANGE MANAGER which use the SSID value in the DOPTs to know to which SSID to connect prdDOPD1 Options Module The job that assembles and links the installation DOPTs module is named xnnDOPT in the JCL data set that the Install System uses to install the product HLQ INSTALL JCL A copy of a stand alone DOPTs job is placed in the HLQ CNTL library When run this job creates a DOPTs module in the products load library The default name of the DOPTs stand alone job and module is prdDOPD1 where prd is the three letter product code ALU for ALTER ACT for CATALOG MANAGER e ACM for CHANGE MANAGER e ASU for DASD MANAGER PLUS BMC Software Inc Confidential and Proprietary Information 3 16 Administrative Products for DB2 Installation Guide Using Catalog Indirection You can change this name in the Install System panels Keep track of any name changes that you make Single Options Module If the DB2 subsystems are using the same product load library they may optionally share the same options load module in that library If you generate only one options module for the load library user
358. synonym qualifiers database names creator names and collection names The default values for these names are listed in Table 7 1 In these default values v indicates the version r indicates the release m indicates the maintenance level and c is a character value indicating the DB2 version where B indicates version 3 1 C indicates version 4 1 D indicates version 5 1 and E indicates version 6 1 or later Table 7 1 CHANGE MANAGER Installation Default Values Part 1 of 2 Installation Default ACMDOPD1 ACMvrmcD Default Options Module Synonym Qualifier BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 5 Installation Considerations Table 7 1 CHANGE MANAGER Installation Default Values Part 2 of 2 Installation Default Value Database Name BMCCMvre Creator Name BMCCMvrc Collection Name ACMvrmc_D_MAIN Server Main Collection Name ACVvrm_D_MAIN Using INFOBMC in the Compare Component The CHANGE MANAGER product s Compare component has the capability to use the INFOBMC command if the DASD MANAGER PLUS product is also installed The INFOBMC command gathers and displays DB2 and DASD MANAGER PLUS statistics in Change Definition Language CDL This feature is available if e you are installing CHANGE MANAGER and DASD MANAGER PLUS simultaneously e you have already installed DASD MANAGER PLUS and choose to activate the interfaces Alternati
359. t Figure 4 14 on page 4 24 shows an example of an INI ACV member BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 23 Configuring TCP IP Figure 4 14 Example of INI ACV Member Server INI file used by ALTER for DB2 sbi sbi sbi sbi sbi VS VS VS VS VS VS VS VS VS VS VS VS VS VS VS VS VS VS VS JSI FORI SCR JISI J T JESSID J JISI J JSI S DBS CP CP DBS MaxAge DBS MAXADD DBS AutoSt DBS Server DB2 Access SPD Access JZS Access FILE Acces TCP Server TCP Operat 037 nts 16 R 16 art 1 1 MVSTCP Driver SBIDB2M Driver SBISPDM Driver SBIJZSM sDriver ACVFILM Enabled 1 ingMode SERVER TCP LocalMethod MultiplexSVP TCP Access TCP Protoc TCP lanada Driver SBIRTMM olDriver SBITCPM pter 0 TCP client TCP server TCP protoc TCP servic TCP packet TCP receiv ol tcp TCPIP Port address assigned to Server e 1313 Packet size must be at least 8192 size 8192 timeout 0 TCP transmitttimeout 0 TCP SASDeb TCP HPNS SISSID SIDDL 0 POOLBYOW EGROUND ST LPT FLUE ug 0 1 JSIl ES2 0 NER 0 ARTEDPROC BMCAKMFG BMCADMN V621 D62 SCRIPT SECTION DOPTS DOPTS BY SSID NICKNAME ST_1 DOPTS DB25_DIRECT BMCADMN V621 D62 LOAD ALUDOPD1 4 24 At the bottom of the INIFACV
360. t Options 004 3 16 Single and Multiple Installation Default Modules 3 16 Using Catalog Indirection LL 3 17 Considerations for Using a Copy of the Catalog 3 19 Considerations for Using Views of the Catalog 3 20 Implementing Catalog Indirection LL 3 20 Creating Collection Names for Multiple Indirect Catalogs 3 22 Post Installation Considerations for Catalog Indirection 3 23 Naming Conventions LL 3 23 Upgrading ALTER to CHANGE MANAGER 3 27 Migrating Data From ALTER to CHANGE MANAGER 3 28 BMC Software Inc Confidential and Proprietary Information vi Administrative Products for DB2 Installation Guide Chapter 4 Chapter 5 Chapter 6 Maintaining BMC Software Administrative Products 3 30 Migrating from DB2 Version 5 to Version 6 3 30 Migrating from DB2 Version 4 to Version 5 3 35 Post Installation Tasks LL 3 40 Performing Post Installation Tasks Performance Considerations 0 0 0 cece cece eee eee 4 2 Adding Products to the BMCDB2PR Panel 4 2 Performing the Post Installation Tasks for Administrative Products 4 3 Enabling the Product CLISTs 0 0 0 02 e eee eee 4 4 Compiling SLIBS eco cus oe etree ey die he one See ao 4 14 Assembling the Modifications to the DOPTs 4 16 Binding the P
361. t set AUTHSW B use the sample security exit ALUEUSX1 to avoid the security exposure Determines whether the BMC Software LOADPLUS utility updates catalog Statistics for the BMCSTATS utility tables during loads for DB2 Version 4 1 or earlier Y or N BMC Software Inc Confidential and Proprietary Information Chapter 5 Installing ALTER 5 13 Default Option Descriptions BLDCU N BMCCHECK N BMCCOPY N BMCLOAD N BMCSTATS N BMCUNLD N BPOOLIX BP0 BPOOLTS BP0 CATAUDIT N Determines whether the BMC Software LOADPLUS utility updates statistics in the DB2 catalog during loads for DB2 Version 4 1 or earlier Y or N Specifies whether to use the BMC Software CHECK PLUS utility in place of the IBM CHECK DATA utility for checking referential constraint violations in DB2 table spaces Y or N Specifies whether to use the BMC Software COPY PLUS utility in place of the IBM COPY utility The DOPTs parameters are defined as follows Use BMCCOPY Use IBMCOPY Do not include copy operations Do not include copy operations but do start objects in copy pending status with ACCESS FORCE 7x ZK Indicates whether to use the BMC Software LOADPLUS utility for loads in place of the IBM LOAD utility Y or N Indicates whether to use the BMC Software BMCSTATS utility for updating statistics in the DB2 catalog in place of the IBM RUNSTATS utility DB2 Version 4 1 or earlier The DOPTs parameters are defined as follows
362. ta set allocation time to define the processing requirements of the data set WSC will appear as STORCLAS in the JCL for non tape workfiles Defines the default work data set secondary space allocation Defines the default work data set unit Post Installation Considerations After installation refer to Chapter 4 Performing Post Installation Tasks for information about how to perform post installation tasks for CHANGE MANAGER To perform any additional post installation tasks or to set up CHANGE MANAGER refer to the ALTER and CHANGE MANAGER for DB2 User Guide BMC Software Inc Confidential and Proprietary Information 7 32 Administrative Products for DB2 Installation Guide Chapter 8 Installing DASD MANAGER PLUS This chapter presents the following topics OVENI EW oo ore Siete ea Mio eames DA le eWay ee age 8 2 Installation Considerations 00 0 ee 8 3 Installation Defaults 0 0 0 0 ee c eee 8 3 Implementing the QMF Report Feature 8 4 Controlling ACCESS ii irc ni ad ak ead hs Geta wea ode 8 5 DASD MANAGER PLUS Plans 8 5 DASD MANAGER PLUS Execution Plans 8 6 Interacting with Other BMC Software Products 8 7 Default Option Listing DOPTS LL 8 7 Default Option Descriptions 0 0 cece eee eee 8 9 Post Installation Considerations 0 LL 8 14 BMC Software Inc Confidential and Proprietary Information
363. tall System Step 1 Starting the Install System When the BMC Software products run the owner of the synonyms is obtained from the QUALIFIER value of the processing plan When the owner is known the object to which the synonym applies is also known When you specify a synonym qualifier e Select NEW status if the qualifier is currently not in use by any other BMC Software product in the target DB2 subsystem e Select USED REUSE status if the BMC Software product is currently using the qualifier but this usage can be replaced For example if you previously installed a BMC Software product with a qualifier of ALU33D and want to install a new release of the same product using the same qualifier ALU33D select USED REUSE Synonyms referencing the old environment are dropped so that synonyms referencing the new environment can be created Warning Reusing existing qualifiers invalidates processing of the product release that is already installed In the TSO Commands Utility panel type the following command EX HLQ INSTALL DCIINSTL HLQ For example the following command uses the high level qualifier BMC DCI EX BMC DCLINSTALL DCIINSTL BMC DCI The Install System displays the Load Library Specification panel see Figure 2 3 on page 2 12 BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 11 Starting the Install System 2 12 Figure 2 3 Install System Load Library Sp
364. tallation uses a separate library for exits and non IBM modules such as EDITPROCs or FIELDPROCs type the name of this second library in ULL2 The name of the LOADPLUS product s load library The name of the utilities plan The SQL Explorer load library If you are installing SQL Explorer together with CATALOG MANAGER type the name of its load library Otherwise comment out the library name URDSP amp amp PREFIX SYSREC URSTP USCPR 10 USCSE 2 USDEV SYSDA USERAUT STATIC USERNAM STATIC USRPR 10 USRSE 2 USRUN SYSDA USWPR 10 USWSE 2 The prefix to be used with the last qualifier of SYSREnnn data sets The name of the REORG PLUS product s load library If you are installing REORG PLUS together with CATALOG MANAGER type the name of the REORG PLUS load library Otherwise comment out the library name The size of the SYSCOPY primary space The size of the SYSCOPY secondary space The name of the sort device type Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM SYSUSERAUTH DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table Specifies whether CATALOG MANAGER uses static SQL or dynamic SQL to access the SYSIBM USERNAMES DB catalog table The default STATIC uses the privileges of the package owner DYNAMIC uses the privileges of the person who is listing the table The
365. tarting client 9 18 Install System 2 10 starting over 1 9 STATAUTH DOPT 8 12 STATS DOPT 5 21 7 29 status USED REUSED 2 11 STMT DOPT 6 20 STOGROU DOPT 6 20 STOPCOMM DOPT 5 21 7 29 stopping client 9 18 Storage Management System classes 2 20 STORCLAS DOPT 5 21 7 29 STRINGS DOPT 6 20 subsystem connections creating 9 18 subtasking 4 39 SWPS DOPT 5 21 7 29 8 12 SWSS DOPT 5 21 7 29 8 12 SWU DOPT 5 21 7 29 8 12 symbols in passwords A 4 SYNCPNT DOPT 5 21 7 29 SYNONYM DOPT 6 20 synonym qualifier Full installation path 2 10 naming conventions 3 23 syntax statement conventions xx SYSADM authorization 1 4 SYSCMAX DOPT 5 21 7 30 8 13 SYSCMAXU DOPT 5 21 7 30 8 13 SYSCPREF DOPT 5 21 7 30 8 13 SYSCPS DOPT 5 21 7 30 8 13 SYSCSS DOPT 5 21 7 30 8 13 SYSCUNIT DOPT 5 22 7 30 8 13 Sysplex 1 11 4 7 SYSRMAX DOPT 5 22 7 30 8 13 SYSRMAXU DOPT 5 22 7 30 8 13 SYSRPREF DOPT 5 22 7 30 8 13 SYSRPS DOPT 5 22 7 30 8 13 SYSRSS DOPT 5 22 7 30 8 13 SYSRUNIT DOPT 5 22 7 30 8 13 SYSTYPE DOPT 5 22 7 30 8 13 SZDEV DOPT 6 20 SZDEVT DOPT 5 22 7 30 8 13 18 Administrative Products for DB2 Installation Guide T TABAUTH DOPT 6 20 table space ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 TABLEACC DOPT 5 22 7 30 TABLEALL DOPT 5 22 7 31 TABLEPA DOPT 6 21 TABLES DOPT 6 21 TABLESP DOPT 6 21 TABSTAT DOPT 6 21 tape unloading Install System 2 6 TAPE1 DOPT 5 22 6 21 7 31 8 13 TAPE2 DOPT 5
366. tarting and Configuring the Client LL 9 18 Starting the Client 9 18 Configuring the Client L LL 9 18 Where to Go From Here 2 0 0 cee eee eee 9 19 Appendix A BMC Software Product Authorization OVELVICW icc vi treed Sod Speciale Mie ini LO AN eit ts OM ed A 2 Product Authorization Tables A 3 Problem Regarding Product Authorization Table Installation A 3 Product Authorization Passwords 0 0 00 ee ee ee eee A 4 Permanent Passwords 0 0 c eee cece eee ee eee A 4 Temporary Passwords 0 0c eee eee ee eens A 5 How to Apply Passwords L LL A 5 How Products Are Licensed A 5 Product Trials and Permanent Licensing A 6 CPU parades i ates can weg seks ane alta Sea edge Sew nae A 6 CPU Fail reS psoriasi a ai des ee boyd odes A 6 Product Maintenance or Version Upgrades A 8 How to Obtain Passwords 2 0 cece cee eee A 9 CPU Information iii ara ide eisai Mined Ss A 10 Online Product Authorization 0 0 cece eee eee eee A 10 Processing a Permanent Password LL A 11 Adding Authorization for a Processor A 13 Deleting Authorization for a Processor A 15 Replacing Authorization for a Processor A 17 Modifying Authorization for an Existing Processor A 19 Resetting Authorization for all Processors A 22 Processing a Tempor
367. ted If they are not set the BMCDB2C variable in the BMCDB2 CLIST to the correct library Exit the CONTAB panel Type TSO BMCMSG BMCnnnnn on the command line where nnnnn is a valid message number for example BMC45680 Verify that a message is displayed Press F3 to exit the BMCMSG CLIST Select one of the products that you installed At the main menu for the Administrative Products type ENVI on the command line Note For DASD MANAGER PLUS select the environment option Review the environment panel to verify the displayed information Exit the ENVI panel Repeat Step 4 through Step 6 for each product that you installed Note If you are installing CATALOG MANAGER and are using the Distributed Data Facility DDF enter CONNECT on the command line from CATALOG MANAGER The CATALOG MANAGER Connect panel appears Then verify connections or attachments to other DB2 subsystems BMC Software Inc Confidential and Proprietary Information 4 20 Administrative Products for DB2 Installation Guide Using Fast Path Navigation Using Fast Path Navigation For Administrative Products the Install System provides Fast Path Navigation which enables you to switch from one product to another without leaving the current product To initiate Fast Path Navigation enter the name of the product that you want to switch to on the Command line of the current product Refer to Table 4 2 for a list of the products and commands T
368. ted in Unloading the Install System on page 2 6 e Start the Install System as instructed in Starting the Install System on page 2 10 e Specify the user options as instructed in Specifying User Options on page 2 19 To Generate the Installation JCL Step 1 Step 2 From the Install System Main Menu type 1 in the selection field and press Enter In the Product Selection panel choose the products that you want to install and the installation path for each product The Product Selection panel lists all of the products available in the installation data set that you created when you unloaded the Install System from the distribution tape For more information about selecting the right installation path see Installation Paths on page 1 10 BMC Software Inc Confidential and Proprietary Information 2 22 Administrative Products for DB2 Installation Guide Generating Installation JCL Step 3 Press Enter to continue The Install System presents a series of panels that let you specify environmental options for the installation and default options for each product you chose in Step 2 Use the information that you gathered before you began this procedure to complete the fields in the panels For more information about default options see the appropriate product chapter To move through the panels use the keys described in Keys and Commands on page 2 14 Step 4 Review your installation choices If
369. ter for DB2 ALP OPERTUNE for DB2 DDT e OPERTUNE for MQSeries DDM PACLOG for DB2 ALM RECOVERY MANAGER for DB2 ARM RECOVERY MANAGER for OS 390 MRM BMC Software Inc Confidential and Proprietary Information 4 2 Administrative Products for DB2 Installation Guide Performing the Post Installation Tasks for Administrative Products After you copy the UPDTBMC CLIST and the UPDTDB2 macro from the ALQ INSTALL library to your TSO USERID CLIST library or a linklisted CLIST library you can execute the CLIST by typing TSO UPDTBMC on the command line You will need to know the location of the BMCDB2PR panel and the above product s CLIST as well as the above product s code Performing the Post Installation Tasks for Administrative Products After you complete the installation procedure for the Administrative Products you must perform the following tasks e Enable the product CLISTs e Compile SLIBs e Assemble the modifications to the default processing options DOPTs e Bind the Administrative Products packages and plans e Verify the Product Authorization e Invoke the BMCDB2 CLIST e Verify the installation To perform post installation tasks for the MVS Server for the Database Administration products see Performing the Post Installation Tasks for the MVS Server on page 4 22 BMC Software Inc Confidential and Proprietary Information Chapter 4 Performing Post Installation Tasks 4 3
370. the BMC Software Install System This installation guide provides documentation for the following products e ALTER for DB2 version 5 4 01 e CATALOG MANAGER for DB2 version 5 4 01 e CHANGE MANAGER for DB2 version 5 4 01 e CM PILOT for DB2 version 5 4 01 e DASD MANAGER PLUS for DB2 version 5 4 01 e PATROL DB Alter for DB2 version 2 2 07 e PATROL DB Change Manager for DB2 for MVS version 2 2 07 e PATROL DB Voyager for DB2 version 2 2 07 e SQL Explorer for DB2 version 2 2 07 BMC Software Inc Confidential and Proprietary Information Summary of Changes xxvii BMC Software Inc Confidential and Proprietary Information xxviii Administrative Products for DB2 Installation Guide Chapter 1 Preparing for Installation This chapter presents the following topics OVETVIEW ic Lol iadale wet aoe ee odes ceo Sa da Ae e A 1 2 Distribution Methods 0 0 cece eee eee ee eee 1 2 Administrative Products Tapes 0 2 0 0 cee eee eee 1 2 TIS Tape eli ieri Lai aS Seid Lee i Bee 1 3 SAT Tape blue Bibi ioni e Maren e cane 1 3 Installation Requirements 1 3 Authorization to Run the Installation Batch Jobs 1 4 Estimated Space Requirements 1 4 ALTER Space Estimates ot EE E ee nee 1 5 CATALOG MANAGER Space Estimates 1 6 CHANGE MANAGER Space Estimates 0 1 7 DASD MANAGER PLUS Space Estimates 1 8 Understanding the Install System 1
371. the Modifications to the DOPTs Assembling the Modifications to the DOPTs Summary You can specify generation data groups GDGs by adding the amp amp GDG symbolic variable to the SYSCOPY and SYSRECV DOPTs parameters As a result the data set names are resolved using the symbolic variables and include the GDG Step 1 Inthe product s DOPTs module specify the symbolic amp amp GDG at the end of the DOPTs listed in Table 4 1 Table 4 1 SYSCOPY and SYSRECV DOPTs Product DOPTs CATALOG MANAGER UCDSP UVDSP ALTER SYSCPREF CHANGE MANAGER RECVPREF DASD MANAGER PLUS For example type amp amp PREFIX amp amp SSID amp amp OBNOD amp amp GDG Step 2 Use the installation job xnnDOPT to assemble these changes to the DOPTs BMC Software Inc Confidential and Proprietary Information 4 16 Administrative Products for DB2 Installation Guide Binding the Packages and Plans for Shared Components Binding the Packages and Plans for Shared Components The Install System is designed to allow you to install more than one Administrative Product simultaneously However you can install Administrative Products at different times If you install the products at different times and any of the products share the same APF authorized load library you need to bind the products for the shared JCL Generation and Execution Monitor components To bind the products complete the steps in Upgrading Shared Components on pa
372. the default primary space allocation for sort work in cylinders Defines the default secondary space allocation for sort work in cylinders Describes the sort work unit Creates additional SYNC commands in a worklist based on the number of SQL commands since the last SYNC command The variable parm specifies the maximum number of SQL commands that can be in the worklist before a SYNC command is created The option also places an additional SYNC command before the next SQL command Valid values for parm are from 0 to 99 Any SYNC command in the worklist resets the count of SQL commands to zero SYNC commands that this keyword generates are in addition to the SYNC commands that Analysis automatically generates BMC Software Inc Confidential and Proprietary Information Chapter 7 Installing CHANGE MANAGER 7 29 Default Option Descriptions SYSCMAX SYSCMAXU The SYSCOPY threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The SYSCOPY secondary or alternate unit that is used for any overflow SYSCPREF amp amp PREFIX amp amp SSID amp amp OBNOD SYSCPS 10 SYSCSS 2 SYSCUNIT SYSDA SYSRMAX SYSRMAXU Defines the default SYSCOPY data set prefix The amp amp OBNOD symbolic variable resolves to database amp SPNAME amp SPNAME resolves t
373. the selection field and retry the action BMC Software Inc Confidential and Proprietary Information Appendix B BMC Software Product Authorization Messages B 5 Error Messages BMC89012E BMC89013E BMC89019E BMC89021E OPTION IS REQUIRED VALID VALUES ARE 1 2 OR 3 Explanation No menu option has been specified System Action All functions are suppressed User Response Type a valid option number in the selection field and retry the action lt command gt IS NOT A VALID COMMAND Explanation The specified command is invalid System Action The command fails User Response Correct the command or remove the command from the command line YOU MAY VIEW PRODUCT AUTHORIZATION FOR THIS PRODUCT FROM ONLY ONE LOGICAL SCREEN AT A TIME Explanation Product Authorization is being displayed on another panel System Action Product Authorization is not displayed on this panel User Response Use the panel currently displaying Product Authorization or cancel that panel and resubmit the job on this one ERROR DURING DYNAMIC ALLOCATION LOAD LIBRARY WAS NOT ALLOCATED ERROR CODE lt code gt INFO CODE lt code gt DDNAME SYSLIB Explanation The product authorization interface and the Product Authorization utility were unable to dynamically allocate the product load library The error codes and information codes returned by the DYNALLOC macro are described in the Authorized Assembler Programming Guide and in the appendi
374. them Note To avoid the possibility of overwriting your production data sets and libraries BMC Software recommends that you review your installation variables before generating installation JCL Step9 Choose an entry field delimiter If your display terminal supports the extended highlighting feature you can change the default entry field delimiter from NONE to USCORE underscore or REVERSE reverse video Step 10 Press Enter to save your changes and return to the Install System Main Menu BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 21 Generating Installation JCL Generating Installation JCL Summary Before You Begin After you define the user options you are ready to generate installation batch jobs for the BMC Software products that you choose to install This procedure helps you navigate through the Install System s panels For information about a specific product see the appropriate product chapter Before you use the Install System to generate the installation JCL complete the following tasks e Gather the information that you will need when specifying the product and environment options for the installation For more information about these options see the appropriate product chapters Refer also to Chapter 3 Performing Additional Installation Tasks and Install System for MVS Related Products Helpful Tips e Unload the Install System as instruc
375. tion 2 12 Install System Main Menu 0 0 cece ee eee eee 2 13 Sample Installation Batch Jobs LL 2 27 Sample BMCDB2 CLIST 0 0 0 cee eee eee 3 15 BMCDB2 CLIST Control Table 0 0 0 0 00 0000 4 5 Setting the GENTABLE Variable in the BMCDB2 CLIST 4 6 Adding CHANGE MANAGER to the Control Table 4 6 Specifying the Location of CHANGE MANAGER Libraries 4 6 Enabling Access to Additional Members 4 7 CATALOG MANAGER CONNECT Command Servers 4 7 BMCDB2 CLIST for Multiple SSID Installation 4 8 BMCDB2PR Panel i agate eee eee keith ag oR Se oe 4 8 Adding CHANGE MANAGER to Subsystem DB31 4 9 Adding CHANGE MANAGER to Subsystem DB41 4 10 Running DB41 Administrative Products from the DB31 BMCDB2 CLIST 4 10 Updated BMCDB2 CLIST secin eiia nyse eee eee eee 4 11 Adding the Profile Name or the Initial Command 4 12 Example of INIFACV Member 4 24 Connection Wizard Screen 4 25 ISPE Edit Panel iraniane pe ile iti 4 26 Sample Logon Mode Definition 4 31 Sample Local LU Definition for VTAM L 4 32 Sample Local LU Definition for APPC MVS 4 33 Sample APPC for MVS Configuration File 4 34 Sample APPC LU Definition for an SNA Gateway Server 4 37 ALTER Default Options Listing Part 1 of 3 LL 5
376. tion 7 22 Administrative Products for DB2 Installation Guide Default Option Descriptions CPLDIAG SYSOUT These DOPTs control the input keywords to Analysis as follows e Local copy parameters parms for the COPYDDN keyword can be COPY01 and COPY02 separated by commas or blanks e Remote copy parameters parms for the COPYDDN keyword can be RECVOI and RECV02 separated by commas or blanks The default name for the CM PILOT component s diagnostic output data set name CPLWDSN amp amp PREFIX amp amp SSID amp amp TASKID DASDMAN Y DATACLAS N DATE amp SYSDATC The default worklist data set name for a new TASKID used in the CM PILOT component The products dynamically allocate the data sets the first time that they are used This data set name can be overridden on the Analysis Interface panel This data set can be either a sequential file or a partitioned data set PDS Indicates whether version 5 1 or later of DASD MANAGER PLUS is installed Y or N ALTER and CHANGE MANAGER select DB2 catalog statistics for space estimation When DASDMAN Y any statistics from the BMCSTATS tables will be merged Indicates whether support for the DATACLAS parameter is required for VCAT defined DB2 objects Y or N This parameter is used only if you have ASMA90 as your assembler DB2CAT or DB2CT DBDBCAT The VSAM CATALOG alias that contains the data sets of the DB2 catalog DBRM1 DBRM2 DBRM3 DBRMLIB N DE
377. tion Guide Installing a Client Command Line Interface Installing a Client Command Line Interface Summary This procedure describes how to install the client by using the command line interface The setup command line interface is provided as a consistent and faster means to install the client To use the command line interface you must first edit the initialization file to make product selections and to specify directory locations for the files After you complete this task you can use this initialization file for every installation in your organization This type of installation ensures that all users connected to a network install the same set of products by entering a single command Step 1 Copy the client images to your hard drive or to a shared network drive The client images are located in the client directory Step 2 Modify the PDB_Install ini file to make product and directory selections When editing the file specify 0 to disable a selection and specify 1 to enable a selection The only requirement when editing this file is that you must select a product in the Selections section Figure 9 1 shows an example PDB_Install ini file In this example the user selected the CHANGE MANAGER product and specified c pdbclient 6 2 01 as the installation folder Figure 9 1 Modifying the PDB_Install ini File Client Installation Selections CHANGE MANAGER for DB2 MVS 1 ALTER for DB2 MVS 0 Information User Name BMC Cu
378. tion to the GLID BMC Software Inc Confidential and Proprietary Information 7 24 Administrative Products for DB2 Installation Guide Default Option Descriptions HSMVOL vol Specifies the volume ID that indicates an archived data set if you are using a disk management system If this volume ID is encountered ALTER or CHANGE MANAGER uses a template of default values for data set allocation IMP CMyrmcDI Defines the Import plan name IMPDIAG SYSOUT Defines the default name for the Import diagnostic output data set ISPSLIB This value is used by the GUI for CHANGE MANAGER for JCL generation IXTYPE 2 For DB2 Versions 4 and 5 the default Index type that ALTER and CHANGE MANAGER use when no type is specified on a create index command 1 Type 1 index 2 Type 2 index DB2 Version 4 and later JC1 amp amp USERID amp amp JOBCHAR JOB ACCT amp amp PGMR JC2 CLASS A MSGCLASS X MSGLEVEL 1 1 JC3 NOTIFY amp amp USERID JC4 JC5 Defines the jobcard that the Front End uses when generating JCL Symbolic variables can be used and are described in the Symbolic Variable appendix of the respective products reference manuals JCLCLEAN N Enables you to generate a job step that automatically deletes many of the permanent also known as non temporary data sets that the Execution component creates These data sets are created during worklist processing and have a disposition NEW CATLG CATLG The automat
379. tions ACTvrmDH Utility Status Display This plan enables display of BMC Software utilities status Grant EXECUTE authority on this plan to users who should be able to display or terminate BMC Software utilities ACTvrmDK Command Generation and Execution Grant EXECUTE authority on this plan to users who should be able to issue DB2 operator commands such as START STOP DISPLAY and TERM BMC Software Inc Confidential and Proprietary Information Chapter 6 Installing CATALOG MANAGER 6 5 Default Option Listing DOPTs ACTvrmDL Log Table Maintenance Grant EXECUTE authority on this plan to users who are responsible for administering CATALOG MANAGER This plan includes authority to browse and archive rows in the CATALOG MANAGER Audit Session and Drop Recovery logs ACTvrmDM Display DB2 Catalog and SQL Information This plan allows the minimum access that is required to use CATALOG MANAGER It displays DB2 catalog and SQL generation and execution information ACTvrmDU Grant Authorities and Submit BMC Software Utilities or DB2 Utilities This plan enables generation and submission of JCL for BMC Software utilities and DB2 utilities Grant EXECUTE authority on this plan to users who should be able to grant authorities or submit DB2 or BMC Software utilities Default Option Listing DOPTs 6 6 This section provides an example of the default options DOPTs module listing for CATALOG MANAGER see Figure 6 1 on page
380. tive Products for DB2 Installation Guide Processing a Temporary Password Processing a Temporary Password Summary Use the Product Authorization Primary Menu to process a temporary password Step 1 On the Product Authorization Primary Menu Figure A 1 on page A 11 select option 1 Step 2 At Product load library type a fully qualified data set name and press Tab Step3 At Authorization password type your temporary password and press Enter A pop up message explains that the product authorization table was built or updated successfully Figure A 11 Figure A 11 Product Authorization Temporary Password Message SECEPPRI lt product name gt Product Authorization Primary Menu COMMAND gt Select an option Type additional information if applicable Then press Enter Options _ 1 Process password Requires product load library and password 2 Display product authorization Requires product load library only 3 Display current processor information 4 Help about 5 Exit Additional information Product load library BMC PRODUCT LOAD Authorization password BMC89110I PRODUCT AUTHORIZATION TABLE WAS SUCCESSFULLY BUILT UPDATED YOU ARE NOW AUTHORIZED TO EXECUTE THIS PRODUCT ON ANY PROCESSOR UNTIL 11 26 1999 PRESS ENTER TO CONTINUE F1 Help F2 Split F3 E 777 5 A A A A A A a 1 Step 4 Press F3 to exit the Product Authorization utility and return to the previous menu or panel
381. to access the DB2 catalog directly After the installation you can use the Install System to implement and maintain catalog indirection e You can use the same copy or view of the catalog for all Administrative Products or you can implement catalog indirection through separate copies or views for each product e Catalog indirection can provide either of two benefits reducing contention for the DB2 catalog or providing an additional level of security for sensitive data in the catalog The following sections provide details Note Although you can implement a view of a copy of the catalog and simultaneously reap both benefits of catalog indirection this approach is extremely complex to maintain and is not recommended Reducing Catalog Contention For data centers that have high DB2 transaction rates contention for the DB2 catalog can be a problem Because the Administrative Products require frequent access to the DB2 catalog they can contribute to catalog contention BMC Software Inc Confidential and Proprietary Information 3 18 Administrative Products for DB2 Installation Guide Using Catalog Indirection When you direct the information queries from specific groups of users to a recent copy of the DB2 catalog the Administrative Products can reduce catalog contention The products also perform better because they do not have to compete with other applications for DB2 catalog information The copy of the catalog can be tuned to
382. ts as follows Ifthe xnnDOPT member is a text options file the Install System copies it to the CNTL data set e Ifthe xnnDOPT member is an assembled options module the Install System generates it into the APF authorized library that you specify during the installation process BMC Software Inc Confidential and Proprietary Information 1 20 Administrative Products for DB2 Installation Guide Rules for Running Multiple Product Releases in a Single Subsystem If you modify any of the values in member xnnDOPT after installation you must rerun the xnnDOPT job for these changes to occur You can also modify the options for a specific product by editing and running the stand alone options job for that product in the product library The name of the options job for each product varies depending on the type of product that you are installing For more information about DOPTs for a specific product see the appropriate product chapter in this book Rules for Running Multiple Product Releases in a Single Subsystem You may need to perform acceptance testing on a new release before you can upgrade it to production To facilitate this requirement you can run multiple releases of some BMC Software products within a single DB2 subsystem If you plan to use the Full installation path to install multiple releases of the BMC Software products follow these rules e Use a unique high level qualifier HLQ that is different from the qualifier
383. tware SQL Explorer for DB2 product e availability of installation guide in HTML format e disuse of the ACVDOPTS DOPTs module e modification of BIND packages and plans e use of SYS1 MODGEN library by a I40INST job during a System Modification Program SMP installation of MVS e default value of the MVSTCP HPNS variable defined as high performance native sockets e DB2 Version 3 no longer supported BMC Software Inc Confidential and Proprietary Information Summary of Changes xxi Version 1 6 90 September 29 2000 This installation guide provides support for the BMC Software Install System for the ISPF products and for the graphical user interface GUI client CD Enhancements for version 1 6 90 include e distribution of the GUI for the BMC Software ALTER CHANGE MANAGER and SQL Explorer products on the Administrative Products for DB2 for OS 390 product CD e the inclusion of information about installing the GUI in this installation guide e the addition of the data editor plan with the default name of ACTvrmDE for the CATALOG MANAGER product e the addition of the DOPCP DOPRP DOPVP DOPLP DOPUP DOPKP NOWRK and EPLAN parameters to the default options module for CATALOG MANAGER e the addition of the DEFERUIX parameter to the default options module for ALTER and CHANGE MANAGER e the addition of support for the DB2 Version 5 installation of the JDSNBG parameter to the default options module for ALTER and CHANGE MA
384. u can also reuse Task IDs for change management jobs that you run repeatedly CM PILOT Applications CM PILOT Worklists You can associate a group of CHANGE MANAGER profiles that will be used repeatedly for the change management tasks of a specific DB2 application This feature is called a CM PILOT Application You can also define a Work ID name template in a CM PILOT Application which lets you standardize naming conventions for CHANGE MANAGER Work IDs that CM PILOT creates There is no limit to the number of Task IDs that can use a CM PILOT Application A CM PILOT worklist which contains commands for CHANGE MANAGER components is created when you execute a Task ID The worklist passes the information that you provide through the CM PILOT dialog The JCL for processing the CM PILOT worklist can also be created for you at the same time The successful processing of a CM PILOT worklist results in the creation of a CHANGE MANAGER worklist along with the associated CHANGE MANAGER Execution JCL to process it You can then submit the Execution JCL for CHANGE MANAGER worklist processing whenever you like thereby allowing you to schedule the jobs that actually perform the data structure changes and migrations Actual data structure changes and migrations occur only when the CHANGE MANAGER worklist is processed BMC Software Inc Confidential and Proprietary Information 7 4 Administrative Products for DB2 Installation Guide Diagnostics
385. u use a subsystem connection to specify the details for that connection For DB2 for OS 390 connections the subsystem connection specifies which Database Administration product host DB2 subsystem and TSO user ID to use during that connection BMC Software Inc Confidential and Proprietary Information 9 18 Administrative Products for DB2 Installation Guide Starting and Configuring the Client If you plan to connect to different combinations of Database Administration products hosts and databases you should create a separate connection profile for each possible combination The name of the subsystem connection must be unique even though multiple connections may use the same host Note Client configuration is not necessarily a one time activity At some point in the future you may need to modify your hosts or subsystem connections Use the Connection Manager any time that you need to add or change a host or subsystem connection See the Help for complete instructions on defining hosts and creating subsystem connections Where to Go From Here After configuring the client you are ready to connect to a database and begin using the product To use the product see the ALTER and CHANGE MANAGER for DB2 User Guide or each product s online Help for more information BMC Software Inc Confidential and Proprietary Information Chapter 9 Installing the Client for ALTER and CHANGE MANAGER 9 19 Starting and Configuring the Client
386. uct S Issue the SQL LOCK TABLE IN SHARE MODE statement X Issue the SQL LOCK TABLE IN EXCLUSIVE MODE statement N Do not issue SQL LOCK TABLE statements LOG N Specifies that records be logged during loads that use the IBM LOAD utility YorN BMC Software Inc Confidential and Proprietary Information 7 26 Administrative Products for DB2 Installation Guide MGMTCLAS N PC ACM PIC N Default Option Descriptions Indicates whether support for the MGMTCLAS parameter is required for VCAT defined DB2 objects Y or N Defines the product code to the CHANGE MANAGER components Pre Image Copy Indicates whether an image copy should be taken of each table space before a database is dropped a table is dropped or the table space is dropped or reorganized Y or N PRODUCT PRODUCT NAME REBLD I RECOV I RECVMAX RECVMAXU Defines the product name For example PRODUCT CHANGE MANAGER For DB2 Version 6 and later specifies whether to use the rebuild utility from IBM or BMC Software or no rebuild utility If REBLD N eligible indexes will not be created with DEFER YES If a non unique index is being dropped or created in a worklist and its parent table is not being dropped or created in the worklist then the index will be created with DEFER YES if REBLD I or REBLD B The DOPTs parameters are defined as follows B BMCRECOVER I IBMREBUILD N NO REBUILD For DB2 Version 5 and earlier specifies whether to use th
387. uent Maintenance 3 3 Upgrading Shared Components 3 4 Interacting with Other BMC Software Products 3 6 ALTER and CHANGE MANAGER 3 6 CATALOG MANAGER 3 7 DASD MANAGER PLUS 3 9 SQL Explorer with DASD MANAGER PLUS 3 11 Refreshing Default Options 0 0 0c eee eee ee eee 3 13 Setting User Options Using DOPTS LL 3 14 Catalog Indirection Default Options LL 3 16 Single and Multiple Installation Default Modules 3 16 Using Catalog Indirection 0 0 0 0 cee eee eee 3 17 Considerations for Using a Copy of the Catalog 3 19 Considerations for Using Views of the Catalog 3 20 Implementing Catalog Indirection L LL 3 20 Creating Collection Names for Multiple Indirect Catalogs 3 22 Post Installation Considerations for Catalog Indirection 3 23 Naming Conventions LL 3 23 Upgrading ALTER to CHANGE MANAGER 3 27 Migrating Data From ALTER to CHANGE MANAGER 3 28 Maintaining BMC Software Administrative Products 3 30 Migrating from DB2 Version 5 to Version 6 3 30 Migrating from DB2 Version 4 to Version 5 3 35 Post Installation Tasks LL 3 40 BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks 3 1 Performing Additional Tasks for Installation Performing Addition
388. ult JOB statement that DASD MANAGER PLUS uses when generating Analysis and Execution JCL Symbolic variables can be used and are covered in the Symbolic Variable appendix of the respective products reference manuals JDSNE amp amp PREFIX EXEC amp amp WKID JPLAN ASUvrmDJ LOCATION OPNDB2ID Y Defines the default data set name that is used for Execution JCL This data set can be either a sequential or partitioned data set A member name is not allowed for a partitioned data set DASD MANAGER PLUS automatically uses the Work ID as the member name The name of the DASD MANAGER PLUS plan that is used for the BMCTRIG utility job generation The local subsystem location If you are using Single Point Entry the parameter is set to SPE METHOD Uses the DB2 authorization ID to update BMCSTATS tables The default option OPNDB2ID Y allows users with STATS authority to collect stats even if their user IDs do not have RACF authority to read the data set Yor N PRODUCT PRODUCT NAME RECVMAX RECVMAXU Defines the product name For example PRODUCT DASD MANAGER The offsite copy threshold in cylinders above which the utility will use the secondary unit for allocation If the size of a data set exceeds the threshold the utility uses the secondary unit To avoid using the secondary unit specify 0 The offsite copy secondary or alternate unit that is used for any overflow RECVPREF amp amp PREFIX amp amp
389. ure 4 13 Figure 4 13 Adding the Profile Name or the Initial Command WHEN ACTEMAIN DO CATALOG MANAGER SET BMCFPCNT 10100 IF amp ACCESS INDIRECT THEN SET CIACCESS YES SET APPLID amp ACTAPPL SET PARM amp STR S amp SSID O amp ACTDOPT D amp ASUDOPTD BC I amp CIACCESS A amp ACMDOPT DB2CAT amp DB2VCAT Add the following lines immediately after the preceding code SET PARM amp STR amp PARM PR PROGRAMMERS SET PARM amp STR amp PARM C DB M BMC Software Inc Confidential and Proprietary Information 4 12 Administrative Products for DB2 Installation Guide Enabling the Product CLISTs The example that is shown causes CATALOG MANAGER to invoke the session profile called PROGRAMMERS The initial entry screen will display a list of databases DB starting with the letter M Step5 Enable the BMCMSG CLIST The Install System generates BMCMSG the BMC Online Message processor BMCMSG is a CLIST that displays information about messages that BMC Software products issue The information includes an explanation of each message and the required user response The BMCMSG CLIST is copied to the product CLIST library during installation This section describes the step that you should perform to enable the processor from anywhere in TSO To enable the CLIST from TSO without having invoked an Administrative Product copy the BMCMSG CLIST from the HLQ INSTALL l
390. uthorization EXECUTE authority on this plan provides a way for users to execute a worklist You should therefore carefully consider who receives authorization to use this plan AEXvrmDM Execution Monitor This plan is used to execute a worklist It will be accessed only if the user has EXECUTE authority on the AEXvrmDA plan Therefore you may grant wide authority PUBLIC to AEXvrmDM BMC Software Inc Confidential and Proprietary Information 8 6 Administrative Products for DB2 Installation Guide Interacting with Other BMC Software Products Interacting with Other BMC Software Products The Install System provides interface capabilities to the BMC Software Utility products for the following BMC Software products e ALTER e CATALOG MANAGER e CHANGE MANAGER e DASD MANAGER PLUS See DASD MANAGER PLUS on page 3 9 for more information about these interface capabilities Default Option Listing DOPTs This section provides an example of the default options DOPTs module listing for DASD MANAGER PLUS see Figure 8 1 on page 8 8 The DOPTs listing is created by the Install System and resides in xnnDOPT The DOPTs listing also resides in HLQ CNTL with the same member name as the DOPTs BMC Software Inc Confidential and Proprietary Information Chapter 8 Installing DASD MANAGER PLUS 8 7 Default Option Listing DOPTs Figure 8 1 DASD MANAGER PLUS Default Options Listing Part 1 of 2 KKKKKKKKKKKKKKKKKKKK
391. uthorization utility batch authorization A 27 online authorization A 10 overview A 2 product codes 3 16 product description ALTER 5 2 CATALOG MANAGER 6 2 CHANGE MANAGER 7 2 DASD MANAGER PLUS 8 2 PRODUCT DOPT 5 19 7 27 8 11 product JCL generating 4 14 product trials A 6 product version 1 12 Q QMFFORM data set DASD MANAGER PLUS dure data set DASD MANAGER PLUS duro data set DASD MANAGER PLUS fai Full installation path 2 10 quick installation 1 10 R RCCOL DOPT 6 19 REBLD DOPT 5 19 7 27 RECOV DOPT 5 19 7 27 RECVDD01 DOPT 5 15 7 22 RECVDD02 DOPT 5 15 7 22 RECVMAX DOPT 5 19 7 27 8 11 BMC Software Inc Confidential and Proprietary Information RECVMAXU DOPT 5 19 7 27 8 11 RECVPREF DOPT 5 19 7 28 8 11 RECVPS DOPT 5 19 7 28 8 12 RECVSS DOPT 5 19 7 28 8 12 RECVUNIT DOPT 5 20 7 28 8 12 refresh unsuccessful 3 13 region statements generating JCL 4 14 reinstalling a product 9 17 related documentation xviii release level determining 1 12 release notes xviii RELS DOPT 6 19 REORG DOPT 5 20 7 28 REPLACE Authorization for a Processor panel A 17 authorization message A 18 requirements client installation 9 3 requirements space ALTER 1 5 CATALOG MANAGER 1 6 CHANGE MANAGER 1 7 DASD MANAGER PLUS 1 8 RESAUTH DOPT 6 19 RESET authorization message A 22 password A 7 product authorization A 22 resetting global properties A 22 resuming install dialog 1 9 return codes 2 24 return codes batch authorization
392. vely you can edit the Compare BIND JCL that is located in the CNTL data set add DBRM member ACMCLDM and then execute the BIND This method requires that CHANGE MANAGER and DASD MANAGER PLUS already be installed Performing a Catalog to Catalog Comparison The CHANGE MANAGER product s Compare component enables you to perform a catalog to catalog comparison A catalog to catalog comparison allows you to compare a specified set of DB2 objects from a catalog to DB2 objects of the same type from another catalog You can also compare objects of the same type within the same catalog You can compare DB2 objects using the following catalog combinations e local catalog to remote catalog e remote catalog to local catalog e remote catalog to remote catalog e local catalog to local catalog BMC Software Inc Confidential and Proprietary Information 7 6 Administrative Products for DB2 Installation Guide Installation Considerations Catalog to Catalog Requirements The following list describes the requirements for performing a catalog to catalog comparison e The subsystems whose catalogs are used as input sources must have DB2 Version 3 1 or later installed e Remote locations must be defined in the SYSIBM LOCATIONS table of the local DB2 subsystem and be connected using the distributed data facility DDF of DB2 Refer to IBM DATABASE 2 Universal Database for OS 390 Administration Guide for instructions on how to define a location na
393. xes of the ISPF help tutorial panels System Action The action fails or the batch utility job terminates User Response Verify that the correct data set name for the product load library was specified and that the data set exists and is cataloged on DASD Retry the action If failure persists contact BMC Software Product Support for assistance BMC Software Inc Confidential and Proprietary Information B 6 Administrative Products for DB2 Installation Guide Error Messages BMC89022E ERROR IN INPUT DSN PLEASE CONTACT BMC PRODUCT SUPPORT Explanation The data set name for the product authorization table was not found System Action All functions are suppressed User Response If the data set name is wrong correct it and resubmit the job If the data set name is correct contact BMC Software Product Support for assistance BMC89029I PRODUCT AUTHORIZATION TABLE WAS SUCCESSFULLY UPDATED PRESS ENTER TO CONTINUE Explanation The table has been updated System Action All functions have been processed User Response Press Enter to continue BMC89050E THE BMC PRODUCT CODE IS MISSING OR IS INVALID CHECK PARM ON JCL EXEC STATEMENT Explanation No product code or an invalid product code was specified in the PARM parameter of the batch JCL System Action The password is not processed User Response Add or correct the product code in the PARM parameter of the JCL EXEC statement See Control Statements and Keywor
394. y or view in exploitation mode SONO DAIS 2 Reinstall catalog indirection 2 Provided that ALTER CHANGE or PATROL MANAGER PATROL DB Alter or DB Change PATROL DB Change Manager still Manager in exists in toleration mode use the toleration mode fallback procedures described for toleration mode to remove the product in exploitation mode 3 Rebind all indirect packages and plans for the previous version by using prdssidZ bind packages and prdssiaB bind plans where ssid is the subsystem ID using catalog Reinstall catalog indirection 1 Provided that the previous indirection indirection and still exists remove the indirect copy or CATALOG view in exploitation mode MANAGER 2 Rebindall indirect packages and plans for the previous version by using prdssidZ bind packages where ssid is the subsystem ID To maintain BMC Software Administrative Products when you create a new DB2 Version 5 catalog use the guidelines in Table 3 18 Table 3 18 Creating a New DB2 Version 5 Catalog If You Are using any of the Administrative Products using catalog indirection BMC Software Inc Confidential and Proprietary Information Chapter 3 Performing Additional Installation Tasks Then Perform a Full installation of the following Administrative Products e ALTER or CHANGE MANAGER 6 2D e CATALOG MANAGER 6 2 e DASD MANAGER PLUS 6 1 Then you will be operating in exploitation mode Instal
395. y some products to create DB2 objects BMC Software Inc Confidential and Proprietary Information Chapter 2 Using the Install System 2 23 Generating Installation JCL The worklist members are structured in a BMC Software executable format and can contain the following types of statements e DB2 Data Definition Language DDL e Data Control Language DCL e Data Manipulation Language DML e DB2 utility parameters 5 C After all of the required jobs are generated press Enter to display the list of generated jobs Step6 Before you submit the jobs review the product documentation for additional installation requirements Some products have specific requirements for submitting the installation batch jobs Use the following sources to determine the requirements for each product that you are installing e the 100DOC member of the installation batch jobs e the product chapters in this book e release notes flashes and technical bulletins that are distributed with the products Step 7 Run the jobs in the order that is shown on the list and as instructed by the product documentation Return Codes Greater than 0 Return codes greater than 0 are specific to the install job that is run and the products that are referenced Refer to the comment block near the beginning of install job I40INST for information about return codes greater than 0 You may receive a return code 4 during the bind steps when installing some products on v

Bloomfield 8780 Coffeemaker User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents