WD> master h:\dailylst\files ; where master files reside (default - WD> current) WD> outpath h:\DAILYLST\output ; where the new output files go WD> mailfiles h:\makenl\mailer ; where mail server places received files WD> messages c:\db\netmail
WD> data WD> ********************************************************************** WD> ... and here's this morning's log-file for the DAILYLST: WD> **********************************************************************
I can reproduce building nodelists, but I cannot reproduce to compile older segment files than 3 weeks back
moving the PUBLISH day by +1 moves the whole daynumbering schema by 1 moving Publish day +2, numbering schema +2 and so on Last Friday it was day# 249 ... a shift to PUBLISH day to MONDAY results in output file 252 and requires segment files with a multiple of 7 starting offset 252 -> ext='252' or ext='245' or ext='238'
in a test round I've renamed all region segment files to a series of 7 decrementing daynumber by 7 for each file with some skipped areas tests 021, 028, 035, 042, .. 077 / 105 / 147 / 189 .. 245 to create an output file .252 only 238, 245 and 252 segments have been imported.
test series II numbering segments from 233 upto 252 segments with daynumber 238, 245, 252 have been implemented, all others "not found"
so I'm still wondering, how you've got the R21 (#238), R23 (#207), R31 (#228), R33 (#294), R38 (#077), R40 (#077), R42 (#004), R45 (#165), R48 (#172), R49 (#077) and all the #249 segments included
I've still used MakeNL 3.3.0 compiled with Watcom C on Nov 18 2012 22:50:26 to make the test results as comparable as possible but a) cannot get any segments that are out of scope of the 3 weeks limit