OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM

OSI/FTAM Configuration and Management Manual—421944-001

3-13

How Configured Information Is Used in Making

FTAM Associations

The following steps occur when Tandem FTAM is started:

1. A system operator or a command file sends the APLMGR process an SCF START

command to start the initiator.

2. The APLMGR process retrieves information from its MIB as follows:

The APLMGR process starts the initiator and sends it the retrieved information.

The following steps take place when an application makes a call to

FTM_INITIALIZE_REQ_:

3. On behalf of the application, the FTAM API sends the specified APLMGR process a

4. The APLMGR process selects an initiator, chooses an initiator subdevice name, and

sends an internal ADD SU request to the initiator.

5. The initiator adds the subdevice and responds to the APLMGR process.

6. The APLMGR returns the subdevice name to the FTAM API.

7. On behalf of the application, the FTAM API opens the initiator’s subdevice and

sends a message to request an association through that subdevice. This message

includes the local common name and/or OSI address if specified, and the (required)

remote common name and/or OSI address. If the FTM_INITIALIZE_REQ_ call

was made in nowait mode, the FTAM API returns to the application a connection

endpoint identifier (CEPI) identifying the association request, as described in the

Tandem OSI/FTAM Programming Guide.

8. The initiator sends a register request to the configured OSI manager process to

establish an ACSE association. The register request includes local and remote

common names (OSI/AS application names) and/or OSI addresses. If the

application did not specify a local common name and/or address, the initiator sends

its configured default.

Using This Item...

The APLMGR Process

Selects This MIB Entry... And Extracts This Information...

Internal initiator

name in the START

command

PROCESS OSI manager process name,

common name, and/or OSI address

(PSEL, SSEL, TSEL, and NSAP),

NAME (Guardian process name),

and other attributes