Hi Kees,

Wednesday January 01 2014 19:27, you wrote to Janis Kracht:

 KE> Hello Janis!
 KE> 01 Jan 14 13:10, you wrote to me:

 JK>> After speaking voice with R19C yesterday, I was informed there is
 JK>> still a problem with the OS/2 version of MakeNl in processing
 JK>> segments. As I understand it right now with v.3.4.1, it  look
 JK>> doesn't look for the most current Julian date for a particular
 JK>> file name.  As I understand the problem, it doesn't process
 JK>> segments older than 6 weeks.

 KE>  Well it is good to hear that at least the program does not crash
 KE> anymore, the issue with finding files older than 6 has been discussed
 KE> in this area before. Then 6 weeks seemed a fair period.

there is a general problem here ....

it exist 2 working modes with makenl

a. the strict numbering schema
     upcoming fridays julian daynumber +  x-7 + x-14 + x-21 + x-28
               + x-35 + x-42

   if you have a segment.362 (one day ahead of last fridays daynumber)
   the segment will be ignored totaly (!)
   This routine still handles the "cleanup" procedure, so it automaticly
   takes care, that the working directory keeps clean
   disadvantage:
   but segment daynumber files out of sequence still remains in the working
   directory unkept and untouched, fully ignored   :-P
   also segments older than 6 weeks cannot be used
   advantage:
   if an segment has been found once while in the correct sequence range
   in the case no new update will be received by the coordinator, makenl
   updates the segment file automaticly to the newly daynumber. So if a
   downlink coordinator sends no new segment for 6 months, makenl
   has incremented the daynumber of the existing segment upto the current
   state after 6 months
   the segment parameter in the control file has to be
           segment
     -or-  segment.

b. The full free numbering
   the disadvantage is, that the cleanup no longer works
   so your working directory gets filled with lot of old segment files :-(
   don't know exactly which segment gets picked up in case multiple of
   one segment file is there
   the segment parameter in the control file has to be
           segment.*




 KE>  A good 2014 to you too.
 KE> Kees
 KE> (2:280/5003.4)

regards, uli   ;-)

---
 * Origin: AMBROSIA - Frankfurt/Main - Germany (2:240/1120)