Job Management Partner 1/Integrated Management - Manager Administration Guide

[Contents][Index][Back][Next]

1.3 Managing the disk capacity

To ensure stable operation of JP1/IM, check the available disk space regularly.

Organization of this section
(1) Managing the database capacity
(2) Managing the log file size
(3) Managing dump files

(1) Managing the database capacity

Databases used by JP1/IM are designed not to increase invalid areas even during continued use. As long as the required capacity is secured, there is no need to check the database during operations.

When the number of JP1 events exceeds the storage limit of the integrated monitoring database, JP1 events are automatically deleted. Therefore, you need to output and save JP1 event information regularly to prevent data loss.

To manage the disk capacity using the output-and-save operation:

  1. View the information related to output-and-save operations.
    Executing the jcoevtreport -showsv command displays the information related to output-and-save operations. Based on this information, estimate the output-and-save frequency and the free space required for outputting and saving information.
    The following table shows the items that are displayed.

    Table 1-9 Displayed items

    Displayed item Description
    Percentage of events that have not been saved Shows the percentage of JP1 events within the integrated monitoring database that have not been output or saved (a ratio relative to the maximum capacity of the integrated monitoring database).
    Size of events that are have not been saved Shows the data size of JP1 events within the integrated monitoring database that have not been output or saved (in megabytes).
    The size displayed is the size within the integrated monitoring database. CSV output will require 1.2 times the size of the displayed events that have not been output.
    Settings for deletion warning notification Shows the value set as the deletion warning notification level.
    If the deletion warning notification is set to OFF, a hyphen (-) is displayed.

  2. Output and save the events that have not been output.
    Executing the jcoevtreport -save command outputs to a CSV file all JP1 events that have not been output and saved.

For details about the jcoevtreport command, see jcoevtreport (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

If too many JP1 events occurred and regular output-and-save operations were too late for them, you can issue a deletion warning notification event. A deletion warning notification event reports when the percentage of JP1 events that have not been output and saved exceeds the deletion warning notification level.

To set up a deletion warning notification:

  1. Enable the issuance of deletion warning notification events.
    Executing the jcoimdef -dbntc ON command enables the function that issues a deletion warning notification event when the percentage of JP1 events within the integrated monitoring database that have not been output and saved (a ratio relative to the maximum capacity of the integrated monitoring database) exceeds the deletion warning notification level. The default for the deletion warning notification event is OFF.

  2. Specify a deletion warning notification level.
    Executing the jcoimdef -dbntcpos 70 command sets the percentage of JP1 events for issuing a deletion warning notification event to 70%. You can specify a value between 20 and 80 for the deletion warning notification level. The default is 80.

For details about the jcoimdef command, see jcoimdef (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

(2) Managing the log file size

One of the factors that can cause insufficient disk capacity is an increase in the size of log files.

In the case of JP1/IM and JP1/Base, if you estimate the log file size in advance, there is no need to consider the possibility of increasing the log file size. This is because JP1/IM and JP1/Base use a method that outputs log files by switching between multiple log files.

For the OS and other products on the same host, check their specifications and make sure that their log file size will not increase.

(3) Managing dump files

If JP1/IM, JP1/Base, or a user program abnormally terminates because of a problem, a dump file such as a Dr. Watson log (in Windows) or a core dump (in UNIX) may be output in some cases.

These dump files are large. Therefore, when a problem occurs, collect the necessary data and then delete the dump files.

For details about collecting data for troubleshooting, see 9. Troubleshooting.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.