RAP with automated IFS replication

The PTF is finally built and running in our test environments which provides the IFS replication capabilities to the Receiver Apply program using the QAUDJRN instead of the user journals. The User journals are very good at replicating the changes in most circumstances but we found a few small issues when testing at a customer recently. The biggest problem we found was the inability of the journal apply process (APYJRNCHG command) to support new IFS objects created by the use of a move or copy option taken from the WRKLNK screens.

We had never intended to create our own IFS replication process as we felt the capabilities provided by the IBM APYJRNCHG command would have been more than adequate but having found this glaring problem we decided to bite the bullet and code up the required functions for replication based on entries deposited in the QAUDJRN. Those who follow the iSeriesNetwork forums or this blog will have seen some notes about the issues we encountered when starting down this path, but we have finally got working code which appears to cover most of the scenarios we can throw at it?

We took the decision to keep it Simple and only allow the configuration at the directory level. We did add the ability to add a directory as an Exclude which allows sub directories to be omitted. The option to set individual objects up for replication was discounted as we felt one of the major issues with the HA products out there today is just how complex it can be to set them up. Having a simple directory based configuration allows us to make programmatic decisions quicker than if we had to filter through loads of generic object entries. Plus the users can become lost with when an object meets an inclusion or exclusion clause! One of the biggest complaints we have heard in the past is just how hard it can be to set up the replication parameters for some of the HA tools! That’s why it takes 2 weeks to install these products using specialized staff.

The changes are pretty significant so the decision to release this as a PTF was not taken lightly, however because another recent PTF which allows the filtering of remote libraries for the apply process excluded the IFS if it was configured meant we had to do something now and provide it to the customer base.

If you would like to test the new functionality let us know, the PTF will be in test for sometime to ensure we have not missed something significant. Replication by the use of journals is still supported and will not be replaced by this technology for the time being.

Chris…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.