PPADB2 Explain connection error after FL510 Maintenance was applied.
search cancel

PPADB2 Explain connection error after FL510 Maintenance was applied.

book

Article ID: 246116

calendar_today

Updated On:

Products

Plan Analyzer for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction

After moving a DB2 V12 subsystem from FL503 to FL510 explain batch job step gets following error.

.CONNECT DSN8                                                          
PTIDB2-CAF: DB2 CONNECT ERR:DSN8 V12R1M510  mismatch SSIDVERF=V12R1M503
 BPA0010E: CONNECTION TO DB2 SSID DSN8 HAS FAILED USING PLAN: RBPAR20. 
RETCODE =     8                                                        

The zparm applcompat is still at 503.  SSIDVERF & SSIDVERC were updated to 510 and plans rebound but it still doesn't work.  The  bind job has applcompat 500 for some reason when executed and that's what the RBP* plan shows in catalog. 

 

Environment

Release : 20.0

Component : Plan Analyzer for DB2 for z/OS

Resolution

PTIDB2-CAF: DB2 CONNECT ERR:DSN8 V12R1M510  mismatch SSIDVERF=V12R1M503

Based on the -DISPLAY GROUP:

CATALOG LEVEL(V12R1M509)

CURRENT FUNCTION LEVEL(V12R1M510)

and the following message" PP011E: A thread to the specified DB2 subsystem could not be established. RC=221,RCODE=0000,DB2 CONNECT ERR:DSN8 V12R1M510 mismatch" it appears the following was specified SSIDVERF(V12R1M509) instead of SIDVERF(V12R1M510) along with SSIDVERC(V12R1M509).