Features from Version 6

The following features were introduced in Version 6.

  • A fully re-entrant engine that extends tableBASE performance benefits to multi-threaded applications.
  • Virtual Table Share (VTS-TSR) — a Virtual tableSPACE Region which provides read and write access to shared tables from any region.
  • The allocation of VTS-TSRs is done in a way that does not impinge upon your site’s MVS MAXCAD parameter.
  • VTS Manager—A three-tiered management product which provides flexible control of VTS-TSRs, and provides automation for VTS-TSR change control.
  • Data Spaces for local TSR and VTS-TSR storage allowing for a TSR size of up to 2G.
  • A single unified API that supports all stubs from prior releases, for all environments, with a single link-edit “include” library. A re-entrant stub allows you to build fully re-entrant application load modules.
    Note:
    VTS users who run applications that employ the TBCALLV and TBASEV interfaces should refer to VTS User access for additional information.
  • Improved locking of objects. The granularity of locking is at the table-level rather than the entire TSR.
  • Shortened code paths to provide faster, more efficient access to tables. The code path for access to VTS-TSR tables is now the same as that for the local TSR.
  • The tableBASE Root and Nucleus modules as well as the tableBASE CICS Resource Manager are above the line.
  • Special handling of DB2 Stored Procedures allowing the use of tableBASE to be extended to the DB2 area.
  • TBOPT parameters to provide runtime overrides for most of the installation options and the ability to list all options. TBOPTV is merged with TBOPT, allowing for a single source of run-time parameter input.
  • I/O routines tolerate open failures and I/O errors that may have resulted in region failures using previous versions of tableBASE.
  • The use of error subcodes in the extended command area for improved diagnostics (see tableBASE messages).
  • Individual libraries may be set to read-only.
  • Any library can be expanded.
  • All API stubs are shown in CICS EDF tracing. In previous releases, TBCALLC, TBASEV, TBCALLV were not captured by the EDF trace.
  • If a CICS task is put into a wait for a table exclusively held (opened for write) by another region, a CEMT INQUIRE task will show TBLBASE in the Suspend Value field.
  • STGPROT may be used with TBASEV and TBCALLV.
  • Since all the API stubs are re-entrant, they may be used to let applications take advantage of the CICS RENTPGM feature.
  • Enhanced support for CICS storage protection keys. Almost all the code run while in tableBASE modules is in the Exec key set by the installation’s CICS EXECKEY definitions, thus affording the protection implied by this CICS feature.
  • Various enhancements to Strobe, such as the production of finished reports directly in CICS.
  • The CICS TBOPT file may now be QSAM (including DD *) or, as it was in previous releases, VSAM.
  • The default date-sensitive processing date rolls over at midnight.