Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI SQL Explorer for Db2 13.1.

Attaching to an additional Db2 subsystem on a different MVS system

From a 

SQL Explorer

 session, you can attach to a Db2 subsystem on another MVS system if you have the Db2 DDF.

 

Example

Assume that you have a production system on one MVS system and a development system on another MVS system. With SQL Explorer running on the development system, you can use DDF to run a SQL Explorer job on the production system. The following figure illustrates the process.

GUID-D2CC117B-2D6A-4178-96E3-3CF057643470-low.png

Before you begin

Ensure that the following requirements are met:

  • Remote locations are defined in the SYSIBM.LOCATIONS table of the local Db2 subsystem and are connected using the Db2 DDF.
  • SQL Explorer is installed on the local SSID, and the object is bound with SQL Explorer on the remote Db2 subsystems.
  • SQL Explorer is installed on the remote Db2 subsystems.
  • The same version of SQL Explorer is on all Db2 subsystems.
  • The collection IDs are the same for all SQL Explorer installations (in order to use DDF to connect). 

    Some content is unavailable due to permissions.

To attach to an additional subsystem on a different MVS system

In the DDF Location field on the SQL Explorer main menu, type the location of the DDF.

Related topic

Attachment-of-SQL-Explorer-to-local-or-remote-Db2-subsystems


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*