A Comparison of Roscoe and TSO

Document ID : KB000055664
Last Modified Date : 14/02/2018
Show Technical Document Details
  1. The Roscoe Library System provides a single repository for user data that is self compressing rather than the TSO environment which results in a multitude of PDS's. There is an obvious time saving in compressing and maintaining a large number of libraries.

  2. Roscoe is cost effective because there are multiple users in a single address space. Approximately 80-90 users can execute in a 8M-9M region with each additional user taking about 45K. TSO requires a flat 7M per user.

  3. Roscoe has its own dispatching logic, while TSO competes with the operating system and can get swapped out.

  4. Roscoe interfaces directly with AllFusion CA-Librarian, AllFusion CA-Panvalet, AllFusion Endevor, and SAR.

  5. Roscoe executes in a single command code vs. panel mode.

  6. Users can run applications in the same address space. (ETSO) The best applications to run under ETSO are those that do not consume a lot of resources. When running something like ISPF under ETSO only one user can really use it at one time. This is understandable if you realize these applications all run in the Roscoe address space. Some applications should stay under TSO. However, there can be a lot of savings even with this.

    NOTE: By adding ETSO applications, you will slow down Roscoe. Roscoe is not designed to run lots of ETSO applications simultaneously. Depending on your application, it can take a lot of resources. For Example, TSO's ISPF is an application that takes a lot of resources. If you add more applications under ISPF, that takes more overhead.

  7. A facility is available whereby users can execute applications in a region separate from Roscoe's. (BTSO)

  8. Roscoe supports CLIST and REXX execs

  9. Users can run CICS, TSO and another Roscoe region under Roscoe.