Object Type Administration

• must have at least three characters and start with a letter (a-z, A-Z).

• must not contain blanks.

• must be unique, and must not be an abbreviated form of an existing object type (for example, Key is not permitted because it could be confused with the predefined object type Keyword).

• must not start with an object type that already exists (for example, Filecard is not permitted).

String that is used in Predict menus and output screens for the respective object type. Can be up to 17 characters long and contain numbers, special characters and blanks.

If no title is specified, the object type name with the first character capitalized will be taken as title.

The associations specified, apply as default values in Predict functions for thedefault parent parameter (for example, in system parameter in maintenance screens of the user-defined object type change enhancement).

Only user-defined association types can be specified.

Up to five maintenance screens can be defined for each object type. When a number between 1 and 5 is entered, the corresponding screen for attribute definition is selected. Only an existing screen or the next free screen can be selected.

If zero is entered, the Metadata Administration menu appears. If 'H' is entered, the header is displayed.

• line (1 < line < 15)

• column (1 < column < 78)

• line (1 < line < 15)

• column (1 < column < 78)

external verification (special check)

For type X (literal) neither edit masks nor verifications can be defined; for type L (logical) no verifications can be defined.

Attributes for which a verification rule with a table of values has been defined must be filled in maintenance screens (mandatory fields). Attributes with a verification rule that allows blank values need not be filled explicitly.

Use the following 24 fields to define the verification values.

For any defined Value_X, AA is a mandatory field with one of the following possible values: EQ (equal), NE (not equal), LT (less than), LE (less than or equal), GT (greater than), GE (greater than or equal). If you enter an asterisk, the possible values are displayed in a selection window.

Value_X are the verification values. Up to six verification values can be defined.

For type A (alphanumeric), the length is restricted to 32 - independent of the length of the attribute itself.

For type N (numeric), the following applies: a maximum of 20 digits before and 7 digits after the decimal point can be entered.

If DATE is entered for type D (date), the verification value is the current date.

BBB is one of the possible values AND or OR which combines the two elementary conditions of one line in a boolean expression.

CCC combines the boolean expressions defined in each line with the operand AND or OR. The logical expressions are always processed line by line.

In the following fields, you can define up to three object attributes, which are defined in one maintenance screen, as input parameters for the subprogram. If you enter an asterisk, the names of the object attributes of this maintenance screen are displayed in a selection window.

Attributes of type X (literal) cannot be defined as input parameters for the subprogram.

The values of these attributes are passed to the defined subprogram in alphanumeric format (length 78) as follows:

• type A: left aligned with leading blanks. If Case = U, letters are converted to capital letters.

• types D and T: right aligned according to their internal representation.

• type L: left aligned; "1" for TRUE and "0" for FALSE.

• type N: right aligned without decimal point. All places after the decimal point (according to the attribute definition) are passed. The number of places after the decimal point is passed by an additional parameter. With negative values, the sign is passed as well. Leading zeros are suppressed.

The following CALLNAT statement is generated:

CALLNAT 'subprogram'
PAR1 PAR2 PAR3
RETURN-CODE RETURN-TEXT1 RETURN-TEXT2

PAR1 PAR2 PAR3:

values of the attributes (format A78);

RETURN-CODE:

number of a Predict error message (format I2); RETURN-TEXT1 and RETURN-TEXT2: texts as parameters for this error message (format A34).

In the subprogram, attribute values of the types D, N, and T can be converted using the Natural function VAL.

The verification rules are processed screen by screen. Independent of the sequential numbers of the attributes to be verified, the verification rules with external verification routines are processed last - they are only processed after all verification rules with tables of values and ranges of values have been processed.