11.3 Step 3: Configuring and Deploying TMA SNA

  1. Install Oracle TMA for SNA Gateway on open system and Oracle TMA for SNA CRM on z/OS. For more information, refer to Oracle Tuxedo Mainframe Adapter for SNA Overview.
  2. Add one line SNAX:::: to your $TUXDIR/udataobj/DMTYPE.
  3. In Tuxedo UBBCONFIG, configure the following:
    • Add two GROUP entries and three SERVER entries as shown in the following Listing.

      Listing UBBCONFIG Configuration

      *GROUPS
      
      DMGRP    GRPNO=**NN**   LMID=**LMNAME**
      GWGRP1   GRPNO=**MM**   LMID=**LMNAME**
      
      *SERVERS
      DMADM       SRVID=**nnn**       SRVGRP=DMGRP
      GWADM       SRVGRP=GWGRP1 SRVID=**nnn** 
                  REPLYQ=N RESTART=Y 
      GWSNAX      SRVGRP=GWGRP1 SRVID=**nnn** 
                  RQADDR="**SNADOM**" REPLYQ=N RESTART=Y
                CLOPT="-A -- -b"

      Note:

      • GRPNO parameters are numeric and must be unique for all groups defined in ubbconfig. LMNAME parameter for the LMID must be one of the LMIDs defined in the *MACHINES section of the ubbconfig. In MP configuration with multiple LMIDs, it is recommended to define multiple groups — one per LMID — for the GWSNAX servers to be replicated across all machines in the cluster.
      • **nnn** is the Server ID number that must be unique for each server in the group. RESTART=Y is recommended; -b in CLOPT is recommended if there is a router or firewall between GWSNAX and CRM on z/OS periodically breaking the connection. This option activates a heartbeat mode that can help maintain the connectivity.

        After updating the ubbconfig, ensure:

        • the Tuxedo domain is not running (otherwise run tmshutdown), and run tmloadcf to compile the updated ubbconfig;
        • BDMCONFIG environment variable points to the latest compiled bdmconfig file;
        • ULOG establishes connections with the CRM after running tmboot to bring up Tuxedo domain with GWSNAX;
        • logs on the CRM side are able to establish connections with the remote CICS region.
        For more information, see Configuring and Starting the System.
    • (Optional) Enable service level security.

      Listing Enabling service level security in UBBCONFIG

      *RESOURCES 
      SECURITY          USER_AUTH
      *SERVERS
      AUTHSVR           SRVGRP=GROUP0 SRVID=2 CLOPT="-A"
    • Add ARTTCPL ARTADM ARTCNX ARTTSQ ARTSTRN ARTDPL to the *SERVERS section.
  4. Configure DMCONFIG:

    Tuxedo dmconfig file is used to define the CRM parameters and services accessed through the TMA SNA connection. Some of these parameters are used locally and others are sent by GWSNAX to CRM on z/OS when the connection is established to dynamically configure the connection attributes. Some of the configuration parameters we have specified are used below in the DM_SNASTACKS, DM_SNALINKS, and DM_REMOTE_SERVICES sections of the dmconfig.

    If you are building a new dmconfig, the following listing may need to be adjusted to your mainframe connection. If it already exists for the same CRM connection, you only need to merge the relevant entries from the DM_SNASTACKS, DM_SNALINKS, and DM_REMOTE_SERVICES sections into the existing configuration. It is shown in bold typeface where you need to change according to your environment in the following listing:

    Listing Sample DMCONFIG Configuration

    *DM_LOCAL_DOMAINS 
    simpsnad 
            GWGRP=GWGRP1 // same as GWSNAX group in ubbconfig 
            TYPE=SNAX 
            DOMAINID="simpsnad"
            DMTLOGDEV=**/tuxedo/path/to/DMTLOG** //GWSNAX domain TLOG file name
    *DM_REMOTE_DOMAINS 
    MVSDOM TYPE=SNAX 
    DOMAINID="MVSDOM" 
    *DM_SNACRM
    simpcrm SNACRMADDR="//host.name:NNNN" //host:port of CRM
            NWDEVICE="/dev/tcp" 
            LDOM="simpsnad" 
    *DM_SNASTACKS 
    stack1
            SNACRM="simpcrm" 
            STACKTYPE="VT210" 
            LOCALLU="**LUNAME**"       // NETNAME in VTAM CONNECTION definition  
            LTPNAME="*"
            STACKPARMS="host.name"    //same as CRM host name
    *DM_SNALINKS 
    link1   STACKREF="stack1"        //Reference to DM_SNASTACKS entry name 
            RDOM="MVSDOM"           //Reference to DOMAINID in DM_REMOTE_DOMAINS 
            LSYSID="OT12"           //VTAM connection name
            RSYSID="**CICX**" 
            RLUNAME="**CICSAPPL**"  //CICS APPLID of CICS region
            MODENAME="**SNANAME**" //MODE NAME in SESSION definition.
            SECURITY="LOCAL"      //if you want to use security features, refer 
    to documentation   
            STARTTYPE="COLD"
            MAXSESS=20
            MINWIN=20 
            MAXSYNCLVL=2 
            *DM_LOCAL_SERVICES 
            *DM_REMOTE_SERVICES
            SVSN_**PROGY** AUTOTRAN=N 
            LDOM="simpsnad"         //Reference to DOMAINID in DM_LOCAL_DOMAINS 
            RDOM=MVSDOM             //Reference to DOMAINID in DM_REMOTE_DOMAINS     
            CONV=N 
            RNAME="**PROGY**"      //Reference to program name defined in remote 
    CICS region      
  5. Use tmloadcf to load UBBCONFIG.

    The application password must match that of ARTCICS.

  6. Use dmloadcf to load DMCONFIG.
  7. Add Tuxedo user using Tuxedo-provided tools:

    tpgrpadd tuxgrp tpusradd -g tuxgrp tuxusr

    Replace tuxgrp and tuxusr with your own and three files — tpgrp, tpusr, and tpacl — will be generated.
  8. Add user mapping in dmadmin:
    addusr -d SNAXDOM -R MVSDOM -u “mfusr” -w
    addumap -d SNAXDOM -R MVSDOM -p “tuxusr” -u “mfusr”
  9. If the service level security is enabled, logon CICS with tuxusr/password.