Re: Peregrine EDI software and trouble shooting a line.

[Pete Hall <pbhall@xxxxxxxxxxxxx>]

At 12:28 11/19/2002, Rob Berendt wrote:
> Normally the Peregrine software, (or whatever their nom du jour is), works
> fine.  But lately we've been having an issue with recurring errors during
> communications.  Sometimes it works; sometimes it doesn't.
> A sample is:
> CPA5902:  Controller CN2196BSC not contacted. Call out request failed. (C
> R)
Busy signal on the other end? I used to write monitor CL programs to watch
the comm jobs and reset them if the line status became unacceptable. I
remember it being pretty easy to do, but it's been way to long to tell you
what they did, other than retrieving the status of the comm objects and
vrycfg. The basic idea is that the comm program submits the monitor,
passing its job number/user/name, and the monitor then has the capability
to end that job and submit another. When comm job is done, both jobs end
based on a marker object, data queue, message queue, whatever.


Pete Hall
pbhall@ameritech.net
http://www.pbhall.us/