![]() |
![]() |
![]() |
![]() |
![]() |
The OracleTuxedo Mainframe Adapter for SNA system may be configured as either a local configuration or a distributed configuration running on a combination of two operating systems: UNIX, Windows, or a mainframe operating system. For a complete list of operating systems, refer to the Oracle Tuxedo Mainframe Adapter for SNA Release Notes. If the CRM is not run on a mainframe, it must run on the same platform as the SNA stack. For this version of OracleTuxedo Mainframe Adapter for SNA, HP-UX 11.23 on PA-RISC is the only non-mainframe platform for which the CRM is available.
• In one type of distributed configuration, the CRM is installed on the mainframe. If the CRM is installed on the mainframe, there is no need to install a third-party SNA stack. However, you must specify your Virtual Telecommunications Access Method (VTAM) in the OracleTuxedo Mainframe Adapter for SNA Gateway configuration file. Figure 2‑2 illustrates the distributed configuration architecture.
• Third-party stack configurations may be set up using stack-specific configuration utilities or by manually creating a configuration file with any text editor. Listing 2‑1 shows an example of an SNA node configuration file. The configuration file is divided into sections for various components of the configuration. Each section defines a component using parameters (or keywords) and values. Some of these keywords and values will affect how your OracleTuxedo Mainframe Adapter for SNA configuration is defined.Listing 2‑1 SNA Node Configuration FileThis definition is set up for use with an emulated IBM 3172 Interconnect Controller for connecting an APPN network node to another APPN node. Note that the definition is for an Ethernet LAN, and the SAPADDR specified must be the same as the LSap specified for the local link station.Listing 2‑2 XCA Major NodeThe switched network definition example in this section (Listing 2‑3) specifies the VTAM PU, representing the local link stations that expect to connect with the host machine. The IDBLK and IDNUM definitions are provided to support 3270 traffic and must be unique, as well as match the values specified in the local link definition.Listing 2‑3 SWNET Major NodeThe APPLID definition shown in Listing 2‑4 shows an example of a VTAM stack configuration to run the CRM on z/OS.Listing 2‑4 APPLID Definition (z/OS)For systems using ACCESSMETHOD(VTAM), you specify with AUTOCONNECT(YES) or (ALL) that sessions are to be established (that is, BIND is to be performed). Such sessions are set up during CICS initialization, or when you use the CEMT or EXEC CICS SET VTAM OPEN command to start communication with VTAM. If the connection cannot be made at these times when the remote system is unavailable, you must subsequently acquire the link by using the CEMT or EXEC CICS SET CONNECTION(sysid) INSERVICE ACQUIRED command, unless the remote system becomes available in the meantime and initiates communications.
For APPC connections with SINGLESESS(NO) specified, CICS tries to bind, on system start-up, the LU services manager sessions in mode group SNASVCMG.AUTOCONNECT(NO) CICS does not attempt to bind sessions when the connection is established.Specifies the network name that identifies the remote system. The name can be up to eight characters in length. The name follows assembler language rules. It must start with an alphabetic character. Here, NETNAME is the APPLID for CRM.Indicates either a CICS/ESA-supplied mode name, such as SMSNA100, or your own defined mode name. If another set of session definitions exists for the BEA connection, this mode name must be unique among all sets defined to the connection. The mode name corresponds to the VTAM LOGMODE name. A mode name defines characteristics such as pacing level and class of service. When transaction programs request a conversation, they usually do not specify which session to use for the conversation, but they can specify the mode name of the session. Each mode name is defined in the logon mode table, which describes the session parameters.Defines the total number of sessions in the set and the total number of winner sessions. The total number of winner sessions must include those for the host and the remote stack. The WINNER number plus the number of remote sessions should equal the SESSNBR.To install the resource definitions, put them on the host in a separate group. Use the CEDA INSTALL command.Before installing OracleTuxedo Mainframe Adapter for SNA software, review Table 2‑1 for an example of Windows or UNIX cross-platform definitions. Consult with your VTAM system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column.
Note: The DCL-based stack referred to in Table 2‑1 is the HP-UX SNAplus2 stack.Listing 2‑5 shows the corresponding OracleTuxedo Mainframe Adapter for SNA Gateway configuration file. Refer to the Oracle OracleTuxedo Mainframe Adapter for SNA User Guide for information about setting up the Gateway configuration.
Table 2‑1 Summary of DCL Definitions Mode Name
(e.g. SNA62) Control Point Name
CPNAME
(e.g. SPARC1) Local LU Name
(e.g. L0F0024A) CICS CONNECTION definition:
Example:
NETNAME(L0F0024A)
DCL-based Stack Configuration:
Example:
lu_name=L0F0024A
lu_alias=L0F0024A CICS LU Name
(e.g. CICSSYN) Terminal Identifier
(e.g. 05DF0024) DCL-based Stack Configuration:
Example:
Sna_tps
<404040...hex representation of 64 EBCDIC spaces...404040>
TYPE=QUEUED
TIMEOUT=-1
USERID=authorized_user_here
GROUP=authorized_group_here
LUALIAS=LOF0024A Listing 2‑5 Corresponding DMCONFIG FileBefore installing OracleTuxedo Mainframe Adapter for SNA software, review Table 2‑2 for an example of SNA definitions when the CRM runs on the z/OS platform. Consult with your system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column.Listing 2‑6 shows the corresponding OracleTuxedo Mainframe Adapter for SNA configuration file. Refer to the Oracle OracleTuxedo Mainframe Adapter for SNA User Guide for information about setting up the Gateway configuration.
Table 2‑2 Summary of z/OS SNA Definitions Local LU Name
(e.g. BEAAPPL1) CICS CONNECTION definition:
Example:
NETNAME(BEAAPPL1)
VTAM Configuration:
Example:
BEASNA VBUILD TYPE=APPL
BEAAPPL1 APPL ACB=BEAAPPL1,
APPC=YES,
PARSESS=YES
GWSNAX Configuration:
Example:
DM_SNASTACKS
LOCALLU="BEAAPPL1" Mode Name
(e.g. SNA62) CICS Sessions Definition:
Example:
MODENAME(SNA62)
GWSNAX Configuration:
Example:
DM_SNALINKS
MODENAME="SNA62"
VTAM Configuration (not required):
Example:
MODEENT=SNA62 CICS LU Name
(e.g. CICSSYN) Listing 2‑6 Corresponding DMCONFIG File