Red Alert for z/OS 1.11 users of GDG's with GDS_RECLAIM set to YES

Is back-to-back the right term for this : two Red Alert posts in a row ?
Here's another Red Alert in about a week's time :

Abstract:
Possible data loss for z/OS 1.11 users of GDG's with GDS_RECLAIM option set to YES (default) in the SMS Parmlib member, IGDSMSxx

Description:
Only GDG users that have GDSs in DEFERRED ROLL IN STATUS and receive message IGD17356I GDG RECLAIM REQUEST WAS SUCCESSFULLY PROCESSED FOR DATASET in the joblog during job execution are affected. During RECLAIM processing, output intended to be directed to the data set is not written but the job receives a CC0.

Please see APAR OA32968 for additional information.

Recommended Action:
Apply ++APAR as soon as possible.

Set the GDS_RECLAIM option to NO until ++APAR can be applied. This will generate a JCL error and prevent any loss of data.

If you want to have en overview of all past Red Alerts, then take a look over here. You can also subscribe on the same page so you'll be notified by mail of any future Red Alert.