Mike Tripp @ 1:382/61.1 wrote on 01-27-98 09:22 about *Squish*
 LL>> This is what I kinda find confusing, Mike; that is, should the
 LL>> author have to support squish's flags?
 MT> Because he's trying to support Squishbases and emulating Squish's
 MT> functions?
Oh sure, I understand what you're saying but there are some squish parameters 
that would not need to be supported in this situation (.sql and .sqo).
 LL>> What I am trying to say, is that really, all SOS is doing is
 LL>> converting from one message format to another.......it shouldn't
 LL>> have to be responsible for the flags as this is squishs (and
 LL>> it's support programs) job.
 MT> But SOS is creating and tossing to the Squishbases, not Squish,
 MT> so it becomes SOS's job to create and toss in a matter consistent
 MT> with how Squish does it...and it evidently doesn't.  How can Squish be 
responsible if you
 MT> aren't using it (for those areas)?
The way I'm thinking about this is that the actual message data and the high 
water marks are stored in two different records; IMHO, there doesn't seem a 
reason why an external program should be fooling around with the high message 
mark.  In fact, again IMHO, it would seem SOS's author made a wise choice by 
not including any routine that would affect the high message mark and 
therefore leaves such manipulation entirely up to squish.........but sqpack 
doesn't seem to refer to squish.cfg if there is no high water records.  Maybe 
though, there is some argument I'm missing in squish.cfg that would enable a 
function in sqpack to do this???  Think maybe I'll join the squish echo to 
get some feedback on this..........:-)
Thanks for the reply Mike and will ttyl.........:-)
--- Sqed/32 1.14/r15155
---------------