Your VTAM administrator and your host system administrator must configure VTAM and OS/390 (or MVS/ESA) to prepare DB2 Universal Database for OS/390 (or DB2 for MVS/ESA) to receive inbound connection requests from your DB2 Connect workstation.
This section provides:
For a summary of the example VTAM names used throughout this book, see Sample Network Element Names (VTAM). For TCP/IP names, see Configuring TCP/IP for DB2 Universal Database for OS/390.
 |
If you anticipate that DB2 for OS/390 will participate in a multisite
update transaction (two phase commit) then please refer to Enabling Multisite Updates (Two-Phase Commit). The additional steps required to set up multisite
updates are not documented here.
|
In order to prepare DB2 Universal Database for OS/390 or DB2 for MVS/ESA to receive connection requests from DB2 Connect, you must complete the following steps at your DB2 Universal Database for OS/390 host:
Step 1. | Verify that the following PTFs for OS/390 are installed:
|
Step 2. | Configure VTAM - see Configuring VTAM, or: |
Step 3. | Configure TCP/IP - see Configuring TCP/IP for DB2 Universal Database for OS/390, or: |
Step 4. | Configure DB2 Universal Database for OS/390 or DB2 for MVS/ESA - see Configuring DB2 Universal Database for OS/390, or Configuring DB2 for MVS/ESA.
|
To configure VTAM, your VTAM Administrator needs to determine the names and options to be used on your system. The following definitions must be provided to enable the DB2 Connect workstation to connect to the host:
The sample VTAM definitions are provided in the sections that follow. These samples use parameters that match the parameters used elsewhere in this book.
Figure 7 shows the sample VTAM definitions used to configure a host database server.
Figure 7. Network Element Names Used in the VTAM Examples
DB2 Connect Server:
- Network ID : SPIFNET
- Local Node Name : NYX1 (PU name)
- Local Node ID : 05D27509
- LU Name : SPIFNET.NYX1GW01 (the same LU is used
for DB2 Connect,
for DB2 Universal Database,
and for the SPM)
- LU Alias : NYX1GW01
HOST:
- Network ID : SPIFNET
- Node Name : NYX
- LU Name : SPIFNET.NYM2DB2
- LU Alias : NYM2DB2
- LAN Destination Address : 400009451902 (NCP TIC address)
MODE DEFINITION:
- Mode Name : IBMRDB
DB2 for MVS/ESA:
- Location : NEW_YORK3
SECURITY:
- Security Type : Program
- Authentication Type : DCS
|
In this scenario, both userid and password are checked only at the host. If you use Authentication SERVER, which is the default, then authentication will also take place at the DB2 Connect server.
Figure 8 shows the sample VTAM application major node definitions. In most cases, such a definition will already exist with a different LU name. Otherwise, this application major node must be defined, and DB2 Universal Database for OS/390 must be customized in order to use the LU name defined. This name is the Partner LU name required by DB2 Connect.
Figure 8. Sample VTAM APPL Definition for DB2 Universal Database for OS/390 or DB2 for MVS/ESA
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
DB2APPLS VBUILD TYPE=APPL
NYM2DB2 APPL APPC=YES, X
AUTH=(ACQ), X
AUTOSES=1, X
DLOGMOD=IBMRDB, X
DMINWNL=512, X
DMINWNR=512, X
DSESSLIM=2048, X
EAS=6000, X
MODETAB=RDBMODES, X
PARSESS=YES, X
PRTCT=SFLU, X
MODETAB=RDBMODES, X
SECACPT=ALREADYV, X
SRBEXIT=YES, X
VERIFY=NONE, X
VPACING=8
|
| Note: | Continuations must begin in column 16, with continuation marks in column 72. |
If your security policies allow it, it is recommended that you enable DYNPU and DYNLU in VTAM to allow any PU and LU access through VTAM. Contact your VTAM administrator for more information.
To enable a specific LU or PU, Figure 9 shows the sample VTAM switched major node definitions.
If you already use SNA applications on the DB2 Connect workstation, then a PU definition already exists. However, an independent LU definition might not. The independent LU definition required for DB2 Connect must have LOCADDR=0 specified.
Figure 9. Sample VTAM Switched Major Node Definition for DB2 Connect
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
SWITCHED MAJOR NODE DEFINITION FOR PU NYX1 and
INDEPENDENT LU NYX1GW01
LOC300 VBUILD TYPE=LOCAL
NYX1 ADDR=01,IDBLK=071,IDNUM=27509,ANS=CONT,DISCNT=NO, X
IRETRY=YES,ISTATUS=ACTIVE,MAXDATA=4302,MAXOUT=7, X
MAXPATH=1,PUTYPE=2,SECNET=NO,MODETAB=RDBMODES X
SSCPFM=USSSCS,PACING=0,VPACING=2
NYX1GW01 LOCADDR=000,MODETAB=RDBMODES,DLOGMODE=IBMRDB
OTHERLU LOCADDR=002
|
Figure 10 shows the sample VTAM logon mode table definition for the IBMRDB and SNASVCMG modes. Note that this example specifies a 4K RUSIZE, which may not be suitable for your environment (for example, if you are using Ethernet, which has a maximum Frame Size of 1536 bytes). Your VTAM Administrator should check these values and advise you which mode table entry name and RUSIZE to specify for DB2 Connect.
Figure 10. Sample VTAM Log Mode Definition for DB2 Connect
----+----1----+----2----+----3----+----4----+----5----+----6----+----7---
RDBMODES MODTAB
IBMRDB MODEENT LOGMODE=IBMRDB, DRDA DEFAULT MODE *
TYPE=0, NEGOTIABLE BIND *
PSNDPAC=X'01', PRIMARY SEND PACING COUNT *
SSNDPAC=X'01', SECONDARY SEND PACING COUNT *
SRCVPAC=X'00', SECONDARY RECEIVE PACING COUNT *
RUSIZES=X'8989', RUSIZES IN-4K OUT-4K *
FMPROF=X'13', LU6.2 FM PROFILE *
TSPROF=X'07', LU6.2 TS PROFILE *
PRIPROT=X'B0', LU6.2 PRIMARY PROTOCOLS *
SECPROT=X'B0', LU6.2 SECONDARY PROTOCOLS *
COMPROT=X'D0B1', LU6.2 COMMON PROTOCOLS *
PSERVIC=X'060200000000000000122F00' LU6.2 LU TYPE
SNASVCMG MODEENT LOGMODE=SNASVCMG, DRDA DEFAULT MODE *
PSNDPAC=X'00', PRIMARY SEND PACING COUNT *
SSNDPAC=X'02', SECONDARY SEND PACING COUNT *
SRCVPAC=X'00', SECONDARY RECEIVE PACING COUNT *
RUSIZES=X'8585', RUSIZES IN-1K OUT-1K *
FMPROF=X'13', LU6.2 FM PROFILE *
TSPROF=X'07', LU6.2 TS PROFILE *
PRIPROT=X'B0', LU6.2 PRIMARY PROTOCOLS *
SECPROT=X'B0', LU6.2 SECONDARY PROTOCOLS *
COMPROT=X'D0B1', LU6.2 COMMON PROTOCOLS *
PSERVIC=X'060200000000000000000300' LU6.2 LU TYPE
|
|
| You must define the SNASVCMG logon mode when using APPC. |
Before you can use DB2 Connect, your DB2 Universal Database for OS/390 Administrator must configure DB2 Universal Database for OS/390 to permit connections from DB2 Connect workstations. This section indicates the minimum updates required in order to permit a DB2 Connect client to make a connection to the DB2 Universal Database for OS/390 database server. For more detailed examples, refer to the Connectivity Supplement, and the DB2 for OS/390 Installation Reference.
The following tables need to be updated, depending on the type of connections you are using (SNA or TCP/IP):
The sections that follow contain examples of commands to update these tables for DB2 Universal Database for OS/390. Work with your DB2 Administrator to determine the updates required for your DB2 Universal Database for OS/390 system. For more information on the DB2 Universal Database for OS/390 Communications Database tables, refer to the DB2 Universal Database for OS/390 SQL Reference.
To permit database connection requests to be accepted from any incoming DB2 Connect LU, just insert a blank row. Use an SQL similar to the following:
INSERT INTO SYSIBM.LUNAMES (LUNAME) VALUES (' ')
Alternatively, if you want to restrict access by LU name, you can use an SQL command similar to the following to update this table:
INSERT INTO SYSIBM.LUNAMES (LUNAME,
SECURITY_OUT,
ENCRYPTPSWDS,
USERNAMES)
VALUES('NYX1GW01','P','N','O');
Result:
COLUMN EXAMPLE REMARK ====== ======= ====== LUNAME NYX1GW01 Name of the DB2 Connect LU SECURITY_OUT P ENCRYPTPSWDS N USERNAMES O
If you want to permit inbound database connection requests for TCP/IP nodes, you can use an SQL command such as the following to update this table:
INSERT INTO SYSIBM.IPNAMES (LINKNAME) VALUES(' ')
Before you can use the DB2 Connect connection, your DB2 for MVS/ESA Administrator must configure DB2 for MVS/ESA to permit connections from the DB2 Connect workstation. To configure DB2 for MVS/ESA, the following tables need to be updated:
The sections that follow contain examples of commands to update these tables. Work with your DB2 Administrator to determine the options required for your DB2 for MVS/ESA system.
If you want to use secondary authorization IDs, you can use the following SQL command to update this table:
INSERT INTO SYSIBM.SYSUSERNAMES VALUES('I','ADBUSER','NYX1GW01',' ',' ');
Result:
COLUMN EXAMPLE REMARK ====== ======= ====== Type I Authid ADBUSER LU Name NYX1GW01 Name of the DB2 Connect LU NewAuthID (blank) Password (blank)
USERNAME types are: O (outbound translation), I (inbound translation), B (both inbound and outbound) and blank (no authorization ids are translated, and no passwords are sent to the server).
If you want to restrict access by LU name, you can use an SQL command similar to the following to update this table:
INSERT INTO SYSIBM.SYSLUNAMES VALUES('NYX1GW01','IBMRDB','A','N',' ','I');
Result:
COLUMN EXAMPLE REMARK ====== ======= ====== LUNAME NYX1GW01 Name of the DB2 Connect LU SYSMODENAME IBMRDB USERSECURITY A ENCRYPTPSWDS N MODESELECT USERNAMES I
Alternatively, just insert a blank row, and this will allow any incoming DB2 Connect LUs to be accepted.
You can use an SQL command such as the following to update this table:
INSERT INTO SYSIBM.SYSLUMODES VALUES ('NYX1 ', 'IBMRDB', 150, 'Y');
where:
This section describes how to configure TCP/IP communications between your DB2 Connect workstation and DB2 Universal Database for OS/390 Version 5.1 or later. It assumes that:
OS/390 R3+ is the minimum operating system level required for TCP/IP support. OS/390 V2R5+ is the recommended operating system level, and the best performer.
The following informational APARS for DB2 for OS/390 are regularly updated with information about PTFs to install for various OS/390 components, particularly TCP/IP for OS/390. If you use TCP/IP connectivity with DB2 for OS/390 it is extremely important that you review and apply PTFs and APAR fixes described in the following DB2 for OS/390 information APARs:
The following fixes are recommended for DB2 for OS/390:
Before you can use DB2 Connect over a TCP/IP connection, you must collect information about both the host database server and the DB2 Connect workstation. For each host server that you are connecting to via TCP/IP, you must have the following information:
You may use a Domain Name Server to avoid maintaining this file on multiple systems.
Refer to your local network administrator and your DB2 for OS/390 administrator for help getting this information. Use one copy of the example work sheet, Table 7, to plan each TCP/IP connection between DB2 Connect and a host database server.
Table 7. Example Worksheet for Planning TCP/IP Connections to DB2 Universal Database for OS/390
| Ref. | Description | Sample Value | Your Value |
|---|---|---|---|
| User Information | |||
| (TCP-1) | User Name | A.D.B.User |
|
| (TCP-2) | Contact Info | (123)-456-7890 |
|
| (TCP-5) | User ID | ADBUSER |
|
| (TCP-6) | Database Type | db2390 |
|
| (TCP-7) | Connection type (must be TCPIP). | TCPIP | TCPIP |
| Network Elements at the Host | |||
| (TCP-8) | Host name | MVSHOST |
|
| (TCP-9) | Host IP address | 9.21.152.100 |
|
| (TCP-10) | Service name | db2inst1c |
|
| (TCP-11) | Port number | 446 |
|
| (TCP-12) | LOCATION NAME | NEW_YORK3 |
|
| (TCP-13) | User ID |
|
|
| (TCP-14) | Password |
|
|
| Network Elements at the DB2 Connect Workstation | |||
| (TCP-18) | Host name | mcook02 |
|
| (TCP-19) | IP address | 9.21.27.179 |
|
| (TCP-20) | Service name | db2inst1c |
|
| (TCP-21) | Port number | 446 |
|
| DB2 Directory Entries (at the DB2 Connect workstation) | |||
| (TCP-30) | Node name | MVSIPNOD |
|
| (TCP-31) | Database name | nyc3 |
|
| (TCP-32) | Database alias | mvsipdb1 |
|
| (TCP-33) | DCS database name | nyc3 |
|
Notes:
TSO NETSTAT HOME
Use the manual steps in this section to complete the configuration and make the connection.
Complete the Worksheet: Complete a copy of the example worksheet for each TCP/IP host:
Note that some additional planning considerations may apply, for example if you are using DCE. See the DB2 Connect User's Guide.
Update the DB2 Universal Database for OS/390 Host: At your OS/390 host:
ping remote_host_name -p port_number
Update the DB2 Connect Configuration: At a command line prompt, issue the following command to update the Database Manager Configuration:
db2 update dbm config using TM_DATABASE 1st_conn
where TM_DATABASE can have one of the following settings:
Update the DB2 Connect Directories:
db2 catalog tcpip node MVSIPNOD remote MVSHOST server db2inst1cwhere:
db2 catalog dcs database NYC3 as NEW_YORK3 db2 catalog database NYC3 as MVSIPDB1 at node MVSIPNOD authentication dcswhere:
CONNECT and BIND: Finally, connect to the target host server and bind the utilities and applications to the server using commands similar to the following in the command line processor:
connect to MVSIPDB1 user USERID using PASSWORD
bind path/bnd/@ddcsmvs.lst blocking all
sqlerror continue blocking all grant public
disconnect all
where path corresponds to the DB2PATH registry value.
These commands are described in detail in the Command Reference.