There is a cobol transaction in CICS that was in a loop 
where it kept writing out data.  Screensurfer kept running 
without timing out the transaction.  Everytime we call it, 
we have tested it up to 20-25 min where it keeps on 
running.  I was under the impression that our settings 
forced a screensurfer timeout, if a transaction took to 
long to process.  

I can send you a trace file.  

I don't have a diagnostic file.  I can try to recreate it 
by tomorrow but it may be difficult because the we will 
have the cobol program fixed.  

There might be something that is tricking the timeout, if 
the CICS app is writing to the screen constantly...if all 
you have is a trace file, that should help in figuring-out 
the repro here.

Trace file, plus the template that is responsible for the 
screen transition should let us figure this one out...sent 
to surfer@ie.com with Ticket #572 in the subject.

Also, we recently added the ability for the 
SSurfer.AspRequest object to timeout for situations like 
this--this is documented in Ticket #568.

Awaiting Screensurfer.

We worked on a lot of issues during the time of this 
ticket--are you still waiting for a resolution to the 
timeout issue with the ASPSurfer object, or is this working 
OK now?