Re: Async comm not timing out

["Synapse Communications, Inc." <office@xxxxxxxxxxx>]

Buck,

In some async programs I wrote about 6-7 years ago I used the TIMER 
option before the INVITE, then checked for a '0310' in Major/Minor 
code, also at that time in RPG only it would not update the MAJ/MIN 
code correctly and the circumvention was to check the *STATUS  for 
'01331'.  They were suppose to fix this, but you never know, it took 
six month's for them to find the problem and admit it.  Maybe other 
errors have cropped in since then!

Good luck

-- Jim Lowary


> This week's question is for the communications programmers.
> I have an async program that does an invite, then a read.
> The WAITRCD is set to 15 seconds, and works most of the 
> time.  The situation where it doesn't work is when I 
> have lots of parity errors on the line.  What happens is...
> nothing.  The line, controller and device all show ACTIVE
> but the READ doesn't time out.  If I cancel the job, the
> controller and device go to FAILED.  If I vary the line, 
> ect. off and on and re-start the job, everything works fine 
> until the parity errors pile up again.
  


  |
  |
  ||  /|
  | |/ |
  |    |
  |    |
  | /| |
  |/ | |          SYNAPSE Communications, Inc.
 ____|_|  _          http://www.synapse.com
(_______)| \
(_______)|  )----------------------------------------
(_______)|  )----------------------------------------
 (______)|_/    
     | |        Tech-Support: (800) 457-5250  
     | |                 BBS: (573) 886-0738 
     | |               
      ||                  office@synapse.com 
      ||                    
      ||
       |
       |
       

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---