RFC 379 (rfc379) - Page 3 of 5

Using TSO at CCN

Disk Space
----------

     TSO will automatically place datasets created in the foreground (e.g., by
     EDIT or ALLOC) on the proper resident disk pack.  All TSO datasets are
     cataloged, and can be referenced by name alone (no volume or unit specifi-
     cation is necessary).  For most purposes, you can pretend we have one big
     disk.                                                             --- ---
     ----

Dataset Names
-------------

     The standard IBM version of TSO uses the TSO user-id as the highest
     index of each dataset name.  At CCN, the _two_ highest levels are the
     charge number and the user-id of the person who created the dataset.
     TSO has been modified accordingly.

Dataset Access Control
----------------------

     In general, under TSO a user can access for reading, writing, or
     execution any dataset named with the charge number with which he is
     logged on.  In addition, he can rename or scratch any dataset with the
     logon charge number.  There is no provision for public or read-only
     datasets a present.

Logging On
----------

     Most Network users will need only the simple form of LOGON:

                   logon     

     EXAMPLE:                         NOTES:
     -------                          -----

          user:  logon uid            (Use your user-id)

          TSO:   LOGON UID            (TSO repeats line for reasons of its own)

          TSO:  ENTER PASSWORD        (TSO asks for password)

          user:  xyz

          TSO:  UID LOGON IN PROGRESS AT 11:37:43 ON AUGUST 9, 1984