Accessing the Mainframe (TSO)
Learn what TSO (Time Sharing Option) is, how to log on, and how it provides an interactive command-line environment on z/OS.
Introduction
Everything you have learned so far has been conceptual. This lesson is where you actually start touching the mainframe: TSO, the Time Sharing Option, is the standard way a person logs on and works interactively with z/OS. Nearly every other topic in this course — editing JCL, browsing datasets, using ISPF — happens inside a TSO session, so understanding it well is a practical necessity, not just background knowledge.
What is TSO?
TSO stands for Time Sharing Option. It is a z/OS facility that lets multiple users log on at the same time and interact with the system directly, each in their own isolated session (running, as you learned in the last lesson, in its own address space). Before TSO existed, mainframe work was almost entirely batch: you submitted a job, waited, and reviewed the output later. TSO added the ability to work conversationally — typing a command, seeing an immediate response, and reacting to it — much like a command-line shell on any other operating system.
TSO is the mainframe's interactive, command-line environment — the thing that lets a human sit down and directly work with z/OS in real time, rather than only submitting work and waiting.
Batch vs. Interactive Work
It is worth being clear about this distinction early, because you will see it constantly in mainframe work.
| Mode | How It Works | Typical Use |
|---|---|---|
| Batch | You submit a unit of work (a job, defined in JCL) and it runs independently; you check results afterward | Large data processing runs, month-end reporting, overnight processing |
| Interactive (TSO) | You type commands and see immediate responses, in a live back-and-forth session | Editing files, browsing data, submitting/monitoring jobs, day-to-day development work |
In practice, the two are closely linked: you commonly use a TSO session (often through ISPF, covered in the next lesson) to create and edit the JCL that defines a batch job, then submit that job to run — and TSO is also how you go check on the results afterward.
Logging On to TSO
To start a TSO session, a user connects to the mainframe (traditionally through a terminal emulator that mimics classic mainframe display terminals) and is presented with a logon screen, where they supply their userid and password.
IBM z/OS - TSO/E LOGON
ENTER LOGON PARAMETERS BELOW: RACF LOGON PARAMETERS
USERID ===> STUDENT1
PASSWORD ===> NEW PASSWORD ===>
PROCEDURE ===> IKJACCNT SIZE ===> 4096 GROUP IDENT ===>
ENTER AN 'S' BEFORE EACH OPTION DESIRED BELOW: -NOMAIL -NONOTICE -RECONNECT -OIDCARD
PF1/PF13 ==> HELP PF3/PF15 ==> LOGOFF PA1 ==> ATTENTION PA2 ==> RESHOWRACF (which you will meet properly in a later lesson) is the security component that validates the userid and password here and determines exactly what that user is permitted to do once logged on. After a successful logon, TSO typically presents either a plain command-line prompt or launches directly into ISPF, depending on how the shop has configured that user's profile.
The TSO READY Prompt
If a user goes to the plain TSO command line rather than straight into ISPF, they see the READY prompt — the mainframe equivalent of a shell prompt, waiting for a command.
READYTIMEIKJ56650I TIME-09.32.17 CPU-00:00:00 SERVICE-210 SESSION-00:04:12READYLISTDS 'STUDENT1.TEST.DATA'STUDENT1.TEST.DATA--RECFM-LRECL-BLKSIZE-DSORG FB 80 27920 PS--VOLUMES-- USER01READYClick Run to see what this code prints.
Common TSO Commands
| Command | Purpose |
|---|---|
| LOGON | Start a TSO session (entered at the logon screen) |
| TIME | Display the current time and session usage information |
| LISTDS | List the attributes of a specified dataset |
| LISTCAT | List catalog information about datasets |
| SUBMIT | Submit a JCL job for batch execution |
| STATUS | Check the status of jobs the user has submitted |
| ISPF | Launch the ISPF menu-driven interface (covered in the next lesson) |
| LOGOFF | End the current TSO session |
Logging Off
Ending a TSO session cleanly with LOGOFF (or the equivalent PF key) releases the resources tied up by that session's address space. Leaving sessions open unnecessarily is generally discouraged in real shops, both as a resource-usage and a security consideration — an unattended, logged-on session is a security exposure.
Common Mistakes
- Confusing TSO (the interactive facility) with ISPF (the menu-driven interface commonly launched from within TSO) — TSO is the underlying session; ISPF is a tool you run inside it.
- Assuming interactive work replaces batch work — most real production processing still happens through batch jobs; TSO is primarily how you develop, manage, and monitor that work.
- Forgetting to log off, leaving an authenticated session open and exposed.
- Typing commands without checking the READY prompt returned first — mainframe terminal sessions traditionally do not always echo instantly like a modern terminal, so it is easy to type ahead of a response.
Best Practices
- Learn a handful of core TSO commands (LISTDS, LISTCAT, SUBMIT, STATUS) early — they cover the majority of everyday interactive tasks.
- Always log off deliberately at the end of a session rather than simply closing the terminal window.
- Treat your TSO userid and password with the same care as any other production credential — RACF is enforcing real security boundaries behind it.
- When something behaves unexpectedly, check for a READY prompt or an error message before assuming the system is unresponsive.
Frequently Asked Questions
Time Sharing Option. It is the z/OS facility that allows multiple users to log on and interact with the system directly, each in an isolated, interactive session.
No. TSO is the underlying interactive session facility. ISPF is a menu-driven interface that typically runs on top of a TSO session, and is what most users actually spend their time in — covered in the next lesson.
Both are common. Many shops configure users to go directly into ISPF after logon since it covers the vast majority of daily tasks, but the plain TSO command line (the READY prompt) is still available and used for certain commands and quick tasks.
RACF, the mainframe security system, enforces logon security policies, which typically include revoking or locking a userid after a defined number of failed attempts, just as most modern systems do.
Key Takeaways
- TSO (Time Sharing Option) is the z/OS facility that provides interactive, command-line access to the mainframe.
- Batch work is submitted and reviewed later; interactive TSO work happens in real time, command by command.
- Logon requires a userid and password, validated by RACF, the mainframe security component.
- The READY prompt is the plain TSO command line, similar in spirit to a shell prompt on other operating systems.
- ISPF, covered next, is a menu-driven interface that typically runs on top of a TSO session and is where most day-to-day work actually happens.
Summary
TSO is your entry point into hands-on mainframe work: it is what lets you log on and interact with z/OS directly, whether at the plain command line or, more commonly, through the menu-driven interface built on top of it. In the next lesson, you will explore that interface — ISPF — including its Primary Option Menu and the common panels used for browsing, editing, and working with datasets and utilities.