RE: Weigh in on Fast400 . . .

James,

You are correct that SPECIAL files lack READC, etc.  I remember some talk
someplace that suggested these are contemplated for future releases.  OTOH,
I know of a company that used SPECIAL files to great advantage, by creating
an MQ file type.  Their average RPG coder could hook to MQ, quite easily.
So apparently, there are workarounds.

Don't know much about how Telnet works, vs. HTTP Server, technically.  But I
believe the Telnet client just executes the same Workstation Manager
functions as dumb terminals, so therefore is interactive.  HTTP Server
doesn't use the Workstation Manager functions.  But it probably could be
made to, if IBM was running short of cash...;-)  (Not...)

jt

> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of James W. Kilgore
> Sent: Thursday, November 08, 2001 6:04 PM
> To: midrange-l@midrange.com
> Subject: Re: Weigh in on Fast400 . . .
>
>
> jt,
>
> AFAIK, SPECIAL files are limited to open, close, read, write and update.
>
> This would have to be expanded to include READC, CHAIN, and
> EXFMT.  So I think
> that Leif is on a better track than using SPECIAL files.
>
> I was giving some thought to why when both the HTTP and telnet
> servers are batch
> jobs, that the telnet client is "interactive" and the http client
> is not.  The
> only thing that I can think of is that the telnet session
> requires a constant
> connection where the http client does not.  The telnet server
> "knows" when Elvis
> left the building and the HTTP server could care less.
>
> Oh well.  I better get back to work.
>
> jt wrote:
> >
> > Hate to throw a sticky wicket into the mix.  The SEPT would
> work fine, but
> > SPECIAL files already include that capability.
> >
> > BTW, James, what you described is exactly what I'm talking
> about.  MI is one
> > approach, SPECIAL files is another...  There are advantages and
> > disadvantages to each, but either can be used to accomplish
> something like
> > this.
> >
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>