Subj : System check ???
To   : Jasen Betts
From : Gerald Miller
Date : Tue Oct 29 2002 04:15 am

Hello Jasen,

    On Monday October 28 2002 at 20:02,
    Jasen Betts [3:640/531.42] wrote to Gerald Miller,
    about:  System check ???

 GM>>>> I'm not familiar with the ISO format....

 JB>>>  echo
 JB>>> %@replace[2,d,%@replace[20,yy,%@replace[1,m,%@makedate[14936,4]]
 JB>>> ]]
 JB>>>                                                             /\
 JB>>> :)                                                          ||

 GM>> In your previous message, you had omitted the ",4" at the end,
 GM>> but it still worked on my system. (???) Help me out and tell me
 GM>> how you achieved the numbers "14936,4" and what is their
 GM>> significance

 JB>  14963 is 22nd of November 2020

Which is the day that I turn 75yo, if I should live that long.  ;-)

 JB> That way I can replace "20" with "YY", "1" with "M" and "2" with "D"

 JB> the ",4" makes it use ISO format here (needs version 7 of 4dos)

 JB> Here it says comes out of makedate as 2020-11-22 which gets translated
 JB> to YYYY-MM-DD

I tried: "echo  %@makedate[14936,4]" and "echo  %@makedate[14936]" and both 
times I got "11-22-20".  It's a little confusing - I don't know if it's 
dropping the millennium 20 or the year 20?  I guess it may not matter much as 
it still yields up my system date format: MM-DD-YY....  ???

 JB> [squiched by me]

 GM>> PATH\PROGRAM TO RUN           ³AFTER³        ³        ³DAYS ³
 GM>>                               ³ DAYS³LAST RUN³NEXT RUN³ LEFT³ASK

 JB> Why all the new fields? - aren't program, After-days, last-run and ask
 JB> enough ? is it so you can add some new scheduling rules?

I hadn't thought about the possibility of adding "some new scheduling rules", 
but I like that concept.  Idea snagged for future expansion...

I'm interested in sending the output of the %prog that DO NOT run %today to a 
log file, so I can see which programs did not run today, when they are 
scheduled to run and how many days remain until they are scheduled to run.

I'm running my mailer program _almost_ 24/7.  The mailer has an event at one 
minute past midnight, where it cold boots the computer and when 4dos comes back 
to life, it can run things like XBOOT and other DOS "maintenance" programs.  I 
can send the output of the XBOOT log to my netmail message area.

Regarding the line:

  ÄÄÄÄ 8402 ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÅMM-DD-YYÅMM-DD-YYÅÄÄÄÄÄÅÄÄÄ

I was hoping that %@date[01.02.03] would provide a unique digit for origin of 
the data file.  Since you told me that command issues 8432 on your system, and 
the same command on a German system also issues 8432, I've decided that the 
digit is not unique enough; but the %_country code WILL provide a unique 
digit....  So, the above line is now:

  ÄÄÄÄ 001 ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÅMM-DD-YYÅMM-DD-YYÅÄÄÄÄÄÅÄÄÄ

Up pops a NEW problem!  Some country codes are a single digit, some country 
codes are double digits and the remaining country codes are triple digits. I 
searched the 4dos help (mine), looking for a %@pad command so I can pad single 
digit country code with "00" and pad double digit country code with "0", but, 
of course, you know there is no %@pad command in 4dos version 6.02.  
Suggestions?

The idea of using the country code in the line is so that the BTM can make a 
comparison of that line and the current system country code.  If the compared 
digits are identical, then the BTM carries on.  If the compared digits are 
different, then the BTM would convert the data file to the current system 
country code AND the correct date format.

           Cheers ... Gerald

--- GoldED+/386 v1.1.5-21026
 * Origin: Assembler lesson #1: POP AX is NOT an electric guitar. (1:342/512)

.