You can use the application requester, the application server, or both in a distributed environment. This section provides a checklist of the required tasks for implementing DRDA over SNA. For information on implementing DRDA over TCP/IP, refer to Chapter 15, Using TCP/IP with DB2 Server for VSE. For detailed information on DRDA, see the Distributed Relational Database Connectivity Guide.
The following tasks must be completed before a batch or online application requester can access a remote server via TCP/IP:
The following tasks must be completed before a CICS online application requester can access a remote DRDA application server via SNA:
Figure 119. Sample commands of the DFHCSDUP command to define a program
* Phase for SYSCCSIDS
DEFINE PROGRAM(ARISCCSD) GROUP(DB2710) LANGUAGE(ASSEMBLER)
* Phase for SYSSTRINGS
DEFINE PROGRAM(ARISSTRD) GROUP(DB2710) LANGUAGE(ASSEMBLER)
* Phase for SYSCHARSETS
DEFINE PROGRAM(ARISSCRD) GROUP(DB2710) LANGUAGE(ASSEMBLER)
Figure 120. Sample commands of the DFHCSDUP command to define a program
* Phase for Online Resource Adapter DRDA Router DEFINE PROGRAM(ARI0RTRM) GROUP(DB2710) LANGUAGE(ASSEMBLER) |
Several CICS definitions are required in order to use DRDA support on the VSE application server. See the following sections for more details.
All CICS transactions used for DRDA processing must be defined in the CICS DFHPCT table CSD. Transactions definitions must include entries for each Transaction Program Name (TPN) in the DBNAME Directory. The default entry is shown as the CAXE entry in the next figure. Additional APPC-to-XPPC exchange transactions can be added with different TRANS IDs, and, optionally, the TCLASS parameter to provide access control. The TCLASS parameter is used in conjunction with the DFHSIT CMXT parameter. The TCLASS parameter is not required for the default CAXE entry. The XTRANID parameter is not required for user-defined AXE transactions.
Transaction definitions must include definitions for DB2 Server for VSE DRDA2 administration routines. This includes the DAXP transaction, which sets parameters that are used when an AXE transaction subsequently autostarts DRDA2 support. This also includes the DAXT transaction, which is responsible for disabling DRDA2 support.
Use the sample entries in Table 31 as a guideline for making your transaction
definitions.
Table 31. DFHPCT Table Entries
| TRansaction | PROGram | TWasize | SPurge | TPurge |
|---|---|---|---|---|
| DRDA Server Support AXE Entries | ||||
| CAXE | ARICAXED | 0 | YES | YES |
| DRDA2 Parm Setting Entry | ||||
| DAXP | ARICDAXD | 0 | YES | YES |
| DRDA2 Disable TRUE Entry | ||||
| DAXT | ARICDAXD | 0 | YES | YES |
All phases that DRDA2 supports will be executed in the CICS partition and must be defined in the CICS DFHPPT table. Entries must be defined for:
Use the sample entries in Table 32 to make your definitions in the CICS System
Definition File.
Table 32. DFHPPT Table Entries
| Program | Description | Resident | Language |
|---|---|---|---|
| ARICDIRD | DBNAME Directory Services |
| ASSEMBLER |
| ARICAXED | APPC-XPCC Exchange (AXE) | YES | ASSEMBLER |
| ARICDAXD | DAXP and DAXT Program | YES | ASSEMBLER |
| ARICDRAD | DRDA2 (TRUE Exit) Support | ASSEMBLER | |
| ARICDR2 | DR2DFLT Control Block | ASSEMBLER | |
| ARICDEBD | DRDA2 Support Enabling Routine | ASSEMBLER |
In order for CICS/VSE to be accessible to the SNA network as an LU (logical unit of type 6.2), you must define the name of the LU using the APPLID parameter of the DFHSIT macro. The name specified must be the same as the name specified on the VTAM "APPL" definition when CICS was defined to VTAM. Also, if you are using user-defined AXE entries in the DFHPCT table and specifying the TCLASS parameter, the DFHSIT macro must include the CMXT parameter to provide access control.
Each remote DRDA system must be defined to CICS as remote LU 6.2 terminals by updating the CICS System Definitions as follows:
Refer to the CICS/VSE Intercommunication Guide, and the CICS/VSE Resource Definition (Online) for complete information on defining remote systems in CICS.
Entries in the CICS System Definition File can be made online using the transaction CEDA, or in a batch job running the DFHCSDUP utility program. The following are sample entries to be included with the batch utility program for DRDA transactions and programs.
DEFINE TRANSACTION(CAXE) GROUP(DB2710) PROGRAM(ARICAXED) *
TWASIZE(0) SPURGE(YES) TPURGE(YES)
DEFINE TRANSACTION(DAXP) GROUP(DB2710) PROGRAM(ARICDAXD) *
TWASIZE(0) SPURGE(YES) TPURGE(YES)
DEFINE TRANSACTION(DAXT) GROUP(DB2710) PROGRAM(ARICDAXD) *
TWASIZE(0) SPURGE(YES) TPURGE(YES)
DEFINE PROG(ARICDIRD) GROUP(DB2710) LANG(ASSEMBLER)
DEFINE PROG(ARICAXED) GROUP(DB2710) RES(YES) LANG(ASSEMBLER)
DEFINE PROG(ARICDAXD) GROUP(DB2710) RES(YES) LANG(ASSEMBLER)
DEFINE PROG(ARICDRAD) GROUP(DB2710) LANG(ASSEMBLER)
DEFINE PROG(ARICDR2) GROUP(DB2710) LANG(ASSEMBLER)
DEFINE PROG(ARICDEBD) GROUP(DB2710) LANG(ASSEMBLER)
Every user ID and password used by a remote DRDA requester must be defined to CICS in the DFHSNT table. Using the DFHSNT TYPE=ENTRY macro, define the user ID using the USERID parameter and define the password using the PASSWRD parameter.
CICS internal security and therefore the CICS Sign-On table (DFHSNT) has been withdrawn in CICS TS for VSE/ESA 2.4. Instead, any external security manager (ESM) may be used that conforms to the VSE/ESA RACROUTE interface. Alternatively, the basic form of external security manager (BSM) provided with VSE/ESA 2.4 may be used. The BSM provides sign-on and transaction attach security only.
When using an ESM, refer to the relevant documentation supplied with the ESM on defining DB2 for VSE user id(s) and operator data and transaction security.
If the BSM is used, DB2 for VSE userids in the DFHSNT and DB2 for VSE transactions must be defined using the VSE Interactive Interface (II).
As the CICS TS System Definition (CSD) file is not compatible with earlier versions of CICS (for example, CICS 2.3), a separate CSD file must be defined and all DB2 for VSE entries added using the DFHCSDUP utility provided with CICS TS.
For DB2 for VSE with CICS TS, the following System Initialization (DFHSIT) parameters are obsolete.
AMXT= EXEC= (command level is mandatory) EXITS= (the user-exit interface is always enabled) MONITOR= (replaced by new monitoring parameters)
Refer to the CICS/VSE Release Guide manual for a complete list of obsolete DFHSIT parameters.
For more information on installing DB2 for VSE V6.1 with CICS TS, refer to the following publications: