TSRs and VTS-TSRs; tableBASE loads tables into memory-resident dataspaces called TSRs. A local TSR belongs to a single address space (e.g., one batch or CICS region) and is closed when that address space ends. A VTS-TSR is owned by a shared VTS Agent address space, so its data is available across multiple address spaces — including both batch and CICS. RESTConnector can expose data from either, but VTS-TSRs are recommended specifically because of their shared accessibility.
Key size and location; when a tableBASE table is defined, its key size and key location determine how the REST API retrieves records via HTTP query parameters — making table design a direct factor in API behavior, not just a backend detail.
Alternate indexes; If an API needs to retrieve multiple records by something other than the table’s primary key, an alternate index must be created on that alternate fields. Refer to the tableBASE Programming Guide for more information about Alternate Indexes.