If any of the following conditions are met you are NOT affected by the problem:
- The RESOURCEUTILIZATION client option is either not explicitly set, or is set to 1 or 2. This option can be set either in the client option set or schedule on the server, or in the local client options.
- Data for the client node is only stored in random-access disk storage pools (such as the preconfigured storage pool, BACKUPPOOL).
- Image backup is used.
- NDMP backup (initiated by client or server) is used.
- Only the API client is used (including programs and products that use only the API client - i.e. TDP's).
A fix is scheduled for release at the end of April, in the meantime make sure you either set any client using a higher RESOURCEUTIL value to 2, or send the client's backup to disk. Also note that any backup to disk using the FILE devclass is impacted by this problem as it affects all sequential media backup types.
I have provided a link to the APAR listing at the Tivoli website.