4.1.2.6.1 BEACONN File: Connection definition

The BEACONN file includes a sample connection definition.

Note: The sample connection definition achieves the minimum requirements for a connection over which the installation verification can be executed. Do not rely on it to provide optimal performance. Consult the CICS/ESA Resource Definition Guide for information about adding options not included in the sample.

The name of the sample connection definition is BEA, which is located under the installation group name BEACONN. It looks like this:

Listing Sample Connection Definition in BEACONN File

DEFINE CONNECTION(BEA)     GROUP(BEACONN)
       DE(TUXEDO MAINFRAME ADAPTER FOR SNA EXAMPLE RDO CONNECTION)
       ACCESSMETHOD(VTAM)  PROTOCOL(APPC)
       NETNAME(**LOCALLU**)
       ATTACHSEC(LOCAL)    AUTOCONNECT(NO)

**LOCALLU** must be changed to the LU name of the SNA stack as known by VTAM. The ATTACHSEC option indicates the level of attach-time user security required for the connection. LOCAL is the simplest security. The authorization of the user is taken to be that of the link itself, relying on the authorization validation provided by the remote security utility. AUTOCONNECT indicates when the connection is acquired. NO is required. This entry means that CICS does not attempt to bind sessions when the connection is established by the stack.

Note:

The Oracle Tuxedo Mainframe Adapter for SNA software must acquire the connection and negotiate the bind when the Oracle Tuxedo Mainframe Adapter for SNA software starts up.

Install the sample connection definition by putting it on the host in a separate group that does not contain existing connection. For example, use the CEDA INSTALL command:

CEDA INSTALL GROUP(BEACONN)