How To
Summary
This document contains instructions to migrate from IBM Tivoli Decision Support for z/OS to IBM Z Decision Support V1.9.0. These migration instructions should be read in conjunction with the installation instructions in the Administration Guide and Reference to develop an installation and migration plan appropriate for your environment.
When the migration has completed successfully, consider turning on the Automated Data Gathering and Continuous Collect functions of IBM Z Decision Support V1.9.0. To activate these new functions, follow the instructions in the Administration Guide and Reference.
Migration pathways from Tivoli Decision Support 1.8.0, 1.8.1 and 1.8.2 are provided. This document contains the following sections:
1. Migrating from Tivoli Decision Support Version 1.8.0
2. Migrating from Tivoli Decision Support Version 1.8.1
3. Migrating from TDSz Version 1.8.2
Change this edition: Add Migration APAR PH18355 to the PTFs required on IBM Z Decision Support Version 1.9.0 before migration is started.
Objective
Section 1: Migrating from Tivoli Decision Support Version 1.8.0
This section describes how to migrate to IBM Z Decision Support Version 1.9.0 from Version 1.8.0.
1. Before you migrate to IBM Z Decision Support Version 1.9.0.
Before you migrate to Version 1.9.0, follow these six steps:
Step 1.1:
It is highly recommended to take a backup of your Tivoli Decision Support database.
Step 1.2:
Apply the PTFs for the IBM Z Decision Support Version 1.9.0 APARs, following the HOLD actions:
GA APAR
• PH01716
Forward fit of Version 1.8.2 APARs
• PH04618
• PH05261
• PH05376
Migration APAR
• PH18355
This APAR is required if you are on Db2 V12 Level M504+. PH18355 makes the IBM Z Decision Support Version 1.9.0 system tables and migration jobs compatible with Db2 V12 Level M504+. You need to put on the PTF for PH18355 before you can install IBM Z Decision Support Version 1.9.0, or migrate to IBM Z Decision Support Version 1.9.0.
Step 1.3:
If you have installed IMS components, please take note of the following:
a) Checkpoint record data sets (records output to DD name DRLICHKO during the IMS collect process) created before migrating to IBM Z Decision Support Version 1.9.0 may not be usable as DRLICHKI input to the IMS collect after the migration is completed, and therefore these checkpoint data sets must be discarded before you migrate. In order to prevent loss of data, specify WRITEPENDING=YES on the last collect run before migrating to IBM Z Decision Support Version 1.9.0.
b) Support for the collection of IMS version 7, 8 and 9 data is removed. If you have installed these components previously, you can continue to collect data to the data tables contained in the components, but further support for these objects will not be provided – you should use the higher versions IMS components instead. If you are still using these earlier IMS versions, we recommend that you delay migration to IBM Z Decision Support Version 1.9.0 until after you have migrated your IMS systems to a supported level of IMS.
Step 1.4:
IBM Z Decision Support Version 1.9.0 (excluding Usage and Accounting Collector) requires Db2 V11. If you are already on Db2 V11+, skip this step. If not, you must migrate to Db2 V11 or higher prior to commencing the migration to IBM Z Decision Support Version 1.9.0.
Once you have migrated to Db2 V11+ your Tivoli Decision Support application runtime must be made compatible with Db2 V11+ by following these steps:
a) Apply the PTFs for PI26707 and PI71656. These APARs provide sample job DRLJDCVM in the DR190.SDRLCNTL library. This job drops and recreates system views which are Db2 version dependent. Copy member DRLJDCVM from DRL190.SDRLCNTL to &HLQ.LOCAL.CNTL and follow the instructions in the DRLJDCVM member to customize the JCL prior to running the job.
b) Db2 V10+ no longer supports binding DBRMs directly into plans. Instead it supports the binding of packages into plans. Pre-existing plans that are bound from DBRMs may be rebound using the REBIND command specifying the COLLID option to create packages. The following sample REBIND command creates a package called DRLPLAN and binds that back into plan DRLPLAN:
REBIND PLAN(DRLPLAN) COLLID(DRLPLAN)
The plan name (DRLPLAN) and collection ID (DRLPLAN) shown here are just examples. You can use any plan name and collection ID that meet your system naming standards. For more information about the BIND and REBIND commands refer to the Db2 publications.
Step 1.5:
If you have installed the Tivoli Performance Modeler for z/OS component, and you have not previously applied the PTFs for PM46135, you will need to discard or extract any existing data in the TPM_LPAR_T and TPM_WORKLOAD_T tables before migrating to IBM Z Decision Support Version 1.9.0. After migrating to IBM Z Decision Support Version 1.9.0 any existing data in these tables will cause extraction errors.
Step 1.6:
As of Tivoli Decision Support Version 1.8.0, the CIMS Mainframe product is integrated into Tivoli Decision Support as the Usage and Accounting Collector (UAC) feature. All CIMS Mainframe implementations must be migrated to Tivoli Decision Support. This migration is discussed in more detail in step 2.13 below.
2. The migration process
Migrating to IBM Z Decision Support Version 1.9.0. consists of the following thirteen steps:
Step 2.1: SMP/E installation
Step 2.2: REBIND Db2 plans and packages
Step 2.3: Review dialog parameters
Step 2.4: Update system tables
Step 2.5: Test the installation of the IBM Z Decision Support base
Step 2.6: Re-introduce customizations
Step 2.7: Review IBM Z Decision Support supplied JCL
Step 2.8 Consider partitioning with table space profiling
Step 2.9: Migrate the database
Step 2.10: Re-install components
Step 2.11: Migrate the Usage and Accounting Collector
Step 2.12: Migrate the IMS light feature
Step 2.13: Migrate CIMS Mainframe to IBM Z Decision Support
Each step is documented here in detail:
Step 2.1: SMP/E installation
Ensure that you include the IBM Z Decision Support Version 1.9.0. GA APAR PH01716 with the SMP/E installation. The SMP/E installation of the IBM Z Decision Support base and its features is described in the IBM Z Decision Support Program Directory.
Confirm that the installation completed successfully by ensuring that the following data sets and file system directory were created during SMP/E installation. The names given are defaults and might not match the names used in your implementation. Check with your Systems Programmer to confirm the actual names used.
a) IBM Z Decision Support data sets
Data set name Description
DRL190.SDRLA400 OS/400
DRL190.SDRLCNTL Sample jobs and Db2 DBRM module
DRL190.SDRLDEFS Definitions of records, tables, and other objects
DRL190.SDRLEXEC REXX execs
DRL190.SDRLEXTR Authorized load modules for the SMF extractor
/usr/lpp/IBM/IDSz/v1r9m0/IBM/ USS file system directory containing tar files (referred to by SMP/E via SDRLIDM DDDEF)
DRL190.SDRLLOAD Load modules
DRL190.SDRLSKEL ISPF skeletons
DRL190.SDRLWS Workstation
*DRL190.SDRLFxxx GDDM/ICU formats
*DRL190.SDRLMxxx ISPF messages
*DRL190.SDRLPxxx ISPF panels
*DRL190.SDRLRxxx Definitions of reports
*DRL190.SDRLTxxx ISPF tables
*These are language-dependent IBM Z Decision Support data sets. The last three letters in these data set names indicate the language version: ENU for English or JPN for Japanese. For example, SDRLRENU contains the English report definition files. The corresponding Japanese version is SDRLRJPN.
b) Local data sets
Data set name Description
&HLQ.LOCAL.ADMCFORM Local GDDM Presentation Graphics Facility(GDDM-PGF) and Interactive Chart Utility (GDDM/ICU) formats
&HLQ.LOCAL.CHARTS Saved graphic reports (GDDM ADMGDF format)
&HLQ.LOCAL.CNTL Local IBM Z Decision Support jobs
&HLQ.LOCAL.DEFS Local IBM Z Decision Support definitions
&HLQ.LOCAL.EXEC Local IBM Z Decision Support execs
&HLQ.LOCAL.MESSAGES Messages sent through the dialog
&HLQ.LOCAL.REPORTS Saved tabular reports
&HLQ.LOCAL.USER.DEFS Local IBM Z Decision Support user/alter definitions
Step 2.2: REBIND Db2 plans and packages
A new DBRM is supplied with IBM Z Decision Support Version 1.9.0. Follow these instructions to rebind to the new DBRM:
1. Copy member DRLJDBND in the DRL190.SDRLCNTL library to the &HLQ.LOCAL.CNTL library.
2. Review and action the customization instructions in the job prolog, before submitting the job.
Step 2.3: Review dialog parameters
Ensure the migration environment refers to the IBM Z Decision Support Version 1.9.0 data sets. For more information, see "Preparing the dialog and updating the dialog profile" in the Administration Guide and Reference.
IBM Z Decision Support Version 1.9.0 contains APARs which introduced the following changes to the dialog parameters:
| Dialog parameter | Parameter description | Description of change | APAR |
| def_Db2plan | Db2 plan name | New | PM07437 |
| def_drlshwid | Show Tivoli Decision Support system info | New | PM07437 |
| Db2ver | Db2 version | This variable no longer allows alphabetical characters - only numerical values are allowed. For example, specify '11' for Db2 V11. | PI09853 |
If you have not previously installed the PTFs for these APARs listed above, review the changes in the new sample DRLFPROF from DRL190.SDRLCNTL and customize your &HLQ.DRLFPROF accordingly. Refer to the Administration Guide and Reference for more information on these dialog parameters.
If you made changes to your &HLQ.DRLFPROF in this step, you must start IBM Z Decision Support Version 1.9.0 specifying the RESET parameter in the next step to activate these DRLFPROF changes.
Step 2.4: Update system tables
Follow these steps to update the system tables using the IBM Z Decision Support dialog:
a) Invoke the IBM Z Decision Support dialog with this command: TSO %DRLEINIT [RESET]
b) Display the Administration window by selecting 2 (Administration) on the Primary Menu.
c) From the Administration window select 1 (System) to display the System window.
d) From the System window select 2 (System tables).
e) From the System Tables window press F6 to update the system tables.
Step 2.5: Test the installation of the IBM Z Decision Support base
Install the Sample component, collect the Sample log and run the Sample report to verify that the IBM Z Decision Support base is operational.
Step 2.6: Re-introduce customizations
If you have previously made changes to Tivoli Decision Support supplied objects in your &HLQ.LOCAL.DEFS, you will need to manually apply the IBM Z Decision Support Version 1.9.0. changes to these objects in your &HLQ.LOCAL.DEFS. Identify the Version 1.9.0 changes by comparing each object in your &HLQ.LOCAL.DEFS with the DRL190.SDRLDEFS version.
If an object exists in the &HLQ.LOCAL.DEFS library, IBM Z Decision Support installs the object from this customized definition, instead of from the shipped DRL190.SDRLDEFS version. Therefore, if you do not take the action described in this step, the Version 1.9.0. changes will not be installed when you re-install the components.
Step 2.7: Review IBM Z Decision Support supplied JCL
The DRL190.SDRLCNTL library contains several batch jobs that you can copy to &HLQ.LOCAL.CNTL and customize to match your installation.
If you have previously customized sample JCL from DRL182.SDRLCNTL, review the Version 1.9.0 changes in the new sample JCL provided in DRL190.SDRLCNTL and manually apply these changes to your customized versions in &HLQ.LOCAL.CNTL.
Step 2.8: Consider partitioning with table space profiling
IBM Z Decision Support Version 1.9.0 introduces table space profiling. A table space profile allows you to define a single copy all the settings for the creation of Db2 table spaces, tables, and indexes. This single copy of the settings could then be used at component install time for all the Db2 table spaces, tables, and indexes.
The following components are table space profiling enabled:
• Key Performance Metric (KPM) CICS (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) Db2 (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) IMS (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) z/OS (default profile enabled: partitioning by growth)
• All CICS partitioned components (default profile enabled: partitioning by range)
Please take note of the following:
• A migration path is not provided to migrate previously installed components to partitioned data tables.
• The table space profiling allows you to implement partitioning by growth or range when installing any of the enabled components for the first time, without having to customize any of the object definitions.
• Although default table space profiles are provided for these components, you have the option to review and modify all the profile settings (which includes partitioning settings as well as table space and index parameters) before you install the components.
When you are migrating to IBM Z Decision Support Version 1.9.0. you need to follow these steps to activate table space profiling before you install any of the components listed above:
1. Run job DRLJDBIP to create the Db2 storage groups required for partitioning support. Only run this job if you have not previously created the storage groups required for partitioning.
2. Run migration job DRLJGENL to insert the default supplied profiles into lookup tables GENERATE_PROFILES and GENERATE_KEYS.
3. Before you install components, review the contents of these lookup tables and amend if required. Refer to the components’ customization chapter in the Reference manual for more information on this step.
Step 2.9: Migrate the database
The following table lists all database migration tasks which may be required to migrate to Version 1.9.0. Review each step, to determine whether it would be required, based on your current Tivoli Decision Support.
Migration tasks are listed by Component. The APAR column lists the Version 1.8.0 APARs with which the migration task was introduced. A migration task is only required if:
- You have previously installed the impacted Component, and
- You have not previously installed the APAR in Version 1.8.0, and
- Your installation meets the additional requirements detailed in the Description column.
For example, if you have the Db2 component installed, and you have not previously installed the PTFs for PI64117, you should consider running the SQL statements provided to improve your data quality.
The Mandatory column indicates whether the migration task is mandatory or optional. Optional migration tasks improve the accuracy/quality of data previously collected. Mandatory migration tasks are needed to make your database compatible with the IBM Z Decision Support Version 1.9.0. definitions.
The Migration instructions column contains either a sample migration job which is supplied in the DRL190.SDRLCNTL library, or actual migration instructions, for example SQL statements.
| Component | APAR | Mandatory Y/N | Migration instructions | Description |
| --- | PI26707 PI71656 | N | DRLJDCVM | Update system views ON THE Db2 CATALOG to make it compatible with Db2 Version 10+. This task is only required if you want to display the system views using the System Tables List panel (DRLDASYT). |
| CICS Monitoring & Key Performance Metrics - CICS | PM23679 PM40234 PM82516 PI47090 PI82173 | Y | DRLJCIF1 | Rebuild the CICS_FIELD table. If this table has been customized (member DRLTCIFI), these customizations must be re-applied before you run this migration job. See step 2.5 above for instructions on reintroducing customizations. Although this job only needs to be run once during the migration, it needs to be run if the PTFs for either of these two APARs have not previously been applied. |
| PM11488 | N | DRLJC001 | If you have compression on and have records written to the DRLNDICT dataset that require reprocessing, this job resets the length of the DRLNDICT records in order for the record to be processed correctly on the subsequent collect. | |
| Db2 | PK89999 | Y | DRLJAGGR | Create lookup table AGGR_VALUE for use in table Db2_PACKAGE_H update definitions. |
| PK52681 | Y | DRLJDB3 | Change primary key of Db2_PACKAGE_* tables. | |
| PK61570 | N | DRLJDB08 | Single table space replaced with multiple for this component's data tables. | |
| PK85596 | Y | DRLJDB09 | Make table space DRLSDb2 available to all Db2 subcomponents. | |
| PM91971 | N | DRLJDBAA | Fix IDAA time values in Db2 data tables. Only run this job if you have previously applied IDAA support APAR PM66403. | |
| PI64117 | N | SQL UPDATE &PREFIX.Db2_IDAA_STAT_H SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; SQL UPDATE &PREFIX.Db2_IDAA_STAT_D SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; | Convert value in column DISK_INUSE_AVG_PCT of tables Db2_IDAA_STAT_H and Db2_IDAA_STAT_D to a percentage value. | |
| IMS V7, IMS V8 & IMS V9 | - | N | DRLJMIC2 | These components are no longer supported. This optional job removes the component objects from the system tables. If you have installed any of these components previously, and wish to continue collecting data to the data tables, do not run this job as it will disable the collection of data. The job contains a step per IMS version – only execute the steps relating to the versions you want to remove from your system tables. |
| Network VTAM Statistics | PM03940 | N | DRLJNW01 | Delete the incorrect entries in the system tables which are causing the -104 when doing an uninstall of the Network VTAM Statistics component. |
| Tivoli Workload Scheduler for z/OS (OPC) | PI67891 | Y | DRLJOPT2 | Add the new column OPERATION_NUMBER with a default of 0 as a primary key of table OPC_OPER_EVENT_T. |
| TCPIP | PM09069 | N | DRLJTCP2 | Correct values in several TCPIP data tables. |
| z/OS Performance Management (MVSPM) | PI17092 | N | UPDATE &PREFIX.MVSPM_LPAR_H SET MSU_4HRA = NULL WHERE FROM_LPAR_NO <> LPAR_NO OR PROCESSOR_TYPE <> 'CP'; | Set MSU_4HRA to null in table MVSPM_LPAR_H for all rows where it should not have been collected, using the provided SQL statement as template. Only run this SQL script if you have previously applied APAR PM61917 to add column MSU_4HRA. |
| z/OS System (MVS) | PK74091 | N | DRLJMVPR | Fix aggregation data error in table MVS_PROCESSOR_M. |
| PM30613 | N | DRLJMVPH | Correct values in the MVS_7700_HBA_* tables. | |
| PM89335 | Y | DRLJMVAM (see note below) | Change primary key of table MVS_ACCNT_PGM_T. | |
| PI17092 | N | UPDATE &PREFIX.MVS_LPAR_D SET MSU_4HRA = NULL WHERE FROM_LPAR_NO <> LPAR_NO OR PROCESSOR_TYPE <> 'CP'; | Set MSU_4HRA to null in tables MVS_LPAR_D and MVS_LPAR_M for all rows where it should not have been collected, using the provided SQL statement as template. Only run this SQL script if you have previously applied APAR PM61917 to add column MSU_4HRA. | |
| PI20342 | N | DRLJMVOM | Swap contents of column SYSCALL_NUMBER and CPU_TIME of tables MVS_OMVSADDR_T and MVS_OMVSADIS_T. |
Note: Step3 of DRLJMVAM will result in RC8 due to existing objects. Member DRLTMVAP is executed to recreate table MVS_ACCNT_PGM_T. However, DRLTMVAP also contains the definition for table MVS_ACCNT23_PGM_T. If the RC8 in Step3 is due to the fact that MVS_ACCNT23_PGM_T exists already, you can ignore this return code. RC8 in Step3 will not halt the execution of this job.
Step 2.10: Re-install components
Now re-install ALL previously installed components.
Step 2.11: Migrate the Usage and Accounting Collector
This step is only required if you make use of the Usage and Accounting Collector.
- The UAC CICS dictionary must be rebuilt if you have not previously applied all of these APARs to Version 1.8.0:
PM13229 PM63035 PM69394 PM98973 PI40948 PI88656
Refer to the IBM Z Decision Support Usage and Accounting Collector User Guide (Chapter 7: Dictionary - CIMSDTVS) for information on rebuilding the dictionary using the dictionary utility DRLCDTLD.
- If you have not previously applied APAR PI26707 to Version 1.8.0:
If you want to create DRLCUNIV Chargeback Records from IDMS v18 or higher SMF records, you must provide an additional control statement to identify that DRLCUN01 is processing an IDMS v18 or higher SMF log.The control statement is IDMS SMF18 REC.
Step 2.12: Migrate the IMS light feature
This step is only required if you make use of the IMS light feature.
IBM Z Decision Support Version 1.9.0 includes changes to the IMS Shared Queue Feature log procedures via the following APARS:
PM22818 PM35939 PM62915 PM64657 PM68203 PM83774 PM91671 PM99061 PI17543 PI26186
PI37652 PI58473 PI58479 PI62464 PI65833 PI73790 PI81275 PI81402 PI83599
PI83741 PI84391 PI85060 PI86689 PI87432 PI87617 PI90217 PI91042 PI92782
If you have not installed all these APARs previously, and you are using the IMS light feature to collect data remotely with program DRLSLOGP for subsequent transmission and processing at a central site, you must review and re-run your customized version of sample job DRLJCSQL. The re-created light feature load library must then be re-sent to all remote sites executing DRLSLOGP.
Step 2.13: Migrate CIMS Mainframe to IBM Z Decision Support
This step is only required is you make use of CIMS Mainframe, and have not previously migrated CIMS Mainframe to Tivoli Decision Support.
As of Tivoli Decision Support Version 1.8.0 the CIMS Mainframe product is integrated into Tivoli Decision Support as the Usage and Accounting Collector (UAC) feature.
Note: Spectrum Writer is not included with UAC. Former CIMS Lab customers have a perpetual license for Spectrum Writer and should retain the CIMS Lab data sets so that they can make use of it. For support of Spectrum Writer, contact Pacific Systems. Customers that require access to CIMS Mainframe 12.2.1 should contact IBM support.
Processing Considerations
CIMS Mainframe implemented new record types in 11.5. These 79x record types are the preferred record types. In IBM Z Decision Support, the 79x records are the only types supported. The first thing to research for the IBM Z Decision Support migration is the current record type created by CIMS Mainframe. If the CIMS Mainframe subsystem programs (CIMSACCT, CIMSCMF2, CIMSDb2, CIMSDISK, CIMSTAPE, CIMSUNIV, and CIMSUN02) are creating DDNAME CIMSACT2 and this is the data set that is passed on to other processing, then the 79x records are created already and you can skip the next section Switching to 79x records and instead continue to JCL Considerations when using 79x records.
Switching to 79x records
The CIMSBILL program is not supported in IBM Z Decision Support. It has been replaced with the DRLCMONY program (this is the IBM Z Decision Support version of CIMSMONY). Executing program CIMSBILL is another indicator that the 79x records are not being created. The conversion from CIMSBILL to CIMSMONY is documented in the CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide. The documentation will explain the options available and decisions that must to be made to migrate to IBM Z Decision Support and use the DRLCMONY (CIMSMONY) program. IBM Z Decision Support will not produce the old 99x records. The default processing in IBM Z Decision Support is the creation of 79x records to the DDNAME CIMSACT2. Switching to the 79x records can be done with the migration to IBM Z Decision Support or it can be done while executing the CIMS Mainframe release. In either case, there are JCL changes that must be made and these are documented in the CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide.
JCL Considerations when using 79x records
The CIMS Mainframe programs were all renamed for IBM Z Decision Support. The program names start with DRLC instead of CIMS. For example, in CIMS Mainframe there is a CIMSEXTR program but in IBM Z Decision Support this is now called DRLCEXTR. The Tivoli Decision Support install links the new programs with an ALIAS of the CIMS Mainframe program name. Therefore, JCL that executes the CIMS Mainframe program CIMSEXTR will also work with IBM Z Decision Support because the DRLCEXTR has an alias of CIMSEXT. IBM Z Decision Support has made very few changes to the control statements that are entered via the DDNAME CIMSCNTL. The CIMS Mainframe JCL that references CIMS.DATAFILE should also work with IBM Z Decision Support.
The IBM Z Decision Support DDNAMEs have not changed. CIMS Mainframe JCLs should work with the new IBM Z Decision Support Usage and Accounting Collector as long as the 79x records are were being produced in the CIMS Mainframe JCLs. Changes should be limited to STEPLIB changes to point to the IBM Z Decision Support load library. IBM Z Decision Support no longer performs password checking. The DDNAME CIMSPASS can be removed from the Tivoli Decision Support JCL, but the presence of passwords will not cause a problem.
Release Considerations
This table outlines the CIMS Mainframe release considerations for migrating to IBM Z Decision Support:
| CIMS Mainframe Release | Migration to IBM Z Decision Support |
| 12.2.1 | Supported |
| 12.2 | |
| 12.1 | Upgrade to 12.2.1 first |
| 12.0 | |
| 11.6 | |
| 11.5 | |
| 11.4 |
The above release considerations are general rules that take into account file conversions. The various files used by CIMS Mainframe must be converted to the 12.2/12.2.1 level before migrating to IBM Z Decision Support. The CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide contains the detailed instructions for upgrading the CIMS Mainframe product. Use the instructions in these manuals to complete the upgrade. The upgrade procedures for the early releases (11.5 and 11.4) are documented in the 12.0 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide. This manual is available from the CIMS Mainframe Information Center web page: http://publib.boulder.ibm.com/tividd/td/IBMCIMSMainframe12.2.1.html
New name conventions
The CIMS Mainframe parts are renamed in IBM Z Decision Support to use the IBM Z Decision Support naming conventions. The load modules have a new name that starts with DRLC (example DRLCEXTR instead of CIMSEXTR). The CIMS.DATAFILE is no longer distributed with IBM Z Decision Support. The sample JCLs are now found in DRL190.SDRLCNTL. The number of JCL members was reduced by including most control statements as instream data instead of separate members.
All CIMS.DATAFILE members were renamed by changing or adding a four-character prefix:
| Prefix | Description |
| DRLC | CLIST or REXX |
| DRLN | Sample JCL |
| DRLM | Control statements and record definitions |
| DRLMR | Record descriptions |
| DRLK | Dictionary definitions |
Use this table as a cross-reference to map the CIMS Mainframe CIMS.DATAFILE member names to the new names in IBM Z Decision Support:
| CIMS Mainframe DATAFILE member name | IBM Z Decision Support member name |
| AAAALIST | DRLMLIST |
| ALIAS | DRLMALS |
| ALIASACC | DRLMALSA |
| ATMONJCL | DRLNATMN |
| BUDGETIN | DRLMBGTI |
| BUDJCL1 | DRLNBDGT |
| CALENDAR | DRLMCLDR |
| CALNDR13 | DRLMCL13 |
| CICSASML | DRLNUR01 |
| CICSRC01 | DRLMRC01 |
| CICSRC02 | DRLMRC02 |
| CIMRCT54 | DRLMRT54 |
| CIMRECAD | DRLMRAD |
| CIMRECCA | DRLMRCA |
| CIMRECDC | DRLMRDC |
| CIMRECFA | DRLMRFA |
| CIMRECID | DRLMRID |
| CIMRECIF | DRLMRIF |
| CIMRECIS | DRLMRIS |
| CIMRECMN | DRLMRMN |
| CIMRECMO | DRLMRMO |
| CIMRECMQ | DRLMRMQ |
| CIMRECM2 | DRLMRM2 |
| CIMRECOR | DRLMROR |
| CIMRECRM | DRLMRRM |
| CIMRECRO | DRLMRRO |
| CIMRECSJ | DRLMRSJ |
| CIMRECSP | DRLMRSP |
The migration to IBM Z Decision Support Version 1.9.0 is now completed.
Section 2: Migrating from Tivoli Decision Support Version 1.8.1
This section describes how to migrate to IBM Z Decision Support Version 1.9.0 from Version 1.8.1.
1. Before you migrate to IBM Z Decision Support Version 1.9.0.
Before you migrate to Version 1.9.0, follow these five steps:
Step 1.1:
It is highly recommended to take a backup of your Tivoli Decision Support database.
Step 1.2:
Apply the PTFs for the IBM Z Decision Support Version 1.9.0 APARs, following the HOLD actions:
GA APAR
• PH01716
Forward fit of Version 1.8.2 APARs
• PH04618
• PH05261
• PH05376
Migration APAR
• PH18355
This APAR is required if you are on Db2 V12 Level M504+. PH18355 makes the IBM Z Decision Support Version 1.9.0 system tables and migration jobs compatible with Db2 V12 Level M504+. You need to put on the PTF for PH18355 before you can install IBM Z Decision Support Version 1.9.0, or migrate to IBM Z Decision Support Version 1.9.0.
Step 1.3:
If you have installed IMS components, please take note of the following:
a) Checkpoint record data sets (records output to DD name DRLICHKO during the IMS collect process) created before migrating to IBM Z Decision Support Version 1.9.0 may not be usable as DRLICHKI input to the IMS collect after the migration is completed, and therefore these checkpoint data sets must be discarded before you migrate. In order to prevent loss of data, specify WRITEPENDING=YES on the last collect run before migrating to IBM Z Decision Support Version 1.9.0.
b) Support for the collection of IMS version 8 and 9 data is removed. If you have installed these components previously, you can continue to collect data to the data tables contained in the components, but further support for these objects will not be provided – you should use the higher versions IMS components instead. If you are still using these earlier IMS versions, we recommend that you delay migration to IBM Z Decision Support Version 1.9.0 until after you have migrated your IMS systems to a supported level of IMS.
Step 1.4:
IBM Z Decision Support Version 1.9.0 (excluding Usage and Accounting Collector) requires Db2 V11. If you are already on Db2 V11+, skip this step. If not, you must migrate to Db2 V11 or higher prior to commencing the migration to IBM Z Decision Support Version 1.9.0.
Once you have migrated to Db2 V11+ your Tivoli Decision Support application runtime must be made compatible with Db2 V11+ by following these steps:
a) Apply the PTFs for PI26707 and PI71656. These APARs provide sample job DRLJDCVM in the DR190.SDRLCNTL library. This job drops and recreates system views which are Db2 version dependent. Copy member DRLJDCVM from DRL190.SDRLCNTL to &HLQ.LOCAL.CNTL and follow the instructions in the DRLJDCVM member to customize the JCL prior to running the job.
b) Db2 V10+ no longer supports binding DBRMs directly into plans. Instead it supports the binding of packages into plans. Pre-existing plans that are bound from DBRMs may be rebound using the REBIND command specifying the COLLID option to create packages. The following sample REBIND command creates a package called DRLPLAN and binds that back into plan DRLPLAN:
REBIND PLAN(DRLPLAN) COLLID(DRLPLAN)
The plan name (DRLPLAN) and collection ID (DRLPLAN) shown here are just examples. You can use any plan name and collection ID that meet your system naming standards. For more information about the BIND and REBIND commands refer to the Db2 publications.
Step 1.5:
If you have installed the Tivoli Performance Modeler for z/OS component, and you have not previously applied the PTFs for PM46135, you will need to discard or extract any existing data in the TPM_LPAR_T and TPM_WORKLOAD_T tables before migrating to IBM Z Decision Support Version 1.9.0. After migrating to IBM Z Decision Support Version 1.9.0 any existing data in these tables will cause extraction errors.
2. The migration process
Migrating to IBM Z Decision Support Version 1.9.0. consists of the following twelve steps:
Step 2.1: SMP/E installation
Step 2.2: REBIND Db2 plans and packages
Step 2.3: Review dialog parameters
Step 2.4: Update system tables
Step 2.5: Test the installation of the IBM Z Decision Support base
Step 2.6: Re-introduce customizations
Step 2.7: Review IBM Z Decision Support supplied JCL
Step 2.8 Consider partitioning with table space profiling
Step 2.9: Migrate the database
Step 2.10: Re-install components
Step 2.11: Migrate the Usage and Accounting Collector
Step 2.12: Migrate the IMS light feature
Each step is documented here in detail:
Step 2.1: SMP/E installation
Ensure that you include the IBM Z Decision Support Version 1.9.0. GA APAR PH01716 with the SMP/E installation. The SMP/E installation of the IBM Z Decision Support base and its features is described in the IBM Z Decision Support Program Directory.
Confirm that the installation completed successfully by ensuring that the following data sets and file system directory were created during SMP/E installation. The names given are defaults and might not match the names in your implementation. Check with your Systems Programmer to confirm the actual names used.
a) IBM Z Decision Support data sets
Data set name Description
DRL190.SDRLA400 OS/400
DRL190.SDRLCNTL Sample jobs and Db2 DBRM module
DRL190.SDRLDEFS Definitions of records, tables, and other objects
DRL190.SDRLEXEC REXX execs
DRL190.SDRLEXTR Authorized load modules for the SMF extractor
/usr/lpp/IBM/IDSz/v1r9m0/IBM/ USS file system directory containing tar files (referred to by SMP/E via SDRLIDM DDDEF)
DRL190.SDRLLOAD Load modules
DRL190.SDRLSKEL ISPF skeletons
DRL190.SDRLWS Workstation
*DRL190.SDRLFxxx GDDM/ICU formats
*DRL190.SDRLMxxx ISPF messages
*DRL190.SDRLPxxx ISPF panels
*DRL190.SDRLRxxx Definitions of reports
*DRL190.SDRLTxxx ISPF tables
*These are language-dependent IBM Z Decision Support data sets. The last three letters in these data set names indicate the language version: ENU for English or JPN for Japanese. For example, SDRLRENU contains the English report definition files. The corresponding Japanese version is SDRLRJPN.
b) Local data sets
Data set name Description
&HLQ.LOCAL.ADMCFORM Local GDDM Presentation Graphics Facility(GDDM-PGF) and Interactive Chart Utility (GDDM/ICU) formats
&HLQ.LOCAL.CHARTS Saved graphic reports (GDDM ADMGDF format)
&HLQ.LOCAL.CNTL Local IBM Z Decision Support jobs
&HLQ.LOCAL.DEFS Local IBM Z Decision Support definitions
&HLQ.LOCAL.EXEC Local IBM Z Decision Support execs
&HLQ.LOCAL.MESSAGES Messages sent through the dialog
&HLQ.LOCAL.REPORTS Saved tabular reports
&HLQ.LOCAL.USER.DEFS Local IBM Z Decision Support user/alter definitions
Step 2.2: REBIND Db2 plans and packages
A new DBRM is supplied with IBM Z Decision Support Version 1.9.0. Follow these instructions to rebind to the new DBRM:
1. Copy member DRLJDBND in the DRL190.SDRLCNTL library to the &HLQ.LOCAL.CNTL library.
2. Review and action the customization instructions in the job prolog, before submitting the job.
Step 2.3: Review dialog parameters
Ensure the migration environment refers to the IBM Z Decision Support Version 1.9.0 data sets. For more information, see "Preparing the dialog and updating the dialog profile" in the Administration Guide and Reference.
IBM Z Decision Support Version 1.9.0 contains APARs which introduced the following changes to the dialog parameters:
| Dialog parameter | Parameter description | Description of change | APAR |
| def_Db2plan | Db2 plan name | New | PM07437 |
| def_drlshwid | Show Tivoli Decision Support system info | New | PM07437 |
| Db2ver | Db2 version | This variable no longer allows alphabetical characters - only numerical values are allowed. For example, specify '11' for Db2 V11. | PI09853 |
If you have not previously installed the PTFs for these APARs listed above, review the changes in the new sample DRLFPROF from DRL190.SDRLCNTL and customize your &HLQ.DRLFPROF accordingly. Refer to the Administration Guide and Reference for more information on these dialog parameters.
If you made changes to your &HLQ.DRLFPROF in this step, you must start IBM Z Decision Support Version 1.9.0 specifying the RESET parameter in the next step to activate these DRLFPROF changes.
Step 2.4: Update system tables
Follow these steps to update the system tables using the IBM Z Decision Support dialog:
a) Invoke the IBM Z Decision Support dialog with this command: TSO %DRLEINIT [RESET]
b) Display the Administration window by selecting 2 (Administration) on the Primary Menu.
c) From the Administration window select 1 (System) to display the System window.
d) From the System window select 2 (System tables).
e) From the System Tables window press F6 to update the system tables.
Step 2.5: Test the installation of the IBM Z Decision Support base
Install the Sample component, collect the Sample log and run the Sample report to verify that the IBM Z Decision Support base is operational.
Step 2.6: Re-introduce customizations
If you have previously made changes to Tivoli Decision Support supplied objects in your &HLQ.LOCAL.DEFS, you will need to manually apply the IBM Z Decision Support Version 1.9.0. changes to these objects in your &HLQ.LOCAL.DEFS. Identify the Version 1.9.0 changes by comparing each object in your &HLQ.LOCAL.DEFS with the DRL190.SDRLDEFS version.
If an object exists in the &HLQ.LOCAL.DEFS library, IBM Z Decision Support installs the object from this customized definition, instead of from the shipped DRL190.SDRLDEFS version. Therefore, if you do not take the action described in this step, the Version 1.9.0. changes will not be installed when you re-install the components.
Step 2.7: Review IBM Z Decision Support supplied JCL
The DRL190.SDRLCNTL library contains several batch jobs that you can copy to &HLQ.LOCAL.CNTL and customize to match your installation.
If you have previously customized sample JCL from DRL182.SDRLCNTL, review the Version 1.9.0 changes in the new sample JCL provided in DRL190.SDRLCNTL and manually apply these changes to your customized versions in &HLQ.LOCAL.CNTL.
Step 2.8: Consider partitioning with table space profiling
IBM Z Decision Support Version 1.9.0 introduces table space profiling. A table space profile allows you to define a single copy all the settings for the creation of Db2 table spaces, tables, and indexes. This single copy of the settings could then be used at component install time for all the Db2 table spaces, tables, and indexes.
The following components are table space profiling enabled:
• Key Performance Metric (KPM) CICS (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) Db2 (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) IMS (default profile enabled: partitioning by growth)
• Key Performance Metric (KPM) z/OS (default profile enabled: partitioning by growth)
• All CICS partitioned components (default profile enabled: partitioning by range)
Please take note of the following:
• A migration path is not provided to migrate previously installed components to partitioned data tables.
• The table space profiling allows you to implement partitioning by growth or range when installing any of the enabled components for the first time, without having to customize any of the object definitions.
• Although default table space profiles are provided for these components, you have the option to review and modify all the profile settings (which includes partitioning settings as well as table space and index parameters) before you install the components.
When you are migrating to IBM Z Decision Support Version 1.9.0. you need to follow these steps to activate table space profiling before you install any of the components listed above:
1. Run job DRLJDBIP to create the Db2 storage groups required for partitioning support. Only run this job if you have not previously created the storage groups required for partitioning.
2. Run migration job DRLJGENL to insert the default supplied profiles into lookup tables GENERATE_PROFILES and GENERATE_KEYS.
3. Before you install components, review the contents of these lookup tables and amend if required. Refer to the components’ customization chapter in the Reference manual for more information on this step.
Step 2.9: Migrate the database
The following table lists all database migration tasks which may be required to migrate to Version 1.9.0. Review each step, to determine whether it would be required, based on your current Tivoli Decision Support.
Migration tasks are listed by Component. The APAR column lists the Version 1.8.1 APARs with which the migration task was introduced. A migration task is only required if:
- You have previously installed the impacted Component, and
- You have not previously installed the APAR in Version 1.8.1, and
- Your installation meets the additional requirements detailed in the Description column.
For example, if you have the Db2 component installed, and you have not previously installed the PTFs for PI64117, you should consider running the SQL statements provided to improve your data quality.
The Mandatory column indicates whether the migration task is mandatory or optional. Optional migration tasks improve the accuracy/quality of data previously collected. Mandatory migration tasks are needed to make your database compatible with the IBM Z Decision Support Version 1.9.0. definitions.
The Migration instructions column contains either a sample migration job which is supplied in the DRL190.SDRLCNTL library, or actual migration instructions, for example SQL statements.
| Component | APAR | Mandatory Y/N | Migration instructions | Description |
| --- | PI26707 PI71656 | N | DRLJDCVM | Update system views ON THE Db2 CATALOG to make it compatible with Db2 Version 10+. This task is only required if you want to display the system views using the System Tables List panel (DRLDASYT). |
| CICS Monitoring & Key Performance Metrics - CICS | PM23679 PM40234 PM82516 PI47090 PI82173 | Y | DRLJCIF1 | Rebuild the CICS_FIELD table. If this table has been customized (member DRLTCIFI), these customizations must be re-applied before you run this migration job. See step 2.5 above for instructions on reintroducing customizations. Although this job only needs to be run once during the migration, it needs to be run if the PTFs for either of these two APARs have not previously been applied. |
| PM11488 | N | DRLJC001 | If you have compression on and have records written to the DRLNDICT dataset that require reprocessing, this job resets the length of the DRLNDICT records in order for the record to be processed correctly on the subsequent collect. | |
| Db2 | PM91971 | N | DRLJDBAA | Fix IDAA time values in Db2 data tables. Only run this job if you have previously applied IDAA support APAR PM66403. |
| PI64117 | N | SQL UPDATE &PREFIX.Db2_IDAA_STAT_H SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; SQL UPDATE &PREFIX.Db2_IDAA_STAT_D SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; | Convert value in column DISK_INUSE_AVG_PCT of tables Db2_IDAA_STAT_H and Db2_IDAA_STAT_D to a percentage value. | |
| IMS V8 & IMS V9 | - | N | DRLJMIC2 | These components are no longer supported. This optional job removes the component objects from the system tables. If you have installed any of these components previously, and wish to continue collecting data to the data tables, do not run this job as it will disable the collection of data. The job contains a step per IMS version – only execute the steps relating to the versions you want to remove from your system tables. |
| Network VTAM Statistics | PM03940 | N | DRLJNW01 | Delete the incorrect entries in the system tables which are causing the -104 when doing an uninstall of the Network VTAM Statistics component. |
| Tivoli Workload Scheduler for z/OS (OPC) | PI67891 | Y | DRLJOPT2 | Add the new column OPERATION_NUMBER with a default of 0 as a primary key of table OPC_OPER_EVENT_T. |
| TCPIP | PM09069 | N | DRLJTCP2 | Correct values in several TCPIP data tables. |
| z/OS Performance Management (MVSPM) | PI17092 | N | UPDATE &PREFIX.MVSPM_LPAR_H SET MSU_4HRA = NULL WHERE FROM_LPAR_NO <> LPAR_NO OR PROCESSOR_TYPE <> 'CP'; | Set MSU_4HRA to null in table MVSPM_LPAR_H for all rows where it should not have been collected, using the provided SQL statement as template. Only run this SQL script if you have previously applied APAR PM61917 to add column MSU_4HRA. |
| z/OS System (MVS) | PM30613 | N | DRLJMVPH | Correct values in the MVS_7700_HBA_* tables. |
| PM89335 | Y | DRLJMVAM (see note below) | Change primary key of table MVS_ACCNT_PGM_T. | |
| PI17092 | N | UPDATE &PREFIX.MVS_LPAR_D SET MSU_4HRA = NULL WHERE FROM_LPAR_NO <> LPAR_NO OR PROCESSOR_TYPE <> 'CP'; | Set MSU_4HRA to null in tables MVS_LPAR_D and MVS_LPAR_M for all rows where it should not have been collected, using the provided SQL statement as template. Only run this SQL script if you have previously applied APAR PM61917 to add column MSU_4HRA. | |
| PI20342 | N | DRLJMVOM | Swap contents of column SYSCALL_NUMBER and CPU_TIME of tables MVS_OMVSADDR_T and MVS_OMVSADIS_T. |
Note: Step3 of DRLJMVAM will result in RC8 due to existing objects. Member DRLTMVAP is executed to recreate table MVS_ACCNT_PGM_T. However, DRLTMVAP also contains the definition for table MVS_ACCNT23_PGM_T. If the RC8 in Step3 is due to the fact that MVS_ACCNT23_PGM_T exists already, you can ignore this return code. RC8 in Step3 will not halt the execution of this job.
Step 2.10: Re-install components
Now re-install ALL previously installed components.
Step 2.11: Migrate the Usage and Accounting Collector
This step is only required if you make use of the Usage and Accounting Collector.
- The UAC CICS dictionary must be rebuilt if you have not previously applied all of these APARs to Version 1.8.1:
PM13229 PM63035 PM69394 PM98973 PI40948 PI88656
Refer to the IBM Z Decision Support Usage and Accounting Collector User Guide (Chapter 7: Dictionary - CIMSDTVS) for information on rebuilding the dictionary using the dictionary utility DRLCDTLD.
- If you have not previously applied APAR PI26707 to Version 1.8.1:
If you want to create DRLCUNIV Chargeback Records from IDMS v18 or higher SMF records, you must provide an additional control statement to identify that DRLCUN01 is processing an IDMS v18 or higher SMF log.The control statement is IDMS SMF18 REC.
Step 2.12: Migrate the IMS light feature
This step is only required if you make use of the IMS light feature.
IBM Z Decision Support Version 1.9.0 includes changes to the IMS Shared Queue Feature log procedures via the following APARS:
PM22818 PM35939 PM62915 PM64657 PM68203 PM83774 PM91671 PM99061 PI17543 PI26186
PI37652 PI58473 PI58479 PI62464 PI65833 PI73790 PI81275 PI81402 PI83599
PI83741 PI84391 PI85060 PI86689 PI87432 PI87617 PI90217 PI91042 PI92782
If you have not installed all these APARs previously, and you are using the IMS light feature to collect data remotely with program DRLSLOGP for subsequent transmission and processing at a central site, you must review and re-run your customized version of sample job DRLJCSQL. The re-created light feature load library must then be re-sent to all remote sites executing DRLSLOGP.
The migration to IBM Z Decision Support Version 1.9.0Migrating to IBM Z Decision Support V190 2019-10-25.pdf is now completed.
Section 3: Migrating from Tivoli Decision Support Version 1.8.2
This section describes how to migrate to IBM Z Decision Support Version 1.9.0 from Version 1.8.2.
1. Before you migrate to IBM Z Decision Support Version 1.9.0.
Before you migrate to Version 1.9.0, follow these three steps:
Step 1.1:
It is highly recommended to take a backup of your Tivoli Decision Support database.
Step 1.2:
Apply the PTFs for the IBM Z Decision Support Version 1.9.0 APARs, following the HOLD actions:
GA APAR
• PH01716
Forward fit of Version 1.8.2 APARs
• PH04618
• PH05261
• PH05376
Migration APAR
• PH18355
This APAR is required if you are on Db2 V12 Level M504+. PH18355 makes the IBM Z Decision Support Version 1.9.0 system tables and migration jobs compatible with Db2 V12 Level M504+. You need to put on the PTF for PH18355 before you can install IBM Z Decision Support Version 1.9.0, or migrate to IBM Z Decision Support Version 1.9.0.
Step 1.3:
If you have installed IMS components, please take note of the following:
Checkpoint record data sets (records output to DD name DRLICHKO during the IMS collect process) created before migrating to IBM Z Decision Support Version 1.9.0 may not be usable as DRLICHKI input to the IMS collect after the migration is completed, and therefore these checkpoint data sets must be discarded before you migrate. In order to prevent loss of data, specify WRITEPENDING=YES on the last collect run before migrating to IBM Z Decision Support Version 1.9.0.
2. The migration process
Migrating to IBM Z Decision Support Version 1.9.0. consists of the following ten steps:
Step 2.1: SMP/E installation
Step 2.2: REBIND Db2 plans and packages
Step 2.3: Test the installation of the IBM Z Decision Support base
Step 2.4: Re-introduce customizations
Step 2.5: Review IBM Z Decision Support supplied JCL
Step 2.6: Update system tables
Step 2.7: Migrate the database
Step 2.8: Re-install components
Step 2.9: Migrate the Usage and Accounting Collector
Step 2.10: Migrate the IMS light feature
Each step is documented here in detail:
Step 2.1: SMP/E installation
Ensure that you include the IBM Z Decision Support Version 1.9.0. GA APAR PH01716 with the SMP/E installation. The SMP/E installation of the IBM Z Decision Support base and its features is described in the IBM Z Decision Support Program Directory.
Confirm that the installation completed successfully by ensuring that the following data sets and file system directory were created during SMP/E installation. The names given are defaults and might not match the names in your implementation. Check with your Systems Programmer to confirm the actual names used.
a) IBM Z Decision Support data sets
Data set name Description
DRL190.SDRLA400 OS/400
DRL190.SDRLCNTL Sample jobs and Db2 DBRM module
DRL190.SDRLDEFS Definitions of records, tables, and other objects
DRL190.SDRLEXEC REXX execs
DRL190.SDRLEXTR Authorized load modules for the SMF extractor
/usr/lpp/IBM/IDSz/v1r9m0/IBM/ USS file system directory containing tar files (referred to by SMP/E via SDRLIDM DDDEF)
DRL190.SDRLLOAD Load modules
DRL190.SDRLSKEL ISPF skeletons
DRL190.SDRLWS Workstation
*DRL190.SDRLFxxx GDDM/ICU formats
*DRL190.SDRLMxxx ISPF messages
*DRL190.SDRLPxxx ISPF panels
*DRL190.SDRLRxxx Definitions of reports
*DRL190.SDRLTxxx ISPF tables
*These are language-dependent IBM Z Decision Support data sets. The last three letters in these data set names indicate the language version: ENU for English or JPN for Japanese. For example, SDRLRENU contains the English report definition files. The corresponding Japanese version is SDRLRJPN.
b) Local data sets
Data set name Description
&HLQ.LOCAL.ADMCFORM Local GDDM Presentation Graphics Facility(GDDM-PGF) and Interactive Chart Utility (GDDM/ICU) formats
&HLQ.LOCAL.CHARTS Saved graphic reports (GDDM ADMGDF format)
&HLQ.LOCAL.CNTL Local IBM Z Decision Support jobs
&HLQ.LOCAL.DEFS Local IBM Z Decision Support definitions
&HLQ.LOCAL.EXEC Local IBM Z Decision Support execs
&HLQ.LOCAL.MESSAGES Messages sent through the dialog
&HLQ.LOCAL.REPORTS Saved tabular reports
&HLQ.LOCAL.USER.DEFS Local IBM Z Decision Support user/alter definitions
Step 2.2: REBIND Db2 plans and packages
A new DBRM is supplied with IBM Z Decision Support Version 1.9.0. Follow these instructions to rebind to the new DBRM:
1. Copy member DRLJDBND in the DRL190.SDRLCNTL library to the &HLQ.LOCAL.CNTL library.
2. Review and action the customization instructions in the job prolog, before submitting the job.
Step 2.3: Test the installation of the IBM Z Decision Support base
Ensure the migration environment refers to the IBM Z Decision Support Version 1.9.0 data sets. For more information, see "Preparing the dialog and updating the dialog profile" in the Administration Guide and Reference.
Install the Sample component, collect the Sample log and run the Sample report to verify that the IBM Z Decision Support base is operational.
Step 2.4: Re-introduce customizations
If you have previously made changes to Tivoli Decision Support supplied objects in your &HLQ.LOCAL.DEFS, you will need to manually apply the IBM Z Decision Support Version 1.9.0. changes to these objects in your &HLQ.LOCAL.DEFS. Identify the Version 1.9.0 changes by comparing each object in your &HLQ.LOCAL.DEFS with the DRL190.SDRLDEFS version.
If an object exists in the &HLQ.LOCAL.DEFS library, IBM Z Decision Support installs the object from this customized definition, instead of from the shipped DRL190.SDRLDEFS version. Therefore, if you do not take the action described in this step, the Version 1.9.0. changes will not be installed when you re-install the components.
Step 2.5: Review IBM Z Decision Support supplied JCL
The DRL190.SDRLCNTL library contains several batch jobs that you can copy to &HLQ.LOCAL.CNTL and customize to match your installation.
If you have previously customized sample JCL from DRL182.SDRLCNTL, review the Version 1.9.0 changes in the new sample JCL provided in DRL190.SDRLCNTL and manually apply these changes to your customized versions in &HLQ.LOCAL.CNTL.
Step 2.6: Update system tables
Follow these steps to update the system tables using the IBM Z Decision Support dialog:
a) Invoke the IBM Z Decision Support dialog with this command: TSO %DRLEINIT [RESET]
b) Display the Administration window by selecting 2 (Administration) on the Primary Menu.
c) From the Administration window select 1 (System) to display the System window.
d) From the System window select 2 (System tables).
e) From the System Tables window press F6 to update the system tables.
Step 2.7: Migrate the database
The following table lists all database migration tasks which may be required to migrate to Version 1.9.0. Review each step, to determine whether it would be required, based on your current Tivoli Decision Support.
Migration tasks are listed by Component. The APAR column lists the Version 1.8.2 APARs with which the migration task was introduced. A migration task is only required if:
- You have previously installed the impacted Component, and
- You have not previously installed the APAR in Version 1.8.2., and
- Your installation meets the additional requirements detailed in the Description column.
For example, if you have the Db2 component installed, and you have not previously installed the PTFs for PI64117, you should consider running the SQL statements provided to improve your data quality.
The Mandatory column indicates whether the migration task is mandatory or optional. Optional migration tasks improve the accuracy/quality of data previously collected. Mandatory migration tasks are needed to make your database compatible with the IBM Z Decision Support Version 1.9.0. definitions.
The Migration instructions column contains either a sample migration job which is supplied in the DRL190.SDRLCNTL library, or actual migration instructions, for example SQL statements.
| Component | APAR | Mandatory Y/N | Migration instructions | Description |
| --- | PI26707 PI71656 | N | DRLJDCVM | Update system views ON THE Db2 CATALOG to make it compatible with Db2 Version 10+. This task is only required if you want to display the system views using the System Tables List panel (DRLDASYT). |
| CICS Monitoring & Key Performance Metrics - CICS | PI47090 PI82173 | Y | DRLJCIF1 | Rebuild the CICS_FIELD table. If this table has been customized (member DRLTCIFI), these customizations must be re-applied before you run this migration job. See step 2.4 above for instructions on reintroducing customizations. Although this job only needs to be run once during the migration, it needs to be run if the PTFs for either of these two APARs have not previously been applied. |
| Db2 | PI64117 | N | SQL UPDATE &PREFIX.Db2_IDAA_STAT_H SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; SQL UPDATE &PREFIX.Db2_IDAA_STAT_D SET DISK_INUSE_AVG_PCT = DISK_INUSE_AVG_PCT/100 WHERE DISK_INUSE_AVG_PCT <> -1; | Convert value in column DISK_INUSE_AVG_PCT of tables Db2_IDAA_STAT_H and Db2_IDAA_STAT_D to a percentage value. |
| Key Performance Metrics - IMS | PI73517 | N | 1. Copy the following members to your &HLQ.LOCAL.DEFS: | This task is only required if you want to collect IMS Application Tracing Facility (ATF) SUMMARY records. The IMS ATF record type is user-defined. IBM Z Decision Support maps these records with a default record type of 160 (X'A0'). |
| Tivoli Workload Scheduler for z/OS (OPC) | PI67891 | Y | DRLJOPT2 | Add the new column OPERATION_NUMBER with a default of 0 as a primary key of table OPC_OPER_EVENT_T. |
Step 2.8: Re-install components
Now re-install ALL previously installed components.
Step 2.9: Migrate the Usage and Accounting Collector
This step is only required if you make use of the Usage and Accounting Collector.
The UAC CICS dictionary must be rebuilt if you have not previously applied both these APARs to Version 1.8.2:
PI40948
PI88656
Refer to the IBM Z Decision Support Usage and Accounting Collector User Guide (Chapter 7: Dictionary - CIMSDTVS) for information on rebuilding the dictionary using the dictionary utility DRLCDTLD.
Step 2.10: Migrate the IMS light feature
This step is only required if you make use of the IMS light feature.
IBM Z Decision Support Version 1.9.0 includes changes to the IMS Shared Queue Feature log procedures via the following APARS:
PI37652 PI58473 PI58479 PI62464 PI65833 PI73790 PI81275 PI81402 PI83599
PI83741 PI84391 PI85060 PI86689 PI87432 PI87617 PI90217 PI91042 PI92782
If you have not installed all these APARs previously, and you are using the IMS light feature to collect data remotely with program DRLSLOGP for subsequent transmission and processing at a central site, you must review and re-run your customized version of sample job DRLJCSQL. The re-created light feature load library must then be re-sent to all remote sites executing DRLSLOGP.
The migration to IBM Z Decision Support Version 1.9.0 is now completed.
Related Information
Product Synonym
Tivoli Decision Support for z/OS
Was this topic helpful?
Document Information
Modified date:
03 December 2019
UID
ibm10731075