Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

OSPI sessions

There are two types of OSPI sessions: scripting sessions and EXEC sessions.

You can use both types of sessions when using OSPI to automate a function. Normally, scripting sessions are used first to record the appropriate interactions with VTAM applications in EXECs. Then, EXEC sessions are used when the functions are automatically performed by BMC AMI Ops Automation.

All OSPI sessions follow the same basic flow regardless of the session type, the application they are interfacing with, or the task they are performing:

  1. A session is established between an OSPI virtual terminal and a VTAM application.
  2. Data is then exchanged between the virtual terminal and the application.
  3. The session is terminated.

All of these tasks are accomplished by using either the Scripting application or IMFEXEC command statements in an EXEC.

This section contains the following topics: 

Related topic

Interacting-with-VTAM-applications-with-OSPI

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*