Mainframe Path Start learning free
Core7 min readLesson 3 of 3

Working on NonStop

Day-to-day work on NonStop uses TACL, the command interpreter; the Guardian environment with its \node.$volume.subvolume.file names, or OSS for POSIX tools; Pathway (TS/MP) to run online servers; Enscribe files and NonStop SQL for data; and EMS for the event log.

Commands and environments

Running online applications: Pathway

Pathway, also called NonStop TS/MP, runs online transaction servers. A server class is a group of identical server processes; requests from clients are routed to a free server, and the number of servers can grow and shrink with demand. PATHMON is the process that manages a Pathway environment. Pathway plays the role that CICS plays on z/OS.

Data

NonStopWhat it isNearest z/OS idea
EnscribeThe native record file system (key-sequenced, entry-sequenced, relative and unstructured files)VSAM KSDS, ESDS and RRDS
NonStop SQL (SQL/MP, SQL/MX)Relational databases, spread across processors and disksDb2 for z/OS
TMFTransaction protection and recoveryDb2 and CICS logging and recovery

Operations tools

TRY IT YOURSELF

What is NonStop's command interpreter called? (four letters)

Show a hint

Tandem Advanced Command Language.

Show the solution

TACL.

Common mistakes

Looking for CICS

Online servers run under Pathway (TS/MP), organised in server classes.

Using z/OS data set names

Guardian names have the form \NODE.$VOLUME.SUBVOL.FILE; OSS uses Unix-style paths.

Ignoring EMS

EMS is where the system and applications report events; it is the first place to look in an incident.

What you will see at work

Key terms

Check your understanding.
Take this lesson's quiz and save your progress. Free.

Take the lesson quiz
← How NonStop keeps runningBack to HPE NonStop (Tandem) fundamentals