× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Communication question
  • From: "Jeffrey Silberberg" <jsilberberg@xxxxxxxxxxxxxx>
  • Date: Thu, 3 Jun 1999 19:24:34 -0400

Tim,

            Who said anything about terminal emulation ??  As to recovery
that's what a watchdog card is for,
 but the E-911 operators get upset when the system is not there for any
reason !!!  An customer service waiting
 for the update to take place in a paging terminal, or phone switch are even
less patient.

    JMS.

-----Original Message-----
From: Tim McCarthy <TimM@softwarejungle.com>
To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
Date: Thursday, June 03, 1999 1:09 PM
Subject: RE: Communication question


>Sorry to have to disagree Jeffrey but a fair percentage of our customers
>move their ASYNC comms from the PC to their AS/400 just because of the
>control and reliability they can get. How much reporting do you get from
>Procomm or HyperTerminal telling you when lines are down or files didn't
>get sent? How do you recover the PC when the comms application locks up
>- the old three finger salute's not much good in an unattended
>operation. We have customers running anywhere from 1 to over 100 comms
>lines without a networking staff. The only downside I see is the max
>speed of the slower comm ports but those can be upgraded.
>
>> -----Original Message-----
>> From: Jeffrey Silberberg [SMTP:jsilberberg@mindspring.com]
>> Sent: Thursday, June 03, 1999 7:12 AM
>> To: MIDRANGE-L@midrange.com
>> Cc: nina jones
>> Subject: Re: Communication question
>>
>>
>> Nina,
>>
>>         Yes, look at the "Asynchronous Communications Programmer's
>> Guide"
>> SC21-9592  for some direction and help in getting the AS/400 to
>> connect to
>> the link.
>>
>>         BUT, the reason I used the approach I have is that ASYNC over
>> a data
>> comm link can be a real issue with dropped or mal-formed bytes, and
>> timimg
>> issues to the ASYNC controller if you have an ACK/NAK protocol.  By
>> puting a
>> device at the interface and using a more robust protocol over the
>> network/DDS connection you will have MUCH less gray hair in the long
>> run.
>>
>>         You do have lot's of good options from list members.
>>
>>         Good Luck,
>>         JMS...
>>
>> -----Original Message-----
>> From: nina jones <ddi@datadesigninc.com>
>> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
>> Date: Wednesday, June 02, 1999 11:07 PM
>> Subject: Re: Communication question
>>
>>
>> >>
>> >>         Nina I do this for clients day in and day out with
>> something that
>> is
>> >> much more critical that what GM is most likely sending, we do E-911
>> >> Automatic Number/Location Information interfaces.   You say the
>> data is
>> >> coming over a DSU/CSU connection in ASCII but not what is
>> generating it,
>> or
>> >> what the over the wire protocol is, if any, do you know ?
>> >>
>> >>         Our interface is a basic PC using COM1: to interface to the
>> ASCII
>> >> hardware, and APPC over Ethernet or Token Ring to talk with the
>> AS/400.
>> All
>> >> messages go in a Data Queue, as well as a Physical file.
>> >>
>> >>         Let me know if you think it's a fit, or if you want more
>> details.
>> >
>> >they wanted the data to go directly to the as/400, if possible, not
>> an
>> >intermediate p/c.
>> >
>> >nj
>> >+---
>> >| 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
>+---

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.