This is John Arnesen with NetView and System Automation level 2 support.
Are you seeing messages about running low or out of storage in the NetView netlog, and want to try and find the cause without recycling or taking a dump. Here is a list of the messages indicating a problem:
BNH162I - THE domainid BELOW 16M STORAGE is nn% USED....
BNH163I - THE domainid ABOVE 16M STORAGE is nn% USED....
DSI374A - THRESHOLD REACHED, number BUFFERS ON MESSAGE QUEUE OF task
DSI124I - STORAGE REQUEST FAILED FOR NCCF domainid
ABEND878 - Indicating that NetView is out of storage.
There are a few things you can do to identify the cause of the messages without taking a dump for analysis.
Please review this technote for further information on if the storage shortage is caused by a message build up.
There are two places that messages can build up.
1) On the Public queue as shown in Taskutil. This is typically caused by a task that is looping or hung and is no longer processing messages. New messages continue to arrive but are not handled, so they buffer up and wait.
2) The Held queue as shown in the List Autotask/Operid command. This storage growth is caused when the message has been processed but not deleted via DOM (Delete Only Message). We often see this with OEM or User messages that are ACTION messages (via descriptor codes) but there is no DOM to delete it.