jimdbstop

Organization of this page

Function

This command terminates the IM database. Use this command to set the termination command with the start sequence control function of JP1/Base.

If the IM database is in restart canceled status, you can forcibly terminate it by executing this command with the -f option specified.

jimdbstop [-h logical-host-name]
          [-f]

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

In UNIX: Superuser permissions

-h logical-host-name: When you are operating in a cluster system, this option specifies the logical host name of the host where the command is executed. The command then stops the IM database for the specified logical host. If this option is omitted, the logical host name specified in the JP1_HOSTNAME environment variable is assumed. If the JP1_HOSTNAME environment variable is not specified, the physical host name is assumed. If you are not using a cluster system, specification of this option is not needed. Note that the logical host name is case sensitive.
-f: Specifies that the IM database is to be terminated forcibly.

`0`	Normal termination
`1`	Abnormal termination
`4`	IM database is engaged in startup or termination processing
`8`	Database has been terminated (IM database restart processing was canceled and the IM database became unstable)
`12`	IM database was terminated (normal termination status)
`20`	IM database has not been set up

If you cancel processing by pressing Ctrl + C or Ctrl + Break, termination of the IM database might fail. If you re-execute the command in such a case, first make sure that the pdstop process is not running. If the pdstop process is running, wait a while and then check again.
JP1/IM - Manager must not be running while the IM database is being used.
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 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.