CA Datacom - DBCA DatacomCA Datacom - ADCA Datacom - ServerCA CISCA Common Services for z/OSCA 90s ServicesCA Database Management Solutions for DB2 for z/OSCA Common Product Services ComponentCA Common ServicesCA Datacom/ADCA ecoMeter Server Component FOCCA Easytrieve Report Generator for Common ServicesCA Infocai MaintenanceCA IPCUnicenter CA-JCLCheck Common ComponentCA Mainframe VM Product ManagerCA Chorus Software ManagerCA On Demand PortalCA Service Desk Manager - Unified Self ServiceCA PAM Client for Linux for zSeriesCA Mainframe Connector for Linux on System zCA Graphical Management InterfaceCA Web Administrator for Top SecretCA CA- Xpertware
PXX dump rc 13 (014) Duplicate Master Key produced at random.
Our MUF is still up but we would like to know why these dump are produced and how to correct it.
Job was deleting Accounting rows but these rows were not committed yet.
At the same time, new rows were added by Accounting generating RC 13(014) - Duplicate Master Key Error.
z/os, CA Datacom/DB 15.1
A way to prevent duplicate master keys on table A02 would be to close this table via accounting with console command ACCT CLOSE=A02 (or if more tables are involved with ACCT CLOSE=ALL) before you run the DELET job.
You would need to wait until accounting has cleared its buffers, i.e. until either message DB01103I or DB01101I has been issued, and then start the DELET job. The above accounting CLOSE commands can also be issued via DBUTLTY.
You may want to change operations to not Delete rows from table A02 at the same time as Accounting is Adding new rows with the same key values.