When trying to edit an ADS dialog process code in DME, a UABT error message was generated.
What does the UABT error message mean and how to resolve the error?
Many of the CA-IDMS DBMS tools products are heavy users of the Scratch Area. UABT errors are usually caused by problems with DME/EDITOR programs and their use of scratch. This abend can occur when not enough Scratch Area is available at the time ADSALIVE requests more. Therefore when using DME/EDITOR programs, be aware to increase the Scratch Area DDLSCSCR when several EDITOR sessions are simultaneously opened.
However for 16.0, level 2 has amended this statement above:
There should be no heavier usage of scratch space in 16.0 than in earlier releases. The problem may not necessarily the lack of scratch space. They could be related to scratch read problems also. Depending on the size of the module source code being edited; the size of the scratch area may not have been sufficient. Or the scratch records are not being deleted.
According to the DME User Guide 16.0 SP4, in Chapter 4.3.3 SCRATCH STORAGE says:
Scratch records are used during the session to store the module being scratch edited. For every 10 lines of module source code, you need 1K of scratch area.
You can check on whether or not the dialog is deleting the scratch records in the CA-ADS dialog statistics, CA-IDMS/DC STATISTICS which includes 'the number of scratch deletes'. This can be displayed SREPORT 003 IDMS-DC System Statistics.
CA IDMS Reports, 9.7.1 for the information on DC/UCF System Statistics Reports
CA ADS for CA-IDMS Reference Guide Appendix
C C.1 Dialog Statistics - Collecting Selected Statistics.