Running a Datacom Server SELECT query on a DATACOM VIEW created under Datacom version 11.0 causes a MUF outage.

CCSR010E DBMUFPR S0C4 at 130C7816 LMOD DBSRPPR CSECT TBLREF +0019CE N/A N/A N/A 
CCSR021I OWNER = CA DATACOM SQL R15.1 
CCSR022I MODULE = TBLREF FMID = CAVEF10 RMID = RO95352 
CCSR060I BREAKING EVENT ADDRESS: 00000000 130C77EC 
CCSR061I PSW: 07840000 80000000 00000000 130C7816 
CCSR062I ILC: 04 INTERRUPT CODE: 10 
CCSR067I COMPLETION CODE S0C4 REASON CODE 00000010 
CCSR063I TRANSLATION EXCEPTION ADDRESS: 00000000_6DCF9800 
CCSR064I DATA AT PSW 130C7810 : 4110D098 0DEF5800 A068A701 
CCSR065I HOME = 01CA PRIMARY = 01CA SECONDARY = 01CA 
CCSR070I GR00 - GR01 00000000_00000000 00000000_D9000000 
CCSR070I GR02 - GR03 00000000_158335C0 00000000_130C7A0E 
CCSR070I GR04 - GR05 02947800_00000000 00000000_00000002 
CCSR070I GR06 - GR07 00000000_FFFFFFFF 00000000_158D11C8 
CCSR070I GR08 - GR09 00000000_14CF91AC 00000000_00000000 
CCSR070I GR10 - GR11 00000000_6DCF91AC 00000000_00000000 
CCSR070I GR12 - GR13 00000000_158CFBD0 00000000_158D1268 
CCSR070I GR14 - GR15 00000000_14CF91AC 00000000_14CF91AC 
CCSR071I AR00 - AR03 00000000 00000000 00000000 00000000 
CCSR071I AR04 - AR07 00000000 00000000 00000000 00000000 
CCSR071I AR08 - AR11 00000000 00000000 00000000 00000000 
CCSR071I AR12 - AR15 00000000 00000000 00000000 00000000 
CCSR066I SDWAEC2 070C0000 92E03680 from RB 
CCSR062I ILC: 04 INTERRUPT CODE: 10 
CCSR063I TRANSLATION EXCEPTION ADDRESS: 00000000_6DCF9800 
CCSR070I GR00 - GR01 00000000_00000000 00000000_D9000000 
CCSR070I GR02 - GR03 00000000_158335C0 00000000_130C7A0E 
CCSR070I GR04 - GR05 00000000_00000000 00000000_00000002 
CCSR070I GR06 - GR07 00000000_FFFFFFFF 00000000_158D11C8 
CCSR070I GR08 - GR09 00000000_14CF91AC 00000000_00000000 
CCSR070I GR10 - GR11 00000000_6DCF91AC 00000000_00000000 
CCSR070I GR12 - GR13 00000000_158CFBD0 00000000_158D1268 
CCSR070I GR14 - GR15 00000000_14CF91AC 00000000_14CF91AC 
CCSR080I DBMUFPR DUMP IN PROGRESS 
CCSR081I DBMUFPR DUMP COMPLETED

Sustaining engineering looked at the dump and said:  
 
Unfortunately, we are all stumped on this one. In the first dump, a function is being called with what should be a QCB control block, but it's a TCB control block. The QCB that should have been passed is in the correct place in the statement. The code that loads the address is different than the code that we see here for that version of that module, so we assume IBM changed the C compiler optimization since March 2017. 

But this is common code for all queries, and it works when you create the view. 

Datacom Views were broke for a while during the Table Expression development. So perhaps if you upgraded to the latest SQL PTFs it would be fixed. But with the only "broke" view in PROD, there wouldn't be a way to test rebind of a datacom view. 

So since you have fixed the problem with re-creating the view, and we don't have anything further we can do from these dumps, I think we have to close the case. 

I certainly hate doing this, but in this case, there doesn't seem to be another option. 

z/OS  
CA Datacom/SQL 15.1  
CA Datacom Server 15.0

1.DROP the DATACOM VIEW.
2.Recreate the VIEW by running CREATE DATACOM VIEW.