Skip to main content

Hello 

When I create a replication group for the first time and use wildcard for INCLUDE spec such as library = XYZA3* (with *ALL for object name and type), I see that iCluster retrieves all corresponding library names into the INCLUDE list for me to save my time and the entry XYZA3* also remains in the list.   I ask the local iCluster specialist if I should leave the entry XYZA3* in the list and the answer is that if I leave it, any subsequent new libraries that match this wildcard name will be added automatically to the replication group without having to restart the replication group. (Sound nice!) This should imply that if I remove this wildcard entry from the group, I have to manually add the new libraries that match this wildcard name by myself in the future into the replication group definition. 

I did a Google search to try to find any formal information from iClsuter web site to confirm this statement but was not able to find any.   I would appreciate any response to confirm or otherwise.   

Another question is whether this use of wildcard entry in the INCLUDE or EXCLUDE spec applies to IFS folder names and any other native object names and types or not? 

Any pointer to any URL relevant to this matter is also much obliged. 

Thanks.

 



------------------------------
Satid Singkorapoom
IBM i SME
Rocket Forum Shared Account
------------------------------

Hello 

When I create a replication group for the first time and use wildcard for INCLUDE spec such as library = XYZA3* (with *ALL for object name and type), I see that iCluster retrieves all corresponding library names into the INCLUDE list for me to save my time and the entry XYZA3* also remains in the list.   I ask the local iCluster specialist if I should leave the entry XYZA3* in the list and the answer is that if I leave it, any subsequent new libraries that match this wildcard name will be added automatically to the replication group without having to restart the replication group. (Sound nice!) This should imply that if I remove this wildcard entry from the group, I have to manually add the new libraries that match this wildcard name by myself in the future into the replication group definition. 

I did a Google search to try to find any formal information from iClsuter web site to confirm this statement but was not able to find any.   I would appreciate any response to confirm or otherwise.   

Another question is whether this use of wildcard entry in the INCLUDE or EXCLUDE spec applies to IFS folder names and any other native object names and types or not? 

Any pointer to any URL relevant to this matter is also much obliged. 

Thanks.

 



------------------------------
Satid Singkorapoom
IBM i SME
Rocket Forum Shared Account
------------------------------

Hi Satid,

You are correct.  After the original invocation of the selection with a generic selection or wildcard, any new libraries that match the generic selection are added automatically to the group.  If you remove the generic selection, any new inclusions would need to be maintained manually.  One thing that is also helpful, if there are added libraries that match the generic selection that are not desired for replication, you can simply CHANGE the individual selection to an EXCLUSION and leave it in the group definition (rather than delete it) to document your final selections and prevent future undesired inclusions.

This capability in iCluster also extends to BSF (byte stream file) selections.

The best place to find Rocket iCluster documentation, installation guides, and release notes (etc.) is on Rocket's Documentation Library web site.    Rocket Software Documentation

Specifically, the section regarding object specifiers for library and IFS objects can be reviewed here:

Object specifiers and path object specifiers (rocketsoftware.com)

Regards,

Mark



------------------------------
Mark Watts
Software Engineer
Rocket Software Inc
Waltham MA US
------------------------------
Terms & ConditionsAccessibility statement