FLSHCPY DB2 AGE / 5608AC6DB / 41A - DB2

This issue can be seen in scenarios where a device class is 
configured to use the hardware type SVC. In that case the 
storage target volumes must also be pre-defined. This behavior 
will happen when all of the following conditions are met: 
1. The user invokes manually the delete function. 
2. The force option is used in  the command line call for the 
delete function. 
3. The involved target volumes have become the last in the 
storage concatenate list of SVC FlashCopy mappings list.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of IBM Spectrum Protect Snapshot for Unix v4.1.4       * 
* versions using SVC device adapter (SVCDTA adapter is not     * 
* affected) and performing the backup delete function with the * 
* "Force" option.                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IBM Spectrum Protect Snapshot for Unix 4.1.6      * 
****************************************************************

- If manually deletion of FCM backups is required, do not use 
the force (-F) option. 
e.g. /db2/DHT/sqllib/acs/fcmcli -p /db2/DHT/sqllib/acs/profile 
-f delete -B 20160216091103 
- Evaluate if your environment can use the new SVCDTA adapter 
which automatically allocates the SVC target volumes. Note that 
the SVCDTA storage adapter that was released with the version 
FCM version 4.1.4 still does not support all the features of the 
legacy SVC CIM adapter.

IBM Spectrum Protect Snapshot will be fixed to not delete the 
target volumes in case of using the "Force" option (-F) with the 
backup delete function.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.06.2016
06.07.2016
06.07.2016