VERSION 12€¦ · because environments are different. When migrating these changes to production, DB2 may choose different access paths, costs, etc. TurboTuneSQL-VIRT will address

TurboTuneSQL-VIRT

VERSION 12.0

DB2 ENVIRONMENT VIRTUALIZATION

USER GUIDE

User Guide Manual

TurboTuneSQL-VIRT V120 – User Guide – 2019. All Rights Reserved.

Preface

This document “as is” without warranty of any kind, including without limitation, anyimplied warranties of merchantability, fitness for a particular purpose or non-infringement. In no event we will be liable to the end user or any third party for any lossor damage, direct or indirect, from the use of this document, including withoutlimitation, lost profits, business interruption, goodwill, or lost data.

This publication may be changed to describe product changes available via fixes orfuture releases or to correct inadvertent misrepresentations. This publication couldinclude technical or typographical errors and this may make changes in the productsdescribed in TurboTuneSQL documentation. Always consult your local softwarerepresentative for updates to this material.

If license period terminates for any reason, it’s the user’s responsibility to have thisdocument destroyed.

This document may not be copied, transferred, reproduced, disclosed or duplicated, inwhole or in part, without the prior written consent of RALPHJCASTALDI.

© Copyright RALPHJCASTALDI, 2007-2019

Trademark Acknowledgments

The following are trademarks or registered trademarks of IBM Corporation: CICS, DB2,DFSMSdfp, IMS, Language Environment, MQSeries, MVS, z/OS, OS/390.

Microsoft Windows and the Windows logo are trademarks of Microsoft Corporation inthe United States, other countries, or both.

Java is a trademark of Oracle in the United States, other countries, or both. BMC is atrademark of BMC Software, Inc. The CA brand is a trademark of Computer Associates.

Other product and company names mentioned herein may be the trademarks orregistered trademarks of their respective owners.

Related Documents

Related documents: TurboTuneSQL-VIRT User Guide TurboTuneSQL-Installation Guide TurboTuneSQL-User Guide TurboTuneSQL-Messages Guide

Revision: 2019-OCT-31 (CHANGE X0560)


2

Chapter 1. Introduction

We know that every business needs to reduce costs and to launch new products inshort time and to spans. The availability and quality of those application systems mustalso be constantly improved. But continual business changeovers alter the systemusage which generates degradation in IT production. These constant changes areassociated to new failures.

There is constant pressure to reduce IT costs. Changes in development to improveperformance not always have the same behavior when migrating to productionbecause environments are different. When migrating these changes to production,DB2 may choose different access paths, costs, etc.

TurboTuneSQL-VIRT will address these issues because it can help DBAs to guaranteethat SQL commands in development environment will have the same behavior inproduction.

What is DB2 access path?

Access Path is the method created by DB2 to solve how data will be retrieved (sort,index, etc).

DB2 always try to create the best Access Path. This allows SQLs statements to beexecuted in the shortest time.

Access Paths are very important. They must be monitored to avoid performanceproblems!

DBAs always monitor Access Paths in development environment. DBAs and SQLanalysis tools are performed in this environment to avoid accessing production due tosecurity issues, etc.

DB2 SQL path analysis in development environment are reliable? Do they reflectproduction environment? The answer is NO!!!

The results of a DB2 explains done in DB2 development environment may not reflectthe same Access Path behavior as in production environment.

In order to create Access Paths, DB2 optimizer will check:– Table statistics;– Total number of processors;– Processor speed;– Total available memory;– DSNZPARM parameters.


3

How DB2 Optimizer works

The figure above shows how DB2 Optimizer works.

Before selecting an Access Path and populating the DB2 Plan Tables, it will take inconsideration System Parameters, DB2 System Parameters, Statistics, DDL Definitions andseveral details about the SQL, like predicates, sort, etc.

What is TurboTuneSQL-VIRT

TurboTuneSQL-VIRT offers a solution to perform environment virtualization so thatDBAs (and tools) are confident that when the SQL is migrated to production, it will havethe same costs, access path, etc as shown in development environment.

With TurboTuneSQL-VIRT, explain commands in development environment will havingthe same behavior as if the explain commands were executed in productionenvironment.

Today, without environment virtualization, DBAs do not have a way to guarantee thatSQLs explained in development environment will have the same behavior in productionenvironment. This sometimes is critical and may lead to serious performance problemswhen migrating programs to production.

This product should and can be used to guarantee the quality of SQLs when migratingSQLs from development to production environments; SQLs will have the same accesspath in both environments.


4

TurboTuneSQL-VIRT basic points are: Non intrusiveness / Transparency Automatically copy DB2 profiles from one environment to another Easy to manipulate DB2 profiles Buffer pool automatic profile configuration Remote compare facility

Non intrusiveness / Transparency

Non intrusiveness: it means TurboTuneSQL-VIRT does not create hooks into the DB2system. Only normal DB2 APIs are used. This is a very important point to consider whenrunning tools on heavy production systems.

Transparency: access Paths are very important. they must be monitored to avoidperformance problems! SQL Analysis tools, DBAs and performance analysts arecontinually examining access path using DB2 explain facility. TurboTuneSQL-VIRT istransparent solution: when active, explain results will be the same as in production,does not matter which solution was used to execute DB2 explain command.

Therefore your current existing SQL analysis Tool installed on development will producemore reliable results.

Automatically copy DB2 profiles from one environment to another

TurboTuneSQL-VIRT allows DBAs to execute batch procedures to automaticallyvirtualize (copy) DB2 environments. Changes are automatically synchronized betweenenvironments using batch jobs. You do not need to worry about regular DB2 changesand machines (new buffer pools, new processor, etc).

TurboTuneSQL-VIRT will provide batch jobs to copy DB2 parameters and environmentvariables from one DB2 subsystem to another DB2 subsystem. Example: copy DB2parameters and environment variables from production system to DB2 in thedevelopment system.

DB2 subsystem parameters (DSNZPARM) will never be automatically changed byTurboTuneSQL-VIRT. Only DB2 profiles are manipulated. .

These jobs can be automated using scheduler to guarantee that data will be alwaysupdate to date.

Easy to manipulate DB2 profiles

DB2 environments can be modeled using DB2 profile tables (shortly speaking:DSN_PROFILE_TABLES). DB2 profiles tables were introduced in DB2 V9. Example ofcapabilities of DB2 profiles:

– Modeling your production environment in test for EXPLAIN– Monitoring remote threads and remote connections (TCP/IP)– Setting or disabling optimization parameters for SQL statements– Managing copies of SQL access paths– Setting thresholds for Query Acceleration – IDAA

TurboTuneSQL-VIRT allows DBAs to query, create and update specific DB2 profilesattributes.

Only profile attributes related to DB2 environment modeling are manipulated byTurboTuneSQL-VIRT.


5

Buffer pool automatic profile configuration

DB2 buffer pools can be automatically configured using remote DB2 as input.

Compare facility

TurboTuneSQL-VIRT has a unique facility to automatically compare several importantaspects of DB2 environment virtualization related to access paths.

TurboTuneSQL-VIRT can compare:– DB2 DSNZPARM parameters related to access path– DB2 Profile data – Buffer pools– Machine environment variables (processor speedy, number of processors, etc).

Benefits using TurboTuneSQL-VIRT

There are very important benefits using TurboTuneSQL-VIRT. Examples:– Increase the stability of your production environment;– No more access paths surprises;– Improve the effectiveness of your current existing SQL analysis tools (it will providemore reliable results);– Transparent solution: no changes;– MIPS savings: Reliable results represents more MIPS being saved and reduceanalysis made in production, saving time and cpu in this expensive environment.

Security Implementation

TurboTuneSQL-VIRT always relies on DB2 security mechanisms.

Some examples of security implementation that can be done to protect yourenvironment:

Authorize TurboTuneSQL DB2 Plan only for people able to use TurboTuneSQL ISPF application.

Create 2 TurboTuneSQL Plan tables. One for batch use and anotherspecifically to use in TurboTuneSQL ISPF application. So batch operators willnot have access to ISPF application.

Use RACF or another facility to protect TurboTuneSQL libraries

Maintain TurboTuneSQL-VIRT

TurboTuneSQL-VIRT is a DB2 application. So, like any other application, you mustalways perform RUNSTATS and rebind your TurboTuneSQL tables and packages. Thereare some sample jobs provided by the product to execute these tasks J000REBI,J000REOR, J000RNST.

Consult TurboTuneSQL-VIRT Installation Guide for more information.

Another point: you must ALWAYS backup TurboTuneSQL tables.

Also, you must look for new fixes at least each 6 months to maintain you system up todate. Check How to apply fixes to TurboTuneSQL for more details.


6


7

Chapter 2. Using TurboTuneSQL-VIRT

TurboTuneSQL-VIRT can improve the accuracy of access path testing by modeling theconfiguration and settings of a production environment in a test subsystem.

This chapter guide to use TurboTuneSQL-VIRT. It was divided in:

o Start TurboTuneSQL-VIRT o Customize TurboTuneSQL Profile o Using TurboTuneSQL-VIRT

Create batch jobs to generate profiles using other subsystems Manage DB2 Profiles Create or update a DB2 Profile ZPARM EDIT ZPARM RELOAD Execute DB2 command


8

Start TurboTuneSQL-VIRT

To start TurboTuneSQL-VIRT, execute the following TSO command:

TSO EX '<TurboTuneSQL.SADVCLST data set.SSID>(START)'

SAMPLE SCREEN

The above screen is the main menu of TurboTuneSQL.

Choose option 3 (ENVIRONMENT VIRTUALIZATION).

SAMPLE SCREEN


9

TurboTuneSQL V120 --------------- MAIN MENU ----------------------------- 15:36 Option ===> Profile : IVP {E} 0 - TurboTuneSQL PROFILE DB2 SSID : DBBG 1 - SQL REAL TIME MONITOR User ID : IBMUSER Time : 15:36 2 - MANAGING COPY OF CATALOG STATISTICS Language : English Tso Logon: DBSPROCB 3 - ENVIRONMENT VIRTUALIZATION System Id: S0W1 MVS Acct : ACCT# 4 - SQL INVENTORY AND WORKLOAD Appl Id : SADV 5 - MANAGING INDEX RECOMMENDATIONS Term CCSID: 00037 Prof CCSID: 00037 Customer Name: CRITICAL PATH SOFTWARE

TurboTuneSQL V120 ------------ ENVIRONMENT VIRTUALIZATION --------------- 15:40 Option ===> Profile : IVP {E} DB2 SSID : DBBG 1 - Jobs to copy profiles from other systems User ID : IBMUSER Time : 15:40 2 - Manage DB2 Profiles Language : English Tso Logon: DBSPROCB 3 - ZPARM edit System Id: S0W1 MVS Acct : ACCT# 4 - ZPARM reload Appl Id : SADV Term CCSID: 00037 Prof CCSID: 00037 Customer Name: CRITICAL PATH SOFTWARE

For more information about TurboTuneSQL for DB2 product, please refer toTurboTuneSQL documentation.

There are several Online Commands that you can use to speed up screen navigation.Check Appendix Online Command for more details.

In the main menu of TurboTuneSQL-VIRT you can see screen name (Main Menu),TurboTuneSQL Profile name (IVP), Edit Mode (the above figure shows that currentprofile are in Edit Mode {E}) and connected SSID (DB9G). Customer name is taken fromthe product password file.

Note: To avoid terminal wrong input/output data, fields Term CCSID (terminal CCSID)and Profile CCSID number (obtained from TurboTuneSQL Profile) should show samenumbers. If numbers does not match, message 'MAIN05' will appear.


10

Customize TurboTuneSQL Profile

TurboTuneSQL products are configured using TurboTuneSQL Profiles. If you haveseveral TurboTuneSQL products, they can share the same TurboTuneSQL Profile.

It contains parameters used by TurboTuneSQL products in both batch and online mode.Almost of all data entered by the user are saved into TurboTuneSQL Profile.

An TurboTuneSQL Profile is a member of PDS data set. Any PDS data set withLRECL=80 and RECFM=FB can be used.

For more information, please consult TurboTuneSQL-User Guide.


11

Using TurboTuneSQL-VIRT

Here we will explain how to use TurboTuneSQL-VIRT.

Create batch jobs to generate profiles using other subsystems

Use this option to automatically copy DB2 access path variables from the source DB2subsystem to the target DB2 subsystem using batch jobs.

SAMPLE SCREEN


12

TurboTuneSQL V120 -------------- Create profiles in Batch --------------- 15:42 Option ===> FILL IN THE INFORMATIONS BELOW AND TYPE "JCL" TO GENERATE JOBS More: + Create profiles in Batch Profile : IVP {E} DB2 SSID : DBBG Curr Loc : DALLASB UNLOAD JOB PARAMETERS: SPECIFY SOURCE ENVIRONMENT Unload environment parameters (source DB2 subsystem) Plan Table Qualifier/Set SQLID: DB2 SSID: Plan Name : SDSNEXIT: SDSNLOAD: JOB Cards: //* //* Shared work data set Name : Unit : UNIT=SYSDA Ex.: UNIT=SYSDA Volser: Ex.: VOL=SER=(VVVV1,VVVV2), LOAD JOB PARAMETERS: SPECIFY TARGET ENVIRONMENT Profile ID to receive unloaded data: 0000000 Automatic START PROFILE after LOAD : N (Y/N) Load Target Environment Parameters ( Taken from product profile setup ) DB2 SSID: DBBG Plan Name: PLANSADV SDSNEXIT: DSNB10.DBBG.SDSNEXIT SDSNLOAD: DSNB10.SDSNLOAD JOB Cards: //JNE1 JOB 'NEW',MSGCLASS=A,CLASS=D,NOTIFY=IBMUSER, // REGION=0M //*

When you type JCL in the command line, it will generate the JCLs necessary to performthis operation. Two batch jobs will be generated:

J920VIUL: This JOB must be submitted in the source DB2 subsystem. This DB2 will provide theaccess path data to be loaded into target DB2.Normally, this JOB will be submitted in production environment.A sequential data set containing data will be created. See field Shared Work dataset. DB2 explain is used to gathering information.Authorities: - SYSADM, SYSOPR and SYSCTRL OR - EXPLAIN or SQLADM or System DBADM. - Authority to execute SET CURRENT SQLID - SELECT, DELETE, UPDATE on PLAN TABLEs - SELECT on SYSIBM.SYSDUMMY1

J921VILD: This JOB must be submitted in the target environment.

The sequential data set generated by job J920VIUL will be used as input.

A new DB2 profile id will be created (or updated) by this job. Normally this job will besubmitted in test environment.

FIELD DESCRIPTIONS

UNLOAD ENVIRONMENT PARAMETERS (source DB2 subsystem) :

JOB CARDS: Enter JOB Cards which will be used to execute the job in the source environment.

Shared Work Data set: Inform the data set name to contain the unloaded information to be loaded into the target system. Plan Table Qualifier/Set SQLID: Choose a valid qualifier for Plan Table. SQLcommand SET current SQLID command will be issued.DB2 SSID : Source DB2 SSID. PLAN NAME : Product DB2 Plan Name. DB2 VERSION: DB2 version. Valid values: V8, V9, VA, VB. Use V8 for DB2 version 8 ENFM/NFM. Use V8 for DB2 version 9 CM. Use V9 for DB2 version 9 ENFM/NFM. Use V9 for DB2 version 10 CM. Use VA for DB2 version 10 ENFM/NFM. Use VB for DB2 version 11 ENFM/NFM. SDSNEXIT : DB2 SDSNEXIT data set. SDSNLOAD : DB2 SDSNLOAD data set.

LOAD JOB PARAMETERS (target DB2 subsystem)

JOB Cards:Enter JOB Cards which will be used to execute the job in the target environment.


13

Profile ID to receive unloaded data:Profile ID that will be created (or updated) in target DB2 subsystem. Valid values: nnnnnn: Profile ID to be created (or updated) in target DB2 subsystem. 000000: Special value. If value 0 is informed, TurboTuneSQL-VIRT will automatically assign the next available Profile ID. .

Automatic Start Profile after LOAD:Y: Execute command Start Profile after profile creation. Start Profile command will be executed only if DB2 profile was successfully created. N: Do not execute command Start Profile.

Note: If Start command executes successfully, any other previous Profile ID with ACCEPTED status will be put as REJECTED by DB2. Load Target Environment Parameters (target DB2 subsystem):Informations of target DB2 parameters are taken from the TurboTuneSQL Profile setup (option 1 from main menu).


14

Manage DB2 Profiles Here you can create, update, delete or view profiles.

You can also start (or stop) profiles using an screen option.

SAMPLE SCREEN

FIELD DESCRIPTIONS

PROFILE is: Status of DB2 profile. Valid values: -ON : DB2 profile facility is enable (started) -OFF: DB2 profile facility is not enable (stopped)

You can use below option START or STOP PROFILE to change the status.

START or STOP PROFILE: Place '/' to request to issue START or STOP PROFILE DB2 command. If PROFILE is ON, STOP PROFILE DB2 command will be available. If PROFILE is OFF, START PROFILE DB2 command will be available. Notes: -If Start command executes successfully, any other previous Profile ID with ACCEPTED status will be put as REJECTED by DB2. -If you just want to refresh DB2 profiles without stop then, return to main menu and select option Execute DB2 command to execute the following DB2 command: START PROFILE.

Create new PROFILE:


15

TurboTuneSQL V120 ------------- Environment Virtualization --- Row 1 to 2 of 2 Option ===> VIRT - Manage DB2 Profiles Profile : IVP {E} DB2 SSID : DBBG Curr Loc : DALLASB PROFILE is: OFF Type '/' to request a START Profile command Create new PROFILE: Type '/' to request Line Actions ------------------------------------------------------------------ (V)View (U)Update (E)Enable (D)Disable (X)Delete (H)ViewProfHist (S)ViewAttrib ------------------------------------------------------------------------------- C Profile Ena Description Status Scp TimeStamp ID - ------- --- ----------------------- --------- --- -------------------------- 0000001 Y CLIENT IVP ACCEPTED V 2019-07-04-09.48.51.693329 0000002 Y AUTOMATIC LOADED (DBBG) ACCEPTED V 2019-08-14-08.47.51.352970 ******************************* Bottom of data ********************************

Place '/' if you want to create a new Profile. This option is only available for Modeling Environment scope.

Profile ID:Unique PROFILE Identification. Ena:Profile status is Enabled or Disable. The values can be Y (enable) or N (disable).

Description:Description or remarks of the profile.

Status:Describes the status of a PROFILE. When the Status shows N/A , it means the PROFILE was only inserted and the DB2START PROFILE command was not issued. Scp:Scope of the PROFILE.Valid values: - V: Modeling Virtualization Environment - O: Others (e.g. System Level Monitoring) - ?: Its is an incomplete profile. You can use option U to create attributes.

Timestamp:Represents the timestamp when the PROFILE was inserted.

AVAILABLE SORT FIELDS Sort Field Field Header prof Profile ID ena Enasta Status

Examples: SORT field D (sort field using descending order) SORT field A (sort field using ascending order)

AVAILABLE LINE ACTIONS(V)ViewView PROFILE parameters. Only available is for environment virtualizationprofiles. (U)Update Update PROFILE parameters. Only available is for environment virtualizationprofiles.

(E)Enable Enable a PROFILE (D)Disable Disable a PROFILE

(X)DeleteDelete DB2 PROFILE. The Delete action is available only if:

– Profile status is different from not ACCEPTED or – Profile status is ACCEPTED but general status is OFF or– Profile is not enable or– Scope '?'

(H)ViewProfHist


16

List the historical result of Start Profile command(S)ViewAttribList Profile internal attributes

Note: Line Actions are available only for Modeling Environment scope. For scope = 'O' , you can update to 'Y' or 'N' to Enable a PROFILE.


17

Create or update a DB2 Profile

Modeling Environment for Access Path.

This option allow you to create or update a DB2 profile. This option allows you tocompare the following access path environment variables:– DB2 DSNZPARM parameters related to access path– DB2 Profile data – Buffer pools– Machine environment variables (processor speedy, number of processors, etc).

SAMPLE SCREEN

Available command line:ZPARM: Edit data set to update ZPARM parameters. This is the same functionality on choosing ZPARM edit in the Menu panel.


18

TurboTuneSQL V120 ------------------- Edit DB2 Profile ------------------ 15:47 Option ===> Modeling Environment for Access Path Profile : IVP DB2 SSID : DBBG Profile ID : 0000001 Enable: Y (Y/N) General Status: NOT CHECKED Description: CLIENT IVP OPTIONAL: To automatically fill remote (and some local ) important fields, inform: LOCAL: Plan Table: REMOTE: Plan Table: Schema: Location: UPDATE SORT POOL AND RID POOL PROFILE PARAMETERS: SORT POOL RID POOL Status : N/C Status : N/C Local : Kb Local : Kb Remote : Kb Remote : Kb Profile: 64000 Kb Profile: 400000 Kb UPDATE BUFFER POOL PROFILE PARAMETERS: Type '/' to configurations: Status: N/C VIEW physical machine characteristics and relevant ZPARM configuration: CPU COUNT CPU SPEED OTHERS Status : N/C Status : N/C Status: N/C Local : Local : Type '/' to show: Remote : Remote : ZPARM-CPU-COUNT: OFF ZPARM-CPU-SPEED: 27

FIELD DESCRIPTIONS

Profile ID: Profile ID number. It may be a automatic sequenced number if option Create Batch jobswas used.

Enable: Inform Y or N to Enable or Disable a PROFILE ID. General STATUS:Show the general result of TurboTuneSQL-VIRT comparison of access path environmentvariables between local DB2 subsystem with a remote DB2 subsystem. Possible values: NOT CHECKED: Parameter could not be checked due to the lack of local and remote informations NOT OK: There is at least one check with status NOT OK WARNING: There is at least one check with STATUS WARNING OK: All checks are ok!

Description:Description or remarks of the PROFILE ID.

OPTIONAL:Optional parameters. To automatically fill some field from local and/or remote DB2, please inform:

Local Plan Table:Inform the SQLID or the local USER Plan Table Qualifier. .

DB2 version:Inform the LOCAL User Plan table layout version.

Remote Plan Table:Inform the SQLID or the REMOTE USER Plan table qualifier.

DB2 Location.Schema:Choose a valid DB2 location and inform TurboTuneSQL-VIRT Stored Procedure

schema (as informed in Bind Qualifier installation panel).

UPDATE SORT POOL AND RID POOL PROFILE PARAMETERS:Set up Rid Pool and Sort Pool attribute into DB2 profile

SortPool: Inform the SORT POOL size in kb.Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identicalN/C - Parameter could not be checked due to the lack of local and remote

informations.

RIDPool: Inform the MAX RIDPOOL BLOCKS.Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identicalN/C - Parameter could not be checked due to the lack of local and remote

informations.

Note: To delete any value from Profile, just erase the field.


19

UPDATE BUFFER POOL PROFILE PARAMETERS:Set up buffer pool attributes into DB2 Profile.

Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identicalN/C - lack of remote information for a comparison or the Bpool has remote value only WARNING - Some buffer pools are presented only in local (or remote) location

If you type '/' in option configurations, the following screen will be shown:

SAMPLE SCREEN

Here you can update Buffer pool profile attributes. Also, this option can automatically fill local DB2 profile using remote buffer pool size.

(Y/N) SYNCHRONIZE PROFILE SIZE WITH REMOTE VALUESUse this option to automatically fill local DB2 profile using as input remote buffer pool size. Available only if remote DB2 location was informed.Valid values: Y - Automatically fill buffer pool size attribute N - Do not automatically fill buffer pool size attribute

BufferPool Buffer pool name.

Buffer Pool Size Local Buffer pool size (local).


20

TurboTuneSQL V120 ------------------- Edit DB2 Parameters -- Row 1 to 12 of 12 Option ===> VIRT - UPDATE BUFFER POOL PROFILE PARAMETERS (Profile ID : 0000001 ) N (Y/N) SYNCHRONIZE PROFILE SIZE WITH REMOTE VALUES Line Actions ------------------------------------------------------------------ (U)Update ------------------------------------------------------------------------------- C BufferPool ------- Buffer Pool Size ------- Remarks Local Remote Profile - ---------- -------- -------- -------- ------------------------------- BP0 20000 20000 REMOTE LOCATION NOT INFORMED! BP1 20000 20000 REMOTE LOCATION NOT INFORMED! BP2 1500 20000 REMOTE LOCATION NOT INFORMED! BP3 20000 20000 REMOTE LOCATION NOT INFORMED! BP4 32000 REMOTE LOCATION NOT INFORMED! BP6 1500 REMOTE LOCATION NOT INFORMED! BP7 1500 REMOTE LOCATION NOT INFORMED! BP40 20000 20000 REMOTE LOCATION NOT INFORMED! BP8K0 2000 2000 REMOTE LOCATION NOT INFORMED! BP8K1 1500 REMOTE LOCATION NOT INFORMED! BP16K0 500 500 REMOTE LOCATION NOT INFORMED! BP32K 250 250 REMOTE LOCATION NOT INFORMED! ******************************* Bottom of data ********************************

Buffer Pool Size Remote Buffer pool size (remote). Available only if remote DB2 location was informed.

Buffer Pool Size Profile Buffer pool size (profile). Available only if profile contains buffer pool attributes.

Remarks Status field. This option will automatically check several conditions: – Compare buffer pool size (local, remote and profile)– Check the existence of buffer pools– etc

VIEW physical machine characteristics and relevant ZPARM configuration:These parameters are just of check. If differences are found, you must update your local ZPARM configuration.

CPU Count: Local and remote machine total number of processors are compared.Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identicalN/C - Parameters could not be checked due to the lack of local and remote

information.

CPU Speed: Local and remote machine CPU speed are compared. Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identical.N/C - Parameter could not be checked due to the lack of local and remote

information.

Others STATUS: Some DSNZPARM parameters related to DB2 access paths are compared. Valid values for STATUS check field:NOT OK - the paired comparison is different.OK - the paired comparison is identical.N/C - lack of remote information for a comparison.

If you type '/' in option show, the following screen will be appear:


21

Option ===> Other ZPARM parameters: LOCAL REMOTE NPGTHRSH: 0 0 STARJOIN: DISABLE DISABLE SJTABLES: 10 10 PARAMDEG: 0 0

This option will allow to compare local ZPARM DB2 access path parameters with remote DB2 location. The following parameters will be compared:– STARTJOIN– SJTABLES– NPGTHRSH – PARAMDEG

For more information, please consult IBM DB2 documentation.


22

View Profile History

This report will list all historical results of START PROFILE command. It can also list allhistorical profile attributes.

FIELD DESCRIPTIONS

Profile ID: Unique Profile Identification. Ena Profile in Enabled status (Y) or not Enabled (N).

Status Status of ProfileID TimeStamp This is the log timestamp.

AVAILABLE LINE ACTIONS

(V)ViewAttribHList of attributes log of the current ProfileID in history. (Z)ZoomReport ZOOM will be started (shows extended fields)


23

------------------------------- Profile History Table -------- Row 1 to 4 of 4Option ===> Profile History Table Line Actions ------------------------------------------------------------------(V)ViewAttribH (Z)Zoom -------------------------------------------------------------------------------C Profile Ena Status TimeStamp ID - ------- --- -------------------------------------- -------------------------- 0000001 Y ACCEPTED 2019-07-22-09.24.09.630281 0000001 Y ACCEPTED 2019-07-18-12.08.13.289112 0000001 Y ACCEPTED 2019-07-17-17.19.04.857854 0000001 Y ACCEPTED 2019-07-04-09.49.05.835978******************************* Bottom of data ********************************

View Profile Attributes - History

This report will list all historical profile attributes.

FIELD DESCRIPTIONSProfile ID: Unique Profile Identification.

Keyword Keyword name of the profile attributes. Value Value of the corresponding Keyword. For other scopes, this information will be zero. Status Status of the attribute. TimeStamp This is the log timestamp.

AVAILABLE LINE ACTIONS(Z)ZoomReport ZOOM will be started (shows extended fields)


24

------------------------------- Profile Attributes (History) Row 1 to 10 of 10 Option ===> Profile Attributes History Table Line Actions ------------------------------------------------------------------ (Z)Zoom ------------------------------------------------------------------------------> C Profile Keyword Value Status ID - ------- -------------- ----------- ------------------------------------------ 0000001 BP0 20000 ACCEPTED 0000001 BP1 20000 ACCEPTED 0000001 BP16K0 500 ACCEPTED 0000001 BP2 20000 ACCEPTED 0000001 BP3 20000 ACCEPTED 0000001 BP32K 250 ACCEPTED 0000001 BP40 20000 ACCEPTED 0000001 BP8K0 2000 ACCEPTED 0000001 MAX_RIDBLOCKS 12500 ACCEPTED 0000001 SORT_POOL_SIZE 65536000 ACCEPTED ******************************* Bottom of data ********************************

View Profile Attributes

This report will list all profile attributes.

FIELD DESCRIPTIONS

Profile ID: Unique Profile Identification.

Keyword Keyword name of the profile attributes. Value Value of the corresponding Keyword. For other scopes, this information will be zero. Status Status of the attribute. TimeStamp Timestamp when the attributes were inserted.


25

------------------------------- Profile Attributes --------- Row 1 to 10 of 10 Option ===> Profile Attributes Table ------------------------------------------------------------------------------- Profile Keyword Value TimeStamp ID ------- -------------- ----------- -------------------------- 0000001 BP8K0 2000 2019-07-04-09.48.51.707393 0000001 BP32K 250 2019-07-04-09.48.51.715676 0000001 BP40 20000 2019-07-04-09.48.51.722917 0000001 BP3 20000 2019-07-04-09.48.51.730065 0000001 BP2 20000 2019-07-04-09.48.51.737380 0000001 BP1 20000 2019-07-04-09.48.51.744914 0000001 BP0 20000 2019-07-04-09.48.51.752086 0000001 MAX_RIDBLOCKS 12500 2019-07-04-09.48.51.759889 0000001 SORT_POOL_SIZE 65536000 2019-07-04-09.48.51.771924 0000001 BP16K0 500 2019-07-04-09.48.51.779133 ******************************* Bottom of data ********************************

ZPARM EDIT

Option to edit DB2 ZPARM (data set SDSNSAMP, member DSNTIJUZ) Change parameters in ZPARM to the new values accordingly. Example of DB2 accesspath parameters and environment virtualization parameters are:– STARTJOIN– SJTABLES– NPGTHRSH – PARAMDEG– SIMULATED-CPU-COUNT– SIMULATED-CPU-SPEED

All parameters above are shown into Edit DB2 Profile option. All parameters above areshown into Edit DB2 Profile option. For more information, please consult IBM DB2documentation. If needed, after you have change and compile DSNZPARM, you can use ZPARM reloadoption from TurboTuneSQL-VIRT menu to refresh DB2 ZPARM parameters.

FIELD DESCRIPTIONS

SDSNSAMP data set:Inform your DB2 installation data set and DSNTIJUZ member name.e.g. DSNA10.SDSNSAMP(DSNTIJUZ).

AVAILABLE LINE COMMANDS

EDITUse this command to edit the data set.


26

Option ===> ZPARM PROCESS SDSNSAMP data set: ____________________________________________ ( ________ ) Tips: DB2 ZPARM Parameters/keywords which can be updated for the Virtualization Environment are: STARJOIN SIMULATED-CPU-COUNT SJTABLES SIMULATED-CPU-SPEED NPGTHRSH PARAMDEG Note: Use EDIT command to edit data set.

ZPARM RELOAD

Option to reload DB2 ZPARM.

If you have submitted DSNTIJUZ job, use this option to order DB2 to automaticallyreflect changed subsystem parameters.

DB2 command SET SYSPARM RELOAD will be executed.

FIELD DESCRIPTIONS

Confirm Action:Enter Y to execute set sysparm reload or N to cancel action.


27

CONFIRM ACTION Y- EXECUTE SET SYSPARM RELOAD N- DO NOT EXECUTE

Execute DB2 Command

Execute any DB2 command. Example: -dis trace(*). Notes: 1: To execute a command place cursor at command line and hit enter (or type numbers 1,2,3,4,5) 2: Only one command can be executed at a time. 3: Command results will be shown at the bottom.


28

------------------------------ DB2 command------------------------------------Option ===> More: + DB2 Commands Profile : IVP {E} DB2 SSID : DBAG (1) -DIS PROCEDURE (*.* ) Curr Loc : DALLASA (2) -DIS TRACE(*) (3) -DIS DB(*) SPACENAM(*) LIMIT(*) (4) -START TRACE(MON) CLASS(1,7,3) (5) -STOP TRACE(A) TNO(5) -------------------------------------------------------------------------------

F1=Help F2=Split F3=Exit F4=LSTREQ F5=FILTER F6=SAVE F7=Up F8=Down F9=Swap Nex F10=Left F11=Right F12=Quit

Appendix A. Online Commands

TurboTuneSQL-VIRT has several Online commands to help you navigate through theISPF online screens and also to help set up variables as a filter for online and helpreports.

Note: Not all commands are available on all screens. See specific help for more details.

DB2Perform DB2 commands. For more information, please consult TurboTuneSQL-UserGuide.

HELPOpen a Help description for the current screen. Note: F1 will activate the same function.

INFOShows applied product FIXES (Changes) and some other general information.

For more information, please consult TurboTuneSQL-User Guide

JCLShows “Create JCL” panel to inform PDS data set to create JCL for a specific function. For more information, please consult TurboTuneSQL-User Guide.

QUITAll consistency will be skipped for all fields and the previous panel is shown.

REFRESH OR REFScreen Refresh for some online Panels. Attention: You cannot use this command inOnline Reports. If you want to refresh an Online Report, please type FILTER.

RESTORERestore panel fields to their original values before entering the current panel.

SAVEAll active configurations are saved into current TurboTuneSQL Profile. Attention: SAVE is only allowed when profile is in Edit Mode {E}.

SECONTurn on security check for resources (data set update only). For more information, please consult TurboTuneSQL-User Guide.


29

SECOFFTurn off security check for resources (data set update only). For more information, please consult TurboTuneSQL-User Guide.

SORTSort fields in Online Report Panels. Use SORT blank to check all available fields for the current Panel.


30

Appendix B. How to apply fixes to TurboTuneSQL-VIRT

TurboTuneSQL CHANGE is a set of software corrections (Fix) available to modify productlibraries, like panels, skeletons, modules, etc.

For more information how to apply fixes to TurboTuneSQL, please consult TurboTuneSQL-User Guide.


31

Contact

If you have any doubts or comments, please contact your local representative.


32