Why do I get DB05108I COVERED DATA RESET message?

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Introduction: 

I modified a table on an existing database which has an area defined as COVERED. When the CICS URT was reopened, I got the following message:

DB05108I - COVERED DATA RESET, BASE - nnn

Question: 

What does DB05108I mean and is there any impact or concern?

Answer: 

There is no impact or concern. DB05108I is expected when the database is not optimized (i.e. there is no ACCESS OPTIMIZE card for that database).

Additional Information:

Refer to the CA Datacom® Messages guide which defines DB05108I as follows:

DB05108I

COVERED DATA RESET, BASE - nnnn

Reason:

This message occurs in a Multi-User Facility when a database with one or more covered areas is opened and the complete covered memory buffers for this database need to be cleared. This occurs each time a table in the database is being opened and the status of the database in memory is not currently open with update intent. When using the MUF startup option ACCESS OPTIMIZE, the update intent is for all opens and also the time when no User Requirements Table is open, but the database has not been closed. In a MUFplex Multi-User Facility, the message also occurs whenever the base goes from a STOPPED state to a STARTED state (see message DB05109I).

Action:

None. This message is for information only.

Environment

Release:
Component: DB