On a mainframe, the third dataset disposition (abnormal termination) is always triggered and processed upon receipt of an S322 abend.
In the Enterprise Server environment however , the abnormal dataset disposition processing for an S322 abend is ONLY processed on the Windows Platform and only when a "soft kill" can be issued. If a "hard kill" is required to stop the job, for example on a UNIX platform, then you must treat the dataset dispositions for failing jobstep as "unknown," and reset the datasets accordingly. The DBMS commit/rollback can be used, and will process as expected
You can check the method: soft kill, or hard kill by examining the joblog for the failing job: