STACKVAL dumps (CTL-064009) showing CPS0 in EXITC processing

As requested by IBM, opening an RFE for what was previously in a PMR.
PMR: 68273 004 000

Problem Details
.
Product or Service: Z/TPF 1.1.0
Component ID: 5748T1501
.
Operating System: TPF
.
Problem title
STACKVAL dumps (CTL-064009) showing CPS0 in EXITC processing
.
Problem description and business impact
We are seeing stackval dumps in our test environment showing CPS0 which requires Engineering to investigate to find the application culprit. We would like to ask IBM to make an update to show the calling application
name on the dump rather than CPS0 in this situation. I'll attach the
dump for your investigation.

IBM Update12/7/17 1:02 PM
Action taken: Development is investigating. It appears that when we to
the ENTRC to CXXC the trace name gets set to CPS0. I suspect that we
should change it to the segment name that exited but further
investigation needs to be done.

IBM Update12/27/17 7:13 AM
Action taken: From development. The failing program name for the
CTL-64009 dump is correctly labeled as CPS0 because the system error is issued by the hook handler for ECB stack validation (CHK3_STKV in CSECT
CCHOOK). At dump processing, both CE3TRNAME and CE3ENTPGM fields are
already set to CPS0 to reflect that it is the issuer of the SERRC macro.
An alternative solution is create a new appended console message for
CTL-64009 dumps that contains the program name that triggered the ECB
stack validation. In the given dump, the program TFOA triggered the ECB stack validation by issuing the EXTIC macro and the stack frame of CPS0 when entering the hook handler shows the ECB trace name to be TFOA. We
need to verify that other triggers of ECB stack validation (ENTxC,
BACKC, etc.) will also have the desired trace name. If you accept this
idea, a RFE can be opened to propose this solution and begin work on
this change.