db2 11 nfm z/os 2.2; activating changes made to communications database tables

Chris Hoelscher

db2 11 nfm z/os 2.2; activating changes made to communications database tables
Good day

We are in the process of converting stand-alone db2 subsystems to single-member (for now) datasharing groups

Part of this conversion requires us to insert/update/delete rows from 3 tables (locations, lunames, lulist) for each partner subsystem with which we wish to remote to
Our experience has shown us that these changes are ignored? Until after DDF is bounced on the partner subsystems

Is there a way to make these changes visible and effective short of bouncing ddf (no one wants their DDF traffic interrupted)

Thanks for any suggestions

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
Humana Inc.
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 476-2538 or 407-7266

Todd Burch

RE: db2 11 nfm z/os 2.2; activating changes made to communications database tables
(in response to Chris Hoelscher)

There are only 2 ways unless there is a 3rd party vendor solution out there. 
1) Bounce DDF. 
2) If you have not made a connection to that site since DDF was last started, you can change anything you want and it will be picked up.

I just answered this question yesterday in a PMR! 

https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/inst/src/tpc/db2z_updatelumodeswconvlimits.html