|
As an alternative to ICFF, consider CPI-C for comm programs. CPI-C is similar to ICFF, but it's done with program calls instead of writing formats to an ICFFile. As far as performance goes, 4 years ago they were neck and neck, but IBM was to keep improving CPI-C and ignoring ICFF. There are some good examples in the CPI-C manual, along with flow diagrams so you get an understanding of how the logic works. Not really complicated, but a lot of detail: you start with the basics, then add additional details for security, error handling, etc. You can consider either type of comm program to be just like a telephone call: Look up number Dial Number Wait for ring Wait for answer You there? Yeah, I"m here. Here's some data. got it. Here's some more got it. you sure you got it? I'm sure. OK, I'm hanging up Thanks, talk to ya later *click* --Paul E Musselman PaulMmn@ix.netcom.com >Hi all, > >How do ICFF programs work? Does it have to be a C program or could I write >this in RPG too (Is there an example somewhere in the Redbooks that I could >use)? I tried to write a program in RPG and had problems in F spec with >this file. I could not define this as workstation and use the write Evoke >record. When I defined this as a Special file, the program compiled but had >problems while running. Could someone throw some light on this please? Here >is what I have for each sending & receiving end : > > >- An ICFF file. >- A workstation file for Menus & other options. >- A CL to overlay the Pgm Dev Entry OVRICFDEVE and call to the (RPG) >program. >- RPG to actually receive/write the ICFF & workstation file. > >Again, should dataques be used with ICFF files? How will they improve the >performance? > >Any and all help would be appreciated. > >Thanks, >Sudha +--- | 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.