Hi:

Not certain if this is the same as what you are having but there is a knowledgebase article that discusses some steps to take. I will copy from that article:

Resolution



1. Log in to the Folder where the Journal Status Monitor is stuck in shutdown mode
2. Navigate to Development, Utilities, Maintenances, In lines (GMAINT)
3. Select the folder, then for table select BATCH
4. In the menu above, select Selection, Selection...
5. In the selection window, enter the following criteria COD = "ACCENTRY", then OK
6. Delete the values in the PID and RQT fields
7. Save the record, then End
8. Navigate to Usage, Batch Server, Accounting Tasks
9. Click Run Now to start the Journal Status Monitor
1. It may take a couple moments to start up, click the Update button to refresh the screen
10. The Task Status should now show Active 

Unfortunately, I don't have the number of the article as I stored this in our private knowledgebase but the title is
Journal Status Monitor stuck in shutting down mode

if you search for that you should be able to locate it.

Best Wishes.

Brilliant - thanks very much. I thought it was a table lock but didn't know which table.

I have also learnt the Selection->Selection function for searching a table for a value which is something I've always thought I needed to use SQL for so that's a bonus!

Hi
Quick question related to the GMAINT since you've been so helpful with the Selection Selection (using it again already!)

After finding my subset of records, is there way to :
- see how many records were found
- limit the display to certain fields only so I can whiz through the records updating as i go

Thanks again

As far as I know the utility is a very basic no frills record editing application. As shown you can jump to various records using keys but after landing on the record you selected, navigation is by using the arrows at the top to step through each record one at a time. It displays all the fields on a record using tabs.

Thought so. Thanks tho

In v6.5, this can happen if the accounting task job has aborted unexpected. I typically fix this by:

1. Pull up Usage > Batch Server > Request Management.
2. use the Selection > Advanced Selection menu
3. Type tache = "ACCBATCH1" and click Ok or enter
4. Locate the most recent run of the job (usually has a status of Aborted) and should be the first one in the list at the top
5. Right click and select Relaunch Query

Click the update button a few times to refresh the screen to be sure that a new task was scheduled.