Re[2]: Time out on DDM data area

[eric.delong@xxxxxxxxxxxxxxxxx]

     The original poster stated that the program was in ICFW status. Try 
     changing QSYS/QCNDDMF WAITRCD(seconds) to set the timeout limit.
     
     Eric 


______________________________ Reply Separator _________________________________
Subject: RE: Time out on DDM data area 
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    9/30/98 11:52 AM


Hey folks.  I have a question.  The original question was about DDM was it not? 
Have we been able to answer this persons question?  I am seeing a lot of stuff 
on ICF files but how would that apply to a DDM file?
     
     
     
     
mcalabro@commsoft.net on 09/30/98 11:50:52 AM 
Please respond to MIDRANGE-L@midrange.com@Internet 
To:        MIDRANGE-L@midrange.com@Internet
cc:         
Subject:        RE: Time out on DDM data area
     
On Wednesday, September 30, 1998 10:48 AM, Tim McCarthy 
[SMTP:twmac@mindspring.com] wrote:
> At 08:12 AM 9/30/98 -0400, you wrote: 
> Hi Buck,
> No, you shouldn't have to do this - the only problem I'm aware of with 
> timeout values not being effective are with bisync and SNA switched
> connections where the first I/O (or ACQ for SNA) cannot be timed out 
> using
> "normal" methods. Make sure you always issue an invite before every read 
> and that the read (in RPG) is from the file name not the record format
> name, otherwise the timer is not in effect. If this is not your problem 
> let
> me know and I can suggest something else.
     
Yup.  Always doing the INVITE then the READ from invited.  More often than 
not, the failure is on the ACQ, but this is not a given, as I also get 
failures on the READ and very rarely on a WRITE (with data, not an 
INVITE.)  WAITFILE is 60 and WAITRCD is 15.  Some applications use TIMER 
to override WAITRCD.  All these things work just great for days on end   
then boom; ICFW and no CPU usage.  While the job is "running" the 
line/ctl/dev show ACTIVE with the job attached.  End the job, vary off and 
the line shows FAILED.  Vary on, restart the job with the exact same 
transaction and it goes just fine.
     
Very puzzling.  The one thing I've never had a good explanation for.
     
Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net
     
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. 
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner/operator: david@midrange.com 
+---
     
     
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. 
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner/operator: david@midrange.com 
+---
     


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---