jco_start (UNIX only)
- Organization of this page
Function
This command is a script for starting JP1/IM - Manager automatically.
To execute this command, you must have performed the following procedure after you completed installation and setup of JP1/IM - Manager:
# cd /etc/opt/jp1cons
# cp -p jco_start.model jco_start
With these operations, JP1/IM - Manager starts automatically when the system starts. If you do not want JP1/IM - Manager to start automatically at the system startup, do not perform these operations.
You must perform these operations if you set JP1/IM - Manager version 10 or earlier to start automatically.
For details about configuring the automatic startup settings, see 2.18.2 Setting automatic startup and automatic stop (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.
To start JP1/IM - Manager manually, execute the /etc/opt/jp1cons/jco_start.model script, or a file to which this script has been copied.
If you use a script to which jco_start.model has been copied in JP1/IM - Manager version 10 or earlier, overwrite it with jco_start.model.
Before you execute this command, make sure that JP1/Base is running. JP1/IM - Manager uses the functions of JP1/Base (prerequisite product).If this command is executed when the following all conditions are satisfied, the command starts the IM database service and then starts JP1/IM - Manager:
-
The IM database service has been set up.
-
The integrated monitoring database is used or IM Configuration Management Service is set to be started.
If you are using Intelligent Integrated Management Database, after starting IM Database services the above, further services start in the order of the Intelligent Integrated Management Database and Trend Data Management Service, and then start JP1/IM - Manager at the end.
The command terminates with a return value of 0 after issuing a startup request to the group of JP1/IM - Manager processes. To check whether the group of processes has started successfully, use the jco_spmd_status command after the jco_start command has terminated to display the process IDs of the services that have started. Note that the process ID of the IM database service is not displayed.
Format
jco_start
Execution permission
Superuser permissions
Storage directory
/etc/opt/jp1cons/
Note
-
If you want to execute this command as a remote shell command, disconnect standard input, standard output, and standard error output (assign /dev/null to standard input, standard output, and standard error output). Note that the remote shell command might not terminate even when processing for starting JP1/IM - Manager has finished.
-
Execute this command in an environment in which the environment variable JP1_HOSTNAME has not been set. If you execute this command in an environment in which the environment variable JP1_HOSTNAME has been set, the command will attempt to start JP1/IM - Manager on the logical host set in the environment variable JP1_HOSTNAME rather than on the physical host. Because this command does not support logical hosts, you must delete the environment variable JP1_HOSTNAME if you want to start JP1/IM - Manager on the physical host.
-
The jco_start command cannot be executed together with the jco_spmd_status command.
Return values
0 |
Normal termination |
1 |
More than one argument is specified, the event service is not running, or the IM database service cannot be started |
2 |
There is no log directory |
Example 1
- When the integrated monitoring database is used:
-
- Input value:
jco_start
- Result:
Please wait a minutes, now starting the IM database service... KNAN11188-I The status of the IM database service will now be confirmed. KNAN11183-I The IM database service is stopped. KNAN11189-I The status of the IM database service was successfully confirmed. Please wait a minutes, now starting JP1/IM - Manager... KAVB3690-I Processing to report the status of JP1_CONS has started. Display the running processes process name process ID evflow 18990 jcamain 19036 evtcon 19037 KAVB3691-I All the processes have started.
Example 2
- When the integrated monitoring database is not used and IM Configuration Management Service has not started:
-
- Input value:
jco_start
- Result:
Please wait a minutes, now starting JP1/IM - Manager... KAVB3690-I Processing to report the status of JP1_CONS has started. Display the running processes process name process ID evflow 19237 jcamain 19277 evtcon 19278 KAVB3691-I All the processes have started.
Example 3
- When the IM database is not used:
-
- Input value:
jco_start
- Result:
Please wait a minutes, now starting the IM database service... KNAN11188-I The status of the IM database service will now be confirmed. KNAN11109-E The IM database service is not set up. Unable start JP1/IM - Manager.
Example 4
- When the integrated monitoring database and the trend data management database are used:
-
- Input value:
jco_start
- Result:
Please wait a minutes, now starting the IM database service... KNAN11188-I The status of the IM database service will now be confirmed. KNAN11183-I The IM database service is stopped. KNAN11189-I The status of the IM database service was successfully confirmed. Please wait a minutes, now starting the Intelligent Integrated DB... KNAN12055-I The Intelligent Integrated Management Database Service will now start. KNAN12057-I The trend data management service will now start. KNAN12056-I The Intelligent Integrated Management Database Service started normally. KNAN12058-I The trend data management service started normally. KNAN12044-I The processing to confirm the service operating status will now start. KNAN12047-I The Intelligent Integrated Management Database Service is running. KNAN12048-I The trend data management service is running. KNAN12045-I The processing to confirm the service operating status ended normally. Please wait a minutes, now starting JP1/IM - Manager... KAVB3690-I Processing to report the status of JP1_CONS has started. Display the running processes process name process ID evflow 26290 jcamain 26374 evtcon 26375 jddmain 26291 KAVB3691-I All the processes have started.