Contents - Index - Previous - Next


DXCC Exceptions


Used in conjunction with the DXCC prefix file is a second datafile that contains the exceptions callsigns. [DXCC_Exceptions.dat] is searched before the main DXCC prefix file.

The [dxcc_pre.dat] file is formatted with prefixes up to 4 characters - which is the maximum character length of DXCC country identifiers. The exceptions file allows full callsigns to be added, and is a way for GenLog to tag callsigns of stations living in countries other than their `Home` DXCC country. The FCC allows U.S. stations to apply for DX callsigns - NP2CB, KG6K and KH6QAI just to name a few. This is crazy! Other countries do it too - check the GB callsigns in the datafile. The contest sponsor will hopefully have an updated DXCC lookup file when judging logs - and they will change your score anyway.

As in the main DXCC prefix file, the exceptions file is format specific - GenLog use 2 fields. 1). The left-most data is the callsign, followed by at least 1 <Space> - not <Tabs>. 2). The data field at the end of each row is the DXCC country identifier - fielded for 4 characters as shown below. Example: the 4 character U.S. identifier would be 3 <Spaces> followed by W. VP2E is already 4 characters.
4U1WB  [USA]<NA>08   W
KH6QAI [USA]<NA>06   W
VP8/MM0TJR/P [Antarctica]<SA>74  CE9

Also - as in the main DXCC prefix file - DXCC prefixes that can be confused with States or RAC provinces like PA, ON, HI, LA etc are followed by ! in this file.
OH0JJS/1 [Finland]<EU>18  OH!
To maintain this format, copy the appropriate line from the [ dxcc_pre.dat ] file and edit it when adding exceptions to the file.

Add as many exceptions to the file as you wish. If you work a station that is in a different DXCC country than listed in the [dxcc_pre.dat] file, then add that call to the Exceptions file.

Check the format by entering the exception callsign into a contest that uses DXCC prefixes. The <Space> after the callsign forces the search to be exactly what is entered in the callsign field. The search function adds a space to the callsign before searching for a match. Without the <Space> delimiter, the search function would find KH6QA in the exceptions callsign KH6QAI - for example.