...previous
BUILT-IN VARIABLES
It is allowed to use special keywords in schedule commands, named
also built-in variables. Such keywords replaced before execution
as well as environment variables. It is possible to use it in any place of
executive path of a command or instruction. All keywords begins from
two simbols *?. Following part of identifier
defines values replaces this variable. Identifiers is case-sensetive!
There are following variables:
- *?TODAY_ - replaced with current date in format "DD.MM.YY". For
example, if command executed on July 7, 1999, then
executed command line will contain such text: 07.07.99
in place of *?TODAY;
- *?DAY-XX - replaced with date XX days ago in format
"DD.MM.YY" . For example, text *?DAY-10 before execution
on July, 7, 1999 will be replaced with 27.06.99.
Two digits are required. If days offset less than 10, you must place
zero as a first digit;
- *?DATE__ - replaced with current date in format "YYYYMMDD".
For example, July 5, 1999 will be replaced with 19990705;
- *?TIME__ - replaced with current time in format "HH:MM:SS".
For example, command, contains this variable and executed on 19:45:14 o'clock
will contains text 19:45:14;
- *?DAT-XX - replaced as well as *?DAY-XX,
but format as *?DATE__
("YYYYMMDD");
- *?USER - replaced with current user name (logon name);
- *?HOST - replaced with host name (computer name).
Examples:
- Command
  xcopy32 c:\source\*.* d:\dest /d:*?DAY-07
on March, 10 will be following
  xcopy32 c:\source\*.* d:\dest /d:03.03.99
and copy files, changed only after March, 3
- Command
  pkzip -a -p e:\dest\*?DATE__ c:\source\*.*
on March, 5 will be following:
  pkzip -a -p e:\dest\19990305 c:\source\*.*
and create archive with filename 19990305.zip
You can offer additional variables.
...next