IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Copy profiles seamlessly across DB2 subsystems on different LPARs

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.

  • Perry Shindle
  • Jun 17 2019
  • Will not implement
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.

Idea Priority Medium
Priority Justification Improved product usability of DB2 Automation Tool as a whole, and improved DBA efficiency.
Customer Name PennDOT
Submitting Organization
Submitter Tags
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions