COBOL Conversion
The COBOL conversion searches for three items within the syntax of a SQL statement that are allowed in the COBOL, but are not valid SQL syntax:
-
A dash or minus in a variable name
-
Comments in the middle of the SQL statement
-
The ]] (double right square bracket) as the concatenate symbol
This conversion is only applied when the Scanner Job is added to the Job Manager window using the COBOL option under the Select Source Code page in the Add Jobs wizard.
Conversion for variable name
If a variable name contains "-" minus sign, then it will be replaced with "_".
Conversion for comment
If the 7th column of the line is an asterisk (*) then the complete line will be recognized as a line comment.
Conversion for concatenate character
If ]] (two right brackets) are used to concatenate column names, they will be replace with a +.
Original SQL statement
SELECT * FROM EMPLOYEE
* Get the department number
WHERE EMP_ID > :employee-id
AND ENAME ]] JOB = :name-job
After conversion
SELECT *
FROM EMPLOYEE -- * Get the department number
WHERE EMP_ID > :employee_id
AND ENAME || JOB = :name_job
Note: If your COBOL file has tags at the beginning of the lines of code, you need to use the Number of characters to be skipped at the beginning of every line for all files option found on the SQL Scanner tab in the Options window.
Job Manager
Quest SQL Optimizer for IBM® DB2® LUWmaximizes SQL performance by automating the manual, time-intensive and uncertain process of ensuring that SQL statements are performing as fast as possible. SQL Optimizer analyzes, rewrites, and evaluates SQL statements within multiple database objects, files, or SQL statements captured by the DB2 Event Monitor. With SQL Optimizer, you can analyze and optimize all your problem SQL from multiple sources. SQL Optimizer also provides you a complete index optimization and plan change analysis solution, from index recommendations to simulated index impact analysis, through comparison of multiple SQL access plans.
SQL Optimizer provides you with the following main modules.
SQL Optimizer (including SQL Rewrite and Generate Indexes functions)
About Job Manager
The Job Manager window provides a work area for the SQL Scanner module. It allows the addition or deletion of items to be scanned. These items, also referred to as Jobs, can be database objects, DB2 Event Monitor files/tables, text/binary files, or COBOL files.
Job Manager Window
View the Job Manager
The Job Manager window consists mainly of two components: grid and status bar.
Grid
The grid from the Job Manager window stores information on each single Job in the Group.
File / Database Object
Displays the job name and associated schema.
|
Icon |
Job Type |
|---|---|
|
|
[Schema name]Object type->Object Name |
|
|
[Schema Name]Event Monitor->Event Monitor Name |
|
|
[Schema name]Text/Binary->Path\File name |
|
|
[Schema name]COBOL->Path\File name |
Status
Displays the current Job status. This column will remain blank until the Job is scanned. It will show the total number of SQL statements found.
Valid SQL
Displays the number of valid SQL statements found in the Job. Valid SQL statements are syntactically correct statements recognized by SQL Scanner, and for which DB2 LUW can provide an access plan. Valid SQL statements are further classified as Simple, Complex and Problematic SQL statements.
Problematic SQL
Displays the number of Problematic SQL statements found.
If the Show Checked SQL figures on the Job Manager window option is selected within Options, you will notice that there are two figures, first one indicates the number of Problematic SQL that have not been checked and the other (enclosed in brackets) is the number of Problematic SQL that have been checked. The total of these two figures represents the total number of Problematic SQL statements.
Complex SQL
Displays the number of Complex SQL statements found.
If the Show Checked SQL figures on the Job Manager window option is selected within Options, you will notice that there are two figures, first one indicates the number of Complex SQL that have not been checked and the other (enclosed in brackets) is the number of Complex SQL that have been checked. The total of these two figures represents the total number of Complex SQL statements.
Simple SQL
Displays the number of Simple SQL statements found.
If the Show Checked SQL figures on the Job Manager window option is selected within Options, you will notice that there are two figures, first one indicates the number of Simple SQL that have not been checked and the other (enclosed in brackets) is the number of Simple SQL that have been checked. The total of these two figures represents the total number of Simple SQL statements.
File Size
Displays the size of the Job in bytes. This cell will show "(n/a)" for Plan Tables and DB2 Event Monitors.
Started At
Displays the start date & time of when scanning began.
Processing Time
Displays the total time taken to scan the Job, time is displays in HH24:MM:SS format.
Status Bar
| Item | Description |
|---|---|
| Data Directory | Directory path where all the data files produced during scanning are saved. The data directory path can be changed in the Options window. While scanning, a progress bar will be presented to show scanning progress. The upper bar shows the current Job progress, while the lower bar shows the total Job status. |
| Group |
Name of the currently opened Group. |
| Total Jobs |
Total number of Jobs. |
| Completed |
Total number of Jobs already scanned. |
| Remaining |
Total number of Jobs that have not been scanned. |