Time Sharing Option

From Wikipedia, the free encyclopedia
Jump to: navigation, search
History of IBM mainframe operating systems

Time Sharing Option (TSO) is an interactive time-sharing environment for IBM mainframe operating systems, including OS/360 MVT, OS/VS2 (SVS), MVS, OS/390, and z/OS.

Use[edit]

TSO fulfills a similar purpose to Unix login sessions. Time-sharing means that many persons can access the operating system concurrently, while unaware that others are also accessing the operating system. It appears to each TSO user that they are the only user on the system.

TSO is most commonly used by mainframe system administrators and programmers. It provides:

TSO interacts with users in either a line-by-line mode or in a full screen, menu-driven mode. In the line-by-line mode, the user enters commands by typing them in at the keyboard; in turn, the system interprets the commands, and then displays responses on the terminal screen. But most mainframe interaction is actually via ISPF, which allows for customized menu-driven interaction. This combination is called TSO/ISPF. TSO can also provide a Unix-style environment on OS/390 and z/OS via the UNIX System Services command shell, with or without ISPF.

TSO commands can be embedded in REXX execs or CLISTs, which can run interactively or in batch.

History[edit]

When it was originally introduced in 1971,[1] IBM considered time-sharing an "optional feature", as compared to standard batch processing, and hence offered TSO as an option for OS/360 MVT. With the introduction of MVS in 1974, IBM made it a standard component of their top-end mainframe operating system. TSO/E ("Time Sharing Option/Extensions") is a set of extensions to the original TSO. TSO/E is a base element of z/OS. Before z/OS, TSO Extensions (TSO/E) was an element of OS/390 and was a licensed program for the MVS and MVS/ESA System Products.[2] Since all z/OS installations usually have both TSO and TSO/E functions installed, it is normal to refer to both TSO and TSO/E as "TSO".

Batch use[edit]

It is common to run TSO in batch (as opposed to interactively): all the usual TSO line-mode interactive commands can be also executed via Job Control Language (JCL) by running any of the programs IKJEFT01, IKJEFT1A, or IKJEFT1B and supplying the line commands in a file pointed to by the SYSTSIN DD. The primary difference between the three programs is their handling of return codes from the executed commands.

Batch execution of TSO is one way to allow an IBM mainframe application to access DB2 resources.

See also[edit]

References[edit]

  1. ^ TSO Times, Spring 2004, p.5, Chicago-Soft, LTD., Hanover, NH
  2. ^ "Overview of TSO/E Programming Services", IBM z/OS V1R9.0 information center

Further reading[edit]

  • Lowe, Doug (1991). MVS TSO, Part 1: Concepts and ISPF (Second Edition ed.). Mike Murach & Associates, Inc. 
  • Lowe, Doug (1991). MVS TSO, Part 2: Commands And Procedures (Second Edition ed.). Mike Murach & Associates, Inc. 

External links[edit]