|
|
|
|
|
A calling program can interface with Control‑M/Tape using either the base level or high level API (Application Programming Interface). The base level API offers versatility with few fixed requirements. The high level API provides more automation but requires an active Control‑M/Tape real-time environment and APF authorization. the following table details the differences between these two types of API access methods.
Note: The term "real-time environment" as used in this chapter refers to the Control‑M/Tape environment initialized by the following operator command: S CTTINIT,PARM=‘MODE=INIT’
Table 245 API Access Method Functions
Function |
Base Level API |
High Level API |
|---|---|---|
Available Functions |
Reads any Media Database record. |
Performs Read, Update, Add, or Delete functions on volume records only. |
Sequential Read |
Supported by the READNEXT function. |
Not supported. |
Authorization Required from the Calling Program |
None. |
APF authorization. |
Keyed and Non‑keyed Access |
Both keyed and non‑keyed (RBA based) access is supported. |
Only keyed access supported. |
Media Database Allocation |
The calling program must allocate DAMDB, DAMDI and DATRC files. |
The calling program does not need to allocate Database components. The real-time environment Data file, Index file, and Trace file are allocated automatically for the calling program. |
Load of Control‑M/Tape Control Table (TCT) |
The calling program must load a Control‑M/Tape Control Table (TCT). |
The calling program need not load a Control‑M/Tape Control Table (TCT). The real-time environment TCT is accessed for the calling program. |
Control‑M/Tape real-time environment |
Base level API can be used regardless of whether the Control‑M/Tape real-time environment is active. |
High level API can be used only if the Control‑M/Tape Real‑ Time Environment is active. |
Parent Topic |