Some Batch jobs take a long time to run. If you have a batch job with the words “trial balance” in the title then its going to take hours… That is a “hashtag internet fact” 😉
A common technique to try to give these jobs a little boost is the jobs outer control program to try ti change itself to run a little faster. This is commonly done by reducing the ru priority (so it gets into run state more often than other batch jobs that are waiting to be processed, one bite at a time) or to increase timeslice (so the job stays in the processing state for longer once its being run).
What security setting does IBM i, AS400 or iSeries user need to CHGJOB
Only a user with job control (*JOBCTL) special authority can change the RUNPTY, TIMESLICE, PURGE, or DFTWAIT values.
If you dont have *JOBCTL then the user that is running the “trial balance” will see an error message:
Message . . . . : -CALL AUDITRUN*NONE Command 12/14/15 09:46:11.744735 QCADRV QSYS 03BA AUDITRUN
To module . . . . . . . . . : AUDITRUN
To procedure . . . . . . . : AUDITRUN
Statement . . . . . . . . . : 5500
Message . . . . : 5500 – CHGJOB JOB(*) RUNPTY(49)
CPF1337 Escape 40 12/14/15 09:46:11.745050 QWTCHGJB QSYS 2F12 AUDITRUN
To module . . . . . . . . . : AUDITRUN
To procedure . . . . . . . : AUDITRUN
Statement . . . . . . . . . : 5500
Message . . . . : 620239/PABOG/AUDT121316 not authorized to change parameters. Fix this by granting the running user:
CHGUSRPRF USER(SOMEBLOKE) SPCAUT(*JOBCTL)