Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

Appendix B. List of Limits

Organization of this section

(1) Limits on the number of JP1/AJS3 product connections

(2) Limits for units

(3) Limits for scheduler services

(4) Limits for the job execution environment

(5) Limits for the submit job execution environment

(6) Limit for queueless job execution control

(7) Limits for the event/action control

(8) Limits for JP1/AJS3 Console

(9) Limits for the definition pre-check function

(1) Limits on the number of JP1/AJS3 product connections

The following table shows the number of JP1/AJS3 - Agents and the number of JP1/AJS3 - Views that can be connected to JP1/AJS3 - Manager.

Table B-1 Limits of JP1/AJS3 - Views and JP1/AJS3 - Agents that can be connected to JP1/AJS3 - Manager

Definition Maximum

Number of JP1/AJS3 - Agents that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration) 1,024

Number of JP1/AJS3 - Views that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration) 128^#

#

Connecting 64 or more JP1/AJS3 - Views will greatly increase the load on JP1/AJS3 - Manager and the network. Therefore, if you want to connect 64 or more JP1/AJS3 - Views, prohibit JP1/AJS3 - Views from automatically refreshing their screens or set the automatic refresh interval to 600 seconds or longer. Also, do not use JP1/AJS3 - Manager and the Monthly Schedule window simultaneously, since the window transfers a large amount of data.

The following table shows the maximum number of JP1/AJS3 - Managers that can be connected to JP1/AJS3 - Agent.

Table B-2 Limit of JP1/AJS3 - Managers that can be connected to JP1/AJS3 - Agent

Definition Maximum

Number of JP1/AJS3 - Managers that can be connected to a single JP1/AJS3 - Agent 16^#

#

The maximum value assumes an environment in which the agent and all managers can communicate smoothly with each other. If there is a manager for which name resolution by the agent takes time or a manager for which a timeout occurs during a connection, operation might be affected even when the number of managers is fewer than the maximum. For example, execution of a job from another manager might be delayed. Also, the number of jobs concurrently processed by the agent might affect operation. Make sure that you consider the load on the system during peak times and configure the system accordingly. Note that for a queueless-job execution environment, the number of JP1/AJS3 - Managers that can be connected is not limited.

Definition	Maximum
Number of JP1/AJS3 - Agents that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration)	1,024
Number of JP1/AJS3 - Views that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration)	128^#

Definition	Maximum
Number of JP1/AJS3 - Managers that can be connected to a single JP1/AJS3 - Agent	16^#

(2) Limits for units

The following table lists the limits of units defined in JP1/AJS3.

Table B-3 Limits of units

Definition Maximum

Comment length for a unit 80 (bytes)

Number of units that can be defined in one level of hierarchy^#7 10,000

Number of root jobnets that can be defined Not limited

Jobnet group name^#1 (full name) 930 (bytes)^#6

Jobnet name^#1 (full name) 930 (bytes)^#6

Job name^#1 (full name) 930 (bytes)

Maximum number of nests of unit^#7 30

Unit name 30 (bytes)

Number of jobnets that can be registered for execution 2,147,483,647^#²

Number of logs to keep 99 (or 999^{#3, #4})

Number of backup files that can be created in a backup box 1,024

Scheduler log file capacity 2,048,000,000 (bytes)

Last date 2036/12/31

Maximum number of scheduled generations in a single jobnet 7,680^#4

Maximum number of concurrently monitored generations waiting for start conditions to be satisfied 7,680^#5

Number of jobs that can be executed simultaneously Not limited^#2

Number of event jobs that can be defined in start conditions 32

Length of the TZ environment variable 95 (bytes)

Length of a host name 255 (bytes)

Length of the LANG environment variable 58 (bytes)

#1

Alphanumeric characters and the following symbols can be used to define unit names:

! # $ % + @ - (hyphen) . (period) _ (underscore)

The following symbols are also available. However, these are provided for migration from previous JP1/AJS product. Do not use the symbols for other purposes.

" & ' * < > ? [ \ ] ^ ` { | } ~

When specifying a unit name containing any of these symbols in the command line of a command that manipulates a unit, enclose the entire unit name in double quotation marks (") and cast the unit name with a backslash (\) before each symbol. For example, to specify unit /net[1] in the ajsprint command, write as follows: ajsprint "/net\[1\]"

Note that some symbols have special meanings to command interpreters such as UNIX shells. In this case, avoid using such symbols for unit names since they might generate incorrect operations.

Periods (.) and at signs (@) are not allowed at the beginning of unit names, except for .CONDITION used as the unit name of a start condition.

Characters that are specific to computers cannot be used for unit names. In addition to unit names, we recommend that you do not use computer-dependent characters for any definition items, since they might become garbled.

#2

This value is calculated independent of resources such as disks and memory, and execution performance.

#3

This is the maximum value available with the extended function for the number of logs to keep.

#4

In accordance with the database restrictions, the total number of logs to keep and scheduled generations cannot exceed 8,000.

With an extended function, the maximum number of logs to keep can be increased to 999. However, if the number of scheduled generations is set to a maximum of 7,680, the maximum permissible number of logs to keep is decreased to 320. Such a restriction is provided to prevent deletion of schedules that are already registered for fixed execution. To increase the maximum permissible number of logs to keep using the extended function, manage operations so as to limit the future schedules to 7,001 or less.

#5

This value indicates the maximum number of concurrently monitored generations waiting for start conditions to be satisfied.

Normally when a generation satisfies the start conditions and begins to run, the generation is excluded from the generations that are subject to this limit.

#6

When the maximum number is reached, no lower units can be created.

#7

Creating many units in one root jobnet might have an operational impact, such as insufficient memory, because a large amount of information needs to be processed. We recommend that you create no more than 40,000 job network elements in one root jobnet.

Definition	Maximum
Comment length for a unit	80 (bytes)
Number of units that can be defined in one level of hierarchy^#7	10,000
Number of root jobnets that can be defined	Not limited
Jobnet group name^#1 (full name)	930 (bytes)^#6
Jobnet name^#1 (full name)	930 (bytes)^#6
Job name^#1 (full name)	930 (bytes)
Maximum number of nests of unit^#7	30
Unit name	30 (bytes)
Number of jobnets that can be registered for execution	2,147,483,647^#²
Number of logs to keep	99 (or 999^{#3, #4})
Number of backup files that can be created in a backup box	1,024
Scheduler log file capacity	2,048,000,000 (bytes)
Last date	2036/12/31
Maximum number of scheduled generations in a single jobnet	7,680^#4
Maximum number of concurrently monitored generations waiting for start conditions to be satisfied	7,680^#5
Number of jobs that can be executed simultaneously	Not limited^#2
Number of event jobs that can be defined in start conditions	32
Length of the TZ environment variable	95 (bytes)
Length of a host name	255 (bytes)
Length of the LANG environment variable	58 (bytes)

(3) Limits for scheduler services

The following table lists the limits for scheduler services.

Table B-4 Limits for the scheduler service

Definition Maximum

Maximum number of scheduler services defined 20^#

#

The maximum number of scheduler services that can be defined per computer (physical and logical hosts) is 20.

Definition	Maximum
Maximum number of scheduler services defined	20^#

(4) Limits for the job execution environment

The following table lists the limits for executing Unix jobs, PC jobs, event jobs, action jobs, and custom jobs in JP1/AJS3.

Table B-5 Limits for the job execution environment

Definition Maximum

Number of registered execution agents 1,024^#

Number of registered execution agent groups 1,024

Number of agent hosts that can be specified for one execution agent 1

Number of execution agents that can be grouped in an execution agent group 1,024

#

Because the default execution agent is defined when JP1/AJS3 is set up, the ajsagtadd command can be used to add 1,023 agents.

Note that the default execution agent cannot be deleted. For details on the default execution agent, see 2.5.1(3) Default execution agent.

Definition	Maximum
Number of registered execution agents	1,024^#
Number of registered execution agent groups	1,024
Number of agent hosts that can be specified for one execution agent	1
Number of execution agents that can be grouped in an execution agent group	1,024

(5) Limits for the submit job execution environment

The following table lists the limits for executing QUEUE jobs and submit jobs.

Table B-6 Limits for the submit job execution environment

Definition Maximum

Maximum number of queues defined 8,192

Number of connectable agents 1,024

Number of execution-locked resources 8,192

Definition	Maximum
Maximum number of queues defined	8,192
Number of connectable agents	1,024
Number of execution-locked resources	8,192

(6) Limit for queueless job execution control

The following table shows the limit for executing queueless jobs in JP1/AJS3.

Table B-7 Limit for queueless job execution control

Definition Maximum

Number of logical hosts that can be attached concurrently to the queueless agent service 9

Definition	Maximum
Number of logical hosts that can be attached concurrently to the queueless agent service	9

(7) Limits for the event/action control

The following table lists the limits for executing event jobs in JP1/AJS3.

Table B-8 Limits for the event/action control

Item Maximum in a standard configuration Maximum in a compatible ISAM configuration

Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on an agent host from one or more manager hosts 1,000^#1 1,000^#1

Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on multiple agent hosts from one manager host 4,000^#1 1,300^#1

Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host 1,000^#1 1,000^#1

Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per scheduler service 4,000^#1 1,300^#1

Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per manager host 80,000^#1 4,000^#1

Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the restart process of a JP1/AJS3 service on an agent host, per agent host 1,000^#1 1,000^#1

Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the execution of the jajs_maintain command with the -F option specified -- 1,000^#1

Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command with the -F option specified per scheduler service -- 1,300^#1

Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command without the -F option specified per manager host -- 4,000^{#1, #2}

Number of ajskill or ajsintrpt commands that can be executed consecutively on event jobs (including those set in start conditions) 4,000^{#1, #3} 1,300^{#1, #3}

Number of Monitoring Log Files jobs that can be executed concurrently on one execution host 150^#4 150^#4

#1

The value when no events have occurred. If events are likely to occur at the same time, configure the system so that the maximum value, counting events and event jobs, will not be exceeded.

If the maximum is exceeded, and an operation is performed on an event job, or an event job (including an event job in a start condition) detects the monitored event, the following issues might occur:

Event jobs registered for execution (including those in start conditions) remain in queuing status.

Active event jobs, and jobnets with start conditions that JP1/AJS3 is monitoring, fail to end when killed.

Event jobs (including those in start conditions) do not detect monitored events.

Be aware of these issues, but note that in some high-performance environments, exceeding any of the limits might not cause problems.

These issues are due to the high volume of communication that takes place in the processing of a large number of jobs. For details about what causes the issues and recovery procedures, see 7.6.8 Notes on restarting the JP1/AJS3 service while event jobs are running in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

#2

In addition to active event jobs, the maximum value includes the number of event jobs (including those set in start conditions) that are scheduled to start at a time when the system is in maintenance mode.

#3

Executing these commands consecutively over a short duration results in a high volume of communication. If the maximum value is exceeded, the issues in #1 above might occur. For details about what causes the issues and recovery procedures, see 7.6.8 Notes on restarting the JP1/AJS3 service while event jobs are running in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

#4

This is the maximum value under the following conditions:

The Monitoring Log Files jobs run under Windows.

Each Monitoring Log Files job monitors one log file only.

Log files are monitored by Monitoring Log Files jobs only, not in conjunction with the JP1/Base log file trapping function.

In UNIX, when one Monitoring Log Files job monitors multiple log files, or is used in conjunction with the JP1/Base log file trapping function, estimate the number of Monitoring Log Files jobs that can be executed based on the number of log files that can be monitored by the log file trapping function. For details, see the Job Management Partner 1/Base User's Guide.

Item	Maximum in a standard configuration	Maximum in a compatible ISAM configuration
Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on an agent host from one or more manager hosts	1,000^#1	1,000^#1
Number of event jobs (including those set in start conditions) that can be concurrently registered for execution or forcibly terminated on multiple agent hosts from one manager host	4,000^#1	1,300^#1
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host	1,000^#1	1,000^#1
Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per scheduler service	4,000^#1	1,300^#1
Maximum number of event jobs (including those set in start conditions) that can continue to run through the warm-start or hot-start process of a JP1/AJS3 service or scheduler service on a manager host, per manager host	80,000^#1	4,000^#1
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the restart process of a JP1/AJS3 service on an agent host, per agent host	1,000^#1	1,000^#1
Maximum number of event jobs (including those set in start conditions) executed on one agent host that can continue to run through the execution of the jajs_maintain command with the -F option specified	--	1,000^#1
Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command with the -F option specified per scheduler service	--	1,300^#1
Maximum number of event jobs (including those set in start conditions) that can continue to run through the execution of the jajs_maintain command without the -F option specified per manager host	--	4,000^{#1, #2}
Number of ajskill or ajsintrpt commands that can be executed consecutively on event jobs (including those set in start conditions)	4,000^{#1, #3}	1,300^{#1, #3}
Number of Monitoring Log Files jobs that can be executed concurrently on one execution host	150^#4	150^#4

(8) Limits for JP1/AJS3 Console

Table B-9 Limits for JP1/AJS3 Console

Definition Maximum

Number of JP1/AJS3 Console Views that can be connected to JP1/AJS3 Console Manager 64 (hosts)

Number of JP1/AJS3 Console Managers that can monitor a single JP1/AJS3 Console Agent 64 (hosts)

Number of JP1/AJS3 Console Agents (manager hosts) that can be monitored by a single root work-task scope 50 (hosts)

Maximum number of levels of work-task scope (a maximum of 3 levels available as nested work-task scope) 3 (levels)

Total number of AJS3 unit monitored objects and nested work-task scope (including AJS3 unit monitored objects under the scope) that can be defined in root work-task scope map area 500 (units)

Name of work-task scope or AJS3 unit monitored object^#1 30 (bytes)

Length of comment for work-task scope or AJS3 unit monitored object 80 (bytes)

Monitored host name 255 (bytes)

Monitored unit name^#2 2,047 (bytes)

Map vertical and horizontal extension sizes 100 (units)

Display zoom 200 (%)

#1

Alphanumeric characters and the following symbols can be used to define these names:

! # $ % + @ - (hyphen) . (period) _ (underscore)

Characters that are specific to computers are not available.

The characters below cannot be input:

(space)

(

)

, (comma)

: (colon)

; (semicolon)

/

=

In addition to this item, we recommend that you do not use computer-dependent characters for any definition items, since they might become garbled.

#2

The characters below cannot be input:

(

)

, (comma)

: (colon)

; (semicolon)

=

Definition	Maximum
Number of JP1/AJS3 Console Views that can be connected to JP1/AJS3 Console Manager	64 (hosts)
Number of JP1/AJS3 Console Managers that can monitor a single JP1/AJS3 Console Agent	64 (hosts)
Number of JP1/AJS3 Console Agents (manager hosts) that can be monitored by a single root work-task scope	50 (hosts)
Maximum number of levels of work-task scope (a maximum of 3 levels available as nested work-task scope)	3 (levels)
Total number of AJS3 unit monitored objects and nested work-task scope (including AJS3 unit monitored objects under the scope) that can be defined in root work-task scope map area	500 (units)
Name of work-task scope or AJS3 unit monitored object^#1	30 (bytes)
Length of comment for work-task scope or AJS3 unit monitored object	80 (bytes)
Monitored host name	255 (bytes)
Monitored unit name^#2	2,047 (bytes)
Map vertical and horizontal extension sizes	100 (units)
Display zoom	200 (%)

(9) Limits for the definition pre-check function

The following table describes the limit for pre-checks on JP1/AJS3 definitions.

Table B-10 Limit for definition pre-check

Definition Maximum number

Number of definition pre-checks that can be executed simultaneously 1

Definition	Maximum number
Number of definition pre-checks that can be executed simultaneously	1

[Contents][Back][Next]

[Trademarks]