jcodbsetup

Function

This is a setup command for creating an integrated monitoring database area for storing JP1 events. You must have already specified in advance in the setup information file the database's size, port number, and storage location.

In Windows, if this command is executed in an environment where the IM Configuration Management database is not set up, the following services are registered in the OS:

• When setting up a physical host: JP1/IM-Manager DB Server, JP1/IM-Manager DB Cluster Service

• When setting up a cluster configuration: JP1/IM-Manager DB Server_logical-host-name, JP1/IM-Manager DB Cluster Service_logical-host-name

In UNIX, if this command is executed in an environment where the IM Configuration Management database is not set up, an entry containing the path to the IM database is added to the /etc/inittab file. The entry is added to the respective physical and logical hosts on which this command was executed. Do not delete, edit, or comment out the entry in the /etc/inittab file that is added when this command is executed.

To Page Top

Format

jcodbsetup {-f setup-information-file-name|-s}
           [-h logical-host-name -c {online|standby}]
           [-q]
           [-v 0]

To Page Top

Execution permission

In Windows: Administrator permissions (if the Windows UAC feature is enabled, the command is executed from the administrator console)

In UNIX: Superuser permissions

To Page Top

Storage directory

In Windows:

Console-path\bin\

In UNIX:

/opt/jp1cons/bin/

To Page Top

Arguments

-f setup-information-file-name

Specifies the setup information file that contains the requisite information, such as the IM database installation folder and the size of the database area. If neither the IM Configuration Management database nor an integrated monitoring database has been set up, you must specify this option. If the IM Configuration Management database has already been set up, specify in this option the setup information file that you specified when you set up the IM Configuration Management database. Alternatively, if the IM Configuration Management database has already been set up, you can specify the -s option instead. In such a case, the command uses the setup information that was specified when the IM Configuration Management database was set up.

This option cannot be specified together with the -s option. Additionally, the -f and -s options cannot both be omitted.

If the path contains a space, enclose the entire path in double-quotation marks ("). If you configure a cluster environment, specify the cluster setup information file name.

-s

If the IM Configuration Management database has already been set up, you can specify this option instead of the -f option. When this option is specified, the command sets up the integrated monitoring database by using the setup information that was specified when the IM Configuration Management database was set up.

If the IM Configuration Management database has not been set up but this option is specified, the command displays the KNAN11193-E message.

This option cannot be specified together with the -f option. Additionally, the -s and -f options cannot both be omitted.

-h logical-host-name

When you are operating in a cluster system, this option specifies the logical host name of the host that executes the command. The command sets up the integrated monitoring database for the specified logical host. If you do not use a cluster system, specification of this option is not needed. Note that this logical host name cannot be JP1_DEFAULT. In addition, the logical host name is case sensitive. For the logical host name, specify a logical host name set in JP1/Base in the correct form, especially case.

-c {online|standby}

Specifies the setup type in the cluster configuration (primary node or secondary node). If you have specified the -h option, you must specify this option. If the IM Configuration Management database has already been set up on the same host, specify the value that you used when you created the IM Configuration Management database. If you are running a logical host in a non-cluster environment, specify online.

• online: Specifies that the primary node is to be set up.

• standby: Specifies that the secondary node is to be set up.

If you specify online, mount the shared disk and establish a connection to the logical host.

-q

Specifies that the command is to be executed without requesting confirmation from the user.

-v 0

Specifies that you want to recover a backup for expansion that was backed up using a table schema from JP1/IM - Manager 09-00 to 10-50. In JP1/IM - Manager 11-00, you can specify 0 as the version of the backup for expansion.

When 0 is specified, the integrated monitoring database is set up using the same table schema as JP1/IM - Manager 09-00 to 10-50.

If the -v option is omitted, the integrated monitoring database is set up using the table schema of JP1/IM - Manager 11-00 or later.

The -v option is ignored if standby is specified for the -c option.

To Page Top

Return values

To Page Top

Notes

• The contents of the cluster setup information files must be identical between the primary and secondary nodes. When you set up the secondary node, copy the cluster setup information file used for the primary node and then use that file. If the contents of the files specified for the primary and secondary nodes are different, cancel the setup at the secondary node, copy the cluster setup information file from the primary node, and then re-execute the command.

• If you execute the command with the -c option specified, do not switch servers during execution. If you switch servers during execution, cancel the setup after the command has terminated, and then re-execute the command.

• If you have canceled the command's execution by pressing Ctrl + C or Ctrl + Break, make sure that the pdistup, pdfmkfs, pddef, and pdload processes are not executing, execute the jcodbunsetup command, and then re-execute this command.

• If the IM Configuration Management database has already been set up and the IM database is being used, JP1/IM - Manager Service must be stopped.

• If you are using the IM Configuration Management database in Windows, the IM database (JP1/IM2-Manager DB Server) must be running and the cluster service for the IM database (JP1/IM2-Manager DB Cluster Service) must be stopped.

• If you are using JP1/IM - MO, the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source must be stopped.

• Before executing the command, verify that the logical host name specified in the argument matches the JP1/Base logical host name in JP1/Base, and that the logical host name can be resolved.

• If you perform unsetup of the IM database by executing the jcodbunsetup or jcfdbunsetup command, you must restart the OS before re-executing the jcfdbsetup command.

• Before executing the command in Windows, in case of existing the Application Experience service, make sure that the startup type of the Application Experience service is not set to Disabled.

To Page Top