Using the Relational Data Framework › Use the Relational Table Editor Batch API › Maintaining Cross-system Serialization

Maintaining Cross-system Serialization

To prevent the simultaneous updating of a relational table by more than one user, the batch API mode of ASOTEAPI uses the same serialization mechanism as the OPSVIEW relational table editor. This pseudo ENQ/DEQ mechanism is implemented using global variables, maintaining cross-system serialization. Thus, any attempt to change a table using the batch API fails if the table is in use by the ISPF relational table editor user or another batch API operation. Therefore, you should generally limit the primary use of the batch API to occasional table modification operations that do not conflict with normal table usage. If you choose to use the batch API as a part of your production operations, you should anticipate possible serialization conflicts in the automation procedure code.