RE: Re[2]: ICF Programming Snafu's! I Don't want to EVOKE!

Eric,

Actually, to be honest, it doesn't much matter to me anyway.  We are 
moving all of our stuff over to TCP/IP....and there is no evoke in 
that.  You must have a "server" job active and running that is just 
waiting for a connection request.

The only form of ICF files I've used has been APPC....and that has 
always been between the AS/400 and PC worlds.  Doing the evoke was not 
a problem for me so I never worried about getting rid of it.

Bob

-----Original Message-----
From:   eric.delong@pmsi-services.com 
[SMTP:eric.delong@pmsi-services.com]
Sent:   Thursday, October 15, 1998 9:58 AM
To:     MIDRANGE-L@midrange.com
Subject:        Re[2]: ICF Programming Snafu's! I Don't want to EVOKE!


     Actually, on retrospect I see we're doing BSCEL via ICF at this
     location. I'm pretty sure I've tested a sample pgm using APPC via 
     ICF without using EVOKE. It was some time ago, testing *Intra
     communications. I'm almost certain that EVOKE is optional.

     As I recall, the test was for a oen-way data transfer on a 
dial-up
     connection. We were receiving data from S36, basic conversation. 
We
     were not using BSC. That's all I can remember out of hand.....
     Perhaps my memory has played me false.

     Eric


______________________________ Reply Separator 
_________________________________
Subject: RE: ICF Programming Snafu's! I Don't want to EVOKE!
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    10/14/98 4:24 PM


Eric,

Using APPC w/ICF, is this possible?  I always thought you had to do
the EVOKE.  In fact, that is how I've done many APPC programs.

How do you indicate what you want to connect to?

Bob

-----Original Message-----
From:        eric.delong@pmsi-services.com
[SMTP:eric.delong@pmsi-services.com]
Sent:        Wednesday, October 14, 1998 3:30 PM
To:        MIDRANGE-L@midrange.com
Subject:        Re: ICF Programming Snafu's! I Don't want to EVOKE!


     Andrew,

     I'm not exactly sure I understand.... is it something like:

     1> AS400 (sys a) always runs a comm job that just waits for
     connection (ICFW or BSCW).

     2> AS400 (sys b) dialing into sysA for testing. As soon as
     connection is established, pgms start talking.

     3> Tandem (sys c) dialing in to sysA for production. like above.


     A waiting for connection
     B or C dialing A
     Connect
     B-->A  (send request) pgm to pgm
     A-->B  (send reply)   pgm to pgm
     Disconnect
     A waiting for connection

     Evoke is not necessary. Just have the comm job active on Sys A,
and
     it will just wait for a valid connection to begin. If this is the 
     scenario, I might be able to provide you with samples. Contact me 
@

     eric.delong@pmsi-services.com


______________________________ Reply Separator
_________________________________
Subject: ICF Programming Snafu's! I Don't want to EVOKE!
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    10/14/98 11:45 AM


I'm trying to simulate connection to a mainframe via an ICF file using 
two AS/400's , and I'm running into a problem in getting the two
AS/400
to chat with one another.  I want to blind transmit information sent
over the ICF to the receiving AS/400 end, and reply using the program
that is sitting and waiting for a communication that would normally be 
to a mainframe (tandom..).  So far, I've run into the snafu that I
have
to evoke the receiving end from the transmitting AS/400 end.  In
reality, I don't want to evoke, and I want the other end just to
startup, and answer messages sent by the mainframe.  Any clues as to
what I do?
-Andrew Borts
Systematic Control, Inc.
(954) 791-9555 x333


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