Since it is a CA Ideal application, your error procedure possibly does not have access to that part of the request area. (access to that information would perhaps be a good suggestion for an "Idea" submission).
Is your MUF startup coded with the SYSOUT parameter (e.g. SYSOUT 0,5M,1M,3M,1M,1M)? If so then the PXXSQLnn SYSOUT should have a "-- DATA BASE SQL ERROR SUMMARY" that corresponds to the date/time when your application failed. As stated previously, the SQLCODE or SQLSTATE should provide the details of why the triggered procedure failed.
If there is no corresponding "-- DATA BASE SQL ERROR SUMMARY" in PXXSQL01, then there should be a Master List dump in PXXMLnn SYSOUT. Search for the DBRW---n (where n is the task number that appears in the dump header for the RC 94(100)) and then go to offset 26 within that request area to view the DBRQDIAG values.
If your MUF is not coded with the SYSOUT parameter (or for z/VSE sites) both the SQL Error summary and the dump will be in the PXX.
If the dump has been suppressed, you can use the RCERROR YES,NO,94100 console command to MUF in order to unsuppress it, and then rerun your application to produce the dump.
Alternatively you could just eyeball the triggered SQL procedure code and check the state of the tables it accesses. Often that shows up obvious conditions (such as table full, Index full, or database disabled) without the need for dump analysis.