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).
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
CHGUSRPRF USER(SOMEBLOKE) SPCAUT(*JOBCTL)
IBM i Software Developer, Digital Dad, AS400 Anarchist, RPG Modernizer, Alpha Nerd and Passionate Eater of Cheese and Biscuits. Nick Litten Dot Com is a mixture of blog posts that can be sometimes serious, frequently playful and probably down-right pointless all in the space of a day. Enjoy your stay, feel free to comment and in the words of the most interesting man in the world: Stay thirsty my friend.
How to find if an IBM i (as400) program is interactive or batch – RPG API example
How to Upload a SAVF with IBM I ACS a.k.a. Upgrade HTTPAPI (LIBHTTP) to V7.2
Developerworks Connections Sunset – How to Extend RDi
Why use IBM i RDi?
Copying iSeries fields from numeric to Alpha – aka using SQL to change column data type
What is IBM i Email and SPF?
Updating Numeric DTAARA in RPGLE
How to capture IBM-i job info for submitted jobs
Register license key in SOFTLANDING SOFTMENU