Thursday, October 22, 2015

Z/OS Unix Services

Many changes have occurred in the world of computing since the announcement of System/360 in 1964.

Among the many significant changes is the development of the UNIX operating system by employees at AT&T's Bell Labs in the 1960s.

Although UNIX has concepts such as processes and threads, which are analogous to z/OS concepts such as address spaces and tasks, many significant differences exist.

For example,
  - In UNIX, files are byte-oriented streams of data,
  - But in z/OS, files (data sets) are record oriented.

../Pict/coursefocus/Ef_UNIX.gif

Within z/OS, you have a complete UNIX environment with z/OS UNIX System Services. 
This UNIX environment is integrated with the "traditional" z/OS environment. For example, you can access a z/OS UNIX file from a batch job and you can access a data set from a z/OS UNIX application.

You can enter the world of UNIX from z/OS in several ways. 

- From TSO, you can enter the z/OS UNIX environment using the OMVS command from the TSO READY prompt.

- Within the ISPF environment, you can type the command tso omvs to enter UNIX (in general, you can run any TSO command from ISPF by prefacing it with tso).

Why OMVS?

When IBM first added the UNIX environment to MVS, it was called Open Edition, with the "Open" designating this environment and set of interfaces as one that was not designed or owned by IBM.

The logical extension of this is Open MVS, which was shortened to the command OMVS. You can see vestiges of this naming convention in the OMVS command, the OMVS segment in user profiles, and the z/OS UNIX "O" commands, such as OGET, OPUT, and OEDIT.

No comments:

Post a Comment