Re: batch job that uses a dspf.

Leif,

I think that the minor detail that you are looking for is the difference
between the system (OS/400) or your program sending the data stream.

From the OS/400 view point, if the client want's to talk 5250 (like an
emulator) it makes a 5250 connection.  If the client want's to just make
a connection, it can be a sockets connection and then both the server
program (yours -not- OS/400) and the client can agree on any data stream
you wish.

And you are correct.  Your scenario could be batch.

From an OS/400 view point a socket connection is -not- a 5250
connection. It's a TCP/IP sockets connection.  What you send through it
(5250, 3270, 3451, HTML, XML, MSGQ, DTAQ, etc.) it doesn't know. 
Computers can't read ;)

Now software like Client Access, TN5250 use TCP/IP as the transport
protocol but they make a 5250 connection.  They pretend to be a 5250
hardware device.



Leif Svalgaard wrote:
> 
> From: James W. Kilgore <eMail@James-W-Kilgore.com>
> 
> > AFAIK, interactive is any 5250 data stream process.  This includes any
> > manner of front end that you may have
> 
> this is still too vague. Imagine this scenario:
> I have a batch job that talks to a PC client using TCP/IP
> sockets. It sends the PC client a 5250 data stream over
> the socket. The PC client converts that to a nicer looking
> screen (GUI or whatever).
> 
> This is clearly a 5250 data stream process but is not
> interactive (AFAIK).
>
+---
| 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
+---