Solve:Operations Storage Leak

Document ID : KB000096562
Last Modified Date : 01/06/2018
Show Technical Document Details
Issue:
We noticed a storage leak on 2 systems that have the Solve:Operations in health checks added by Solve when it starts up. 

We're seeing the WSS size increasing by around 1 MB per hour - eventually system will start using aux storage (normally there is none on that system). 
Environment:
We are running Solve:Operations Automation R11.9 on Z/OS 2.2
 
Cause:
IBM APAR OA38553

A new feature in Netview V6 that creates a 2GB dataspace attached to the *MASTER* task which will gradually grow from 0 to 2 GB in size and is somewhat catastrophic to a system that isn't expecting this - the systems affected were previously quite happy to run in 2GB real memory with no paging 

This is the default behavior - and you can't turn the new feature off (though you can restrict the size of the dataspace to 512M) 
Resolution:
This is the default behavior - and you can't turn the new feature off (though you can restrict the size of the dataspace to 512M).
 
For more information about how to limit the size of the dataspace, see OA38553.
Additional Information:
To run SOLVE:Operations without Health checks see KB000012030

If you issue this command on a SOLVE region it will show the storage used every hour (note the full stop after the 1, without that the default is to assume minutes and that will produce too much log output): 

SUB BSYS EVERY 1. KEEP=SYS CMD=SH BUFF 

You could put it in the NMREADY member so it gets executed at start-up and will be there even if the region is recycled. 

If the log is then in a file that can be viewed with ISPF edit it's easy to issue: 
X ALL;F ALL N11910 
to see the total storage messages together.