Available from version 15.0
Previously, the system supported only sequential writing to the Condition Record Item Keys (CRCI1 - CRCI12). To improve performance, parallel writing to Condition Record Sets has been implemented.
To enable parallel writing, a Condition Record Splicing job has been developed. This job writes the Condition Record Item Keys to the distinct Condition Record Sets (CRCS). Each job is dedicated to writing to one specific Condition Record Set. (For more information see Condition Records Splicing Options). This enhancement ensures data access safety for concurrent processes. Parallel jobs can execute simultaneously across the different Condition Record Sets. However, if the multiple Condition Record logics need to write to the same Condition Record Set (i.e., share the same concurrent key, representing the Condition Record Set), the corresponding Splicing jobs will be executed serially, one after the other.
This approach also ensures the consistency of splicing operations. By allowing only one running splicing job per Condition Record Set, Condition Records are spliced correctly.
Specifically, the Condition Record Processing job executes Condition Record logics, generating the Condition Record Processings. Subsequently, the Condition Record Splicing job performs splicing operations and writes these Condition Record Processings into the appropriate Condition Record Sets, creating the Condition Record Item Keys (CRCI1 - CRCI12).
Additionally, please note that, specifically for loaddata, Condition Record Splicing jobs are created directly, without involving Processing Jobs or executing Condition Record logic. In this case, loaddata loads Condition Record Processing directly. For more information see Condition Records Splicing Options.