Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

7.12.1 CHANGE Parameters

FIELD

PRECISION

ROUND_UP

TO


Anchor
FIELD
FIELD
FIELD

Specifies the name(s) of the field(s), list(s) or expandable group expression which is/are to be changed.

Anchor
TO
TO
TO

Specifies the new value which field(s) nominated in the FIELD parameter are to take on. The new value specified can be another field name, an alphanumeric literal, a numeric literal, a system variable, a process parameter or an expression involving any of these in combination.

...

Special Value

FIELD type

Notes

*NULL

Integer, Float, or Boolean

Treat as per Signed/Packed, i.e. *ZERO (For Boolean *ZERO means Off/False)

*NULL

Date or Datetime

1900-01-01

*NULL

Time

Midnight (00:00:00)

*NULL

Char, String, Binary, VarBinary, CLOB, BLOB

Empty string. Note that this is considered equivalent to *BLANKS for comparisons.

BLOB & CLOB: Filename is empty.

*NAVAIL

Integer, Float, Time or Boolean

As for Signed/Packed, i.e. *ZERO

*NAVAIL

Date,Datetime, Binary, VarBinary

FFC Error as cannot put character string into these fields

*NAVAIL

Char, String, CLOB, BLOB

As for Alpha.

BLOB & CLOB: Filename is "N/AVAILABLE".

*DEFAULT

Any

Field default

*SQLNULL

Any

If the field does not have the ASQN attribute it is an FFC Error. Otherwise, it is okay.

*HIVAL
*LOVAL

Integer

Set to the maximum value (positive) for the integer.
Set to the minimum value (negative) for the integer. If a field has SUNS attribute, minimum is *ZERO.

*HIVAL
*LOVAL

Boolean

Set to On/True.
Set to Off/False.

*HIVAL

*LOVAL

Float, Date,Time

FFC Error as no logical upper or lower, especially for Date, as different databases support different values.

*HIVAL

*LOVAL

Datetime

*TIMESTAMP_HIVAL

*TIMESTAMP_LOVAL

*REMEMBERED_VALUE*

CLOB, BLOB, Date, Time, Datetime, Integer, Float, Boolean

Store in the registry as a string, as per current fields.

*REMEMBERED_VALUE*

Char, String

There may be a limit to the size of the string that may be stored (Char/String allows up to 64Kb). If there is a limit, and the field size is greater than the limit, FFC Error. If there is no limit, or the field size is less than the limit, store it in the registry as a String, as per current fields.

*REMEMBERED_VALUE*

Binary, VarBinary

There may be a limit to the size of the string that may be stored (Binary/VarBinary allows up to 32Kb). If there is a limit, and the field size is greater than the limit, FFC Error. If there is no limit, or the field size is less than the limit, store it in the registry as a Binary.

Anchor
PRECISION
PRECISION
PRECISION

Specifies, for numeric expressions only, what precision is to be used for any intermediate work fields generated by the RDML compiler. When a numeric expression is evaluated the RDML compiler, by default, attempts to compute the precision of any intermediate work fields. This is what happens when this parameter is not specified, or specified using the default values.

...

It would be unusual to code a PRECISION parameter in which the number of decimals required was less than the number of decimals in any individual field involved in the expression.

Also See

Field Types


Anchor
ROUND_UP
ROUND_UP
ROUND_UP

Specifies, for numeric and date-time expressions only, whether or not the result of the expression is to be "rounded up" before it is placed into the result field nominated in the FIELD parameter.

...