Protecting tableBASE tables

tableBASE tables can be protected in the library (using read and write passwords) and when loaded in memory (using the LOCK-LATCH password feature). These passwords offer only limited protection against unauthorized use of tableBASE tables. More formal security can be implemented via user exits and third party measures such as Resource Access Control Facility (RACF), eTrust CA-ACF2 Security for z/OS, and eTrust CA-Top Secret Security for z/OS. Such data security systems may be used to protect tableBASE libraries. If invalid access to a library is attempted via application use of tableBASE, the access will be refused.

In the event that a table password or LOCK-LATCH password is lost or forgotten, please notify your tableBASE administrator.

Read and write passwords

Passwords are used when opening tables from the library. Once in memory (i.e., in a TSR), the tables can be accessed by any application with access to that TSR or VTS-TSR. A read password protects a table from being opened for either read or write. A write password protects a table from being opened for write. For more information on passwords see 5. RPSWD (8 bytes), and 6. WPSWD (8 bytes).


LOCK-LATCH passwords are used by applications to protect a tableBASE table from being changed in memory by unauthorized users in a multi-user environment. To control the user(s) or transactions that perform the subsequent updates in a multi-user environment after a table is opened for write, place a password in the LOCK-LATCH field when Opening a table for Write. Only the update commands that have the same password in the LOCK-LATCH field are authorized to perform the update. LOCK-LATCH is needed for Read-Write VTS-TSRs, but not Read-Only VTS-TSRs.

For further information, see 9. LOCK-LATCH (8 bytes).