Troubleshooting
Problem
How can you determine who deleted jobs from Job Scheduler?
Resolving The Problem
How can you determine who deleted jobs from both Job Schedulers?
When using the Advanced Job Scheduler, do the following to see what changes were made:
Although this message does not detail particular changes, it does show what user job made the adjustments.
You can also audit the AJS commands such as CHGJOBJS; however, this does not track the changes when WRKJOBJS, Option 2, next to a job is used. If a more thorough auditing of the Advanced Job Scheduler is needed, the developer has an application that can be purchased. A support representative can pass along client information to the developer for the developer to work with the client.
When using the Work Job Scheduled Entries (WRKJOBSCDE) command, finding out what happened to the scheduler may not be possible. There are no DO entries (enabled by the Security Auditing Level (QAUDLVL) system value containing *DELETE as one of its values) whenever a job schedule entry is made, so it is not possible to track specific changes to the schedule. You can set up change auditing of the job scheduler object so you can see when changes are made and by whom. This will not show the explicit changes though. The audit entries in this case would be ZC (object change).
The object to turn on auditing for is QDFTJOBSCD in library QUSRSYS type *JOBSCD. The object auditing value should be set to *CHANGE. Whenever a user changes any job on the scheduler, a ZC audit record will be generated. Ignore any of the records for which the generating job is QJOBSCD. The Auditing Control (QAUDCTL) system value will have to have *OBJAUD as one of its values for object auditing to be enabled.
More information on security auditing can be found in Chapter 9 of the Security Reference Manual .
When using the Advanced Job Scheduler, do the following to see what changes were made:
| o | On an operating system command line, type the following: GO JS Press the Enter key. |
| o | Select Option 2 for Job History and press Enter. |
| o | Select Option 2 for Display Log and press Enter. |
| o | Press F10, then adjust the starting/ending time/date as appropriate. Page down and, for the 'Message identifier' parameter, type IJS1095. Press Enter to see results. |
You can also audit the AJS commands such as CHGJOBJS; however, this does not track the changes when WRKJOBJS, Option 2, next to a job is used. If a more thorough auditing of the Advanced Job Scheduler is needed, the developer has an application that can be purchased. A support representative can pass along client information to the developer for the developer to work with the client.
When using the Work Job Scheduled Entries (WRKJOBSCDE) command, finding out what happened to the scheduler may not be possible. There are no DO entries (enabled by the Security Auditing Level (QAUDLVL) system value containing *DELETE as one of its values) whenever a job schedule entry is made, so it is not possible to track specific changes to the schedule. You can set up change auditing of the job scheduler object so you can see when changes are made and by whom. This will not show the explicit changes though. The audit entries in this case would be ZC (object change).
The object to turn on auditing for is QDFTJOBSCD in library QUSRSYS type *JOBSCD. The object auditing value should be set to *CHANGE. Whenever a user changes any job on the scheduler, a ZC audit record will be generated. Ignore any of the records for which the generating job is QJOBSCD. The Auditing Control (QAUDCTL) system value will have to have *OBJAUD as one of its values for object auditing to be enabled.
More information on security auditing can be found in Chapter 9 of the Security Reference Manual .
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CNEAA2","label":"Advanced Job Scheduler"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
23105515
Was this topic helpful?
Document Information
Modified date:
08 September 2025
UID
nas8N1017386