Post-Installation

About this task

The following steps may be run using typical DB2 for z/OS interfaces; e.g. SPUFI, DB2 Connect or batch DB2. Supply site-appropriate values to replace those in angle brackets (e.g. <storage_group>):

Procedure

Create the necessary database Storage Group.

CREATE STOGROUP <storage_group> VOLUMES (<volumes>)
  VCAT <catalog_name>;

Create the Cúram application database - the database can be configured forEBCDIC,ASCII, orUNICODE mode, this can be done when creating the database using theCCSID keyword. ForASCII orUNICODE databases see Bootstrap properties for information about setting the required property curam.db.zos.encoding.
```
CREATE DATABASE CURAM BUFFERPOOL BP0 INDEXBP BP0
  STOGROUP <storage_group> CCSID <EBCDIC, ASCII or UNICODE>;
```
Ensure that the DSNZPARM RRULOCK parameter, of the DSN6SPRM macro, is set to YES.
An environment variable called DB2JCC_LICENSE_CISUZ_JAR must be created in your z/OS UNIX System Services shell environment that points to the installed DB2 for z/OS license jar file used for connectivity to DB2 for z/OS servers on z/OS. This is normally named db2jcc_license_cisuz.jar and is provided as part of your DB2 for z/OS installation.

Results

Note:

Settings in the DSNZPARM parameter module may need adjustment for compatibility with Cúram. One parameter of particular note is the idle transaction timeout threshold (IDTHTOIN). It may need to be increased for certain CER initialization-related activities following a database build, such as the prepare.application.data Ant target as this can run longer than is typically encountered with DB2 for z/OS applications. The time these activities might take and whether they timeout depends on a number of factors, but the symptoms of needing this change may be manifested with the client shell receiving an error similar to:

[java] infrastructure:RUN_ID_RUNTIME: A runtime exception occurred:
[jcc][t4][10335][10366][3.63.131] Invalid operation: Connection is closed.
ERRORCODE=-4470, SQLSTATE=08003.

Also, in the the z/OS SYSLOG a DSNL027I timeout message with a reason code of 00D3003B may be produced by DB2 in the same timeframe. The relevant DB2 for z/OS documentation provides information on changing the idle thread timeout value.