Operations › The Role of TSO in the Architecture › How TSO TMP Is Used

How TSO TMP Is Used

One of the TSO service routines is the terminal monitor program (TMP). The TMP accepts, interprets, and schedules commands that you issue at your terminal.

CA OPS/MVS uses the TMP in various ways, including:

• Processes run requests

  When requests to run OPS/REXX programs, TSO commands, and TSO/E REXX programs or CLISTs are sent to them, OPSOSF servers use the TMP to process the requests.

• Runs the OPSTART1 initialization CLIST

  When CA OPS/MVS initializes, the OPSMAIN address space invokes the TMP to run an initialization CLIST called OPSTART1. The OPSTART1 CLIST, in turn, invokes an OPS/REXX program (or optionally another CLIST) that sets the CA OPS/MVS initial parameter values.

  This approach offers these advantages:

  • Ease of programmability. Your site can run more than one copy of CA OPS/MVS. Typically, 10 percent or less of the parameter values you specify for one copy of CA OPS/MVS differ from the parameter values you want to specify for the other copies. With the capabilities of the OPS/REXX or TSO CLIST language, you can maintain a single set of parameters with conditional logic that handles the differences among the systems.
  • Familiarity. Systems programmers who install and maintain CA OPS/MVS already know the TSO/E REXX or TSO CLIST language.
  • Interactive access. You can use the TSO interactive facilities to invoke the OPSPARM command just as easily as it can be invoked from a CLIST. Thus, any parameter that can be changed after initialization can be set from TSO by issuing OPSPARM commands either directly or from an ISPF dialog that builds and executes CA OPS/MVS commands.