News archive
Final Run Close to be submitted to batch
The Final Run Close is one of the procedures on the system that requires other users to be offline. For that reason many choose to run the job 'out of hours'. Until now the job has been an interactive one, requiring a screen to be left on to run the job – and this has not been popular with those wanting to start the job running remotely.
The Final Run Close will no longer run interactively; instead, it will be automatically submitted to batch.
To reduce the amount of time that the system is unavailable the process will be run as two jobs. The Final Run Close processing and the save of the data files will be submitted as the first routine, and the Multi Period History file update will be a second routine. The system will become generally available after the first routine has completed.
Having to restore and rerun the Final Run Close simply because of a lost network connection should now be a thing of the past.
This amendment will also reduce the time that the system is unavailable while the Final Run Close is updating the Multi Period History files (for the Multi Period History module users).
