CA-Datacom DB00229E - FATAL INTERNAL ERROR
Article ID: 132281
Updated On:
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
After two Datacom instances with Mode = S were started in the sysplex, I tried to switch the shadow via Command.
But it results: DB00229E and both STCs have stopped.
DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - XES-1BFC
Customer would like to use the MIGRATE_TO_SHADOW command.
Before getting DB00229E error message the following can be seen:
CFNAME ALLOCATION STATUS/FAILURE REASON
-------- ----------------------------------------
ICF1W1S STRUCTURE ALLOCATED C4000800
ICF2W1S PREFERRED CF ALREADY SELECTED C4000800
PREFERRED CF HIGHER IN PREFLIST
It sounds that you are picking up another CF different that the one you want.
IXL015I show CONNECTIVITY= DEFAULT
The connector specified CONNECTIVITY=DEFAULT or did not specify CONNECTIVITY. When the coupling facilities are being ordered for allocation, the eligibility queue is primarily sorted by attribute weight.
PREFERRED CF ALREADY SELECTED
The system did not select the coupling facility because a more preferable coupling facility was already selected.
When the coupling facility status is PREFERRED CF ALREADY SELECTED, the message displays one of the following lines that gives the primary reason why this coupling facility was placed lower than the previous one in the eligibility queue. Because of how different requirements are weighted, this information does not imply that all coupling facilities higher in the eligibility queue meet the requirement:
PREFERRED CF HIGHER IN PREFLIST
This coupling facility is lower in the PREFLIST than another coupling facility that is suitable for allocation.
Extracted from: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieama00/ixl015i.htm
But it results: DB00229E and both STCs have stopped.
DB00229E - FATAL INTERNAL ERROR - JOB TERMINATED - XES-1BFC
Customer would like to use the MIGRATE_TO_SHADOW command.
Before getting DB00229E error message the following can be seen:
CFNAME ALLOCATION STATUS/FAILURE REASON
-------- ----------------------------------------
ICF1W1S STRUCTURE ALLOCATED C4000800
ICF2W1S PREFERRED CF ALREADY SELECTED C4000800
PREFERRED CF HIGHER IN PREFLIST
It sounds that you are picking up another CF different that the one you want.
IXL015I show CONNECTIVITY= DEFAULT
The connector specified CONNECTIVITY=DEFAULT or did not specify CONNECTIVITY. When the coupling facilities are being ordered for allocation, the eligibility queue is primarily sorted by attribute weight.
PREFERRED CF ALREADY SELECTED
The system did not select the coupling facility because a more preferable coupling facility was already selected.
When the coupling facility status is PREFERRED CF ALREADY SELECTED, the message displays one of the following lines that gives the primary reason why this coupling facility was placed lower than the previous one in the eligibility queue. Because of how different requirements are weighted, this information does not imply that all coupling facilities higher in the eligibility queue meet the requirement:
PREFERRED CF HIGHER IN PREFLIST
This coupling facility is lower in the PREFLIST than another coupling facility that is suitable for allocation.
Extracted from: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieama00/ixl015i.htm
Environment
z/os, CA Datacom/AD 15.0 for DISKOS (CADISK)
Cause
Structure allocation too low.
"Without a dump I cannot be sure, but it looks like a LIST WRITE to the coupler failed. The LIST STRUCTURE size looks woefully under-allocated, so most likely that is the problem. (MAX ENTRIES is 1 !, from previous DBMXMPR and DBMXEPR calculations for a different customer the capacity required for the LIST STRUCTURE was about 10 times as much).
"Without a dump I cannot be sure, but it looks like a LIST WRITE to the coupler failed. The LIST STRUCTURE size looks woefully under-allocated, so most likely that is the problem. (MAX ENTRIES is 1 !, from previous DBMXMPR and DBMXEPR calculations for a different customer the capacity required for the LIST STRUCTURE was about 10 times as much).
Resolution
after increasing structure allocation, all work.
we have increased the XCF structure size:
DB02319I - LIST STRUCTURE SIZE = 20,480 K
DB02320I - LIST STRUCTURE MAX ENTRIES = 2,430
DB02321I - LIST STRUCTURE MAX ELEMENTS = 37,649
Now all commands to switch manually (planned outage) works.
we have increased the XCF structure size:
DB02319I - LIST STRUCTURE SIZE = 20,480 K
DB02320I - LIST STRUCTURE MAX ENTRIES = 2,430
DB02321I - LIST STRUCTURE MAX ELEMENTS = 37,649
Now all commands to switch manually (planned outage) works.
Additional Information
Just to clarify a point about SHADOW MUF, since there are two installation options:
- 1 unplanned outage implementation.
LPAR Failure, MUF region failure, it only requires XCF protocol.
- 2 planned outage implementation. (schedule outage).
IPL, applying a Service Pack, changing MUF startup parameters. It requires Sysplex
Coupling facility.
With option 1, there is only one MUF up and running (either the primary or the secondary). If primary fails then secondary starts and vice et versa.
With option 2, both MUFs run in parallel.
You may find out more about SHADOW MUF in the following knowledge document:
https://comm.support.ca.com/kb/implementing-shadow-muf/KB000025223
https://comm.support.ca.com/kb/how-to-use-and-configure-a-ca-datacom-shadow-muf/KB000027261
- 1 unplanned outage implementation.
LPAR Failure, MUF region failure, it only requires XCF protocol.
- 2 planned outage implementation. (schedule outage).
IPL, applying a Service Pack, changing MUF startup parameters. It requires Sysplex
Coupling facility.
With option 1, there is only one MUF up and running (either the primary or the secondary). If primary fails then secondary starts and vice et versa.
With option 2, both MUFs run in parallel.
You may find out more about SHADOW MUF in the following knowledge document:
https://comm.support.ca.com/kb/implementing-shadow-muf/KB000025223
https://comm.support.ca.com/kb/how-to-use-and-configure-a-ca-datacom-shadow-muf/KB000027261
Feedback
Yes
No
Powered by
