Version 14.0 › CA Datacom Tools Products › Enhancements to the Previous Release › PDCs for CA Datacom SQL

PDCs for CA Datacom SQL

APAR: RI33540 Solution 98 (z/OS and z/VSE)

For the SQL code -316, this solution replaced the existing Explanation section with the following text:

Explanation: The indicated column reference in an ON clause refers to a column in a table that may be accessed after the join of the ON clause. Column references in predicates of the ON clause must refer to the tables in the ON clause or tables that must to be accessed before the join of the ON clause due to the order of the INNER or LEFT joins. Tables in the FROM list separated by commas may be joined in a different order than written to provide the lowest possible cost of execution.

The following are examples of queries that will result in the -316 SQL code:

Example 1: Join order may change such that T1 is read after the join of T3 and T4.

select count(*)
from sql_status T1, sql_status T2,
(sql_status T3 left join sql_status T4
on T1.urts = 1)
;

Example 2: T4 has not been read before the join of T1 and T2.

select count(*)
from (sql_status T1 left join sql_status T2 on T4.urts = 1)
left join
(sql_status T3 left join sql_status T4)

APAR: RI33608 Solution 99 (z/OS and z/VSE)

This PDC updated CA Technologies recommendation on the Multi-User Facility (MUF) startup option, SQL_OPTIMIZATION_LEVEL.

There are three updates in this PDC:

• Add documentation on the SQL_OPTIMIZATION_LEVEL MUF startup option CA Datacom/DB Database and System Administration Guide. It was previously omitted.
• Update the recommended value for SQL_OPTIMIZATION_LEVEL in CA Datacom Release Notes.
• Update the recommended value for SQL_OPTIMIZATION_LEVEL in CA Datacom/DB Database and System Administration Guide.

APAR: RI23690 Solution 153

If your COBOL compiler supports 'OPTION PGMN(LM)' and you use a program name longer than 8 bytes, this Product Documentation Change applies to you.

Replace the current content for message DB21020E in the CA Datacom/DB Message Reference Guide Version 12.0.00 with the following:

DB21020E PROGRAM-ID > 32 CHARACTERS

APAR: RI23690 Solution 153

There is a need to set SQLDATA and SQLIND in SQLVAR to address of host variable, but COBOL does not allow these fields to be declared as pointer variables. DBXHAPR is only for COBOL programs using dynamic SQL. COBOL does not allow the SQLDATA and SQLIND fields to be declared as pointer variables. When you nevertheless need to set them to the address of host variables in SQLVAR, follow these steps:

1. Link DBXHAPR to the OBJLIB that is being used by adding the following to your COBOL programs:

   CALL 'DBXHAPR' USING <SQLDATA>, <host-var>.

2. Set the address of each SQLDATA and SQLIND field used before SQLDA with the following in the linkedit step:

   INCLUDE OBJLIB(DBXHAPR)

Changes from the Previous Release

CA Dataquery

Beginning with Version 14.0, the CA Dataquery Report Facility is no longer distributed as part of the product. You may want to use the CA Datacom/DB Reporting Facility, CA Datacom SQL queries or other facilities instead.