Subj : Compression question
To   : Jerry Schwartz
From : Peter Knapper
Date : Wed Jul 23 2003 12:33 pm

Hi Jerry,

Incidentally, your message made me remember my rationale for the way I have 
done things for so long, I had forgotten the little details......;-)

 JS> Jul 21, 2003 at 20:00, Peter Knapper wrote to Bo Simonsen:

 PK> In addition, you can use the SEND and ROUTE commands to process 
 PK> traffic for a specific set of nodes, and then the output of those 
 PK> commands is NOT included in any other ROUTE 
 PK> statement processing that 
 PK> encompass those nodes within a global statement (EG 4:ALL). However 
 PK> note that this ALL must happen within ONE Squish operation to work 
 PK> this way.

 JS> I don't think that's really true. Even within a single 
 JS> run, SEND and ROUTE commands only operate on mail that 
 JS> is marked NORMAL at the time the command is executed.

I don't now how the above mis-conception stared, but Squish has always worked 
fine for me by ONLY processing mail in HOLD status. In fact I determined quite 
some time ago (I started using Squish V1.01 when it first came out), that HOLD 
was the ONLY status mail that could be safely processed by Squish, expecially 
when running multi-node. 

Here is an example of my default Schedule that is called every time mail is 
processed except during ZMH. Note that I use Macros for the node details and 
mail procesed by a preceeding SEND/ROUTE statement is ignored for following 
SEND/ROUTE statements unless explicitly stated in the parameter lists -
===========================================================
;       Normal packing procedure.
SCHED   Standard        All
        CHANGE  NORMAL HOLD     All
        SEND    HOLD    NOARC   NOCOMPS
        SEND    HOLD            MYBOARDS FAKENET 4DPOINTS
        SEND    HOLD            IPNODES
        ROUTE   HOLD            Z3CR
        ROUTE   HOLD            N772CR
        ROUTE   HOLD            BBBOARDS
        ROUTE   HOLD            Z1FEED
        ROUTE   HOLD            AKHUB2 WORLD
;
===========================================================
and that in essence is the way this system has processed mail since Squish 
V1.01 came alive. Mail here is only ever set to NORMAL status during ZMH, or I 
have a specific situation requiring me to manually set it. ALL my mail 
processing by Squish normally takes place using HOLD status. The very FIRST 
statement in a Schedule CHANGES all mail to HOLD, and the LAST statements in 
any of my Schedules CHANGE's a HOLD packet to whatever Flavour is needed. Also 
note that I use other utilities that will change the Flavour of a packet, 
usually as a result of other external events that Squish does not manage.


 JS> For example, assume that you have mail for 123/45 that 
 JS> is marked DIRECT, and mail for 123/67 that is marked 
 JS> NORMAL. The following commands

 JS>         ROUTE CRASH 123/0 ALL
 JS>         SEND CRASH 123/67

Yep, I am sure you are seeing exactly the reason I abandoned using a ROUTE or 
SEND output FLAVOUR of anything other than HOLD, many years ago, there were 
quite a few gotchas that could upset things, especially when running 
multi-node. The only way I manage Mail into any status other than HOLD, is via 
the CHANGE Command, I dont use ROUTE (or SEND) CRASH/NORMAL/DIRECT etc, I 
always use ROUTE (or SEND) HOLD ... and then CHANGE the Flavour.

I hope this helps..............pk.

--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

.