MAP FIELD OF PTLF (BASE24 CLASIC)

Highlighted
05 Base Camper

MAP FIELD OF PTLF (BASE24 CLASIC)

Hello,

 

In our PTLF file each transaction has a length of 988 positions, we want to show a specific field in PROGNOSIS within the first 200 positions, is this possible?

 

Regards

1 ACCEPTED SOLUTION

Accepted Solutions

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

@MANUEL_AUNA 

Sometimes it is a bit 'finicky' especially around invoking the changes especially on a Nonstop where the Base24 configuration won't start.  Technically all you "should" have to do is add the configuration and click "start".. BUT...

 

If you have previously defined say FLD1 (correct or not) and click start.. to make modifications to it you have to ensure ANYTHING requesting the record is stopped or closed to modify it.. so if you have a 60s or 5 minute DB Collection with FLD1 in its collection.. its not going to invoke the change and you will get no-start conditions.   

 

The only way to get around this is to hard stop the configuration in the Prognosis Subsys "SET RUN" statement and setting it to "N".. waiting at least 10 seconds.. then changing it back to "Y".

So its very important you flush these out in a test environment to avoid needing to do stop/start in Production. IRTSVCOL (DETAIL) will reposition when to the last interval up to a point as configured.. but IRTXNCOL (Summaries) will not and you will have a gap. 

 

If you need further assistance I would suggest a support case with a FUP COPY of at least 5 PTLF TX Records (DO NOT PUT IT IN HERE) into a word  document highlighting the data you are trying to retrieve, the name of it, and what you have previously tried. 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Sr. Services Solution Engineer, Payments & Infrastructure – MSci. PA, CISSP, ITIL.

View solution in original post

6 REPLIES 6
Highlighted

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

Yes, this is easily done as long as:

1. The field you want to select is in a fixed position in the PTLF -or- is in a fixed position within a Token

2. The field is a string value or numeric of type signed INT (2 bytes), INT32 (4 bytes) or INT64 (8 bytes)

The values will appear in one of the 'User Fields': FLD1 - FLD20  (you select which field when you configure)

 

For Transaction Manager (i.e. transaction summary records) this is configured in the BASE24 configuration (for BASE24 classic).  The syntax is in the online help section: https://help.prognosis.com/prognosis/117/base24-and-base24-eps-user-defined-key-fields-25170130.html

 

Examples:

! Extract 4 characters (string) from fixed offset 10 bytes into TLF log record
! and put it into FLD11
User Field (EXAMPLEATM, FLD11, "STRING(10,4)")

! Extract first 20 characters from ‘B4’ token and put into FLD1
User Field (EXAMPLEATM, FLD1, "TOKEN (B4, STRING(0,20))")

 

For Transaction Surveillance (transaction detail and exception records), it is configured in the IRTSVCOI file and the syntax is very similar: https://help.prognosis.com/prognosis/117/user-defined-fields-for-base24-25170222.html

(NOTE: they are referred to, somewhat confusingly as 'User Defined Fields' in this section, rather than 'User Defined Key Fields' - don't confuse them with the completely different User Defined Fields (UDF) available in the Prognosis Client and WebUI)

 

Same examples as above, but for TSV:

; Extract 4 characters (string) from fixed offset 10 bytes into TLF log record
; and put it into FLD11
FLD11 = STRING(10,4)

; Extract first 20 characters from ‘B4’ token and put into FLD1
FLD1 = TOKEN ("B4", STRING(0,20))

(the above examples need to go into one or more of the [TRANSACTION-LOG-LOCATION-n] sections, depending on which log file sources you want to extract the User defined Key Fields from)

 

By the way, the same applies to TLF (for other readers) and also for other transaction sources such as BASE24-eps, Postilion, Connex, etc

 

Highlighted

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

@MANUEL_AUNA  To also add that after you have the field mapped, if it is just a coded value like "231" and you want to also assign a description.. if you are on 11.6 or later this is very easy to do using the Message Mapping Functionality which is available out-of-the-box to all customers utilizing a FTM/GTC based collector like Base24/Postilion/Connex/etc. 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Sr. Services Solution Engineer, Payments & Infrastructure – MSci. PA, CISSP, ITIL.
Highlighted
05 Base Camper

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

Hi @ChristopherS ,

 

Use the recommended configuration but it does not get any value, in the ptlf layout the value puts it as follows


179 [1] auth.responder PIC X(1).

Indicates where the response message to this
transaction originated. Valid values are:
1 = Device controlled by BASE24
2 = Device handler
3 = Authorization process
4 = Host Interface process
5 = Host
6 = Interchange Interface process
7 = Interchange
S = Secondary Authorizer


based on this I put the configuration:

USER FIELD ($DATA3.PRO6PTLF, FLD1, "INT(179)")

 

It is right ?

 

Regards

Highlighted

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

@MANUEL_AUNA 

The first field needs to be the logical name not the physical path.

I don't have the token manual open, but doesn't the responder have its own token as well and then you could use the offset.. if not use STRING(179,1)  not INT(179) I believe. .. sometimes having to adjust a position or two as well. 

 

The syntax is also slightly different between Transaction Manager and IRTSVCOI.

 

Note: The responder though is a standard field in Base24eps: 

The value of this field is obtained from TDE Transaction Responder (ID 2120).

 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Sr. Services Solution Engineer, Payments & Infrastructure – MSci. PA, CISSP, ITIL.
Highlighted
05 Base Camper

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

@ChristopherS 

 

I already tried as you mentioned, but I still have problems displaying information, when I configure the BASE24 module from the GUI, sometimes it starts correctly and sometimes it no longer starts, and tried with different fields of the PTLF without success, will there be any other way of knowing how to configure it?

Regards

Re: MAP FIELD OF PTLF (BASE24 CLASIC)

@MANUEL_AUNA 

Sometimes it is a bit 'finicky' especially around invoking the changes especially on a Nonstop where the Base24 configuration won't start.  Technically all you "should" have to do is add the configuration and click "start".. BUT...

 

If you have previously defined say FLD1 (correct or not) and click start.. to make modifications to it you have to ensure ANYTHING requesting the record is stopped or closed to modify it.. so if you have a 60s or 5 minute DB Collection with FLD1 in its collection.. its not going to invoke the change and you will get no-start conditions.   

 

The only way to get around this is to hard stop the configuration in the Prognosis Subsys "SET RUN" statement and setting it to "N".. waiting at least 10 seconds.. then changing it back to "Y".

So its very important you flush these out in a test environment to avoid needing to do stop/start in Production. IRTSVCOL (DETAIL) will reposition when to the last interval up to a point as configured.. but IRTXNCOL (Summaries) will not and you will have a gap. 

 

If you need further assistance I would suggest a support case with a FUP COPY of at least 5 PTLF TX Records (DO NOT PUT IT IN HERE) into a word  document highlighting the data you are trying to retrieve, the name of it, and what you have previously tried. 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Sr. Services Solution Engineer, Payments & Infrastructure – MSci. PA, CISSP, ITIL.

View solution in original post

Webinar: Top Ten Predictions in Retail Payments for 2020

Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...

Join Webinar
Top Liked Members