The following table contains a summary of the limits for an Ispec Class for each target host. It is intended as a guide only and should be read in conjunction with the information in the subsections following the table.
|
Limit |
Windows® |
MCP |
|---|---|---|
| Number of Ispec Classes | No Limit | 1500 (1000 for Output or I/O) |
| Number of Attributes in Output Structure | 1024 | 3020 |
| Length of Attributes in Output Structure | 29 characters (For Numeric) 2 31 – 1 characters (For Text) | 24570 characters |
| Byte length of Input/ Output Ispec classes | 4000 bytes (65000 for Big Buffer Ispecs) | 26,450 characters |
| Number of Logic Lines in an Ispec class | 2097151 Number of lines in a Class | 999999 |
| Number of Nested Database Commands | 32 | No defined Limit (MCP architecture dependent) |
| References to other Ispec classes | 65535 (within a method) 2097151 (within a class) | 6009 |
| References to Methods | 2000 (includes references to other Ispec classes) | |
| Painted Items in an Ispec class | 9990 | 320 |
| Painted Items in a Copy.From area | 9990 | 100 |
| Maximum size of External Automatic Entry (HUB) transaction | 9999 characters | 2000 bytes |
Number of Attributes in the Output Structure
In Windows-based systems there is a limit of 950.
In MCP-based systems, the maximum number of persistent attributes is 3,020 (and is limited by the accumulated size).
The number of fields reserved for the different types of generated fields are listed in the following table.
|
Generated Field |
Subtract |
|---|---|
| GLB_DTIME (Ispec) | 1 |
| GLB_DTIME, MAINT (Std component) | 3 |
| ACTMTH, GLB_DTIME, GLB-REPORT, INPUT-DATE, ISPEC, XTRANNO | 6 |
| Descending key fields | 1 for each |
Notes:
Component arrays often result in a long Attribute.
In SQL Server, this limitation of allowing only a single field within a table to exceed 4000 characters is not present. However, this limit is enforced at the validation phase of Generate for all database types to ensure that specifications developed in Agile Business Suite are consistent for all deployed database types.
Size of Ispec Class or Profile Record in MCP-based Systems
Usage Input-Output and Usage Output Attributes are limited to an accumulated size of 4,065 words (24,570 characters), which is the DMS II record size limit.
Size of Ispec Class or Profile Record in Windows-based Systems
An Attribute Item of type long might not be used as a Key or Profile Key.
For SQL Server, the size of an index must be smaller than 900 bytes.
Byte length limit for Windows-based Systems
For Input/Output Ispecs that are to be generated to a Windows® operating system, there is a 4,000 byte data limit. The combined maximum size of user defined fields is 3,893 bytes. The remaining 107 bytes are made up of the following system-defined fields:
ACTMTH
LB.SOURCE
INPUT-DATE
MAINT
TRANNO
1 byte for the @-sign field
80 bytes for the status line
This limit is due to the internal buffer RDATA-AREA having a maximum length of 4,000 bytes. RDATA-AREA stores the Input/Output buffer for the Ispec. Anything over the 4,000 byte limit causes memory to be overwritten.
The limit is checked during the Model Validation phase of the Builder generate process. If the maximum length is exceeded an error is given and the generate is stopped.
Note: This limitation does not apply to Big Buffer Ispecs classes. For Input/Output Big Buffer Ispec classes, the maximum byte length is 65000 bytes for a Windows operating system.
Database Commands
In Windows-based systems there is no limit to the number of Database Commands.
In MCP-based systems, there is a limit of 999 references to other Ispec classes (all Events count as one reference) from an Ispec class.
Painted Items in an Ispec Class
For Windows and MCP-based systems the limit to the number of painted items in an Ispec Class, or a Copy.From area is as follows:
Limit of 320. Maximum of 100 items in the Copy.From area of the screen layout for a Copy.From Ispec classes.
Note: This limitation does not apply to Big Buffer Ispec classes. The maximum number of painted items in a Big Buffer Ispec class is 1000.
Internal Database Storage Order
In MCP-based systems, Ispec Attributes are stored in the database in the following order: alphanumeric items (in alphabetical order), numeric items (in alphabetical order), and a filler item if defined.
In Windows-based systems, Attributes used as Keys are defined first (in alphabetical order), followed by all other Attributes (in alphabetical order).
Ispec Class and Report Ordering
MCP is an EBCDIC-based platform, The Windows environment is ASCII based. Builder converts ASCII to EBCDIC during the generate file transfer process.
Because of this difference, Ispec and Report Classes appear differently in lists in Developer and MCP Runtime, when their names contain numeric characters. MCP Runtime displays the name containing the numeric after those with no numeric characters. Developer displays the name containing the numeric before those with no numeric characters. For example, MCP displays Ispec classes in the following order, ABCD, ABC2, while Developer displays them in the opposite order, ABC2, ABCD.
You must also be aware that the sort order is based on the collating sequence of the native character set for the host platform on which you are running the application. This affects the order in which items are stored and retrieved from the database.
You should make appropriate allowances for this if your application is to run on both Windows® and MCP operating systems.