Add TSM for ERP session identifier for the improved collocation

Currently, when TSM for ERP is used to backup DB2 database, it assignes the same filespace name to all backups stored on the TSM Server. This results in various undesired consequences for the backups of large databases which are normally performed using multiple DB2 sessions (streams). Specifcially, a given non-DPF database is normally backed up under the same TSM nodename so a backup of such large database results in a creation of multiple backup images on the TSM Server, with all these images assigned the same nodename and filespace name. Due to such behaviour the target stg pool is required to be configured with the collocation disabled. However, after subsequent TSM Server processing, such as reclamation, backup storage pool and export/import, these images are always re-shuffled in an unpredictable manner so the recovery of the DB2 database cannot be performed with the same concurrency which was originally used during the backup.
Please consider changing the backup behaviour to generate session number identified as part of the filespace string to allow filespace-based distiction between images within the same backup; this would enable customers to configure target stg pool collocated by filespace which would in turn allow the preservation of the concurrency during the restore. Also note that when SEGMENTSIZE parameter is used, this may result in creation of dozens of images during the backup so it is important to ensure that images belonging to different sessions are not collocated together on the same tape media after collocation, backup storage pool or export/import.