Chris Mason wrote:
comprehensive functions for my "silent running" automation. In other words there may have been a short period in the history of NCCF/NetView when TSSO offered the cleverest way - maybe the only way - decently to automate MVS, that is, better than using the internal reader for commands and a "wait" program.
The first version of TSSO appeared not too long after TSO. I am not certain who the original author was, but recall seeing Bill Godfrey's name in the documentation. That version allowed the operators to issue (some) TSO commands from a console. In the mid or late seventies, Marc Share at Bell Labs presented an updated version that provided the capability to intercept console messages, and take some action (message, OS command, etc.); the nice part was the extraction by position or word count from the message, and insertion into an MVS or TSO command. When I was at AMS, and several later centers, I used this to automate just about everything possible (e.g., VTAM line and terminal error recovery, deletion of unwanted messages, etc.). IIRC, the early versions of NETVIEW/NCCF were a chargeable item, so TSSO was it. And it certainly was more flexible than (the early) linked exits, because it was table driven and the tables could be reloaded on the fly.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- 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
