I taken a look at the new publication, 'IBM Integrated Synchronization - Incremental Updates Unleashed', and found it to be a valuable resource in terms of stopping incremental updates, modifying DDF Alias (xx).
First, I must emphasize the need to follow all installation, activation, and set-up guides. If you didn't follow such guidelines, you must refer to the product documentation, and certain Redbook, Redpaper, primary network, and the Distributed Data Facility documentation.
There are a few other concerns involved such as meeting the Integrated Synchronization pre-requisites, requirements, correct configuration settings; inclusive of activation Instructions. Other instructional guides, e.g. the SMPE/E report MISSINGFIX command to specify in FIX Category, also need to be run. There are additional resources and installations that will pull in almost all maintenance issues.
"When incremental updates are enabled later in the configuration console, the application name <app|Name> as well as the signon key <key> will be needed, so that information can be passed onto the accelerator administrator."
If this is a configuration issue , we need to disable incremental updates, and we need to provision a command to perform such:
MODIFY DDF ALIAS(<alias-name>) STOP
And new connections to the secure port can be enabled again with this command:
-MODIFY DDF ALIAS(<alias-name>) START
where
�� <alias-name> is the name for the location alias for Integrated Synchronization.
"An advantage of location aliases is that they can be started and stopped individually per Db2 member. This can be used to control resources and availability of the secure port for Integrated Synchronization on each Db2 member in a data sharing group, e.g. for planned maintenance. Other distributed workloads that access the general Db2 secure port would not be affected by stopping a location alias."
To stop receiving incoming connections on the secure port defined by the location alias the above stated Db2 command is needed would be needed.
I encourage you to visit the documentation at:
http://www.redbooks.ibm.com/redpieces/pdfs/redp5616.pdf
There is plenty of information on activating/deactivating incremental updates utilizing IBM's Integrated Synchronization - Incremental Updates Unleashed strategies and techniques. The documentation specifies the information needed for permissions on transferring a certificate for verification of encrypted connection to DB2; enabling incremental updates in the configuration console, and more . . .
I sincerely hope this helps.
Yvonne
Sent from my iPhone
Original Message:
Sent: 12/24/2020 12:52:00 AM
From: Ron Hameiri
Subject: RE: Question about how to stop incremental updates
Hi,
You can write a REXX program to execute the the ACCEL_CONTROL_ACCELERATOR stored procedure with the "<stopReplication/>" parameter.
------------------------------
Ron Hameiri
z/OS Db2 System Programmer and DBA
Email: Ron.Hameiri@gmail.com
Linkedin: https://il.linkedin.com/in/ron-hameiri
------------------------------
Original Message:
Sent: Wed December 23, 2020 01:46 AM
From: KATSUKO HAYASHI
Subject: Question about how to stop incremental updates
Hello,
I have a question about how to stop incremental updates, in case of using Integrated Synchronization .
(*) Assuming defining location alias and SECPORT for Integrated Synchronization.
According to the description in manual, when stopping ( or starting ) incremental updates, the user is guided to operate from IBM Db2 Analytics Accelerator Studio. But, our customer prefers to fire the command from SDSF ( or z/OS console ).
So, is it possible to fire "MODIFY DDF ALIAS(xx) STOP" command for stopping incremental updates, instead of using IDAA Studio ?
If not, If not, please let me know the reason why.
#Db2forz/OS