gtpa3m0gApplication Requester User's Guide

DB2 Requirements

To connect the TPF system with a DB2 system:

The following considerations pertain solely to the DB2 system running on MVS.

The DB2 system Installation Panel DSNTIPF allows you to set the coded character set identifier (CCSID) for the DB2 subsystem. This must match the CCSID in the TPF system SDD entry for this database. For detailed information about the DB2 Installation Panels DSNTIPR, DSNTIPE, and DSNTIPF, see the DB2 Administration Guide. The location name (RDB name), the LU name, and the CCSID specified on these panels are the same values that must be used when issuing the ZSQLD command to define this database to TPF. See the TPF Operations and Commands for more information about ZSQLD command.

Under the DB2 system, the DB2 Distributed Data Facility (DDF) uses the system installation parameters to connect DB2 to VTAM. The DB2 Installation Panel DSNTIPR allows you to enter the required DDF BSDS information that describes the connection parameters between the DB2 system and VTAM, such as the location name (RDB name), LU name, and password. The DB2 Installation Panel DSNTIPE allows you to set the number of maximum number of remote database access threads that can be allocated concurrently. There must be one thread available for each LU 6.2 session from the TPF system you plan on using.

DDF connects to VTAM and passes the LU name and optional password to VTAM. VTAM verifies the LU name and password, if specified, with what was coded on the VTAM APPL statement. See VTAM Requirements for LU 6.2 for more information about the VTAM APPL definition.

The communications database is made up of five interrelated tables and is an important source of information about the system. To run TPFAR with a DB2 system, minimum changes are required in two tables, the SYSIBM.SYSLUNAMES (LU 6.2 only) and the SYSIBM.SYSUSERNAMES tables. These changes cause DB2 to bypass the verifying of the ID sent on the LU 6.2 ALLOCATE verb with RACF. For TCP/IP, USER.ID security will be used to verify the TPFAR client. See the DB2 Administration Guide for more information about these tables.

Because the communications database consists of five interrelated tables, the information that you specify in one table might have to be specified in the other tables. See the Distributed Relational Database Connectivity Guide for detailed information about the communications database.

The system administrator also needs to grant access for the TPFAR application's AUTHID. TPFAR uses the TPF system complex name found in CTKI as its application AUTHID. Depending upon the SQL commands that are issued from the TPF system, the AUTHID needs sufficient privileges to perform the commands. See the DB2 SQL Reference guide for more information about the SQL GRANT command necessary to set up the access.