|
If you want your program to sit and wait, you may want to have a look at
prestart jobs.
This type of program can be active before remote program starts and is
waiting for EVOKE to arrive.
Best regards,
Alexei Pytel
> -----Original Message-----
> From: Bob Crothers [SMTP:bob@cstoneindy.com]
> Sent: Wednesday, October 14, 1998 5:08 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: ICF Programming Snafu's! I Don't want to EVOKE!
>
> Andrew,
>
> I assume you are talking about APPC since EVOKE is an APPC thing. If
> you are using BYSYNC, ignore my message as I know nothing about it.
>
> The EVOKE is what causes the other end to "startup and do its thing".
> This is how APPC works.
>
> If you want want the other end to just sit there (already active) and
> wait for a connection, that is how TCP/IP works. In fact, there is NO
>
> equivalent to an EVOKE in TCP/IP. You must always have a program
> monitoring the address/port.
>
> Regards,
> Bob Crothers
> Cornerstone Communications, LLC
> www.faxserver401.com
>
>
>
> -----Original Message-----
> From: Andrew Borts [SMTP:adborts@ibm.net]
> Sent: Wednesday, October 14, 1998 10:46 AM
> To: MIDRANGE-L@midrange.com
> Subject: ICF Programming Snafu's! I Don't want to EVOKE!
>
> << File: vcard.vcf >> 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
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.