ACCESS is the term given to the Com-plete access method: communication is performed via the Adabas router interface.
This is used, for example, to provide communication with other TP-monitors in the Adabas TPF environment. It is also used in Com-plete Batch support to provide the basic communication between the Batch job and the Com-plete Batch interface utility UBATCH.
Communication with the Adabas router is provided by modules supplied on the Adabas load library. These modules are loaded during initialization from the Adabas load library.
Com-plete issues the appropriate calls to sign onto and initiate communication with the Adabas router using the parameters supplied during Com-plete initialization.
Sysparm ACCESS-NCQE defines the number of command queue elements which are allocated by the Adabas router. This restricts the maximum number of concurrent Com-plete transactions. Note that this is not the same as the number of logged on users: this is normally higher and is only restricted by the availability of TIBTAB entries.
Sysparm ACCESS-NABS defines the number of attached buffers which are allocated by the Adabas router for cross-memory services. The Adabas router acquires storage for the attached buffers during ACCESS initialization, the size of this acquired area is approximately (NABS * 4 Kbytes). This restricts the amount of data which can be transmitted. Adabas TPF requires approximately 7K of attached buffers per active transaction (see ACCESS-NCQEs).
Sysparm ACCESS-ID defines the (pseudo-)data base ID with which the server Com-plete signs on to the Adabas router.
Sysparm ACCESS-SVC defines the router SVC number. Note that this SVC need not be the same as for normal data base communication.