|Some installations need some subsystems and/or some jobs be always active.|
Command epolice/chksbsjob provides a way to implement such a requirement.
|1- The CHKSBSJOB command|
If run in interactive mode, this command starts a job named CHKSBSJOB into subsystem QSYSWRK.
This is a non-ending job, which performs a control cycle every five minutes.
During such a cycle, it
- checks whether some given subsystems are active.
Subsystems supposed to be active and found not active are then started.
- checks whether some given jobs are active.
In case they are not active, they are started.
|2- Control files|
Information about subsystems and jobs to be checked are maintained in two control files:
You have two ways to maintain those control files:
This file documents the subsystems that must be restarted, if found not active.
- subsystem name
- subsystem lib.
This file documents the jobs that must be started if found not active in the system.
- job name
name of the job that is looked for (generic* name supported)
- user name
job user profile name that is looked for or *ANY
- job start command
command that should be executed to start the job.
||job start command
- use command STRDFU (option 5), or
- use our maintenance commands (in library EPOLICE):
- updDueSbs, to maintain control file EPOLICEDTA/DUESBS
- updDueJob, to maintain control file EPOLICEDTA/DUEJOB.