Maintaining Objects of Type Verification

This document covers the following topics:

For general information on how to manage objects (for example, how to add or copy an object), see the Object Description documentation.

Verification Status

The table below contains a list of all valid verification status.

Code Verification Status
A Automatic
C Conceptual
D Documented (no rule)
F Free
N Natural Construct
S SQL

Verification Formats

The table below contains a list of all valid verification formats.

Code Format
A Alphanumeric
B Binary
D Date/time
K Function key
L Logical
N Numeric
blank Unknown (no rule defined)

Add a Verification

When you add a verification, you first have to specify the verification status in the Type dialog box.

Select type

When you choose the OK button, a verification status-specific window appears. The verification status is indicated in the title bar.

Verification attributes

Note:
The tabs Documented Processing rule and Activated Processing rule are only shown for specific verification status. Parameters not listed here are described under Global Attributes.

Parameters
Status The status assigned by Predict to the verification rule. See Verification Status for list of valid values.
Format The format of the verification rule. See Verification Formats for list of valid values.
Modifier User and or user groups defined in Natural Security who can be authorized to modify free rules of the verification. This information is specified on the Modifier tab.

The parameter is evaluated by Predict according to the setting of the default parameters Rule in Map Editor / Rule in SYSDIC. If any of these parameters is set to force, Predict checks the following:

  • that at least one modifier is specified,

  • that each modifier of the object is a Natural Security administrator, person or group,

  • that the user is listed as a modifier of the object.

See also description of Rule in Map Editor / Rule in SYSDIC in the section Defaults in the Predict Administration documentation and Protecting Processing Rules in the section Protecting External Objects in Predict with Natural Security in the Predict Security documentation.
Type The type of rule. The table also shows the number of values to be specified with each type of rule:
Code Type of Rule No. of Values
E Equal to 1
0 or 1 for format logical
G Greater than 1
L Less than 1
N Not equal to n
0 or 1 for format logical
R Range of values 2
T Table of values n
U User routine  
B Range, but not 3 or 4
I Not in range 2
M Mask n
O Not Equal Mask n
S Scan n
V Not Equal Scan n
blank (none) - no rule defined  
For a list of the generated code, see Rule Editor in the Predict Reference documentation. .
Message nr Number of Natural error message. The message will be displayed if a validation fails. Up to three replacement strings can be inserted into an error message if the respective targets (:1:, :2:, :3:) are provided.
Replacement Strings to be inserted into a Natural message. See description of Message nr above.
Message text Message to be displayed if a validation fails. A standard message will be created if neither Message text nor Message nr have been specified.
Values The values used to perform the verification. The following rules apply:

  • The number of values to be specified depends on the verification type. See table above.

  • Values are delimited

    • with blanks

    • with the Natural INPUT delimiter character (ID) defined in the Natural environment

    • by entering them in separate lines.

  • Hexadecimal values can be specified in two ways:

    • if Format=B, hexadecimal values can be specified directly. Example: F0

    • if Format=A, hexadecimal values must be preceded by uppercase X or H and be enclosed in single quotes. Example: X'F0' or H'F0'

  • Blanks can be specified in one of the following ways: ' ', BLANK or SPACE. Strings that include blanks must be enclosed in single quotes, apostrophes in strings have to be doubled (for example: 'six o''clock').

  • Line comments can be specified by preceding them with /* (a slash and an asterisk). Line comments can be used by SYSHELP as descriptive text in input windows. Strings that include the comment delimiter /* must be enclosed in single quotes.