Handling of Parameter Values

Jade handles initialization file parameter values as follows.

• The value for a Jade initialization file section and parameter pair can be <default> (which is case‑insensitive). This applies to all primitive types; for example, Boolean, Integer, or String.

  If you specify a parameter value of <default>, Jade uses what it recognizes as the correct default value. This enables you to have a parameter in your initialization file and have a reasonable default value used so that if the default value changes between releases, you do not have to change the parameter value to ensure that an out-dated default value is not used.

• If the Integer values of some parameters are sizes (for example, a maximum file size or a buffer size), you can replace a large value decimal notation such as 22020096, which is difficult to read, with the corresponding measure of storage and memory, or 21M in this example. As simple numbers continue to be supported, you do not have to change existing parameter values unless you want to do so.

  A number can be followed by a case‑insensitive K, M, G, T, or P prefix multiplier. This multiplies the prefix number by 1024 (1 kilo), 1048576 (1 mega), 1073741824 (1 giga), 1099511627776 (1 tera), or 1125899906842624 (1 peta), respectively.

  These prefix multipliers are binary multiples; that is, they are multiples of 1,024 rather than of 1,000.

  As the number must be an integral value (which has no decimal points), a value of 1.5M is treated as 1 and not as 1048576. You can use 1572864 or 1536K if you want a value of one and a half megabytes. If the specified number is too large, Jade reduces this to the appropriate value; for example, if you specify an ObjectCacheSizeLimit parameter value of 10G bytes, this is reduced to 2^32 (4294967296, or 4G) bytes.

  These prefix multipliers apply only to Jade initialization file parameters and sections defined by Jade (that is, this facility is not supported in parameters and sections that you define).