ISN assignment by batch (ICL)

Transaction Server item sequence number (ISN) assignment can be done before the extraction process.
Note: Configure only one ISN assignment method at the same time. Use either ISN assignment by transmission or ISN assignment by batch (ICL).
ISN assignment for a batch (ICL) can be started when:
  • A PresentmentStateChange event occurs indicating that the batch (ICL) is loaded.
  • The Preload ISN Task scheduled Services Framework task runs.

In both cases, the preload ISN task must be registered and configured. For this example, the task configuration name is “Pre Load ISN Task”. The configuration name must match the destinationID parameter of the event stanza. Also, in the task configuration, the value for the UOW Type for Sweep and Manual Mode parameter must be set to BATCH. For more information on all the specific configuration parameters used by this task, see Services Framework task registration and configuration.

The event and scheduled task methods can be used together to ensure that all batches (ICLs) are assigned ISNs. Event processing initiates assignment immediately after a batch (ICL) is loaded, while a repeating, scheduled task provides a method of running assignment for eligible batches (ICLs) that possibly failed processing by the event handler.

The following example shows how to configure an event task to perform an ISN assignment before an extraction. A scheduled repeating task is configured by using the Services Framework Scheduler page.

Create a PresentmentStateChange event that starts the preload ISN task. The event should occur when the batch (ICL) is loaded, is not yet processed by the preload ISN task, and has a condition of accepted. The following shows the example event stanza that is provided in the SchedulerReference.xml file, which is included with the product:

<EVENT>
   <NAME>ISN Allocation</NAME>
   <TYPE>PresentmentStateChange</TYPE>
   <TYPE>PresentmentGroupColumnChange</TYPE>
   <TYPE>PresentmentColumnChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
   </EXEC>
   <PARAMETER name="msgType">TaskInitiation</PARAMETER>
   <PARAMETER name="presStates1">LOADED,!ISN_ALLOCATED</PARAMETER>
   <PARAMETER name="condition">ACCEPTED</PARAMETER>
   <PARAMETER name="pending">N</PARAMETER>
   <PARAMETER name="group.condition">ACCEPTED</PARAMETER>
   <PARAMETER name="group.pending">N</PARAMETER>
   <PARAMETER name="group.schemeId">Check</PARAMETER>
   <PARAMETER name="presLevel">PROC</PARAMETER>
   <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF>	
   <PARAMETER name="destinationID">Pre Load ISN Task</PARAMETER>
   <PARAMETER name="jmsSendQueue">FXH.SERVICESFRAMEWORK.INPUT.QUEUE</PARAMETER>
</EVENT>
Note: Extraction and ISN assignment cannot both be running at the same time for the same batch (ICL).