× 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: ICF Problem
  • From: Kirk Goins <KirkG@xxxxxxxxxxxxxx>
  • Date: Thu, 9 Mar 2000 13:12:32 -0800

You're probably right. I've done very little bisync stuff and it's been
awhile since I've done any ICF work. I just remember what a pain bisync
is/was compared to some of the other protocols
 

---------------------------------
Kirk Goins
IBM Certified AS/400 Technical Solutions
Pacific Information Systems - An IBM Premier Business Partner
503-290-2104
kirkg@pacinfosys.com
---------------------------------


> -----Original Message-----
> From: Carl Galgano [SMTP:cgalgano@ediconsulting.com]
> Sent: Thursday, March 09, 2000 10:49 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: ICF  Problem
> 
> Kirk:
> Never having done a BSC to ASYNC conversion I can't say for sure, but
> I
> thought the whole idea of using an ICF file and ICF communications is
> that
> is took the device and protocol dependencies and buried them all at
> the
> device level? On the S/38 we had a file type called BSCF (later BSC38
> on the
> AS400)and they were BSC specifies. Should you not be able to just
> acquire a
> new device with the correct ICF device entries and communicate.  I
> agree
> there are some keywords in the ICF file that only pertain to BSC
> (TRNRND,
> etc).  Just curious.
> CJG
> 
> 
> Carl J. Galgano
> EDI Consulting Services, Inc.
> 540 Powder Springs Street, Suite C19
> Marietta, GA  30064
> (770) 422-2995 - voice
> (419) 730-8212 - fax
> mailto:cgalgano@ediconsulting.com
> http://www.ediconsulting.com
> AS400 EDI, Networking, E-Commerce and Communications Consulting and
> Implementation
> 
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Kirk Goins
> Sent: Thursday, March 09, 2000 12:28 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: ICF Problem
> 
> 
> In general terms... bisync is a whole different world. In bisync the
> system initiates the call, causing the modem to dial. Once the other
> modem answers, it's up to the program(application) to control the
> link(read keep the line up). For most other protocols the low level
> connection(modem to modem) is done at the system level and the
> application only uses the connection.
> 
> With all that said I think you will have some programming changes to
> make to go from a bisync connection anything else.
> 
> ---------------------------------
> Kirk Goins
> IBM Certified AS/400 Technical Solutions
> Pacific Information Systems - An IBM Premier Business Partner
> 503-290-2104
> kirkg@pacinfosys.com
> ---------------------------------
> 
> 
> > -----Original Message-----
> > From:       SHISHIRKSINGH [SMTP:SHISHIRKSINGH@inf.com]
> > Sent:       Thursday, March 09, 2000 6:24 AM
> > To: 'MIDRANGE-L@midrange.com'
> > Subject:    ICF  Problem
> > Importance: High
> >
> > We had a bisynchronous connection between two AS400. Now we need to
> > switch
> > over to Asysnchronous connection. I have created the
> > line/Conctoller/device
> > description for Async connection. The parameters are more or less
> same
> > as
> > that for bysync.. connection. But the RPG program fails while
> > acquiring the
> > device.
> >
> > Is there anything that I am missing?
> >
> > Thanks
> > Shishir
> > +---
> > | 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.