Attaching to an additional Db2 subsystem on a different MVS system


From a 

Some content is unavailable due to permissions.

 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

Some content is unavailable due to permissions.

running on the development system, you can use DDF to run a

Some content is unavailable due to permissions.

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.
  • Some content is unavailable due to permissions.

    is installed on the local SSID, and the object is bound with

    Some content is unavailable due to permissions.

    on the remote Db2 subsystems.
  • Some content is unavailable due to permissions.

    is installed on the remote Db2 subsystems.
  • The same version of

    Some content is unavailable due to permissions.

    is on all Db2 subsystems.
  • The collection IDs are the same for all

    Some content is unavailable due to permissions.

    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

Some content is unavailable due to permissions.

main menu, type the location of the DDF.


 

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