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.


        -----Original Message-----
        From:   jt []
        Sent:   Wednesday, January 02, 2002 12:22 PM
        Subject:        RE: Brazen pre-announcement of vaporware

        Nathan, Albert



        | -----Original Message-----
        | From:
        | []On Behalf Of Nathan M.
        | Sent: Wednesday, January 02, 2002 3:09 PM
        | To:
        | Subject: Re: Brazen pre-announcement of vaporware
        | From: "York, Albert" <>
        | > 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
        | clients, not cut interactive CPW.
        | Nathan M. Andelin

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

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