If the database being used supports multithreaded stored procedures, the applications that call SSA-NAME3 may be implemented as database stored procedures that dynamically call the SSA-NAME3 DLL.

The CICS application can call the SSA-NAME3 Server, a process which is started in a separate region. CICS applications communicate with the SSA-NAME3 Server through a SSA-NAME3 stub program which uses sockets and TCP/IP. The additional requirements for CICS applications calling the SSA-NAME3 Server are therefore:

CICS TCP/IP Socket Interface support must be installed, configured and enabled.
Language Environment (LE) must be enabled in CICS.

The CICS application can call the SSA-NAME3 DLL locally, within the CICS region. Using this method, it is the user application’s responsibility to serialize the Open and Close calls to SSA-NAME3. The recommended approach for doing this is through the ENQ/DEQ commands using a fixed name ENQ as illustrated below:

01 SSAN3SID PIC X(8) VALUE "SSAN3SID".

EXEC CICS ENQ RESOURCE(SSAN3SID) LENGTH(8) END-EXEC
CALL SSAN3-OPEN .... (or SSAN3-CLOSE)
EXEC CICS DEQ RESOURCE(SSAN3SID) LENGTH(8) END-EXEC

Using this method, LE must also be enabled in CICS.

If multiple CICS regions are involved, ENQ/DEQ can be ’externalized’ across LPARs / CICS regions and managed by Global Resource Serialization (GRS) using appropriate ENQ MODEL resource definitions.