B.3 Limits for units
The following table lists the limits of units defined in JP1/AJS3.
Definition |
Maximum |
---|---|
Comment length for a unit |
80 (bytes)#1 |
Number of units that can be defined in one level of hierarchy below the job group |
Not limited |
Number of units that can be defined in one level of hierarchy below the jobnet#13 |
10,000 |
Number of root jobnets that can be defined |
Not limited |
Job group name#3 (full name) |
930 (bytes)#4 |
Jobnet name#3 (full name) |
930 (bytes)#4 |
Job name#3 (full name) |
930 (bytes) |
Maximum number of nests of unit |
30#5 |
Unit name |
30 (bytes)#1 |
Number of jobnets that can be registered for execution |
2,147,483,647#6 |
Number of logs to keep |
99 (or 999#7, #8) |
Number of backup boxes that can be created |
Not limited |
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 |
Four-digit year set for the SCHEDULELIMIT environment setting parameter/12/31#9 |
Maximum number of scheduled generations in a single jobnet |
7,680#8 |
Maximum number of concurrently monitored generations waiting for start conditions to be satisfied |
7,680#10 |
Number of queuing jobs and running jobs that can be executed concurrently |
Maximum value of MaximumContentJob #6, #12 |
Number of event jobs that can be defined in start conditions |
32 |
Number of units whose ends are being waited for and that can be set for one unit with a wait condition |
32 |
Maximum number of generations per day for which the temporary change operation management function can store temporary change information #11 |
999 |
Length of the TZ environment variable |
95 (bytes) |
Length of a host name |
255 (bytes) |
Length of the LANG environment variable |
58 (bytes) |
Maximum number of job network elements in one root jobnet#2 |
40,000 |
- #1
-
If UTF-8 encoding is used and sjis is specified for the DEFLENTYPE environment setting parameter, this value is the number of bytes that is converted to Shift-JIS.
- #2
-
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.
- #3
-
Alphanumeric characters, multi-byte 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.
- #4
-
When the maximum number is reached, no lower units can be created.
- #5
-
The limit is 10 if UTF-8 encoding is used and sjis is specified for the DEFLENTYPE environment setting parameter.
- #6
-
This value is calculated independent of resources such as disks and memory, and execution performance.
- #7
-
This is the maximum value available with the extended function for the number of logs to keep.
- #8
-
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.
- #9
-
For details about the SCHEDULELIMIT environment setting parameter, see 20.4.2(123) SCHEDULELIMIT in the JP1/Automatic Job Management System 3 Configuration Guide. If the version of the connection-target JP1/AJS3 - Manager is 12-60 or earlier, the value of this item is 2036/12/31.
- #10
-
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.
- #11
-
The temporary change operation management function can store temporary change information for a maximum of 999 generations per day for one root jobnet. If you attempt to make temporary changes to the 1,000th and later generations, an error occurs and the temporary change information will not be stored. When you use the temporary change operation management function, make sure the number of generations executed per day by one root jobnet does not exceed 999.
- #12
-
This value is also the maximum value that can be specified for the MaximumContentJob environment setting parameter. For details about the MaximumContentJob environment setting parameter, see 20.5.2(12) MaximumContentJob in the JP1/Automatic Job Management System 3 Configuration Guide.
- #13
-
The value used for multiplying the horizontal and vertical sizes of the map area set in the Jobnet Editor window is the number of units that can be defined in one level of hierarchy.