Need new options to prevent dumps from taking too long

If a dump takes a long time to process this represents an effective "outage" to work as all i/streams are perched. Common impacts are that OSA polling may not be possible or may not occur frequently enough while the dump is being taken so OSA buffers may fill up, and timeouts are more likely once the dump has completed if the dump itself takes a long time to process. We'd like new safeguards added to dump processing to try to ensure dumps don't take too long.
1) New ZASER or similar option setting the max time (in ms) to allow cpse to spend identifying/sorting/getting info on ECB heap nodes to include in the dump. If this time is exceeded, cpse should just dump the ECB heap it has identified to be dumped in the order it has worked out so far without any further sorting or getcic calls. A constant string of some sort should be added to the dump to indicate ECB heap processing was curtailed due to the time limit being exceeded.

2) New ZASER or similar option setting the max time (in ms) to allow cpse to spend processing an OPR dump on a native TPF system. If this time is exceeded, the dump process should be terminated and a constant string should be added to the dump to indicate the dump data is incomplete due to the exceeding this new time limit. Terminating the dump before all data was complete would need to ensure the datax user exit interface was not broken, or else make changes to datax expectations part of the migration considerations.

In addition, we'd like to see a constant string of some sort added to the dump to indicate when all ECB heap nodes are not dumped because the HEAPBUF limit on heap buffers to include was reached.