Trappable Events
In TBXDS'
<MetaData>, most
<Event> messages should not be
automatically processed, although it is possible to
log all critical and fatal events.
However, some Events can be highly useful for automated
processing of the
<TBMData> responses.
| 331 |
No data at all in TBXDS response; this denotes
that the TBXDS was probably not able to return
the data you requested, and the only contents
of the <TBMData> structure
is its <MetaData>.
|
| 341 |
The TBXDS engine was not able to locate any
information for the requested ticker; if this
happens for tickers that were previously
known, the affected issues have either been removed
or renamed, so please contact Infront.
Currently, it is not yet possible to retrieve
information on the exact ticker; the (non-parseable)
event message gives the complete description.
|
| 342 |
The TBXDS engine was not able to locate any
quote information for the requested ticker;
it does mean, however, that the issue
itself is known to the database. One reason
for lacking data could be that the trade for
this issue has been suspended. Currently,
it is not yet possible to retrieve information
on the exact ticker; the (non-parseable) event
message gives the complete description.
|
| 343 |
There is no news available for a particular
news agency. This is quite common if the
news is requested regularly (e.g., every 10
minutes or less for personalized news,
or every minute for general news). Currently,
it is not yet possible to retrieve information
on the exact agency; the (non-parseable) event
message gives the complete description.
|
| 345 |
There is no chart available for a particular
ticker and chart type combination.
Note
Charts are not created 'on the fly' for
every request; this means that you will
have to buy a new chart type for every
non-default chart (the default charts are
67, 68 and 69: intraday, 8-weeks and
2-years).
Currently,
it is not yet possible to retrieve information
on the exact chart details; the (non-parseable)
event message gives the complete description.
|
| 622 |
The database for the TBXDS service is down.
Please contact Infront, if Infront has
not already contacted you.
|
| 802 |
The TBXDS service is currently 'under maintenance',
which usually means that the web service or database
is being upgraded. Normally this event only occurs
outside of the AEX/Bel20 opening times, so this
event shouldn't form a problem. Most updates happen
without taking the TBXDS service off line, however.
Formally speaking, you should monitor the
<SystemMaintenance> node emitted
some time before and during the maintenance period.
|
See also
<Event>