Hi.
I have Bse24-eps (V2.1.8) running a Nonstop machine. (NB56000) and monitoring with Prognosis.
I need to add in my monitoring system 3 new custom fields. 2 of this fields correspond to object Id 2144 an 2146
and the third field is the object Id 30020 ( is a CSM)
in the file IRTSVCOI I made the following configuration:
FLD3 = TOKEN(2144,INT(0))
FLD4 = TOKEN(2146,INT(0))
FLD5 = TOKEN(30020,STRING(1,3))
As a result the FLD3 and FLD4 show the corresponding data, but the FLD5 does not show it.
Anyone have any idea if for the CSM (programmed in C ++) I need something additional so that prognosis can capture the data and show it?
thanks.
Mario Z.
Hi Mario,
I supposed you have checked the Online Help:
I need to confirm with Product Manager if CSM is supported by Prognosis.
Cheers
Linda
Hello Mario,
Thank you for bringing this to our attention. Custom Key fields can be defined when there are fields in the transaction data files that cannot be successfully mapped to the 'standard' Key fields. There is a specific set of Custom Keys for the type of financial transaction switch being used. "CSM" is not currently showing on our list of fields, but does not mean we do not support it at this time.
We would like to assist you more on this issue. In order to do so, we will need the following:
1. We need to have a Support case opened up in order for us to track and review log details.
2. Prognosis sees the raw journal format, as it appears on disk. We will need to get a masked copy of the Journal log, without changes to the positions for us to review.
3. We will also need an IRfax of the Nonstop server to be added to the case. See below for instructions on pulling an IRFAX.
Process to create an IRFAX on NonStop:
Please let me know if you have any questions?
Thanks,
Dale
In general, yes you should be able to use any Base24eps TDE that meets certain criteria in the user fields in both Transaction Surviellence and Summary (IRTXNCOL) - Base24 configuration.
If you are using a Base24eps Realtime Feed and not a direct journal feed, you need to have them consistent between IRTXNCOL & IRTSVCOL though as they are likely configured in a forwarded situation.
Some of the caveats though where User Fields will just not work though are:
1) The TDE is binary
2) The TDE is not exposed to Prognosis and internal only
3) the TDE is filtered out in the ACI Desktop Configuration (I don't remember the name of the utility to do this)
4) The TDE format is highly variable in itrs structure.. such as there are some TDEs which could be over 500 characters long if I recall right and you need to do additional logic parsing within the TDE to determine what is actually contained within it.
According to the TDE Manual 2144 & 2146 looks like it is a string so your syntax doesn't look quite right and you would want to use a string format.
Your custom token as long as the token length is less than 11 characters and it passes the caveats above you should be just fine.
I need to add in my monitoring system 3 new custom fields. 2 of this fields correspond to object Id 2144 an 2146
and the third field is the object Id 30020 ( is a CSM)
in the file IRTSVCOI I made the following configuration:
FLD3 = TOKEN(2144,INT(0))
FLD4 = TOKEN(2146,INT(0))
FLD5 = TOKEN(30020,STRING(1,3))
Members | Likes |
---|---|
46 | |
13 | |
13 | |
12 | |
10 |