Abend RCM00011: DB2 connection error: $CTDIR LOCVER error. Request fail RC=00000008 RS=00000014

book

Article ID: 103629

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

In the process of upgrading R19 CA Database Management for DB2 for Z/OS suite to a new maintenance level the first job ssid0000 fails in step COMPRT in ssid0000: DB2 connection error $CTDIR LOCVER error. Request fail RC=00000008 RS=00000014.


 

Cause

In many previous cases with more than one PTXMAN running on different maintenance levels, Xmanager caused the problem because it was not running at the SAME maintenance level. Such a situation can cause unpredictable results like the : $CTDIR LOCVER error.

 

Environment

DB2 for Z/OS

Resolution

The xmanager in use was already pointing to the updated CDBALOAD library. Customer has two PTXMAN's running one for current maintenance level and the other on the updated maintenance level pointing them to a different XMANID. The XSYS value was changed to XSYS=N on the updated PTXMAN level and was able to complete the ssid0000 job. Until the new maintenance level is installed in all environments this same setting should be maintained.

Stopping and Starting the Xmanager started task and changing the value of XSYS=Y to XSYS=N after making sure that the CDBALOAD library being used is the updated one often solves the problem.

Additional Information

Prepare the Xmanager Started Task Procedure

See section XSYS(Y|N)

Note: When XSYS=Y, we recommend that the involved Xmanagers use the same load library so they are at the same maintenance level. If the Xmanagers are at different maintenance levels, you must access data from the local Xmanager. The maintenance mismatch can potentially result in the display of user values that are inaccurate, an unexpected user abend, or both.