An application using SSA-NAME3 Version 2 will normally make 5 API calls:

In addition, if using the SSA-NAME3 Server, it is necessary to make the following two calls to open and close the socket connections:

If used, the

ssan3_connect

call should be done prior to the

ssan3_open call

, and the

ssan3_disconnect

call done after the

ssan3_close call

.

Only one connect, open, close and disconnect call should be made during the active life of the application or thread, that is from when the time the application or thread is started to the time it is terminated. These calls should frame the rest of the work done by the application.

It is imperative that socket-handles and Session-IDs are not shared across concurrent transactions or threads.

In addition, if using the SSA-NAME3 Server and you wish to use 5-byte binary keys in order to save on disk space, it is necessary to make the following two calls to convert the 8-byte keys passed from the SSA-NAME3 Server:

Note that some databases, programming languages and transport mechanisms will not support binary keys. If you are unsure, you need to contact Informatica Corporation.

At a very high level, the sequence of API’s in an application using SSA-NAME3 is depicted as shown below: