Thursday, 11 October 2007

Dynamic XFL - (1)

Merhaba!

Yüce Allah'tan dileğim,
Mübarek Ramazan'ın bereketi ve
milletimizin Şeker Bayramı cömerdliği
daim olsun...

Bir de ATC bulmacası:
Kontrol ettiğiniz uçaklardan birisi
Mısır'dan çok eski bir mumyayı taşıyor olsun...
Mumya 2-3 bin yıl önce gömülürken tabutun içine
onu korusun diye sevdikleri tarafından
The Book of The Dead,
Ölünün Dua Kitabı konmuş olsun.

Üç soru:
1. Ne yaparsınız?
2. Ne düşünürsünüz?
3. Ne duyarsınız?

Benim cevaplarım:
1.İşimi yaparım.
2. Uçak düşerse mumya da tuzla buz olur.
3. Ona acırım. (Bu eşsiz mabedin sade bir hizmetkarı olarak)

Aşağıda 1990 yılında sanıyorum Avrupa'da ilk defa olarak
Herr Ehrenberger ve diğer arkadaşların katkıları ile yaptığım
OD9044'ün özetlenmiş dökümanlarını koyuyorum...
Daha öte bilgi istenirse ücret karşılığı olmadan
arsaral(at)yahoo.com dan alabilirsiniz.
(kimlik, görev yeri vb bilgilerinizi göndermeyi unutmayınız)

Amin.

Ali R+ SARAL

OD9044001 920623 SAL OD 90/44
OD9044002 920623 SAL OD 90/44 Sample routes
Final test cases
TEST CASES for TID alone
OD9044003 920706 SAL OD 90/44 List of things to be done... EERRFL is set by:..........................
EERCFL is set by:..........................
EERKFL is set by:..........................
EERSFL is set by:..........................
OD9044004 920707 SAL RFL, CFL and XFL in the OPERATING SYSTEM MANUAL OD9044005 920707 SAL 4444 flight level related parts
OD9044006 920709 SAL CFL related variables
OD9044008 920709 SAL XFL filed of KDS indicates there is a special
OD9044009 920709 SAL KNACACT should have only XFLTAB change.
OD9044010 920710 SAL KNACACT test on real time TEST system.
OD9044011 920727 SAL KNACACT use of RFL ios tested with SPR and KDS
OD9044012 920728 SAL Where is the CFL value of the ACT message set
OD9044013 920731 SAL Where is the ESTXFL value used.
OD9044014 920731 SAL Where is the EESKFL value used. OD9044015 920804 SAL XFL processing (strip printing) KNEBALV TODO007 920804 SAL XFL rules
TODO008 920929 SAL XFL business
OD9044016 920804 SAL XFL processing KNAE(EST and APL processor
OD9044018 920804 SAL syntax checking for EST fields
OD9044019 920804 SAL KNAFEST works before the output of every screen
OD9044020 920810 SAL How to add a new error message ?
OD9044021 920814 SAL How to change SDB.
OD9044022 920814 SAL Use of TID on MCRTES.
OD9044023 920814 SAL TID related ouput on MCRTES.
TODO009 920930 SAL XFL business
OD9044025 920930 SAL link rules for OD 90/44
OD9044026 921012 SAL entry for Oct progress report
OD9044027 930127 SAL Report on realization of OD/90/44 -------
1. The content of the OD.
2. Content and possible effects of the changes.
2.1. Which programs are changed ?
EERP
This table has the definitions of flags that show
the various qualities of extracted route points.
XFLT
This table contains the definitions of fields
on the XFLTAB table.
XFLTAB
This table indicates the XFL points and their qualities.
PEAQXEW
Static databank's error/warning message table.
KNACACT
Extraction of erm- and act- message for adjacent centers
KNAE
Estimate Message processor of KDS.
KNFC
MODETA, ALLOC and reclearence processor for TID.
2.2. Operationally effected facilities ?
2.2.1. KDS Keyboard Display System
---------------------------
1. Confirmation of a flight without a KFL reclear
2. Confirmation of a flight with reclear
3. Change of data on the screen after a warning
message
2.2.2. TID Touch Input Device
----------------------
1. Single KFL reclearence before the XFL point
2. Multiple reclearence before the XFL point
3. Upper two cases mixed with a KFL on the XFL point
4. Upper 3 cases mixed with a UIRCFL reclearence
2.3. The scope of the changes and how the effects are limited ?
2.3.1. The existance of an XFL value.
This is achieved through a combination of
EERSFL, EERKFL, EERKPT and EERKFP values.
An EERKFL point can not occur without EERKPT and
EERKFP by definition. So this requires the use and
the careful handling of these values.
2.3.2. The existance of a previously set dynamic XFL flag
namely EERXPT. EERXPT is newly created and added to
the static data bank (SDB) EER structure.
EERXPT is set if there are special XFL rules that
depend on the CFL. In this case the XFL
is not a static value but a dynamically changing
value.
2.3.3. The aerodrom of destination should
be equal to the XFL table's aerodrom of destination
value for the related adjacent center.
2.4. Which operational functions are effected ?
2.4.1. Anything related to KFL changes
might have been effected by the OD90/44.
2.4.2.Anything related to previous XFL points
might have been effected by the OD90/44.
2.4.3. Anything related to previous routes which pass
through an XFL point but not end in an aerodrom
which requires a dynamic XFL application from
KARLDAP.
3. The TEST procedure.
3.1. Unit tests.
3.1.1. KDS should be tested with the cases listed below.
I. from LOWW to EDVV via UB5 UG5
CFL KFL XFL KFP XFP
*** *** *** *** ***
260 - - - - (CFL <> XFL) AND no KFL change
260 270 - SULUS - (CFL <> XFL) before XFL point
310 260 - SULUS - (CFL > XFL) AND (KFL <> XFL) AND (KFL > XFL) before XFL point
260 270 - FUL - (CFL <> XFL) on the XFL point
310 340 280 FUL FUL REJECTED- KFL can not be higher than XFL
(CFL > XFL) AND (KFL > XFL) on the XFL point
310 260 - FUL - REJECTED KFL can not be lower than XFL
(CFL > XFL) AND (KFL <> XFL) AND no KFL change
ERL
SULUS
FUL 280
280 LAU
260 RDG (CFL <> XFL) before XFL point
ERL 310
SULUS
310 FUL 280
280 LAU
310 RDG (CFL > XFL) AND (KFL <> XFL) AND (KFL > XFL) before XFL point
ERL 340
SULUS
340 FUL 280
280 LAU
I.II.II. cases with single KFL reclearences on XFL point
260 RDG (CFL <> XFL) on the XFL point
ERL
SULUS
FUL 310 REJECTED
310 LAU
310 RDG (CFL > XFL) AND (KFL <> XFL) AND (KFL > XFL) on the XFL point
ERL
SULUS REJECTED
FUL 310
310 LAU
I.II.III. single KFL reclearence and witha KFL equal to XFL on XFL point
260 RDG (CFL <> XFL) before XFL point
ERL 310 AND (KFL <> XFL) on the XFL point
SULUS
270 FUL 310 REJECTED
310 LAU
260 RDG (CFL <> XFL) on the XFL point
SULUS
270 FUL 310 REJECTED
310 LAU
310 RDG (CFL > XFL) AND (KFL <> XFL) AND (KFL > XFL) before XFL point
ERL 340 AND (KFL <> XFL) AND (KFL <> XFL) on the XFL point
SULUS
260 FUL 340 REJECTED
340 LAU
310 RDG (CFL > XFL) AND (KFL > XFL) before XFL point
ERL 340 AND (KFL > XFL) on the XFL point
SULUS
340 FUL 310 REJECTED
310 LAU
I.II.V. Double KFL reclearences, one before and one on the XFL point
with the KFL value on the XFL point equal to the XFL value.
I.II.VI. Double KFL reclearences, two before and one on the XFL point.
I.II.VII. All five types of cases listed upto now should be tested
with a UIRCFL reclearence after they are done.
I.II.VIII. L modifications should set or erase the XFL and XP fields
of the KDS screen.
I.II.IX. TID reclearences should set or erase the XFL and XP fields
of the KDS screen.
3.2. System tests
3.2.1. Control cases
I. Control cases for KDS
I.I. from EKCH to LFSB via UA9
CFL KFL XFL KFP XFP
*** *** *** *** ***
270 - 250 - - A static XFL point without XPT quality.
270 290 250 FFM HERBI
I.II. from LOWW to EDLP via UB5 UG5(Paderborn)
CFL KFL XFL KFP XFP
*** *** *** *** ***
310 - - - - A flight which passes over a dynamic XFL
point but is not destined to end in the
XFL related aerodrome of arrival.
I.III. from LOWW to KJFK via UG1
CFL KFL XFL KFP XFP
*** *** *** *** ***
310 - - - - A flight which has no relation to OD90/44.
3.2.2.Control cases for TID
The control cases listed above for KDS should be tested with all
possibilities listed above in the TID unit tests.
3.2.3. Connection of KDS to TID
The cases listed in unit tests of KDS and TID should be tested
sequentially. For each case in the KDS unit test, TID-FDM
outputs should be checked and then TID reclearences of the
TID unit test should be checked.
3.2.4.Strips
The strips produced in all the tests upto now should be gathered
and checked.
3.2.5.ERM messages
ERM messages on the TID screen sholud be checked with different
time values in each case listed above.
4. The entities used or created.
CFL CLEARED FLIGHT LEVEL
KFL KARLSRUHE ALLOCATED/COORDINATED FLIGHT LEVEL
KPT KFL CHANGE POINT FLAG
KFP KFL CHANGE POINT
XFL EXIT FLIGHT LEVEL
XPT DYNAMIC XFL POINT INDICATOR
4.1. The operational face of the entity.
An XFL point has all the qualities of a KFL point.
But it is forced automatically. Contrarily, KFL point
and its value has to be entered during a KDS or
TID reclearence.
A static XFL point has a preset flight level. A
dynamic XFL point, namely an XFL point with a
XPT quality, has a preset threshold level.
A XPT point enforces its value automatically,
depending on a threshold. If the proposed
physical flight level is higher then this threshold,
the cleared flight level will be set to the XFL
value automatically. If it is lower, then the
level that has been proposed will be accepted.
A KFL change on a static XFL point is disabled by the
system. Contrarily, it is enabled on a dynamic XFL,
namely XPT point with some limitations.
In the static XFL case, multiple KFL changes can be
made before the XFL point. Whatever the previous
flight level is, the TID program enforces the standard
XFL level. The static XFL case is valid if the adjacent
center requires to have the delivery of a plane at a
fixed flight level.
In the dynamic case, multiple KFL changes before the XFL
point are also enabled. But the existance of an XFL
depends on the proposed flight level, on the XFL point.
If the CFL or the last KFL before the XFL point is lower
than the dynamic XFL threshold, then the XFL is canceled.
In this case, the automatical generation of a XFL is
disabled. The operator sees no KFL change on the XFL
point, which is created automatically by the TID program.
Also, the strips are printed without an XFL indication.
In the dynamic XFL case, KFL changes on the XFL point are
limited. There are two cases
4.1.1. The CFL or the last KFL change is lower than XFL
.1. If the proposed KFL change on the XFL point is
lower than XFL, then it is accepted.
.2. If the proposed KFL change on the XFL point is
higher than XFL, then it is rejected.
4.1.2. The CFL or the last KFL change is higher than XFL
Refuse all possible KFL changes and enforce the
XFL level.
4.1.3. 4.1.1. and 4.1.2. can be outlined in terms of
CFL-KFL conditions as input and final cleared
flight level of the aircraft :
*. If KFL point is before XFL point
CFL > XFL
KFL > XFL KFL + 280
KFL <> XFL KFL + 280
KFL <> XFL
KFL > XFL 280
KFL <> XFL keep old values + err message
KFL < eerkpt =" logical"> 0
A static XFL point (SXFL) is a point where
EERKPT = logical 1
EERKFL > 0
EERSFL > 0 & EERSFL = XFLXFL value of the XFLTAB
A dynamic XFL (DXFL) point is a point where
EERKPT can be anything
EERKFL can be anything
EERSFL can be anything
EERXPT = logical 1
EERXPT flag is added to the DATA definitions of
the existing DYNF3 flag of the EERP table.
XFLXPT field is added to the DATA definitions of
the XFLT table.
All the members of the XFLXPT field of the XFLTAB
table are set to 0, except for EDVV and EDVE
arrivals passing over FUL and LAU.
New additions can be made by changing XFLTAB
for different arrivals on adjacent centers.
5. The effect of the change on the system resources
and performance.
5.1. Resource usage.
#lines
#statements commented(/**/ed) and not commented(^/**/)
#comments
#statements
#/**/ #line ^/**/ed /**/ed
KNAE before OD : 410 1458 832 11
KNAE after OD : 520 1725 976 27
OD90/44 KNACXFL : 59 121 52 1
KNFC before OD : 345 2475 1377 4
KNFC after OD : 455 2754 1550 20
OD90/44 KNACXFL : 59 121 52 1
KNACACT bef OD : 373 976 486 11
KNACACT aft OD : 380 983 491 11
EERP bef OD : 240 386 118 0
EERP aft OD : 242 390 120 0
XFLT bef OD : 22 27 4 0
XFLT aft OD : 23 28 4 0
XFLTAB bef OD : 139 166 104 1
XFLTAB aft OD : 167 194 131 1
******************************************
DIFFERENCES
******************************************
#/**/ #line ^/**/ed /**/ed
KNAE after OD : 110 267 144 16
OD90/44 KNACXFL : 59 121 52 1
KNFC after OD : 100 279 173 16
OD90/44 KNACXFL : 59 121 52 1
KNACACT aft OD : 7 7 5 0
EERP aft OD : 2 4 2 0
XFLT aft OD : 1 1 0 0
XFLTAB aft OD : 28 32 27 0
+ #/**/ #line ^/**/ed /**/ed
-------------------------------------------
366 832 455 34
#labels
#characters in comments
#characters in statements
#math and logical operations (effective+commented)
#of+ #of- #of/ #of* #of= #test #set #clear #compare
KNAE before OD : 8+2 5+ 312 66 18 15 0
KNAE after OD : 9+2 6+ 348 80 24 18 0
OD90/44 KNACXFL : 1+ 21 2 2 2 0
KNFC before OD : 3+0 24+ 638 113 37 39 8
KNFC after OD : 3+0 25+ 694 124 42 41 8
OD90/44 KNACXFL : 1+ 21 2 2 2 0
KNACACT bef OD : 5+0 33+ 204 32 26 16 2
KNACACT aft OD : 5+0 34+ 205 32 27 16 2
EERP bef OD : 0+ 267
EERP aft OD : 0+ 270
XFLT bef OD : 0+ 2
XFLT aft OD : 0+ 2
XFLTAB bef OD : 1+ 101
XFLTAB aft OD : 1+ 128
******************************************
DIFFERENCES
******************************************
#of+ #of- #of/ #of* #of= #test #set #clear #compare
KNAE after OD : 36 14 6 3 0
OD90/44 KNACXFL : 21 2 2 2 0
KNFC after OD : 26 11 5 2 0
OD90/44 KNACXFL : 21 2 2 2 0
KNACACT aft OD : 1 0 1 0 0
EERP aft OD : 3
XFLT aft OD : 0
XFLTAB aft OD : 27
+ #of= #test #set #clear #compare
--------------------------------------------------------------------
135 29 16 9 0
#loops
#iterations per loop
#nests
#d1 #d2 #d3 #d4 #d5 #d6 #d7 #d8 #d9 #10 #11 #12 #13
*** *** *** *** *** *** *** *** *** *** *** *** ***
KNAE before OD :
KNAE after OD :
OD90/44 KNACXFL :
KNFC before OD :
KNFC after OD :
OD90/44 KNACXFL :
#DO, IF, CALL, FUNC, MCRTES, INCL, labels, procs
#DO #IF #CALL #FUNC #MCRTES #INCL #:s #proc #GOTO
*** *** ***** *()** ******* ***** *** ***** *****
KNAE before OD : 175 167 54 383 27 43 42 2 49
KNAE after OD : 203 188 81 468 37 45 56 14 49
OD90/44 KNACXFL : 11 5 2 36 1 0 12 2 0
KNFC before OD : 202 312 77 718 99 45 132 40 89
KNFC after OD : 233 330 97 785 107 49 145 52 89
OD90/44 KNACXFL : 11 5 2 36 1 0 12 2 0
KNACACT bef OD : 110 87 4 366 53 23 35 3 9
KNACACT aft OD : 110 88 4 372 54 23 36 3 9
EERP bef OD : 64 1
EERP aft OD : 65 1
XFLT bef OD : 12 2
XFLT aft OD : 13 2
XFLTAB bef OD : 1 102 1 3 6
XFLTAB aft OD : 1 129 1 3
******************************************
DIFFERENCES
******************************************
#DO #IF #CALL #FUNC #MCRTES #INCL #:s #proc #GOTO
*** *** ***** *()** ******* ***** *** ***** *****
KNAE after OD : 28 21 27 15 10 2 14 12 0
OD90/44 KNACXFL : 11 5 2 36 1 0 12 2 0
KNFC after OD : 31 18 20 67 8 4 13 8 0
OD90/44 KNACXFL : 11 5 2 36 1 0 12 2 0
KNACACT aft OD : 0 1 0 6 1 0 1 0 0
EERP aft OD : 1
XFLT aft OD : 1
XFLTAB aft OD : 27 6
+ #DO #IF #CALL #FUNC #MCRTES #INCL #:s #proc #GOTO
--------------------------------------------------------------------
71 50 160 189 21 6 52 26 6
#nests and depths
#procedures
#vars created
#global vars used
size of the link module
size of the load module
#goto #l var #g var objsz loadsz
***** ****** ***** ***** ******
KNAE before OD : 49
KNAE after OD : 49
OD90/44 KNACXFL : 0
KNFC before OD : 89
KNFC after OD : 89
OD90/44 KNACXFL : 0
KNACACT bef OD : 9
KNACACT aft OD : 9
EERP bef OD :
EERP aft OD :
XFLT bef OD :
XFLT aft OD :
XFLTAB bef OD : 6
6
#old version
#new version
#lib name where it resides
Version # : OLD NEW RESIDES
VER DATE VER DATE IN
**** ********** **** ********** *******
KNACACT : 2.77 01/10/1992 2.79 12/02/1993 L1MCR0
KNACXFL : - 1.14 16/02/1993 L1MCR0 ?????
KNAE : 3.14 03/02/1992 3.15 16/02/1993 L1MCR0
KNAFSPS : 1.13 22/09/1976 1.24 10/02/1993 L1MCR0
VKNFC : 3.81 28/09/1992 3.86 10/02/1993 L1MCR0
XFLT : 1.05 11/05/1992 1.07 30/07/1992 L1DIFAR0 (L1DSTR0)
XFLTAB : 1.16 12/05/1992 1.22 22/02/1993 L1COMR0
EERP : 1.32 13/12/1989 1.33 30/07/1992 L1DIFAR0 (L1DSTR0)
PEAQXEW : 2.34 24/07/1992 2.30 16/02/1993 L1PEAR0
5.2. Processing time.
Its effect on the performance of the system.
5.3. Maintainability.
Use of tables
The way additions are made.
#additions
#reusable routines
6. Technical content of the change
6.1. The parts of the changed programs
6.2. Line by line explanation of the change.
7. Problems and proposals to be taken into consideration
7.1. Local
The case of KFL on XFL point with KFL value equal to XFL
ERM message problems in case of KFL on XFL point
7.2. General
Style considerations
The need for testing tools
The need for quality control tools
The need for a static EERXFL field on EERP.
XFLTAB should be moved into the SDB.
pros performance, maintainability
cons investment
OD9044028 921012 SAL Contents of report on realization of OD/9044 -------
1. The content of the OD.
2. Content and possible effects of the changes.
2.1. Which programs are changed ?
2.2. Operationally effected facilities ?
2.3. How the effects are limited ?
2.4. Which operational functions are effected ?
3. The TEST procedures.
3.1. Unit tests.
3.2. System tests.
3.3. Cycle tests.
4. The entities used or created.
4.1. Operational face of the entity.
4.2. System face of the entity.
5. The effect of the change on the system resources
and performance.
5.1. Resource usage in terms of language
#lines
#statements
#comments
#labels
#characters in comments
#characters in statements
#math operations
#logical operations
#loops
#iterations per loop
#DO, IF, CALL, INCLUDE, MCRTES
#nests and depths
#procedures
#vars created
#global vars used
5.2. Memory usage.
size of the link module
size of the load module
5.3. Processing time.
5.4. Maintainability.
6. Technical content of the change
6.1. The parts of the changed programs
6.2. Line by line explanation of the change.
7. Problems to be taken into consideration
7.1. Local
7.2. General