Hi Janis,

Wednesday January 01 2014 13:10, you wrote to Kees Van Eeten:

 JK> Hello Kees!
 >>> What has happened is known, it crashes the OS/2 systems of 'top'
 >>> *Cs...

 >> You seem not to be up to date with the news. What you are talking
 >> about, was the state in the first half of last year. In the mean
 >> time the bug has been traced back to to the compiler. The compiler
 >> bug has been worked around and a proper working version has been
 >> avalable for at least two months.

 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 doesn't
 JK> look for the most current Julian date for a particular file name.  As
 JK> I understand the problem, it doesn't process segments older than 6
 JK> weeks.

yes, this is a known issue, where i've invented ...

the search for segments routine is a bit odd ...
it still searches the todays daynumber + the 6 daynumbers of the last 6 weeks
back
if there is a daynumber (361 last valid), next back in sequence is 361-7 = 354,
say the file has the daynumber 355, makenl will not find it ...

there is one exception:
if the segment file in the control file is defined as   file.*
default definition for numbered segment files is  file. or  file
then the strict daynumbers calculation is used

the search for segment files probably requires a complete rewrite,
die allow whatever segments in the working directory, with a more analysing
routine ... search for files by mask   eg  segment.*
analyse by date, daynumber, admin line info, sort the result and pick the
latest segment




A workaround in starting with the makenl 3.4.1 is, to bring all segment files
in sync with current daynumbers schema.
so this is a one-time job, search the latest segment of each segment, rename
it once to .361 and it will be handled subsequently by makenl in each new
process week by week  =;)


eg this weeks working dir:
    segment1.361
    segment2.004
    segment3.361
    resultseg.361

after processing makenl updates the two .361 files to  segment.004 and
segment3.004 so your working dir looks like
    segment1.004
    segment2.004
    segment3.004
    resultseg.004

makenl holds a copy from the previous week and with cleanup in the control
file defined, removes the "older" segments .354 and before




If you want to use daily nodelist creation, you have to switch to segment.*
definition, with whatever daynumbering ...
but then the cleanup no longer works
and you have to clean the working directory manualy   :-P


related bugs (closed)
https://sourceforge.net/p/makenl/bugs/9/
and discussion about "search for old segments" starts here:
https://sourceforge.net/p/makenl/bugs/9/?page=1
as the ticket has been closed, the request has been lost in development :-P

reopened as new bug/feature request
https://sourceforge.net/p/makenl/bugs/21/



 JK> Have a good 2014, Kees :)
 JK> Take care,
 JK> Janis
 JK>  $ Origin: Prism bbs (1:261/38)

regards, uli   ;-)

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