PI86942 enhanced z/TPFDF data event processing on PUT 14 so that you can use data events with z/TPFDF databases that do not require holding a record for updates. Now, APARs PI89192 and PJ45037 provide additional enhancements to z/TPFDF data event processing on PUT 14.
z/TPFDF data event processing collected data event information only for updated LRECs or the full subfile. However, when data event information was collected only for updated LRECs, there might not be enough context for applications to properly process these LRECs. Unchanged LRECs in a subfile can contain identifying information for updated LRECs in the subfile, which might be needed. For example, unchanged LRECs might contain the customer ID, while the changed LRECs contain the latest transaction information. In this example, you had to write additional application or enrichment code to collect the customer ID.
Furthermore, when data events were defined for a partitioned z/TPFDF file, data events were enabled for all partitions in the file. No mechanism was provided to collect data only for certain partitions. An application developer had to write an application or enrichment program to query the partition for each data event and then chose to either ignore or process it.
With z/TPFDF APAR PI89192 and co-requisite z/TPF APAR PJ45037, z/TPFDF data event processing now provides the ability to automatically collect LRECs when the z/TPFDF subfile is opened for updating. This enhancement allows all or selected unchanged LRECs to be collected and provide missing context for changed LRECs. With this support, you do not need to write additional application or enrichment code to collect these unchanged LRECs.
Furthermore, these APARs provide selected partition support for z/TPFDF data event processing. With this support, a database administrator can use the <partitionIncludeList> element in the business event specification to specify which partitions to create data events for. If the <partitionIncludeList> element is defined, a data event is created for a changed subfile only if the subfile is in a partition list specified by the <partitionIncludeList> element.
For more information about APARs PI89192 and PJ45037, see the APEDIT.