The new property :
##Enable Job Scheduler automatically suppressionJobScheduler=false
- Set this property to false (default) if you want ESA to submit the scheduler jobs.
- Set this property to true if you do not want ESA to submit the scheduler jobs.
Resolving The Problem
If you don’t need to manually create job scheduler entries, this document could be ignored.
When ESA for IBM i is activated, there will be 5 jobs* schedulers created by default.
This job scheduler entry causes the auto PTF task to be run. The entry is created when ESA is enabled (using the CHGSRVAGTA command) and Auto PTF is enabled (using the AUTOPTF parameter of the CHGSRVAGTAcommand).
The job scheduler entry is run once a week. The day of the week that is used can be selected by the system operator, but which days the system operator can select from are limited to three. The three days available to choose from are calculated based on the system serial number.
The auto PTF task requests download of the auto PTF policy once every several weeks. As the maximum period for a job scheduler entry is one week, the auto PTF task maintains counters in the QS9AUTOPTF data area to keep track of the number of elapsed weeks.
This job scheduler entry causes inventory to be collected (and optionally sent as well). The entry is created when ESA is enabled (using the CHGSRVAGTA command).
This job scheduler entry is run every day of the week. The user can select the time the inventory is collected by using the SRVINF parameter of the CHGSRVAGTA command. If the send time is set to be the same as the collect time, then this job scheduler entry causes collection and sending of inventory.
This job scheduler entry is run once whenever
the CHGSRVAGTA command enables ESA. This entry collects inventory for immediate problem reporting. This consists of sending a hardware and software inventory as well as processing any ESA reported software problems that are identified in the QSRVAGT/QASJPRBDOC database file.
This job scheduler entry is also run by QS9PRBSND for software problems.
This job scheduler entry causes the heartbeat task to be run. The entry is created when ESA is enabled (using the CHGSRVAGTA command).
The job scheduler entry is daily. The heartbeat task runs once every several days.
The length of this interval is specified on the SRVINF parameter of the CHGSRVAGTA command. The heartbeat task maintains counters in the QSJHEARTBT data area to keep track of the number of elapsed days.
This job scheduler entry causes Update Access Key refreshing. The entry is created when ESA is enabled (using the CHGSRVAGTA command).
The job scheduler entry is run once a week. The day of the week that is used can be selected by the system operator.
Note: QS9UAK might also be shown as scheduled job. This job is only required when system is a Standalone partition over a Power 8 or higher. Otherwise, it's not required. Could be disable by doing CHGSRVAGTA REFRESHUAK(*NO)
Below is an example of how to create job scheduler entries using default job schedulers.
QSYS/ADDJOBSCDE JOB(QS9UAK) CMD(QSYS/WRKSRVAGT TYPE(*UAK)) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(DAY) SCDTIME(TIME) JOBD(*LIBL/QS9SRVAGT) USER(*CURRENT) RCYACN(*SBMRLS) JOBQ(*JOBD) MSGQ(*USRPRF)
Generally, ESA specifies the day of the week and the time on the scheduled date at which the job is submitted. We could specify any parameters according to our requirement.
When using different job schedulers, the command line may be different. But command should be same (CMD parameter).
JOB name and JOBD are recommend to keep the same so that it could continue to keep consistency with previous (JOB and JOBD parameters). We don’t need to take more time to refresh our information about it when debug.
16 June 2020