Below you will find the components with which you can configure the NDZ according to your specifications.
NDZ server started task streamline and executes the Db2 requests remotely using JDBC and SQLJ drivers. You can find more information about sample job to create NDZ started task in the NDZ installation here, Installing Natural for Db2 for zIIP . For detailed information about NDZ server started task parameters, refer to section NDZ started task procedure.
You specify Natural for Db2 for zIIP(NDZ) parameters in the ndz.properties present in /etc directory to configure NDZ. These parameters control the properties of NDZ started task and the client related configurations of NDZ. For detailed information about the NDZ parameters refer to the following section, NDZ configuration file (ndz.properties).
<NDZ-directory>/bin/setenv.sh script is used in the other scripts and batch jobs for static preparation to set the required environment variables. NDZ builds the environment variables like CLASS_PATH and LIB_PATH based on the parameters supplied by you. For detailed information about the parameters to specify in the setenv.sh script, refer to the section NDZ USS environment configuration file (setenv.sh).
Natural for Db2 for zIIP (NDZ) requires Db2 related information to connect to Db2 and modify Db2, JDBC and SQLJ driver properties. You can add these parameters in db2.properties. To know more about parameters required for Db2 configuration, refer to section, Db2 configuration file (db2.properties). Other than the parameters mentioned in the section, you can also specify JDBC and SQLJ properties in the Db2 configuration file.
Natural for Db2 for zIIP provides a password encryption mechanism to safely encrypt your password using encryption keys.
You need to generate an encryption key, and this key is used to encrypt the password. You can generate the key and encrypt the password using the script <NDZ home directory>/bin/ndz-db2-pass.sh.
Execute the following script and enter the Db2 connection password when prompted:
<NDZ home directory>/bin/ndz-db2-pass.sh
Options:
-g To generate the key file.
Use the option –g when you generate the key file or change the
existing encryption key.
Example:
ndz-db2-pass.sh -g
This option -g should be used when you execute the script for
the first time to generate an encryption key file.
However, if you want to change the password without changing the key file, execute the
script without option -g.
Example:
ndz-db2-pass.sh
Note:
If your Db2 connection password is encrypted, the password parameter in the
db2.properties will be ignored.
If your Db2 connection password is not encrypted, you will receive a warning
message when you start the NDZ server.
Message:
WARNING - Db2 encrypted password is not available at <NDZ home directory/var>.
Using password from db2.properties
You specify the following parameters for the NDZ started task procedure.
| Parameter name | Mandatory | Description |
|---|---|---|
PATH |
Y | The home directory where the NDZ files were installed in Unix System Services (USS). |
PORT |
Y | The number of the socket port used internally by NDZ. Accepted values are 0-65535. |
Example:
//NDZ11 EXEC PGM=NDZNUC11,REGION=0M,
//PARM=('PATH=/u/nat/ndz/dev/ndz11','PORT=4932')
You specify the following parameters for Natural for Db2 for zIIP(NDZ) to connect to Db2 and to perform SQL operations.
| Parameter name | Mandatory | Description |
|---|---|---|
| user | Y | Userid to connect to Db2. Note that the user should have required access on Db2 to perform required SQL operations. This is a mandatory parameter. |
| password | Y |
Password for the Db2 user mentioned above. Note that you can encrypt the password using NDZ Db2 password encryption capability, be aware that this is the recommended method to store your password. If you do not have an encrypted password, you can mention the password here. However, it is recommended to encrypt your password using NDZ Db2 password encryption. |
| databaseName | Y | Db2 database location name to connect to the specific Db2 system. Example – DAEFDB2D. This is a mandatory parameter. |
| serverName | Y | Fully qualified domain address of the z/OS system you need to connect. This is a mandatory parameter. |
| portNumber | Y | TCP/IP port number that identifies the specific Db2 subsystem. This is a mandatory parameter. |
You can also set the IBM JDBC and SQLJ properties by specifying the properties in db2.properties file. Refer to ‘Application Programming Guide and Reference for Java’ related to different JDBC and SQLJ properties.
You specify the following parameters to configure the NDZ server instance.
| Parameter name | Mandatory | Description |
|---|---|---|
| java.home | Y | The Java JDK installation directory. |
| db2.home | Y | The Db2 installation directory which contains licenses, JDBC and SQLJ drivers. |
| ndz.maxClients | Y | The maximum number of clients that can connect simultaneously to NDZ server to execute Db2 requests. Accepted values are 1-999. |
| ndz.initDb2Connection | Y | Number of initial connections to Db2. |
| ndz.bufferLentgh | Length of the client buffer in MB. Accepted values are 1-5000. | |
| ndz.staticPath | Y | Path(s) for the static profiles. During the static preparation, serialized profiles are generated in the directory mentioned in this parameter. The profiles in the static path are used during the runtime to execute the SQL statements statically. |
| ndz.automaticProfileReload | N | Specifies if static profiles cache will be reloaded when changes occur in the directory specified in the ndz.staticPath. Possible values are true/false. The default value is false. When it is set to true, there is an additional CPU consumption to monitor the directory for any changes and reload the static profiles. If the value is set to false, you can reload static profiles using modify command R. |
The following are the parameters needed for the Natural for Db2 for zIIP(NDZ) to set the environment variables.
| Parameter name | Mandatory | Description |
|---|---|---|
DB2_HOME |
Y | Update the Db2 installation directory which contains licenses, JDBC and SQLJ drivers. (Ex - /usr/lpp/db2vrs) |
JAVA_HOME |
Y | Update the Java JDK installation directory (Ex - /usr/lpp/java/Jvrs) |
NDZ_HOME |
Y | NDZ installation directory path where NDZ files are present. |