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.