IBM i Batch Window Capacity Calculator
Batch windows rarely fail suddenly. They erode a few percent per year until a heavy month end pushes the last job into the morning. This calculator tells you how close you are and how much faster the batch must run to stay safe.
Your numbers
Elapsed time from first to last job on your heaviest night, such as month end.
Time between the last user leaving and the first user or interface needing the system.
Jobs with no dependency on each other that could run in separate job queues.
Your results
Assumes runtime scales linearly with volume. Batch jobs with sort or index rebuild steps can scale worse.
Runtime at horizon vs annual growth
Sweeps Annual transaction volume growth from 0 to 40, holding your other inputs fixed.
Batch history analysis
Optional: we read your scheduler history and mark the critical path.
Optional. The tool and every export work without this. No spam.
How to use it
Take your longest night from the last twelve months, not the average. Use the job scheduler or QHST history to find the first start and last end time. Enter the window the business really needs, which for a plant often ends when the first shift scans in. Add volume growth from order and receipt counts, not revenue.
The formulas
If runtime scales with volume, then after t years runtime equals current runtime times (1 + g) to the power t. The window is full when that equals the window, so years left is ln(window / runtime) divided by ln(1 + g). The reduction needed is one minus window divided by the future runtime. The chart sweeps growth from 0 to 40 percent so you can test optimistic and pessimistic cases.
What to do with the answer
If you have more than three years of headroom, monitor and move on. Between one and three, start with the cheap wins: run independent jobs in parallel job queues, purge or archive large history files before month end, and fix full-file scans with proper logical files or SQL indexes. Under one year, add the hardware or tuning work to the budget now, since hardware and skills have lead time.
- Check that the interface jobs after the batch have a fixed deadline
- Look for a single long job holding the critical path
- Test after each change on the same heavy night, not a quiet one
Common mistakes
Using average runtimes, ignoring year-end or quarter-end peaks, and assuming parallelism is free. Jobs that lock the same files serialise anyway. Another common error is mixing runtime caused by waiting on a tape or an interface partner with CPU work, which behave differently as volume grows.
Frequently Asked Questions
Does it matter which ERP I run?
No. The model works for any IBM i batch, including JD Edwards World nightly processing, custom RPG jobs and third-party applications. Only the runtime, window and growth rate matter.
Why use the heaviest night?
Because failures happen on the peak. A batch that fits comfortably on an average night can still overrun at month end, when volumes and reports are highest.
What if growth is zero?
Then the batch never overruns on volume alone and years left shows zero. Check whether any other changes, such as new reports or interfaces, will add work.
Is the parallelism number a promise?
No. It is a rough upper bound. Real gains depend on CPU cores, memory, file locking and dependencies, so test on your own system.
If you would like job run history analysed to find the critical path in your batch, Netray can do a read-only review of your scheduler data.
Related Tools
AS/400 Disk Storage Growth Forecast Calculator
Estimate how many years of disk you have left on IBM i given data growth, journal receivers and your safe utilisation threshold.
OracleIBM i Restore Time and RTO Calculator
Add up restore, journal apply and verification time for an IBM i recovery and compare it with your recovery time objective.
OracleIBM i Power Hosting Cost Comparison Calculator
Compare the multi-year cost of keeping an IBM Power server on premises with moving IBM i to a hosted Power environment, including payback months.
ERP Migration & SelectionJD Edwards World Parallel Run Cost Calculator
Add up the cost of running the old and new systems together, including reconciliation and slippage, and see the true incremental cost of the overlap.
More Oracle tools
See all- JDE World DREAM Writer Version Documentation Template
- JD Edwards World Key File Reference Table
- JD Edwards World to EnterpriseOne Data Conversion Mapping Worksheet
- JD Edwards World Custom Program and Modification Inventory Worksheet
- JD Edwards World Custom Object Conversion Effort Calculator
- AS/400 Skills Succession Risk Assessment
- IBM i System Values Reference
- IBM i CL Command Cheat Sheet
- JD Edwards Julian Date (CYYDDD) SQL Converter