Micro Focus Server Enterprise Edition for UNIX > Mainframe Support for Deployed Applications > MSS Configuration and Administration > JCL Support > Configuring JCL Timeouts > Difference with the TIME= parameter > Abends - S322:

Abends - S322:

On a mainframe, a job abends with an S322 abend code when the TIME value has been exceeded on a per job or per step basis.

The method used to end a job is as follows, depending on the platform on which Studio Enterprise Edition for UNIX is operating:

on a Unix environment, all terminations due to timeout are of the "hard kill" variety.
on the Win32 platform, the process first attempts a "soft kill." If this is unsuccessful it is immediately followed by a "hard kill".
on Enterprise Server running on a PC, it is possible that your code is executing in a loop that is so tight that the timing mechanism is unable to break execution to terminate the job gracefully. In this event, it performs a "hard kill" on the process.

For all timeouts, the ESMAC Condition Code associated with the job is an S322. The job termination codes, as shown in the joblog, are either S222 in the event of a successful "soft kill" or nothing in the event of a successful "hard kill" In both cases a message similar to the one below is written to the console.log file:

CASKC6002I JOB10347 terminated due to exceeding TIME parameter 05:01:20