One of the problems a lot of people have complained about with the RAP product is the need to split the Object and Database objects into 2 separate Journal Environments. This requirement was placed upon the product to allow the APYJRNCHGX command support which is in-turn needed to allow the automatic enrollment within the replication environment of any newly created DB files. APYJRNCHG command can be used to automatically create Data Area, Data Queue and IFS objects but not Database Files. We had been looking at new support which is due in Version 6 Release 1 of the OS which removes the need to use the APYJRNCHGX command to support automatic enrollment of the Database files, but felt this was going to be too late for many customers.
We discussed a possible alternative with IBM which would use the QDBRPLAY API in conjunction with the APYJRNCHG command and remove the APYJRNCHGX command entirely. they felt the only problem would be if Commitment Control was being used, this is because the journal entries would have to be rolled back in sequence etc giving the program logic a few challenges to overcome. As this product is aimed at the smaller customer, many of whom do not have Journalling set up let alone Commitment Control we felt this was a minor shortcoming and one we would advertise and live with until the Version 6 release of i5OS is released and available.
We will be releasing a new PTF probably at the end of this month with the new feature. It will only change the user interface in one area which is you will now be able to configure a *BTH journal which supports Object and DB File auto enrollment. The rest of it will be hidden in programs that handle the new API calls.
The above activity is obviously taking quite a bit of development time, this is limiting the time that I can spend on the LAMPS build project, but it is still ongoing and as soon as I get time to take the next step I will post the procedures we took.
Chris…