A recovery job can be registered as a job. The recovery job is started if a job is abended.
In a recovery job, the executable file that carries out actions against unexpected termination is registered. Only one recovery job can be connected to a job. The recovery job cannot connect more than one preceding job. No job can be connected after a recovery job. After a recovery job is completed normally, the preceding job that has abended can be restarted. The job net configuration in the screenshot below describes the flow of a recovery job.
When Job B abends, recovery Job D starts up.
After recovery Job D starts up normally, original Job B is restarted only once provided that restart of the original job is specified.
After Job B starts up normally, the next job in succession, Job C starts up.
After Job C starts up, the job net starts up normally.
The job net is terminated abnormally if any of the followings has occurred.
Recovery job D was abended.
Restart of original job B is not specified in recovery job D.
Although restart of job B is specified in recovery job D, recovery job D was terminated normally but job B was abended again after its restart.
