On a STORE operation (verb 42) the BFOR image is always empty. If the AFTR is also empty it means the STORE encountered a non-zero ERROR-STATUS that requires the DBMS to back out any changes made so far.
The STORE operation gets far enough to write the Empty BFOR but in the process of checking for dups, connecting to automatic sets or finding space for the new record encounters an error and simply backs out what was done so far and writes the empty AFTR and returns the ERROR-STATUS to the program.
I would check the pgm in question to see what kind of non-zero ERROR-STATUS on STORE it ignores and why. There may be valid reasons for ignoring certain ERROR-STATUS but pgms should always check ERROR-STATUS and have valid reasons for ignoring and not doing the ROLLBACK and Abort at the time of the error.