If APCDDS is used in conjunction with a product called "Smart/RESTART," a S0C4 ABEND can occur in IBM module IGG0201W + 5C8.
How do we resolve the S0C4 ABEND in IBM module IGG0201W + 5C8.
APCDDS is most commonly used via the wrap-around JCL method. In this method, APCDDS runs as a super-task, setting up its operating environment and then sub-tasking out the actual user program that will produce output for balancing. Part of setting up its environment is the dynamic allocation of several files including the main audit trail file "". After the user program has completed processing, control is passed back to CA APCDDS where extractions are made and/or rules are interpreted. APCDDS then writes to the DDSTRAIL file, closes all files and terminates.
The problem occurs if a APCDDS job step has to be rerun in a restart scenario controlled by Smart/RESTART. Part of this product's function is to CLOSE and FREE all dynamically allocated files. Following successful completion of Smart/RESTART processing, CA APCDDS can terminate with a S0C4 ABEND due to a corrupted DCB for the DDSTRAIL file.
In order to prevent this ABEND from occurring, special APAR, QS31228 (CM-W9 solution 53) is available for data centers that are using both APCDDS and Smart/RESTART. QS31228 causes memory allocated to the DDSTRAIL BUFFER pool to be orphaned for the duration of any job executing APCDDS. This may cause minimal storage and/or processing degradation.