The following table contains a summary of the limits for Profiles for each target host.
| Limit | Windows® | MCP |
|---|---|---|
| Number of Profiles | 99 | No defined Limit (MCP architecture dependent) |
| Number of Keys in a Profile | 20 (SQL Server 2000/2005:16) | 20 |
| Length of Profile Keys | 240 bytes | No defined Limit (MCP architecture dependent) |
| Number of Lines in a Profile Definition | 99 | 99 |
| Alphanumeric Key Length | 78 | 78 |
| Usage Output Alphanumeric Key | 4095 | 4095 |
| Unsigned Numeric Key | 12 | 12 |
| Signed Numeric Key | 11 | 11 |
Number of Profiles
The number of Profiles over any Ispec class is limited to 99 for all hosts.
Length of Profile Keys
On MCP-based systems, there is no limit, although DASDL might impose an upper limit.
On Windows-based systems, the sum of the lengths of all Profile Keys is limited to half the database block size. An Attribute of type long might not be used as a Key. For SQL Server, the size of an index must be smaller than 900 bytes.
Number of Lines in a Profile Definition
For Windows and MCP-based systems the limit on the number of lines in a Profile definition is as follows:
There is a limit of 99 lines when defining your Profile (that is, lines for COMP.NAME; or EVENT.NAME; commands, KEY; commands, DO.WHEN; conditions and for MCP-based Systems, DATA; commands). You should use this limit at your discretion as your system might experience memory problems.