Modes of Operation
This section describes the modes of operation that Adabas Service for Java employs for the processing of Adabas direct commands.
The following table lists the available modes of operation you can configure using the AJZPARMS parameter MODE=, along with any necessary APF authorization and license requirements.

Mode | Description | APF Authorization Required | AZPAD License Required
1 | JNI operation issuing Adabas commands synchronously. | No | No
2 | JNI operation issuing Adabas commands synchronously with increased potential of zIIP eligibility. | No | No
3 | JNI operation issuing Adabas commands asynchronously with explicit WAIT. | No | No
4 | JNI operation issuing Adabas commands asynchronously with explicit WAIT using a helper thread. | No | No
5 | JNI operation issuing Adabas commands asynchronously with an implicit WAIT. | No | No
6 | zIIP enclave operation using TCP/IP for synchronizing tasks. | Yes | Yes
7 | Reserved. | – | –
8 | zIIP enclave operation using TRANSFER through a JNI for synchronizing tasks. | Yes | Yes
9 | zIIP enclave operation using PAUSE/RELEASE through a JNI for synchronizing tasks. | Yes | Yes

Note:
Although Mode=3 is the installation default, each mode of operation has varying advantages and disadvantages in relation to the performance indicators such as GP CPU, zIIP CPU, and elapsed time. Software AG recommends the testing of all appropriate modes to determine which might be the most suitable based on your performance requirements.