C.1 Limit values
The following table lists limit values on CPA.
|
No. |
Item |
Limit value |
|---|---|---|
|
1 |
The number of units (actions, action flows, and event monitors) that an action flow can contain |
64 |
|
2 |
Unit depth (The depth indicates the level of a nested action flow. Referencing another action flow increases the depth of the hierarchical structure.) |
2 |
|
3 |
The number of jobs that can be registered with the job execution service#1 |
16 |
|
4 |
The number of actions that the job execution service can execute concurrently |
32 |
|
5 |
The number of actions that can run concurrently for a job |
8 |
|
6 |
The maximum number of results stored for a job executed on time |
5 |
|
7 |
The maximum number of results stored for a job executed on event |
5 |
|
8 |
The length (Unit: bytes) of the name of a job or item |
1 to 45 |
|
9 |
The length (Unit: bytes) of the description of a job or item |
0 to 1,024 |
|
10 |
Dates allowed for schedules |
2013/01/01 to 2037/12/31 |
|
11 |
The acceptable delay (Unit: minutes) from the scheduled time for a job to start |
60 |
|
12 |
The number of files monitored by the Monitor file item (when the monitored file name is specified with wildcards) |
10 |
|
13 |
Timeout period (Unit: minutes) of an event monitor |
0 to 1,440 |
|
14 |
The maximum size (Unit: bytes) of data sent to standard output |
32,768 |
|
15 |
The maximum size (Unit: bytes) of data sent to standard error output |
32,768 |
|
16 |
The length (Unit: bytes) of the name of a command to be executed |
1 to 256 |
|
17 |
The length (Unit: bytes) of the parameter specified with a command to be executed |
0 to 512 |
|
18 |
The timeout period (Unit: minutes) for the Command execution in window item |
0 to 1,440 |
|
19 |
The maximum number of queued instances of a job executed on event#2 |
16 |
|
20 |
The maximum number of profiles that can be registered |
16 |
|
21 |
The maximum number of virtual users that can be registered |
10 |
|
22 |
The number of input items that can be created for an item |
10 |
- #1
-
You can expand the number of registered jobs up to 64 by specifying job_ent_max in the system settings definition file. For details on the definition file, see E.1 System settings definition file.
- #2
-
During a run of a job executed on event, if the execution condition of the job becomes satisfied, the job enters the Wait for start state and the event causes a new instance to be queued unless the queue is full. If the queue is full (that is, this maximum number is already reached), the event queue overflows and the event is discarded without triggering the job.