Quick Beginnings

Planning to Configure Your DB2 Connect for Solaris System

Refer to the example worksheet (Table 20):

For an OS/390, MVS, VM, or VSE connection, do the following:

For XID node ID, use a combination of the IDBLK and IDNUM values ((22) and (23)). For example, X'07127509'.
For Network name, use the NETID ((18)).
For Control point name, use the PU name ((19)).
Leave the token ring (DLC) profile name ((17)) blank for now.
For Mode name, use the MODEENT ((24)).
For Local LU name, use (20).
For Local LU alias, choose an alias ((21)). This can be the same as the LU name or different. Usually we recommend this be the same as the LU name itself.
Repeat steps 6 and 7 above for any additional LUs that you may need to define.

For an OS/400 connection, do the following:

For XID node ID, write an asterisk (*). This means that you will use the default.
For Network name, use the host network name ((8)).
For the host mode name, use (13).
Leave the other items blank for now.

Planning for Each Server Connection

For each DRDA server that you are connecting to, fill in a copy of the worksheet (Table 20) as follows:

For DLC profile name ((17)), choose a suitable value.
For Remote link address, use (16).
For Symbolic destination name ((25)), choose a suitable value.
For the host partner CP name, use (11). For OS/390, MVS, VM, or VSE it is the host System Services Control Point (SSCP) name. For an OS/400 it is the local control point name (see "Preparing DB2 for AS/400 for DB2 Connect").
For Partner LU name for OS/390, MVS, VM, or VSE, use (9) (VTAM APPL name) from the worksheet.
You will also need to provide the network name ((8)) for the remote node (for example, SPIFNET). Usually this is the same as the network name at the DB2 Connect workstation. Together, these make up the fully-qualified partner LU name (SPIFNET.NYM2DB2).
For OS/400, use the local CP name of the AS/400.
For Remote transaction program ((26)), copy the value from the worksheet. The default is X'07F6C4C2' for OS/390, MVS, and OS/400, and the RDB_NAME for VM and VSE. We recommend that you use DB2DRDA for OS/390 or MVS.
For Target database name ((12)), this is the LOCATION NAME value for OS/390 or MVS, the RDB_NAME for VM or VSE, or a relational database name for OS/400.

Planning for Inbound APPC Client Connections

In addition to setting up an SNA connection between DB2 Connect and your DRDA host AR, you may also want to support inbound APPC connections from one or more clients, either workstations running DB2 Universal Database Client Application Enabler, or a DRDA host acting as an AR. If so, please see the additional definitions that may also be required in the SNA Server configuration file in "Optional sections".

Configuring SunLink SNA for Solaris

You can use vi or your favorite editor to create the configuration files.

CPIC Side File

This file must be placed in the application's path for a standalone DB2 Connect for Solaris system. However, if DB2 Connect for Solaris is being used as a gateway, in order for DB2 agents to be able to access it, the file should be in either:

$HOME/sqllib/adm or
$HOME/sqllib/bin

Note:

The name of the CPIC side file must be the same as the Symbolic destination name specified in the DB2 node directory on the DB2 Connect for Solaris system.

Sample CPIC side file

The file name must be the same as the Symbolic destination name specified in the DB2 node directory for the server.

# CPIC Side File information
#
PTNR_LU_NAME=NYM2DB2
MODE_NAME=IBMRDB
TP_NAME= x'07F6C4C2'
SECURITY=PROGRAM

SNA Server Configuration File

This file is called sunpu2.config, and it must be placed in /opt/SUNWpu21, or the directory where SunLink SNA PU 2.1 Server is installed. The example shown in Figure 17 matches the scenario in DB2 Connect Enterprise Edition Quick BeginningsFigure 16.

Figure 17. Sample Solaris PU 2.1 SNA Server Configuration File

// SunLink SunLU6.2/SunPU2.1 SNA Server Sample Configuration // Token Ring Peer-to-Peer System A @(#)sunlu62.a.tr // // The physical connection is a Token Ring interface adapter. CP NAME=NYX1 // Local name (8 char max) NQ_CP_NAME=SPIFNET.NYX11 // Network Qualified Name ; TRLINE NAME=MAC1 // SunLink specific name SOURCE_ADDRESS=x'400011527509' // sysA_mac_addr for Sun machine ; DLC NAME=HOSTLINK // User defined name (8 char max) LINK_NAME=MAC1 // Line name this station is on LCLLSAP=x'04' // Local Link Service Access Point RMTLSAP=x'04' // Remove Link Service Access Point RMTMACADDR=x'400009451902' // sysB_mac_addr TERMID=x'07127509' // XID negotiation ; LU NAME=NYX1GW01 // Local name (8 char max) NQ_LU_NAME=SPIFNET.NYX1GW01 // Network Qualified Name SESS_LMT=50 // Max LU sessions LUTYPE=6.2 ; PTNR_LU NAME=NYM2DB2 // Partner LU name(8 char max) LOC_LU_NAME=NYX1GW01 // Associated Local LU NQ_LU_NAME=SPIFNET.NYM2DB2 // Network Qualified Name ; MODE NAME=IBMRDB // Mode Name (8 char max) DLC_NAME=HOSTLINK // Associated DLC PTNR_LU_NAME=NYM2DB2NYX1GW01 // Associated Partner LU LCL_MAX_SESS_LMT=30 // Max Session Limit MIN_CW_SESS=15 // Min Conwinners MIN_CL_SESS=15 // Min Conlosers ;

Optional sections

The following additional sections would also be required in the configuration file in order to support the inbound APPC client support.

Figure 18. Additional Sun SNA Server configuration sections for inbound APPC client

// This section adds DLC for the inbound APPC client NYX2 DLC NAME=NYX2, // User defined name (8 char max) LINK_NAME=MAC1, // Line name this station is on LCLLSAP=x'04', // Local Link Service Access Point RMTLSAP=x'04', // Remove Link Service Access Point RMTMACADDR=x'400011528901', // sysB_mac_addr TERMID=x'05d27510', // IDNUM and IDBLK = XID MAXDATA=4096, ACTIVITY_TIMEOUT=0, RETRIES=20, REPLY_TIMEOUT=20, RESPONSE_TIMEOUT=20, ACTPU_SUPPRESS=yes ; // This section defines the partner LU NYX2 PTNR_LU NAME=NYX2, // Partner LU name(8 char max) LOC_LU_NAME=NYX2, // Associated Local LU NQ_LU_NAME=SPIFNET.NYX2 // Network Qualified Name SEC_ACCEPT=ALREADY_VERIFIED // Accept client as already verified ; // This section adds the TP name NYSERVER // and associates it with the local LU NYX1GW01 TP TP_NAME=NYSERVER, // TP Name LOC_LU_NAME=NYX1GW01, // Associated Local LU CONV_TYPE=BASIC, // Conversation Type ; // SECURITY LOC_LU_NAME=NYX1GW01, // Local LU Alias USER_ID=USERID, // User id PASSWORD=PASSWORD, // Password (since UNIX_SEC=NO) ; ;

Additional Steps Required to Enable Inbound APPC Clients

You need to:

Create any additional APPC partner LU and link profiles that may be required.
Ensure the inbound clients are also properly configured.
Use SNA session control functions, without using DB2 Connect, in order to validate that all the APPC sessions that you need to establish can be.
Update the database manager configuration on the DB2 Connect workstation by entering the following command in the command line processor:
```
   update dbm cfg using tpname NYSERVER
```
Add the string APPC to the DB2COMM environment variable.
Stop and restart DB2 in order to activate the APPC listener.

Starting the SunLink SNA Subsystem

Perform the following steps, in sequence:

Logon as root.
Change to the SunLink directory, usually;
```
   cd /opt/SUNWpu21
```

Set up environment variables for FlexLM licensing, for example:

   export LD_LIBRARY_PATH=/usr/openwin/lib:/usr/lib
   export LM_LICENSE_FILE=/etc/opt/licenses/licenses_combined

Refer to the SunLink documentation for full details.

Ensure you have created the CPIC side file as described in "CPIC Side File", and that it is in the right directory.
Ensure you have created the SNA server configuration file in the /opt/SUNWpu21 directory, as shown in Figure 17.
Use the sunop utility to check the status of SunLink SNA if it is already started.
Check to see if the PU and/or DLC status is connected. Refer to the SunLink documentation for details of the sunop utility.
Stop SunLink if it is active. For example, enter:
```
   kill -9 sunpu2.pid
   kill -9 sunlu2.pid
```
Start SunLink using the following command:
```
   sunpu2.1
```

You can use sunop to check the status of links.

Restart the Database Manager

Stop the database manager, if it is running:
```
   db2stop
```
Ensure that the db2comm environment variable setting includes APPC. Enter:
```
  db2set -lr
```
If APPC does not appear as a value for db2comm, you need to add it. One way to do this would be to enter a command similar to this:
```
  db2set db2comm=tcpip,appc,ipxspx -g
```
(You should remove any protocols you do not use from that command. There are several different options available with the db2set command. For details, see Chapter 39. "Controlling Your DB2 Environment".)
Start the database manager:
```
   db2start
```

Completing the Configuration

When you have configured your system and all of the server connections, do the following:

Start and stop the SunLINK subsystem (see "Starting the SunLink SNA Subsystem").
Update the DB2 node directory, system database directory, and DCS directory.
To do this, you will need to know the symbolic destination name ((25)) and the target database name ((12)) from the worksheet.
Enter the following commands in the command line processor:
```
   catalog appc node db2node remote sym_dest_name security program
```
Note that the sym_dest_name value must be the same name in the same case as the name of the CPIC side file (cpicmvs in the examples in this chapter).
```
   db2 catalog dcs database db2db as new_york3
   db2 catalog db db2db as nyc3 at node db2node authentication dcs
```
In order to run any application, you must set the following environment variables:

APPC_GATEWAY
Name of the DB2 for Solaris server (usually the TCP/IP hostname).
APPC_LOCAL_LU
Name of the local LU name provided in the SNA configuration file (usually sunpu2.config).

For a DB2 Connect for Solaris server, export these on the DB2 Connect machine before issuing db2start.
Connect to the DRDA Server and bind the utilities and applications to the DRDA server using commands similar to the following in the command line processor:
```
   connect to dbalias  user userid using password
   bind path@ddcsmvs.lst blocking all
        sqlerror continue messages mvs.msg grant public
   connect reset
```
For further information please refer to the online DB2 Connect User's Guide.

To install remote clients, see Chapter 26. "Installing DB2 Clients".

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]