ACI expanded the PTLF record with tokens instead of just making the PTLF record bigger. This allowed different fields to be added to the PTLF without having a lot of waisted space in the PTLF record for fields that that are not filled in. These tokens have a special format and may not always be at the same offset from the beginning of the PTLF record. The TOKEN param in the BASE24 static config allows Prognosis to find data in the PTLF record that is in one of these Tokens.
i.e.
The Stand in code from Visa is placed in the PTLF when it exists, with the "B0" token at offset 59 for 4 bytes. Since the TOKEN is not guaranteed to be at the same location in the PTLF every time, the TOKEN param tells Prognosis to find the Token in the PTLF record, then place the data in to FLD1 of the Prognosis record.
The below example text from our BASE24 static config shows that we are pulling the 4 byte STIP code from the PTLF that is in the "B0" token at offset 59. The field this then mapped and we have 2 keys enabled so we can create threshold and analysts to trigger when a specific STIP code is logged
!custom fields for VISA
!stip-cde
USER FIELD (POS1LOGS, FLD1, "TOKEN (B0, STRING (59,4))")
USER FIELD (POS2LOGS, FLD1, "TOKEN (B0, STRING (59,4))")
Map Field ( *, Base24PosTransactionSummary, FLD1, FLD1 )
Enable Key ( Base24PosTransactionSummary, FLD1 )
Enable Key ( Base24PosTransactionSummary, ACQUIRER+FLD1 )
