Re: Z6 to YU

Alec SP2EWQ <aleksander.otulak@...>
 

Dave,

be serious, man - Z6 was NEVER Serbia.
Z6 has been either 'NOT VALID FOR DXCC' or 'KOSOVO'.

Read that
http://www.arrl.org/news/assigning-kosovo-z6-call-signs-unauthorized-and-illegal-itu-secretary-general-says
Quote
' “ITU has not allocated call sign series Z6 to any of its member states,” Houlin Zhou said. “Consequently, the utilization of call signs series Z6 by any entity without a formal allocation and consent of the ITU represents an unauthorized and illegal usage of this international numbering resource.”
Unquote

Repair that recomputing facility,
please...

Best regards,
Alec

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, December 6, 2019 12:34 AM
To: DXLab@groups.io
Subject: Re: [DXLab] Z6 to YU

The Recompute function's after action report is clear, Alec:

--------------------
Z66DH 2018-12-17 0841 40M CW 296 Serbia

Action: changed DXCC prefix from Z6 to YU
--------------------

DXCC Country Code is 296

DXCC Prefix was Z6

It looks like the root cause lies in the FIX-EU script, which was evidently not updated after Kosovo became a DXCC entity. Here's the relevant excerpt:

filter (QSO_Begin between #01-Sept-2012# and #31-Dec-3000#) and call like 'Z6*'
modify DXCCid 296
modify QSL_RCVD='I'
modify APP_DXKeeper_REGION='YU8'
modify QTH='Kosovo - NOT VALID FOR DXCC'

Note that this set of commands does not modify the QSO's "DXCC Prefix", so it's reasonable to expect it was Z6 -- as the Recompute report shows.

To confirm this diagnosis, check the QTH item in your Z66DH QSOs; is it set to

'Kosovo - NOT VALID FOR DXCC'

?

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Alec SP2EWQ
Sent: Thursday, December 05, 2019 6:03 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Z6 to YU


Dave,

Negative to the presented logic.
I have first run the scripts checking/correcting possible DXCC inconsistencies.
Which of those four scripts corrected that to Z6 I cannot say.

Later on, recomputing changed it to Serbia. Of course the latter was wrong.
Those stations operated from Kosovo.

Best regards,
Alec




-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Thursday, December 5, 2019 11:01 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Z6 to YU

+ AA6YQ comments below

after recomputing, I got such an action summary as below.
Is that action correct, please?

+ The QSOs listed below were logged with a DXCC Country Code of 296 (Serbia), but with a DXCC Prefix of Z6 (Kosovo). Those are inconsistent.

+ DXKeeper's Recompute function resolved these inconsistencies by changing the DXCC Prefix to match the Country Code. Why? Because DXCC Prefixes can change, but DXCC Country Codes are immutable.

+ IF Z66DH was operating from Kosovo rather than Serbia, then you should change each Z66DH QSO's DXCC Prefix to Z6, which will automatically change each Z66DH QSO's DXCC Country Code to 522. You can make this change "en masse" by filtering the Log Page Display to contain only your Z66DH QSOs, and then using the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window:

<https://www.dxlabsuite.com/dxlabwiki/QSOModifying>

+ Be sure to backup your log first, as recommended in the above instructions.

73,

Dave, AA6YQ




SP2EWQ Recompute Actions Report 05-gru-2019
Call Date Band Mode DXCC ID DXCC
Entity Error, or Action
Z66DH 2018-12-17 0841 40M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-17 1048 30M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-17 0946 20M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-18 0850 20M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-18 0728 40M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-17 2130 80M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-18 1740 80M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-16 2238 160M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-11 1402 40M FT8 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-19 1320 15M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-19 1232 15M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-19 2128 160M SSB 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66DH 2018-12-19 2042 20M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66X 2019-01-25 1536 80M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66X 2019-01-25 1533 160M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66X 2019-01-25 2317 160M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z66X 2019-01-25 0807 30M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z68M 2019-02-01 2042 80M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z68M 2019-01-27 1906 160M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z68M 2019-01-28 2246 160M FT8 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Z68M 2019-01-28 0934 30M CW 296 Serbia
Action: changed DXCC prefix from Z6 to YU
Best regards,
Alec





<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>












--
This email has been checked for viruses by AVG.
https://www.avg.com

Join DXLab@groups.io to automatically receive all group messages.