/* JTick.Doc version 0.81 Jtick.rexx by James McOrmond Features: --------- passes through lines it doesn't understand accepts multiple DESC lines uses standard AmigaDOS filenote descriptions uses flow.library for outbound queue's scans flow.library to make sure files aren't already queue'd for the system uses file links for outbound files to save space (if possible) unlimited number of file echos (ram dependant) unlimited number of systems per area seperate passwords per system per area ability to send only the files (no .tic files) can set whether you accept files from a system, and dumps them in BAD if not converts *all* addresses to 4d - accepts 163/165, 1:163/165 or 163/165.0 (zone 1 def) .TIC files are set with "pri"-1 so files are always first. logfile used passthru areas makelinks on outbound files that try to use your "file area" copy of the file to save space. Deletes old versions using "Replaces" .tic keyword if present now creates simple "nice looking" log file which can be used for an autopost. this file is by default "inbound:jtick-nice.log" JtickPost.rexx now included with archive. Posts simple echomail announcement Now creates .readme file for files with long descriptions Now has LinkDir option to duplicate "copies" of the same file for a "NewFiles" dir on your system. The Link Dir must be on the same device, as the AREA path. files in these directories can be deleted at will (ie, after two weeks or so) with no harm to the copy in the actual file area. Jhatch preliminary version included. JtickCfg program which fixes up the config for faster reading by Jtick.rexx Now works with XferQ (wow, one line :-) Future: (No particular order) ------- Multiple .tic readings for the same run of the script (to save time!!!) CRC checking execute command on inbound file per area quick "script" file, 'filenote zippy.lha "Note"' to send as .tic alternative (or just send the .readme files?) Command Line Options: --------------------- -i Set Inbound dir. -s Set Dir for .TIC files. (outbound .tic storage) -w Set Temp Work dir. (outbound file storage) -c Set Config file. -l Set Log File. -t Tick File to process (full path) (required) Format for Area def: -------------------- AREA PATH [LINK ] NODE [:]/.[] [A][T][F] NODE ... AREA ... etc... Flags: ------ At least one of these are required A: Accept files from this site T: Send .TIC files to this site (with Files) F: Send Files Only (No Ticks) Suggested Priority Values: -------------------------- -50 = hold 0 = norm 30 = direct 50 = crash The default file priority is 1, .tic files are at 0. Operation: ---------- On my own system, I run this program automatically whenever a .tic file comes in through Welmat. This assumes that the .tic files come after their corresponding file. Sometimes this is good, sometimes this is not. To get over this limitation, the system supports a very easy method of scanning. This is what the command would look like on my system. jtickcfg mail:jtick.cfg t:jtick.cfg Spat "rx rexx:tick/jtick -c t:jtick.cfg -t " inbound:#?.tic rx jtickpost t:jtick.cfg delete t:jtick.cfg This uses the SPAT script that is by default in your S: directory, and runs JTick once per .tic file that exists in there. I receive echos from a site that is using an AllFix program to pass the files along, and its .tic files start with AF, so I don't require TK as the first two characters. To automate your JtickPost announcements, you can run it after each Spat, or you can run it once a day, whatever. If no Jtick.post file exists, it will simply exit, so you can run it when no files had been processed. JtickPost is run on *my* system, after every time I do a Spat (after every session), like so rx rexx:tick/jtickpost mail:jtick.cfg it requires the name of the config as the one and only command line option. It uses the same config as Jtick itself, but a few keywords were added to it. All config options in your Jtick.cfg file should be before the first AREA is defined. */