The export/import functionality in the DB2 Automation Tool can be used to seamlessly copy object, exception, utility, or job profiles from one DB2 subsystem to another as long as both the source and target subsystems are running on the same LPAR. However, this process does not work in this same manner if the source and target DB2 subsystems are running on different LPARs. In this case all source profiles must be exported to data sets on the source, FTPed to the target LPAR, and imported from these datasets on the target subsystem.
Test and Production DB2 subsystems are almost always running on separate LPARs, and this would enhancement would make it much easier to copy Automation Tool profiles from a pre-production DB2 subsystem to a production DB2 subsystem.
The ability to access remote DB2 subsystems currently exists in other DB2 Tools, such as the DB2 Administration Tool.
Why is it useful?
|Who would benefit from this IDEA?||Anyone setting up autonomics|
How should it work?
The DB2 Automation Tool should be able to use the Distributed Data Facility of DB2 along with the definitions stored in the Communications Data ase (CDB) tables of the DB2 Catalog to allow Automation Tool profiles to be seamlessly copied to a remote target DB2 subsystem that is defined and known by the source DB2 subsystem.
|Priority Justification||Improved product usability of DB2 Automation Tool as a whole, and improved DBA efficiency.|