18.4.1 How to collect data (in Windows)

Organization of this subsection

(1) Execute the data collection tool
(2) Check the status of the process
(3) Check the operation data
(4) Collect the error information on the screen
(5) Collect problem reports

(1) Execute the data collection tool

Execute the data collection tool (jbs_log.bat).

By executing jbs_log.bat, you can collect the data needed for investigating a JP1/Base error on that host.

The amount of data collected varies greatly depending on your operating environment. Before executing the data collection tool, estimate the amount of data as follows, and make sure you have sufficient disk space.

Data size when a physical host is specified in jbs_log.bat

If you specify a physical host (by omitting the -h option) in the jbs_log.bat command, use the following equation to estimate how much data will be collected about JP1/Base and the computer environment:

Data size = 5 + a + b + c + d (MB)

a

Size of all the files in installation-folder\log\ (maximum 45 MB^#1)

b

Size of all the files in installation-folder\sys\ (maximum 55 MB^#2)

c

Data size of the Dr. Watson log and crash dump

d

Total size of the following files

system-drive (such as C:\WINNT) \system32\config\AppEvent.evt
system-drive (such as C:\WINNT) \system32\config\SysEvent.evt

#1: An extra 142 MB is required if you are running JP1/IM - Manager on the same host.

#2: This is the default value. This value increases if you change the size of the event database.

Data size when a logical host is specified in jbs_log.bat

If you specify a logical host in the jbs_log.bat command, use the following equation to estimate how much data will be collected about JP1/Base and the computer environment:

Data size = 5 + a + b + c + d + e + f (MB)

a

Size of all the files in installation-folder\log\ (maximum 45 MB^#1)

b

Size of all the files in installation-folder\sys\ (maximum 55 MB^#2)

c

Data size of the Dr. Watson log and crash dump

d

Total size of the following files

system-drive (such as C:\WINNT) \system32\config\AppEvent.evt
system-drive (such as C:\WINNT) \system32\config\SysEvent.evt

e

Data size of shared-folder\jp1base\log\ (maximum 45 MB^#1)

f

Data size of shared-folder\jp1base\event\ (maximum 55 MB^#2)

#1: An extra 142 MB is required if you are running JP1/IM - Manager on the same host.

#2: This is the default value. This value increases if you change the size of the event database. For details on estimating the maximum size, see the Release Notes.

To check the size of each folder in Internet Explorer, right-click the folder, and then display the Properties window.

For details on estimating the maximum disk space requirements of each folder, see the Release Notes.

An example of jbs_log.bat execution is shown below.

c:\>c:\usertools\jbs_log.bat data-folder

Specify a full path for data-folder. If the path contains a space, enclose the path in double quotation marks (").

When you execute the tool, a jp1_default folder is created in the directory you specified in data-folder. If you specify the -h option, in addition to the jp1_default folder, a folder with the name of the logical host is created. Two further folders, base_1st and base_2nd are created in each of these folders, and the data collected by jbs_log.bat is copied under them. If necessary, you can compress the collected data by using an archiving tool.

The jbs_log.bat command provides options for excluding specific files, such as command execution logs (ISAM) and event database files. For details, see jbs_log.bat (Windows only) in 15. Commands.

To Page Top

(2) Check the status of the process

Use the Windows task manager to check the operating status of a desired process. The system displays the following process names when the processes are operating normally. The value in parentheses in the table indicates the number of processes that can be executed simultaneously.

Parent process name	Function	Child process name	Function
`hntr2srv.exe` (1)	Starts the Hitachi Network Objectplaza Trace Library (HNTRLib2)	--	--
`hntr2mon.exe` (1)	Hitachi Network Objectplaza Trace Library (HNTRLib2)	--	--
`jbs_service.exe` (1)	Starts the JP1/Base process management^#1	--	--
`jbs_spmd.exe` (1)	JP1/Base process management^#1	`jbssessionmgr.exe` (1)	Authentication server^{#1, #3} This process exists only on the host that is set as the authentication server. The displayed name is `jbssessionmgr` when the `jbs_spmd_status` command is executed.
		`jbsroute.exe` (1)	Configuration management^{#1, #3} The displayed name is `jbsroute` when the `jbs_spmd_status` command is executed.
		`jcocmd.exe` (1) `jcocmdexe.exe` (1) `jcocmdapi.exe` (number of screens where commands are executed^#2+ 1 (when JP1/IM - Manager has been installed))	Command execution^{#1, #3} The displayed name is `jcocmd` when the `jbs_spmd_status` command is executed.
		`jbsplugind.exe`	Plug-in service^{#1, #3} The displayed name is `jbsplugin` when the `jbs_spmd_status` command is executed.
		`jbshcd.exe` (1)	Health check (for local host monitoring)^{#1, #3} The displayed name is `jbshcd` when the `jbs_spmd_status` command is executed.
		`jbshchostd.exe` (1)	Health check (for remote host monitoring)^{#1, #3} The displayed name is `jbshchostd` when the `jbs_spmd_status` command is executed.
		`jbssrvmgr.exe` (1)	Service management control function^#1,#3 The displayed name is `jbssrvmgr` when the `jbs_spmd_status` command is executed.
		`jbslcact.exe` (1)	Local action function^#1,#3 The displayed name is `jbslcact` when the `jbs_spmd_status` command is executed.
		`jbscomd.exe` (1) `jbscomd_api.exe` (1) `jbscomd_ses.exe` (1) `jbscomd_snd.exe` (1) `jbscomd_rcv.exe` (1)	Inter-process communication^#1,#3 The displayed name is `jbscomd` when the `jbs_spmd_status` command is executed.
`jbapmsrvcecon.exe` (1)	Startup control	`powendar.exe` (1)	Power control This process is generated when JP1/Power Monitor is installed.
`jevservice.exe` (1)	Event service^{#1, #4}	`jevsessvc.exe` (1)	Event service This process is generated only on physical hosts.
`jevtraplog.exe` (1)	Log file trap	--	This process is generated only when the log file trapping function is used.
`jevtrapevt.exe` (1)	Event log trap	--	This process is generated only when the event log trapping function is used.

Legend:: --: None

#1: The maximum number of processes that can be executed simultaneously with the indicated process is the calculation result of the following format when multiple logical hosts operate on one physical host in the cluster system or when one logical host and one physical host are started at the same time: (number-of-logical-hosts + 1) x number-of-processes

#2: The number of Execute Command windows opened by the connected JP1/IM - View. The number of processes increases as the number of open windows increases. When you close an Execute Command window, the corresponding process disappears.

#3: You can use the jbs_spmd_status command to check the status of these processes. If the processes are running normally, the jbs_spmd_status command returns the following information.

If an authentication server has been set:

jbssessionmgr

jbsroute

jcocmd

jbsplugin

jbshcd

jbshchostd

jbssrvmgr

jbslcact

jbscomd
If an authentication server has not been set:

jbsroute

jcocmd

jbsplugin

jbshcd

jbshchostd

jbssrvmgr

jbslcact

jbscomd

#4: The status of these processes can be checked with the jevstat command. Executing the jevstat command when the processes are running normally displays the following string:

jevservice

To Page Top

(3) Check the operation data

If a problem occurs, check the operation data and record it. You need to check the following information:

Details of the operation
Time the error occurred
Machine configuration (version of each OS, host name, configuration of JP1/IM - Manager)
Whether the error occurs repeatedly under the same conditions
User name used to log in from JP1/IM - View

To Page Top

(4) Collect the error information on the screen

If an error is displayed on the screen, also collect that information. Collect hard copies of the following:

The error dialog boxes

In addition, copy the contents of the details if the dialog box contains a Details button.

To Page Top

(5) Collect problem reports

When an application error causes the JP1/Base process to stop, perform the following actions to collect a problem report:

In the Control Panel, click Action Center.
Click Maintenance.
Under Check for solutions to problem reports, click View reliability history.
Click View all problem report.
Click the appropriate problem.
Click Copy to clipboard.
Paste the clipboard into a file such as a text file, and then save the file.

To Page Top