PTIDB2-CAF / BPA0010E / RC=008, RCODE=0024 ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE

Article Id: 197063
Status: Published
Updated On: 01-09-2020 11:11
Products:
CA RC Compare for DB2 for z/OS , CA Database Management for DB2 for z/OS - Administration Suite , CA Endevor SCM Interface for DB2 for z/OS , CA Endevor SCM Interface for Remote DB2 for z/OS , CA RC/Extract for DB2 for z/OS , CA RC/Migrator for DB2 for z/OS , CA RC/Merger for DB2 for z/OS , CA RC/Query for DB2 for z/OS , CA RC/Secure for DB2 for z/OS , CA RC/Update for DB2 for z/OS
Issue/Introduction:

While in Split Screen on various products (SQLEASE,RC/Update/ISQL): it fails with: 

PTIDB2-CAF: ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE BPA0010E: CONNECTION TO DB2 SSID DB2X HAS FAILED USING.

BPA0010E: CONNECTION TO DB2 SSID DB2B HAS FAILED USING PLAN: RBPAR190.

These were executed on DB2V12, CATALOG LEVEL(V12R1M500), FUNCTION LEVEL(V12R1M100) on DB2 Tools R19 at Current Maintenance Levels. 

 

Environment:

Release : 19.0

Component : CA RC/Update for DB2 for z/OS

DB2 V12 

Resolution:

The CONNECT(AUTO) option is mainly used for RRSAF authorization when using Enhanced Explain function DDLFILE. Batch processor switches DB2 connection to RRSAF while executing SQL statement when CONNECT(AUTO) is specified in CDBAPARM and this looks to be the reason for the failure.

In the future Broadcom will actively work on the resolving the current CAF/RRSAF issue, it will be available in near future.

    Eliminate use of the CONNECT keyword in favor of our products determining proper behavior. 
    Force RRSAF-only usage in TSO
    Force AUTO in batch to allow mixed usage as needed

There are two known instance where connection remains active even when user gets the control back from product. One when browsing a table in RC/Edit using background fetch option along with PAUSE mode and second while using SQL editor in ISQL online.

Until the above formulated plan gets implemented, its recommended to avoid using split screen when using SQL editor in ISQL or Plan Analyzer use case when CONNECT(AUTO) is in place.