Core6 min readLesson 1 of 3
z/OS Unix in one page
z/OS contains a certified Unix. There is a hierarchical file system with directories and permissions, a shell, and the usual commands. It is not an emulator and not a separate machine — it is part of the operating system, sharing the same security manager and the same processors.
Two ways of naming things, side by side
MVS side
PROD.PAY.MASTERDatasets, catalogued44-char names, uppercaseAccessed by DD statement
Unix side
/u/vsaha1/pay/master.txtFiles in directoriesLong, case-sensitive namesAccessed by path
Getting to the shell
| Route | How |
|---|---|
| From TSO | Type OMVS at the READY prompt or from ISPF option 6 |
| From ISPF | Option 3.17 gives a file-system browser (ISHELL) |
| From your laptop | SSH to the system, if your site enables it |
| From batch | BPXBATCH, or the shell via a JCL step |
What lives where
| Path | Holds |
|---|---|
| /bin, /usr/bin | Shell commands and utilities |
| /etc | Configuration |
| /u/userid or /home/userid | Home directories |
| /var | Variable data, logs |
| /tmp | Scratch space, cleared periodically |
| Product directories under /usr/lpp | Installed products, e.g. Java, Python, web servers |
What actually runs here
- Java applications — z/OS Java runs in USS, and a great deal of modern mainframe work is Java.
- Web and application servers, message brokers, and API gateways.
- File transfer and integration — SFTP, scripts, and scheduled jobs that bridge platforms.
- Git and modern tooling — many sites now keep mainframe source in Git repositories held in USS.
- Python, Node and shell scripting for automation.
Common mistakes
Assuming it is a separate machine
It shares the same security, the same processors and the same address space model. A USS process is a z/OS address space.
Expecting Linux behaviour everywhere
Most commands are the same. Character encoding, file tagging and some option flags are not.
Writing large temporary files to /tmp in production
It is shared and finite. Use a directory your application owns.
What you will see at work
- USS permissions are POSIX (owner/group/other) but backed by your site's security manager, so a permission problem may need a security request, not a chmod.
- Your userid needs an OMVS segment to use USS at all. 'I cannot get to the shell' is often that, not a password problem.
- File system space is managed like any other dataset. A full file system stops applications in a way that looks mysterious from the MVS side.
Key terms
Check your understanding.
Take this lesson's quiz and save your progress. Free.