An option so that awsstop does not complete until all threads have.

Currently awsstop completes before they have .  I have had the 'joy' of dealing with systems where the completion of awsstop is taken as a signal that the Linux host can be terminated.  Unfortunately until the awsckd tasks have closed their file (and have ended), z/OS level disk updates can still reside in the Linux cache - leading to corrupted, well, Db2 databases.  With this enhancement the awsckd files would be nicely closed before awsstop completes with less chance of this corruption.

Hello James,

can I ask you to please open an RFE for your described enhancement request. With a recorded RFE there is a better chance that other users pitch in and want that enhancement as well. Also, RFE's help to bring the requirements up to development.

Regards

Heinrich

Haven't RFEs become AHAs?  Which AHA product?  None seemed suitable. 

And my experience, from other products, is that few users pitch in unless it is put in front of them. 

James, for external requirements (and I assume you are asking on behalf of a customer) RFE is still the way to raise enhancement requests. Aha! is used internally and customers will have no insight into it, hence cannot vote for a specific RFE or don't see the status of it.