|
It sounds like you want to run interactive jobs in a batch subsystem (or at least run them as batch jobs) but still present the user with a screen. TNAPI allows a batch job run interactive programs, emulating key strokes. You're right, however, it does not reduce interactive overhead. That's why I asked for clarification. Albert -----Original Message----- From: jt [SMTP:jt@ee.net] Sent: Wednesday, January 02, 2002 12:22 PM To: midrange-l@midrange.com Subject: RE: Brazen pre-announcement of vaporware Nathan, Albert Precisely. jt | -----Original Message----- | From: midrange-l-admin@midrange.com | [mailto:midrange-l-admin@midrange.com]On Behalf Of Nathan M. Andelin | Sent: Wednesday, January 02, 2002 3:09 PM | To: midrange-l@midrange.com | Subject: Re: Brazen pre-announcement of vaporware | | | From: "York, Albert" <albert.york@nissan-usa.com> | > Jt, | > | > I'm not sure what your goal is, but I already have a shareware | > tool for running interactive jobs in batch. It is called tnapi | > (telnet API) and works with all of the languages you listed. | | Albert, | | I'd say the goal is to cut the amount of interactive CPW used by | interactive | jobs. It looks like your telnet API makes it easier to write telnet | clients, not cut interactive CPW. | | Nathan M. Andelin | www.relational-data.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.