1.19.2 Settings for handling JP1/IM - Manager failures

(1) Preparations for collecting data in the event of a failure

JP1/IM - Manager provides a batch file (jim_log.bat) as a tool for collecting data in the event of a problem. This tool enables you to collect data needed for resolving problems in batch mode.

The data collection tool of JP1/IM - Manager can collect troubleshooting data for JP1/IM - Manager, JP1/Base, and JP1/IM - View (on the same host). For details about the data that can be collected, see 10.3 Data that needs to be collected when a problem occurs in the Job Management Partner 1/Integrated Management - Manager Administration Guide.

About the data collection tool

• About jim_log.bat

  See jim_log.bat (Windows only) in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

In the event of a problem, it may be advisable to obtain a memory dump and a crash dump. To collect these dumps, specify the settings described below so that memory and crash dumps are output (when these output settings are specified, these dumps can also be collected by the data collection tool).

Memory dump output settings

The following procedure describes how to set the output destination for a memory dump when the OS is Windows Server 2003. This procedure is not necessary for Windows Server 2012 and Windows Server 2008.

1. From Control Panel, double-click System.

2. On the Advanced page, in Startup and Recovery, click the Settings button.

3. In Write debugging information, select Kernel memory dump, and then specify an output file.

   Important note

   The size of a memory dump depends on the size of the real memory. If the installed physical memory is large, the size of a memory dump will also be large. Take care to allocate sufficient disk space for collecting a memory dump. For details, see the Windows Help topic Stop error.

Crash dump output settings

The following procedure describes how to set the output destination for a crash dump when the OS is Windows Server 2003. This procedure is not necessary for Windows Server 2012 and Windows Server 2008.

1. From the Start menu, choose Run.

2. In the text box, enter drwtsn32 and then click the OK button.

   The Dr. Watson for Windows dialog box appears.

3. Select the Create Crash Dump File check box and then specify the output file in the Crash Dump text box.

4. Click the OK button.

   Important note

   In addition to JP1 information, error information for other application programs is also output to the crash dump. For this reason, output of a crash dump requires a fair amount of disk space. If you specify the setting to output crash dumps, take care that sufficient disk space is available.

To Page Top

(2) Restart settings in the event of abnormal process termination

To specify restart settings in the event of abnormal process termination:

1. Define process restart.

   Edit the following extended startup process definition file (jp1co_service.conf) so that process restart is enabled:

   Console-path\conf\jp1co_service.conf

   The restart parameter is the third value separated by the vertical bars (|). Set either 0 (do not restart (default)) or 1 (restart). Do not change the first value separated by the vertical bars (|).

2. Apply the definition information.

   If JP1/IM - Manager is running, execute JP1/IM - Manager's reload command so that the process restart setting is enabled:

   jco_spmd_reload

3. Set Dr. Watson.

   The following procedure describes how to hide the Dr. Watson dialog box when the OS is Windows Server 2003. This procedure is not necessary for Windows Server 2012 and Windows Server 2008.

   To enable process restart, set the Dr. Watson dialog box to be hidden. This is because a process cannot restart if the Dr. Watson dialog box is displayed in the event of an applicable error.

   From the Start menu, choose Run, then execute drwtsn32. When the Dr. Watson dialog box appears, clear the Visual Notification check box.

   Note that because the Dr. Watson settings are common settings, the setting specified here applies to all programs in the entire system.

   To enable the Dr. Watson settings, execute the following command at the command prompt:

   drwtsn32 -i

   Dr. Watson is installed as the default application debugger.

4. Suppress error reporting to Microsoft.

   The following procedure describes how to suppress error reporting to Microsoft when the OS is Windows Server 2003. This procedure is not necessary for Windows Server 2012 and Windows Server 2008.

   When you enable process restart, you must specify settings so that the Microsoft error reporting dialog box, which is displayed in the event of an error detection, is not displayed. This is because a process cannot restart if this dialog box is displayed.

   1. From Control Panel, double-click System.

   2. On the Advanced page, click the Error Reporting button.

   3. Choose Disable error reporting and make sure that the But notify me when critical errors occur check box is not selected.

About process restart definition

• About the extended startup process definition file (jp1co_service.conf)

  See Extended startup process definition file (jp1co_service.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

Note:

In a cluster system, do not enable process restart in the event of abnormal process termination. If JP1/IM - Manager fails, the process restart function might also be affected. If you want to restart processes in the event of abnormal process termination in a cluster system, use the cluster software (not JP1/IM - Manager) to control the restart.

To Page Top

(3) Setting JP1 event issuance in the event of abnormal process termination

To set JP1 event issuance in the event of abnormal process termination:

1. Set JP1 event issuance.

   Edit the following IM parameter definition file (jp1co_param_V7.conf):

   Console-path\conf\jp1co_param_V7.conf

   In this file, SEND_PROCESS_TERMINATED_ABNORMALLY_EVENT and SEND_PROCESS_RESTART_EVENT are the JP1 event issuance setting parameters. To issue JP1 events, change the value to dword:1.

2. Execute the jbssetcnf command to apply the definition information.

   jbssetcnf Console-path\conf\jp1co_param_V7.conf

3. Restart JP1/Base and the products that require JP1/Base.

   The specified settings take effect after the restart.

About JP1 event issuance settings

• About the IM parameter definition file (jp1co_param_V7.conf)

  See IM parameter definition file (jp1co_param_V7.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

To Page Top

(4) Setting the health check function

To set the health check function in order to detect JP1/IM - Manager process hang-ups:

1. Open the health check definition file (jcohc.conf) and specify parameters.

   To enable the health check function, specify ENABLE=true.

   Specify EVENT=true to issue a JP1 event and COMMAND=command-to-be-executed to execute a notification command when a hang-up is detected.

2. Use the jco_spmd_reload command to reload JP1/IM - Manager, or restart JP1/IM - Manager.

3. If you specified a notification command, execute the jcohctest command to check the notification command's execution validity.

   Execute the jcohctest command to determine whether the command specified in COMMAND executes correctly. If the operation is not valid, check and, if necessary, revise the specification.

   Important note

   In Windows 8.1 (x64), Windows 8 (x64), Windows Server 2012 (x64), Windows 7 (x64), Windows Server 2008 (x64), and Windows Vista (x64), if you execute a command in the %WINDIR%\System32 folder, the redirection function of WOW64 redirects the command to the command in the %WINDIR%\SysWow64 folder. If the command does not exist at the redirection destination, the command execution might fail. Be careful when you specify a command in the %WINDIR%\System32 folder as the execution command.

About the health check function settings

• About the health check definition file (jcohc.conf)

  See Health check definition file (jcohc.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

• About the jcohctest command

  See jcohctest in 1. Commands in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

To Page Top

(5) Automatic backup and recovery settings for a monitoring object database

You specify these settings when you will be using the functions of Central Scope.

If the OS shuts down while the monitoring tree is being updated, or a failover occurs during cluster operation, the monitoring object database may be corrupted. Therefore, you must set the monitoring object database to be backed up and recovered automatically when the monitoring tree is being updated.

These settings are enabled when you have performed a new installation, and they are disabled if the settings were disabled in the old version of JP1/IM - Manager or JP1/IM - Central Scope. Change the settings as appropriate to your operation.

To specify automatic backup and recovery settings for a monitoring object database:

1. Terminate JP1/IM - Manager.

2. Execute the jbssetcnf command using the following file for the parameters:

   To enable the automatic backup and recovery functions for the monitoring object database: auto_dbbackup_on.conf

   To disable the automatic backup and recovery functions for the monitoring object database: auto_dbbackup_off.conf

   When you execute the jbssetcnf command, the settings are applied to the JP1 common definition information.

   For details about the jbssetcnf command, see the Job Management Partner 1/Base User's Guide.

   About the settings in the file

   For details about the settings in the file, see Automatic backup and recovery settings file for the monitoring object database (auto_dbbackup_xxx.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

3. Start JP1/IM - Manager.

To Page Top