|
On Thursday, June 11, 1998 7:36 PM, Jeff Carey [SMTP:jeffreycarey@usa.net] wrote: > Unfortunately, the application isn't interactie - its a batch job talking > over the 3277 > devices. > Any ideas? -snip- > > > Now we need to move the application using thast line to another > > > AS/400 on our LAN > > > (but not at the same location, so I can't just change the physical > > > connection > > > (RS232 into a modem into a leased line). Jeff, Perhaps you can leave the application where it is and trigger it from the new machine. You can write an ICF program on the new box that EVOKEs the communications app on the old box. You'll have to modify the comms app to send the data back down the ICF link to the new box, but you have tight control over stuff like error detection/recovery. Alternately, create DDM files that link the old box to the new box. Leave the existing comms app alone; just point it's "output" to the DDM files via OVRDBFs. Trigger the communications application via SBMNETJOB from the new box. It's not as "tight" as ICF, but it requires less modification. hth, Buck Calabro Commsoft, Albany, NY mailto:mcalabro@commsoft.net +--- | 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-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.