Within a time sharing address space, in essence, TPUTs are solicited by TGETs. That's what makes it interactive -- the synchronicity.
Messages from a submitted job back to its submittor are asynchronous, with '***' alerts that require a change from fullscreen mode to line mode, and back. The SEND command achieves this reasonably well and is suited to occasional notification messages. However, defining a file with TERM=TS implies that there may be a large number of asynchronous messages. Interleaving these with the user's routine interactive messages would not be pretty. > Date: Thu, 2 Sep 2010 21:48:06 +0200 > From: r.skoru...@bremultibank.com.pl > Subject: Re: DD TERM=TS,SYSOUT=* > To: IBM-MAIN@bama.ua.edu > > W dniu 2010-09-02 19:54, Ted MacNEIL pisze: > >> Would be nice to have(i.e TERM=TS from a batch job) > > > > > > Why? > Isn't it obvious? > More functionality is usually better. If you don't like it, then just > don't use it. > > > Wouldn't that violate so many integrity rules? > Well, it is non-existent feature, so it's quite hard to discuss the > details, but I could imagine a solution which is acceptable. > > > > There is always the SEnd command. > Which is not the same, although it can address some needs. > > -- > Radoslaw Skorupka > Lodz, Poland > > > -- > BRE Bank SA > ul. Senatorska 18 > 00-950 Warszawa > www.brebank.pl ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html