Previous Topic: Format

Next Topic: Arithmetic Expressions


Operands

field-name1

can be either a new field, a glossary-defined field, or a field previously defined with a DEFINE or COMPUTE statement.

If it is a new field name, it can contain up to 16 characters. Blank characters are valid, but can only be used one at a time. Otherwise, the valid characters are the letters A through Z and the digits 0 through 9. The slash (/) character can also be used; it causes the characters of the name before it and after it to print as two separate lines on a column heading.

CA JARS Wizard establishes the field as a four-byte packed decimal field unless the field name has a suffix code specifying a different format.

If it is a new field, suffixes can be used to specify special attributes for field-name1. (Refer to Appendix B for a discussion on the suffixes.)

field-name2

must be a glossary-defined field or a field previously defined with a DEFINE, DECODE, or COMPUTE statement.

Field-name1 and field-name2 must have the same or similar format. Allowable combinations of formats are:

character and numeric
packed and numeric
packed and binary
binary and numeric

Field Format:

Can be converted to:

binary

numeric and packed formats

character

numeric format

numeric

binary, character, and packed formats

packed

binary and numeric formats

[(x,y)]

specifies a subfield within a character field, where x is the starting position and y is the length of the subfield. This is not valid for date or numeric fields.

value

can be any character or numeric literal. A character field can contain up to 255 letters, digits, and special characters. A numeric field can be up to 9,999,999 unless the field name has a suffix code establishing a larger format.

The keywords BLANK, BLANKS, SPACE, and SPACES can be used to establish values of blanks for character fields.

The keywords LOVALUE and LOVALUES can be used to establish values of zeros for numeric fields, according to the field's format.

fCCa-b

The CC notation refers to positions in a nonglossary file in the run.

a

specifies the starting position of the field in the record.

b

specifies the ending position of the field in the record.

f

specifies which physical file is being referenced, that is, f = 1 specifies the first physical file, etc. The f can be omitted if only one nonglossary file is present.