13-Sep-2007
T4 batch stopped
T4 wasn’t started in the reboot, since the batch that holds these jobs (T4$BATCH) wasn’t started after reboot. The job was there - two entries of T4$COLLECT, actually - but the queue was stopped and therefore, both jobs were held.
So that is one thing to be changed: it has been the only issue that didn’t work on booting. It could be that it is just the queue that needs a review.
The job has now been rescheduled for next midnight - the right way, using T4$CONFIG.COM.
Comments:
You must be logged in to post a comment.