Undoing Fast400 (Re: Tiger Tools )

[thomas@xxxxxxxxxxx]

Jon:

On Wed, 07 November 2001, "Jon Paris" wrote:

> I would think that if IBM do decide to blow this "fix" away the easiest way
> to do it would be to have the Workststion Data Management check to see if
> the bit was set for any job attempting to use workstation IO and error the
> job if it was not set.  Nice and simple and no fixable without patching the
> OS.

Since I don't know how the bit gets set in the first place, I can only guess; 
but it seems this would need to be slightly modified. I can submit a batch job 
that at some point chooses to ACQuire a device, do some interactive stuff and 
later RELease the device. I've never had a need, but I can't see why any number 
of devices couldn't be ACQuired by a job even concurrently.

Questions just for thought: How much of that job's CPU usage would get charged 
under interactive CPW? Once the bit is set, is it ever cleared? I can see that 
an ACQuire might be what sets the bit, but is there only a single bit per 
job/task? If so, the determination of when to clear the bit would be complex if 
it ever gets cleared at all.

Tom Liotta


--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/