How do I setup ACF2 to propogate to multiple systems. Some share databases others do not.

Document ID : KB000044751
Last Modified Date : 14/02/2018
Show Technical Document Details


How do i setup ACF2 CPF to send updates to lpars that are sharing databases so that they do not duplicate updates.



The recommendation would be to use CCI's Generic Resources in your setup.

First let me explain how CA has always recommended setting up your system when communicating with multiple systems sharing the same set of databases. We have always said that when you have multiple systems communicating to multiple systems, you should send out commands from all systems and only receive commands into one of them.

Here is a sample system setup:
PROD and PRD2 share a LID database (call it LID DB1)
DEV1, DEV2, AVT1, AVT2 share a LID database. (call it LID DB2)
PRD3 is a standalone LPAR with it's own database. (call it LID DB3)

On PROD & PRD2 you update the CCI parms to have a SYSPLEX parm. The SYSPLEX name for these 2 systems would be the same thing, like SYSPLEX(LIDDB1). DEV1, DEV2, AVT1, AVT2 would all have SYSPLEX(LIDDB2). And PRD3 would be left alone.

With this setup, you would put a target list on PROD & PRD2 of
With this setup, you would put a target list on DEV1, DEV2, AVT1, AVT2 of
With this setup, you would put a target list on PRD3 of

What generic resources gains you over the other setup is more of a guarantee that the request will make it to the other databases right away. What I mean by this is that with this setup, if the connection between PROD & DEV1 is down, the request is held in CCI until the connection comes back up. With generic resources, if that connection is down, CCI knows by the SYSPLEX values that those 4 systems are connected. CCI will then try to pass the request to the next node in the sysplex. This is used to try and guarantee that the request only gets sent once to a group of nodes and it gets sent right away.

Each LPAR will have a Control(CPF) OPTIONS record created and the HOME() value will equate to the SYSID() parameter
in the CCI parms dataset.

In addition, each lpar will have all the other lpars defined in NODEDEF records.
Finally, each SYSPLEX definition will have a nodedef record on eaxch system so that commands can be sent to the SYSPLEX ID or the standard NODE ID.