build

Purpose

The build command repairs the data integrity control information for database tables.

Required access rights:	User has to be a data integrity operator as described in Table 1
Predefined roles that provide required access rights:	None

Format

Event options

MQ client

To display command help:

Notes:

FTM SWIFT events are not written unless the instance's remote event service DNI_R_EVENT is running.
You must specify parameters -host, -channel and -port only if you want the data integrity checker to connect to the queue manager specified by parameter -qmgr in client mode. If you omit these parameters, the data integrity checker connects in bindings mode.
You must specify parameters -ciphersuite, -truststore and -fips only if you want to use SSL/TLS.

Parameters

-Djava.security.policy=policy_file

policy_file is the policy file that was provided for the runtime system. You can omit this parameter if your system administrator has added the required policies to the JVM default security properties file. For more information, see Java Policy files.

-passphrase phrase

The passphrase that the data integrity administrator specified when issuing the vault utility command create as described in activation of the data integrity framework, step 2.a.

Notes:

If you omit this parameter, the data integrity checker prompts for the passphrase.
Instead of specifying the phrase itself, you can also provide a stash file as described in Stash File Utility, for example:
```
-passphrase @/var/ftmswift_v300/run/passphrase.stash
```

-table table_name

If you want the data integrity checker to process a specific database table only, table_name specifies the name of this table. Use this parameter if you want, for example, to re-build the control information for a table that was reported to be manipulated.

-dsn data_source_name

The data source name of the FTM SWIFT runtime database. By default, the value of environment variable DNI_DSN is used.

-schema schema

The schema name of the tables in the FTM SWIFT runtime database. By default, the value of environment variable DNI_SN is used.

-commitcount (or -cc) number

The number of operations in one database transaction. The default is 50.

-uid user_id

The user ID to be used when connecting to the FTM SWIFT runtime database. Specify your own user ID as user_id.

-pw password

The password of the user ID specified in the -uid parameter.

Notes:

If you omit this parameter, the data integrity checker prompts for the password.
Instead of specifying the password itself, you can also provide a stash file as described in Stash File Utility, for example:
```
-pw @/var/ftmswift_v300/run/db2.stash
```

-instance (or -in or -i) instance

The name of the FTM SWIFT instance used to write events. If not specified, the environment variable DNI_I is used.

-qmgr qmgr

The name of the queue manager that is associated with the specified FTM SWIFT instance. If not specified the environment variable DNI_QM_instance is used.

-host host

The host name of the IBM® MQ server on which the queue manager runs. Specify this parameter if you want the data integrity checker to connect to the queue manager in client mode instead of bindings mode.

-channel channel

The channel to be used to connect to the queue manager. Specify this parameter if you want the data integrity checker to connect in client mode instead of bindings mode.

-port number

The port number of the IBM MQ server on which the queue manager runs. Specify this parameter if you want the data integrity checker to connect in client mode instead of bindings mode. The default is 1414.

-ciphersuite name

The name of the SSL cipher suite to be used in client connections to the IBM MQ server on which the queue manager runs. Use the name of the SSL cipher suite that matches the SSL definition for the channel name used. Refer to the IBM MQ documentation, SSL CipherSpecs and CipherSuites in MQ classes for Java, for more information on cipher suite naming.

-truststore filename

The file name of a trust store which contains the certificate information of the IBM MQ queue manager. Refer to the IBM MQ documentation, Configuring SSL security, for details on how to set up SSL/TLS connections and certificate information.

-fips

Use this parameter to enable Federal Information Processing Standards (FIPS) conforming SSL/TLS operations.

-help or -h

Show the help text that describes the parameters.

Note: To improve database performance, it is recommended to run the RUNSTATS utility for the following table spaces:

DNIROR
DNIvMWH if you use message warehouse
DNIvAUM if you use message audit log

Note: The parameter -keystore is deprecated. For compatibility reasons you can still specify it, but it is ignored during processing. The build command now uses the vault that was specified by the data integrity administrator when issuing the init command.

Return codes

The build command terminates with one of the following return codes:

Code: Description
0: Successful processing.
4: No processing was done because an invalid parameter was specified.
8: Processing terminated because the vault file could not be read.
12: Processing terminated due to a fatal error. For more information, see the command output in the shell.

Example

The following command (issued on a single line) builds the control information for the database table DNI.DNF_OAMS in the FTM SWIFT database with data source name DNIDBRUN. It uses the stash file /var/ftmswift_v300/run/passphrase.stash to provide the vault's passphrase, uses John's credentials to connect to the database and writes events for the instance that is identified by environment variable DNI_I:

dnpdic -build -Djava.security.policy=/var/ftmswift_v300/run/ftmswift.policy
       -passphrase @/var/ftmswift_v300/run/passphrase.stash
       -dsn DNIDBRUN -schema DNI -uid john -pw johns_password
       -table DNF_OAMS