|
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] - >It is a wonder that no-one has come out with such a product before. Well (and this is a serious question - I'm not trying to be flip), why not you, Leif? Maybe you knew about this "technique", but didn't think there was a market for it? Or maybe it just didn't click for you like it did for the developer of FAST400? Or maybe, and I realize this is wild speculation, but that you would be required by any "trade secret" agreement to deny it (so don't bother <g>), but just maybe *you* are the developer! Yeah, that's it! <bg> Then again, you probably wouldn't be writing a chapter in your ebook about the 5250 flag in job threads if it was you, eh? Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 D.Bale@Handleman.com > -----Original Message----- > From: Leif Svalgaard [SMTP:leif@leif.org] > Sent: Thursday, October 18, 2001 2:38 PM > To: mi400@midrange.com > Subject: Re: [MI400] iSeries NEWS knowledge of FAST400 method > > From: Steve Richter <srichter@AutoCoder.com> > > CFINT has been factor on our system for some time. Have the > technical > > writers at iSeries NEWS speculated in the past on how to negate > CFINT, do > > they have theories on how FAST400 works? > > Steve, when someone asked what "reengineering" FAST400 would reveal > my answer was: (I elaborate a bit here): > > Every job runs one or more threads. In each thread there is a bit > set by the 5250 "drivers" every time the thread does 5250 I/O. > Simply scan all threads and reset the bit if set and CFINT doesn't > know about this job using 5250. No voodoo, no tricks, real simple. > It is a wonder that no-one has come out with such a product before. > Maybe FUD was a factor here? Certainly many posts to this list reek > of FUD :-) >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.