# Determining Tokens within the Honeywell ULM Log Files

Token usages are logged in two parts of the Honeywell logs:

Honeywell Logs
04/29/2019 8:06 License: UniSimDesign.Token (USDTemp) +124 Referencer: UniSimDesign.Process
This 04/29/2019 8:06 TokenLicense: UniSimDesign.Process (USDTemp) +1 Referencer: UniSimDesign R461 @ host1.domain.com:user1@domain.com {IP:10.99.75.33}

The first part contains token details such as the token pool, token cost, and the feature check in/out.

Honeywell Logs
04/29/2019 8:06 License: UniSimDesign.Token (USDTemp) +124 Referencer: UniSimDesign.Process
This 04/29/2019 8:06 TokenLicense: UniSimDesign.Process (USDTemp) +1 Referencer: UniSimDesign R461 @ host1.domain.com:user1@domain.com {IP:10.99.75.33}

The second part is the license check in/out information. This part contains the main feature, user, and hostname.

Note that the second part line is already supported in the current Honeywell ULM implementation, and to extend the current support to token-based licenses, the TokenLicense keyword will be used to determine if it is a token-based or a regular feature.

There are also cases wherein the first part has two lines:

Honeywell Logs
06/04/2020 9:50 License: UniSimDesign.Token (USD) +170 Referencer: UniSimDesign.Dynamic
06/04/2020 9:50 License: UniSimDesign.Token (USD_AddTKN) +55
06/04/2020 9:50 TokenLicense: UniSimDesign.Dynamic (USD) +1 Referencer: UniSimDesign@host1.domain.com:user1@domain.com

For this example, the license token pool is UniSimDesign.Token while its feature is UnisimDesign.Dynamic. The token cost of UnisimDesign.Dynamic is 170 from the (USD) bucket and 55 from the (USD_AddTKN) bucket, for a total 225.