Any user data that you can save to a save file, you can save
to a TSM server by using the BRMS TSM Client. Typically, this data is created
by the user and is not required to restore i5/OS to a functional level. Therefore, security
data, configuration data, and licensed programs are excluded from save operations
to TSM servers.
Following is a list of additional restrictions that are placed on BRMS
TSM Client operations.
Save-while-active *SYNCLIB is not supported when saving libraries to TSM
servers. When libraries are saved to TSM servers, one save command is used
to save each library because i5/OS requires the save to be set up as a
save to a save file. The *SYNCLIB value will be ignored if it is specified.
You cannot save system data to a TSM server. You must store system data
on local media so that it is available for system recovery. This includes
security and configuration data.
BRMS does not save *IBM type libraries to TSM servers.
BRMS does not save IBM-supplied libraries that are considered user data,
such as QGPL, QUSRBRM, or QUSRSYS libraries to TSM servers.
You cannot schedule operations from a TSM server, though you can schedule
operations by using BRMS.
BRMS uses its own media policies to manage the retention and expiration
of data that is stored on the TSM server. TSM policies are not used for this
purpose.
You cannot save BRMS media information about a TSM server. You must save
this information to local media so that it is available for recovery.