• Subject: RE: ICF woes :(
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 29 Jul 1998 10:10:51 -0400
  • Organization: commsoft

On Tuesday, July 28, 1998 7:58 PM, Tim Truax [SMTP:truax@usaor.net] wrote:
> I have a (local) RPG program that utilizes an ICF file.  Here is the
> problem I am having.  There is a (local) CLP program written that when
> run on the (local) source system, it loads the (local) RPG program and
> it receives requests from the remote location.  Then, it loads another
> RPG program that turns around and generates responses back to the remote
> system.  However, when this CLP program is run in a recovery mode, it is
> attempting to send residual (left over) responses FIRST and this
> particular (local) RPG program (or the program running on the remote
> system) is not working in this response-first manner.  Now, the question
> is:  Is there some modification that needs to be made on the program at
> the remote system that the AS400 is talking to so that it knows, when a
> linkage is established using the EVOKE keyword, instead of doing a
> receive then a response, it's just going to do the responses first?

On the source system, pass a parameter on your EVOKE so that the target 
knows whether to send first or receive first.  See the DDS or ICF manuals 
for more info on EVOKE.

Buck Calabro
Commsoft, Albany, NY

| 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 thread ...

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

This mailing list archive is Copyright 1997-2019 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].