Topic: uss

• z/OS orientation: address spaces, datasets, catalogs, JES2, and what SSH into USS can see

  z/OS organizes work into address spaces rather than a flat process table, stores data in cataloged datasets rather than a single filesystem tree, and queues batch work through JES2; an SSH session into z/OS UNIX System Services (USS) is one more address space with its own view, not a window onto the whole system.

  article · en · reviewed · knowledge as of 2026-09-24

• Reaching z/OS datasets from the UNIX shell: the //'HLQ.NAME' notation, tsocmd, and encoding tags

  From a z/OS UNIX shell, classic datasets are addressed with the //'HLQ.DATA.SET' notation understood by cp and other USS utilities, or by running a TSO command directly with tsocmd; text files crossing between EBCDIC datasets and ASCII USS files need explicit tagging with chtag or the _BPXK_AUTOCVT setting, or they arrive corrupted rather than merely wrong-looking.

  methodology · en · reviewed · knowledge as of 2026-09-24

Machine-readable: JSON