The following table contains a summary of the limits for Setup Attributes for the different target hosts.
| Limit | Windows® | MCP |
|---|---|---|
| Number of Ispec Attributes | 2097151 | No defined Limit (MCP architecture dependent) |
| Size of an alphanumeric Ispec Attribute | 231 – 1 characters | 9,999 |
| Size of an Ispec Attribute with alphanumeric literal | 231 – 1 characters | 160 |
| Size of a numeric Ispec Attribute | 29 | 18 |
| Size of an Ispec Attribute with numeric literal | 29 | 18 |
| Total size of an Ispec Attribute array (characters) | Size of public Array variable of any datatype | 1MB |
| Size of all Ispec Attributes with initial values | 29 characters (for numeric) 231 – 1 characters (for text) | No defined Limit (MCP architecture dependent) |
| Size of all Ispec Attributes without initial values | 29 characters (for numeric) 231 – 1 characters (for text) | Refer to text |
| Ispec Attributes in an Ispec class | 2097151 | No defined Limit (MCP architecture dependent) |
| Ispec Attributes in Report | 2097151 | No defined Limit (MCP architecture dependent) |
| Ispec Attributes in a Method | 2097151 | Refer to text |
Size of Ispec Attributes on MCP-based Systems
Ispec Attributes without initial values have a maximum limit of 99 Ispec classes with greater than 64K byes of Ispec Attributes or the equivalent size in one Ispec class.
Ipsec Attributes in a Method
If you intend to access a Method using the Component Enabler interface, you can only use 5000 Ispec Attributes to define the parameters of the Method. Also, if a parameter is longer than 5000 bytes, only the first 5000 bytes are transferred.
These limits only apply if you use the Component Enabler interface. They are not enforced by Developer.