DFHWS2LS java/lang/OutOfMemoryError Out Of Memory OOM

When too many Operations are chosen, the job executing DFHWS2LS gets error message
"java/lang/OutOfMemoryError"
The problem is that it doesn't take very many operations to be "too many". Also, there is not guidance on how many operations can be included in a WS2LS job.

We have one web service that needs to support around 20 operations (from a list of over one thousand choices).
We had to keep choosing fewer and fewer operations to get DFHWS2LS to work.
This forces us to run DFHWS2LS multiple times and then we have to deploy and use multiple web services in CICS. This is not ideal. We would prefer to be able to deploy a single web service that can host all of the operations needed.
To do this, DFHWS2LS needs to be improved. This need is similar to RFE 45614. But, the request for how to improve DFHWS2LS' ability to process larger numbers of Operations is different.
DFHWS2LS builds up objects in memory to be written out to files at the end. This implementation avoids the need to write out temporary state to files and read them back in later. However, it doesn't take very many operations to require a very large amount of storage.
Using only memory may make the individual DFHWS2LS job run faster. But, it makes the process of creating the web service take longer as a whole. Multiple DFHWS2LS jobs have to be run. Then, we have to configure multiple services.
We propose that DFHWS2LS be change to allow the customer to chose to run in "I/O" mode. This would write out temporary data to disk as it processes, reducing memory consumption. It may take longer to run the one DFHWS2LS process, but that time would be gained by in future configuration steps. The default could remain "memory" mode. But, the option to chose "I/O" would make DFHWS2LS easier to use in more complex web services.