Defining Transaction Programs for SNA API Clients

The SNA API Client Attach Manager only supports operator started or nonqueued attach manager started programs.

Transaction programs located at client machines require transaction program definitions on both Communications Server and client machines in order to be remotely started. Following is the transaction program information required on the server:
  • Transaction program name
  • Conversation type
  • Conversation style
  • Synchronization level
  • Whether or not conversation security is required

Communications Server will verify this information when the incoming allocate arrives. In addition, the local LU that receives the incoming allocation request must be enabled to route the request to the client machine.

The client attach manager must have a transaction program defined so that it knows how to start the requested program. Following is the transaction program information required on the client:
  • Transaction program name
  • The local LU that receives the incoming allocation request
  • The path name of the program
  • Any parameters that need to be passed to the transaction program

Once these definitions are complete and the client attach manager is started, incoming allocates for transaction programs located on client machines will be routed to the client for processing.

The default local LU alias for each user can be assigned using the appropriate configuration utility, either INI configuration or LDAP.

Attach manager started programs can also choose to use a default local LU alias rather than specify one directly. When the local_LU_alias field is left blank in the attach manager record, the attach manager uses the configured default local LU alias when processing incoming conversation requests.