Message PDT0137 ERROR UPDATING DATASTORE CONTROL INFORMATION REASON=BAD RBA DSID=nn DB2=ssid

book

Article ID: 50803

calendar_today

Updated On:

Products

CA RC Compare for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer 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

Description:

Xmanager receives message- PDT0137 ERROR UPDATING DATASTORE CONTROL INFORMATION REASON=BAD RBA DSID=nn DB2=ssid

Can you tell me about this error? What caused it? What do we have to do to correct it?

Solution:

PDT0137 ERROR UPDATING DATASTORE CONTROL INFORMATION REASON=BAD RBA DSID=nn
DB2=ssid

Where DSID=data store number

Possible values for the data store number variable are:

  1. Standard collection data store. (DTR0001)
  2. Dynamic SQL collection data store. (DTR0002)
  3. SQL error collection data store. (DTR0003)

In r11.5, a module was changed to check for RBA=0 prior to writing a data record to DTR0001 and to validate the Control record before it is re-written. If either validation fails, message PDT0137 is issued to record the error. Instead of overlaying the control record, message PDT0137 will be issued and will skip the bad record. The PDT0137 message is issued as a warning when a bad RBA is encountered. As a consequence, some data maybe lost. The reason could be the cause of an incorrect file. If the message is persistent, then a new control file should be created.

For more information regarding the Detector control file, reference - CA Detector for DB2 for z/OS User Guide.

Environment

Release:
Component: PXM