CA Database Management for Db2 for z/os: Different DB2 Connection types during one TSO session
Article ID: 191108
Updated On:
Products
Database Management for DB2 for z/OS - Administration Suite
Issue/Introduction
With parameter CONNECT(AUTO) in SETUP00 this error is seen when executing some DDL using CA Batch Processor:
PTIDB2-CAF: ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE
BPA0010E: CONNECTION TO DB2 SSID SDGA HAS FAILED USING PLAN: RBPAPLAN
With CONNECT(AUTO) in CDBAPARM(SETUP00).
A split screen is being used in ISPF:
1) In the first screen an IBM Db2 Administration tool is opened
2) in second an ISQL session will execute some DDL with CA Batch Processor
In the ISQL session this error is received when CA Batch Processor is executing:
PTIDB2-CAF: ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE
BPA0010E: CONNECTION TO DB2 SSID ssid HAS FAILED USING PLAN: RBPAPLAN.
with CONNECT(CAF) in CDBAPARM(SETUP00) the same error is not seen.
PTIDB2-CAF: ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE
BPA0010E: CONNECTION TO DB2 SSID SDGA HAS FAILED USING PLAN: RBPAPLAN
With CONNECT(AUTO) in CDBAPARM(SETUP00).
A split screen is being used in ISPF:
1) In the first screen an IBM Db2 Administration tool is opened
2) in second an ISQL session will execute some DDL with CA Batch Processor
In the ISQL session this error is received when CA Batch Processor is executing:
PTIDB2-CAF: ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE
BPA0010E: CONNECTION TO DB2 SSID ssid HAS FAILED USING PLAN: RBPAPLAN.
with CONNECT(CAF) in CDBAPARM(SETUP00) the same error is not seen.
Environment
DB2 for Z/OS
Resolution
Regarding the split screen situation where two utilities are accessing DB2 the IBM documentation states:
https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/apsg/src/tpc/db2z_connectapplication.html
Note the "Requirement" box.
"Different attachment facilities cannot be active concurrently within the same address space. Specifically, the following requirements exist:
An application must not use CAF or RRSAF in an CICS or IMS address space.
An application that runs in an address space that has a CAF connection to Db2 cannot connect to Db2 by using RRSAF.
An application that runs in an address space that has an RRSAF connection to Db2 cannot connect to Db2 by using CAF.
An application cannot invoke the z/OS AXSET macro after executing the CAF CONNECT call and before executing the CAF DISCONNECT call."
So, in this case the IBM DB2 Admin tool is using a CAF connection. The Db2 connection type, CONNECT(AUTO) is the parameter option that enables the CA Database Management Solutions for DB2 for z/OS to switch to RRSAF as required.
As the Db2 Admin Tool is using CAF and CA Batch Processor is using RRSAF, the problem of simultaneous accesses (CAF and RRSAF) is the reason for the PTIDB2-CAF.
When the user has CONNECT (AUTO) in SETUPxx and does not have a split screen(no other application running) the ISQL / Batch processor does not have a problem with the RRSAF setting being used.
https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/apsg/src/tpc/db2z_connectapplication.html
Note the "Requirement" box.
"Different attachment facilities cannot be active concurrently within the same address space. Specifically, the following requirements exist:
An application must not use CAF or RRSAF in an CICS or IMS address space.
An application that runs in an address space that has a CAF connection to Db2 cannot connect to Db2 by using RRSAF.
An application that runs in an address space that has an RRSAF connection to Db2 cannot connect to Db2 by using CAF.
An application cannot invoke the z/OS AXSET macro after executing the CAF CONNECT call and before executing the CAF DISCONNECT call."
So, in this case the IBM DB2 Admin tool is using a CAF connection. The Db2 connection type, CONNECT(AUTO) is the parameter option that enables the CA Database Management Solutions for DB2 for z/OS to switch to RRSAF as required.
As the Db2 Admin Tool is using CAF and CA Batch Processor is using RRSAF, the problem of simultaneous accesses (CAF and RRSAF) is the reason for the PTIDB2-CAF.
When the user has CONNECT (AUTO) in SETUPxx and does not have a split screen(no other application running) the ISQL / Batch processor does not have a problem with the RRSAF setting being used.
Additional Information
Connections to DB2 for application programs.
RRSAF Authorization in the CA Database Management Solutions for DB2 for z/OS
"Update the hlq.CDBAPARM(SETUPxx) member to specify AUTO for the Db2 connection type, CONNECT(AUTO). This parameter option enables the CA Database Management Solutions for DB2 for z/OS to switch to RRSAF as required."
RRSAF Authorization in the CA Database Management Solutions for DB2 for z/OS
"Update the hlq.CDBAPARM(SETUPxx) member to specify AUTO for the Db2 connection type, CONNECT(AUTO). This parameter option enables the CA Database Management Solutions for DB2 for z/OS to switch to RRSAF as required."
Feedback
Yes
No
Powered by
