On Sun, 25 Oct 2020 19:21:24 +0000, Jesse 1 Robinson wrote: >I had that problem in a shop long ago. In defense of the 'perpetrators', if a >user got caught by timeout chopper, getting back on could be long and >difficult. The real culprit was lousy tuning and inadequate resources. The >resource problem eventually got solved by an upgrade. No users were harmed in >the process. > At one time our admin installed a timeout chopper for CMS users. He was generous and naive enough to provide a "two minute warning". The first time I was away from my desk long enough to miss that warning I installed a background process to trap the warning.
-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
