Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

Appendix D. Limits

This appendix shows the limits of JP1/IM.

Organization of this section

(1) Limits when using the Central Console

(2) Limits when using the Central Scope

(3) Limits when using IM Configuration Management

(1) Limits when using the Central Console

The tables below describe the limits that apply to JP1/IM - Manager and JP1/IM - View when using the Central Console. The Web-based JP1/IM - View, as a feature of JP1/IM - Manager (JP1/IM - Central Console), is subject to the JP1/IM - Manager limits.

(a) JP1/IM - Manager limits

The following table describes the limits that apply to JP1/IM - Manager and the Web-based JP1/IM - View.

Table D-1 Limits for JP1/IM - Manager

Item Limit

Number of instances of JP1/IM - View that can connect to one JP1/IM - Manager 64

Number of instances of the Web-based JP1/IM - View that can run on one machine 1

Number of hosts that can be managed by one instance of JP1/IM - Manager (the number of JP1/Base hosts that can be configured directly under JP1/IM - Manager)

1,024

When close is specified as the communication type in the event server settings file (conf) of JP1/Base on the manager

100 (UNIX); 62 (Windows)

When a value other than close is specified as the communication type in the event server settings file (conf) of JP1/Base on the manager

This value is for a maximum configuration. The number of managed hosts is restricted by the system configuration and network traffic.

Number of hosts that can execute commands from one instance of JP1/IM - Manager

1,024

When the managed hosts include a host running JP1/Base 06-51 or earlier, a maximum of 60 such hosts can be configured directly under JP1/IM - Manager.

In this case, the maximum number of hosts that can execute commands concurrently from one JP1/IM - Manager is 60 (in Windows) or equal to the number of file descriptors^#1 that can be used in one process minus 10 (in UNIX). The calculation here assumes that a host running JP1/Base 06-51 or earlier under JP1/IM - Manager is executing commands even if it is not doing so in reality.

Event buffer size (number of extracted events that can be buffered from the event database) 2,000

Scroll buffer size (number of events that can be displayed in a window) in the Web-based JP1/IM - View 1,000

Number of events that can be acquired when a window is refreshed in the Web-based JP1/IM - View 200

Number of events that can be acquired in a search in the Web-based JP1/IM - View 1,000

Maximum length of an event acquisition filter

60 KB

When an exclusion condition group or a valid common exclusion condition group is not set.

64 KB

When an exclusion condition group or a valid common exclusion condition group is set.

Maximum length of an event receiver filter 1 MB (total size when more than one event receiver filter is set)

Maximum length of a severe events filter 64 KB

Maximum length of a view filter 1 MB per JP1 user (total size when more than one view filter is set)^#2

Maximum length of an event search 64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)^#2

Number of event receiver filters 128

Number of conditions that can be set in a filter (applies to passing conditions and exclusion conditions)

Event acquisition filter: 30 per filter

Event receiver filter: 30 per filter

Severe events filter: 30

View filter: 5 per filter

Event search: 5

Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#3 of the Web-based JP1/IM - View 30,000 bytes

Number of filters that can be defined in the list of event acquisition filters 50

Maximum length of a filter name specified in the list of event acquisition filters 50 bytes

Number of common exclusion conditions that can be defined in the list of event acquisition filters

30

Maximum size of the file containing the list of event acquisition filters 1 MB

Number of queued commands executed by automated actions

65,535

When the target host on which the automated actions are to be executed is running JP1/Base 06-71 or later

64

When the target host on which the automated actions are to be executed is running JP1/Base 06-51 or earlier

Length of an action definition parameter 5,706 bytes
The following limits apply to the individual items specified in the action definition parameter:

Length of an event monitoring condition: 1,040 bytes

Length of an action: 4,096 bytes

Length of the user name for executing an action: 31 bytes

Length of an environment variable file name: 255 bytes

Length of a target host name: 255 bytes

Length of a target group name 30 bytes

File size of an event guide information file 1 MB

File size of an event-guide message file 1 MB

Total number of items that can be defined in an event guide information file 1,000

Length of an event-guide message after processing of placeholders (variables) and HTML encoding 196,608 characters^#4

Length of an event guide-message file name that can be specified in an event guide information file 1,024 characters^#4

Number of comparison conditions that can be defined in event guide information 100

Number of correlation event generation conditions that can be defined in a correlation event generation definition file 1,000

Number of filtering conditions for the correlation target range that can be defined in one correlation event generation condition 1

Number of event conditions that can be defined in one correlation event generation condition 10

Timeout period for a correlation event generation condition 1 second to 86,400 seconds (24 hours)

Maximum value that can be specified in the threshold event correlation type 100 events

Number of duplicate attribute value conditions that can be defined in one correlation event generation condition 3

Number of maximum correlation numbers that can be defined in one correlation event generation condition 1

Maximum length of the attribute value used in defining a correlation approval event 1,023 bytes

Number of sets of JP1 events that can be correlated simultaneously by one correlation event generation condition 1,024 sets

Number of sets of JP1 events that can be correlated simultaneously by all correlation event generation conditions 20,000 sets

Health check timeout period 216,000 seconds (60 hours)

#1: The number of file descriptors available to one process is system-dependent.

#2: This limit applies to the Web-based JP1/IM - View.

#3: Filter windows are the Severe Event Definitions window, Event Search Conditions window, Settings for View Filter window, and Detailed Settings for Event Receiver Filter window.

#4: Each one-byte character counts as one character. For example, AAA counts as three characters.

(b) JP1/IM - View limits

The following table describes the limits that apply to JP1/IM - View.

Table D-2 Limits for JP1/IM - View

Item Limit

Number of concurrent logins from one instance of JP1/IM - View 3^#1

Scroll buffer size (number of events that can be displayed in a window) 2,000

Number of events that can be acquired when a window is refreshed 200

Number of events that can be acquired in a search 2,000

Maximum length of a filter

View filter: 1 MB per JP1 user (total size when more than one view filter is set)

Event search: 64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)

Number of view filters 50

Maximum length of a name of a view filter 50 bytes

Number of condition groups that can be set in a filter (applies to passing conditions and exclusion conditions)

Event acquisition filter: 30 per filter

Event receiver filter: 30 per filter

Severe events filter: 30

View filter: 5 per filter

Event search: 5

Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#2 30,000 bytes

Number of filters that can be defined in the list of event acquisition filters 50 (When connected to JP1/IM - Central Console 07-00 or later)

Number of common exclusion condition groups that can be defined in the list of event acquisition filters

30

Longest environment variable file name that can be specified in the Execute Command window 255 bytes

Longest target host name that can be specified in the Execute Command window 255 bytes

Length of an action definition parameter When connected to JP1/IM - Manager 08-01 or later: 5,706 bytes
The following limits apply to the individual items specified in the action definition parameter:

Length of an event monitoring condition: 1,040 bytes

Length of an action: 4,096 bytes

Length of the user name for executing an action: 31 bytes

Length of an environment variable file name: 255 bytes

Length of a target host name: 255 bytes

When connected to JP1/IM - Central Console 07-01 or earlier: 1,023 bytes
The following limits apply to the individual items specified in the action definition parameter:

Length of an event monitoring condition: 1,023 bytes

Length of an action: 1,023 bytes

Length of the user name for executing an action: 31 bytes

Length of an environment variable file name: 255 bytes

Length of a target host name: 255 bytes

Number of lines of execution results to display in the Execute Command window that can be specified in the Preferences window 100 to 10,000 lines

Column width for display of messages in the Execute Command window that can be specified in the Preferences window 50,000 pixels

Size of text data that can be copied to the clipboard 6 MB

#1: The larger the number of concurrent logins, the greater the memory and disk space requirements.

#2: Filter windows are the Severe Event Definitions window, Event Search Conditions window, Settings for View Filter window, and Detailed Settings for Event Receiver Filter window.

Item	Limit
Number of instances of JP1/IM - View that can connect to one JP1/IM - Manager	64
Number of instances of the Web-based JP1/IM - View that can run on one machine	1
Number of hosts that can be managed by one instance of JP1/IM - Manager (the number of JP1/Base hosts that can be configured directly under JP1/IM - Manager)	1,024 When close is specified as the communication type in the event server settings file (conf) of JP1/Base on the manager 100 (UNIX); 62 (Windows) When a value other than close is specified as the communication type in the event server settings file (conf) of JP1/Base on the manager This value is for a maximum configuration. The number of managed hosts is restricted by the system configuration and network traffic.
Number of hosts that can execute commands from one instance of JP1/IM - Manager	1,024 When the managed hosts include a host running JP1/Base 06-51 or earlier, a maximum of 60 such hosts can be configured directly under JP1/IM - Manager. In this case, the maximum number of hosts that can execute commands concurrently from one JP1/IM - Manager is 60 (in Windows) or equal to the number of file descriptors^#1 that can be used in one process minus 10 (in UNIX). The calculation here assumes that a host running JP1/Base 06-51 or earlier under JP1/IM - Manager is executing commands even if it is not doing so in reality.
Event buffer size (number of extracted events that can be buffered from the event database)	2,000
Scroll buffer size (number of events that can be displayed in a window) in the Web-based JP1/IM - View	1,000
Number of events that can be acquired when a window is refreshed in the Web-based JP1/IM - View	200
Number of events that can be acquired in a search in the Web-based JP1/IM - View	1,000
Maximum length of an event acquisition filter	60 KB When an exclusion condition group or a valid common exclusion condition group is not set. 64 KB When an exclusion condition group or a valid common exclusion condition group is set.
Maximum length of an event receiver filter	1 MB (total size when more than one event receiver filter is set)
Maximum length of a severe events filter	64 KB
Maximum length of a view filter	1 MB per JP1 user (total size when more than one view filter is set)^#2
Maximum length of an event search	64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)^#2
Number of event receiver filters	128
Number of conditions that can be set in a filter (applies to passing conditions and exclusion conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#3 of the Web-based JP1/IM - View	30,000 bytes
Number of filters that can be defined in the list of event acquisition filters	50
Maximum length of a filter name specified in the list of event acquisition filters	50 bytes
Number of common exclusion conditions that can be defined in the list of event acquisition filters	30
Maximum size of the file containing the list of event acquisition filters	1 MB
Number of queued commands executed by automated actions	65,535 When the target host on which the automated actions are to be executed is running JP1/Base 06-71 or later 64 When the target host on which the automated actions are to be executed is running JP1/Base 06-51 or earlier
Length of an action definition parameter	5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
Length of a target group name	30 bytes
File size of an event guide information file	1 MB
File size of an event-guide message file	1 MB
Total number of items that can be defined in an event guide information file	1,000
Length of an event-guide message after processing of placeholders (variables) and HTML encoding	196,608 characters^#4
Length of an event guide-message file name that can be specified in an event guide information file	1,024 characters^#4
Number of comparison conditions that can be defined in event guide information	100
Number of correlation event generation conditions that can be defined in a correlation event generation definition file	1,000
Number of filtering conditions for the correlation target range that can be defined in one correlation event generation condition	1
Number of event conditions that can be defined in one correlation event generation condition	10
Timeout period for a correlation event generation condition	1 second to 86,400 seconds (24 hours)
Maximum value that can be specified in the threshold event correlation type	100 events
Number of duplicate attribute value conditions that can be defined in one correlation event generation condition	3
Number of maximum correlation numbers that can be defined in one correlation event generation condition	1
Maximum length of the attribute value used in defining a correlation approval event	1,023 bytes
Number of sets of JP1 events that can be correlated simultaneously by one correlation event generation condition	1,024 sets
Number of sets of JP1 events that can be correlated simultaneously by all correlation event generation conditions	20,000 sets
Health check timeout period	216,000 seconds (60 hours)

Item	Limit
Number of concurrent logins from one instance of JP1/IM - View	3^#1
Scroll buffer size (number of events that can be displayed in a window)	2,000
Number of events that can be acquired when a window is refreshed	200
Number of events that can be acquired in a search	2,000
Maximum length of a filter	View filter: 1 MB per JP1 user (total size when more than one view filter is set) Event search: 64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)
Number of view filters	50
Maximum length of a name of a view filter	50 bytes
Number of condition groups that can be set in a filter (applies to passing conditions and exclusion conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#2	30,000 bytes
Number of filters that can be defined in the list of event acquisition filters	50 (When connected to JP1/IM - Central Console 07-00 or later)
Number of common exclusion condition groups that can be defined in the list of event acquisition filters	30
Longest environment variable file name that can be specified in the Execute Command window	255 bytes
Longest target host name that can be specified in the Execute Command window	255 bytes
Length of an action definition parameter	When connected to JP1/IM - Manager 08-01 or later: 5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes When connected to JP1/IM - Central Console 07-01 or earlier: 1,023 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,023 bytes Length of an action: 1,023 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
Number of lines of execution results to display in the Execute Command window that can be specified in the Preferences window	100 to 10,000 lines
Column width for display of messages in the Execute Command window that can be specified in the Preferences window	50,000 pixels
Size of text data that can be copied to the clipboard	6 MB

(2) Limits when using the Central Scope

The following tables describe the limits that apply to JP1/IM - Manager and JP1/IM - View when using the Central Scope.

(a) JP1/IM - Manager limits

The following table describes the limits that apply to JP1/IM - Manager.

Table D-3 Limits for JP1/IM - Manager

Item Limit

Number of instances of JP1/IM - View that can connect to one JP1/IM - Manager 64

Number of hosts that can be monitored by one instance of the Central Scope 5,000
This value includes all hosts being monitored from the Central Scope, such as JP1/AJS - Agent hosts and hosts being monitored using the SNMP trap converter of JP1/Base, in addition to hosts configured under JP1/IM - Manager.

Number of Monitoring Tree windows that can be managed by JP1/IM - Manager 1

Longest monitoring node name that can be set in a configuration file for a monitoring tree 255 bytes

Longest basic information for a monitoring node that can be set in a configuration file for a monitoring tree Attribute value: 1,023 bytes^#

Longest status change condition name that can be set in a configuration file for a monitoring tree 63 bytes

Longest value specifiable for individual conditions in a configuration file for a monitoring tree Attribute value: 1,023 bytes^#

File size of a guide information file 1 MB

File size of a guide-message file 1 MB

#: The total for all fields is a maximum of 1,280 bytes. (For example, if five conditions are set, the total size of the five attribute values must not exceed 1,280 bytes.)

(b) JP1/IM - View limits

The following table describes the limits that apply to JP1/IM - View.

Table D-4 Limits for JP1/IM - View

Item Limit

Number of concurrent logins from one viewer host 3^#1

Number of monitoring nodes that can be monitored in a Monitoring Tree window 50,000

Length of a monitoring node name 255 bytes

Number of basic information items that can be set for one monitoring node 5

Number of characters that can be entered in a basic information field Attribute name: 32 bytes
Attribute value: 1,023 bytes^#2

Number of status change conditions that can be set for one monitoring node 8

Length of a status change condition name 63 bytes

Number of individual conditions that can be set in one status change condition for monitoring objects 5

Percentage value that can be set as a comparison condition in one status change condition for monitoring groups 100

Maximum count that can be set as a comparison condition in one status change condition for monitoring groups 50,000

Number of characters that can be entered in an individual condition field Attribute name: 32 bytes
Attribute value: 1,023 bytes^#2

Number of JP1 events that can be issued by one monitoring node 7

Number of status change event logs that can be kept by each monitoring node 100

File name length of a background image that can be set in a monitoring group 260 bytes

File name length of an image file used as an icon for a monitoring node (for the normal and expanded status, and Visual Icon) 260 bytes

Number of common conditions that can be added by the user 191

Length of the common condition name set in the Common Condition Detailed Settings window 63 bytes

Number of characters that can be entered in a Common condition details field (other than the Extended attribute area) of the Common Condition Detailed Settings window 1,023 bytes

Number of characters that can be entered in a Common condition details field (Extended attribute area) of the Common Condition Detailed Settings window Attribute name: 32 bytes
Attribute value: 1,023 bytes^#2

Length of the file name of the background image in a Visual Monitoring window 260 bytes

Number of monitoring nodes that can be placed in one Visual Monitoring window 128

Number of Visual Monitoring windows that users can create 64

Length of the name set for a Visual Monitoring window 63 bytes

Length of a comment about a Visual Monitoring window 80 bytes

#1: The larger the number of concurrent logins, the greater the memory and disk space requirements.

#2: The total for all fields is a maximum of 1,280 bytes. (For example, if five conditions are set, the total size of the five attribute values must not exceed 1,280 bytes.)

Item	Limit
Number of instances of JP1/IM - View that can connect to one JP1/IM - Manager	64
Number of hosts that can be monitored by one instance of the Central Scope	5,000 This value includes all hosts being monitored from the Central Scope, such as JP1/AJS - Agent hosts and hosts being monitored using the SNMP trap converter of JP1/Base, in addition to hosts configured under JP1/IM - Manager.
Number of Monitoring Tree windows that can be managed by JP1/IM - Manager	1
Longest monitoring node name that can be set in a configuration file for a monitoring tree	255 bytes
Longest basic information for a monitoring node that can be set in a configuration file for a monitoring tree	Attribute value: 1,023 bytes^#
Longest status change condition name that can be set in a configuration file for a monitoring tree	63 bytes
Longest value specifiable for individual conditions in a configuration file for a monitoring tree	Attribute value: 1,023 bytes^#
File size of a guide information file	1 MB
File size of a guide-message file	1 MB

Item	Limit
Number of concurrent logins from one viewer host	3^#1
Number of monitoring nodes that can be monitored in a Monitoring Tree window	50,000
Length of a monitoring node name	255 bytes
Number of basic information items that can be set for one monitoring node	5
Number of characters that can be entered in a basic information field	Attribute name: 32 bytes Attribute value: 1,023 bytes^#2
Number of status change conditions that can be set for one monitoring node	8
Length of a status change condition name	63 bytes
Number of individual conditions that can be set in one status change condition for monitoring objects	5
Percentage value that can be set as a comparison condition in one status change condition for monitoring groups	100
Maximum count that can be set as a comparison condition in one status change condition for monitoring groups	50,000
Number of characters that can be entered in an individual condition field	Attribute name: 32 bytes Attribute value: 1,023 bytes^#2
Number of JP1 events that can be issued by one monitoring node	7
Number of status change event logs that can be kept by each monitoring node	100
File name length of a background image that can be set in a monitoring group	260 bytes
File name length of an image file used as an icon for a monitoring node (for the normal and expanded status, and Visual Icon)	260 bytes
Number of common conditions that can be added by the user	191
Length of the common condition name set in the Common Condition Detailed Settings window	63 bytes
Number of characters that can be entered in a Common condition details field (other than the Extended attribute area) of the Common Condition Detailed Settings window	1,023 bytes
Number of characters that can be entered in a Common condition details field (Extended attribute area) of the Common Condition Detailed Settings window	Attribute name: 32 bytes Attribute value: 1,023 bytes^#2
Length of the file name of the background image in a Visual Monitoring window	260 bytes
Number of monitoring nodes that can be placed in one Visual Monitoring window	128
Number of Visual Monitoring windows that users can create	64
Length of the name set for a Visual Monitoring window	63 bytes
Length of a comment about a Visual Monitoring window	80 bytes

(3) Limits when using IM Configuration Management

The tables below describe the limits that apply to JP1/IM - Manager and JP1/IM - IM Configuration Management - View when using IM Configuration Management.

(a) JP1/IM - Manager limits

The following table describes the limits that apply to JP1/IM - Manager.

Table D-5 Limits for JP1/IM - Manager

Item Limit

Number of instances of JP1/IM - IM Configuration Management - View that can connect to one JP1/IM - Manager 64

Number of hosts that can be monitored from one instance of IM Configuration Management 10,000
1,024 agents can be configured directly under IM Configuration Management

Number of hierarchical levels that can be monitored from one instance of IM Configuration Management 3 levels

Maximum number of log file traps that can be managed 100^#

Number of standby hosts that can be set up on one logical host 4

Number of IP addresses that can be displayed for one host 4

Number of alias host names that can be displayed for one host 4

#: If 101 or more log trap files are active, the message KNAN22450-W is output and the first 100 are collected.

(b) JP1/IM - View limits

The following table describes the limits that apply to JP1/IM - View.

Table D-6 Limits for JP1/IM - View

Item Limit

Number of concurrent logins from one instance of JP1/IM - View 3^#

#: The larger the number of concurrent logins, the greater the memory and disk space requirements.

Item	Limit
Number of instances of JP1/IM - IM Configuration Management - View that can connect to one JP1/IM - Manager	64
Number of hosts that can be monitored from one instance of IM Configuration Management	10,000 1,024 agents can be configured directly under IM Configuration Management
Number of hierarchical levels that can be monitored from one instance of IM Configuration Management	3 levels
Maximum number of log file traps that can be managed	100^#
Number of standby hosts that can be set up on one logical host	4
Number of IP addresses that can be displayed for one host	4
Number of alias host names that can be displayed for one host	4

Item	Limit
Number of concurrent logins from one instance of JP1/IM - View	3^#

[Contents][Back][Next]

[Trademarks]