{ COLUMN } { NUMBER } { IS } integer-1 { PLUS } integer-2{ COLUMNS } { NUMBERS } { ARE } { + }{ COL }{ COLS }NOTE: Columns might not line up in a report if the printable characters are not of a fixed size, such as in the characterset UTF-8.NOTE: The value of integer-2 minus 1 is the number of blank columns, if any, immediately preceding the item.
{POS }
1.
2. PLUS and '+' are synonyms.
3. Data-Name-3 shall be described in the file, working-storage or linkage section as an elementary unsigned integer data item.
4. Neither the PLUS phrase nor the '-' phrase shall be specified for the first elementary item in a screen record.
1. The COLUMN clause specifies the column in which the leftmost character of the screen item is to appear on the screen during the execution of an ACCEPT screen or a DISPLAY screen Statement. Positioning of the screen record and within the screen record appears the same on the terminal display regardless of whether the whole screen record or just a portion of it is referenced in an ACCEPT screen or a DISPLAY screen Statement.
2. If the COLUMN clause does not specify PLUS or MINUS, the clause gives the column number relative to the first column of the screen record. A column number of 1 represents the first column of the screen record.
3. If the PLUS or '-' phrase is specified in the COLUMN clause, the column number is relative to the end of the preceding screen item in the same screen record, such that if COLUMN PLUS 1 is specified, the screen item starts immediately following the preceding screen item. PLUS denotes a column position that is increased by the value of Data-Name-3 or Integer-3. '-' denotes a column position that is decreased by the value of Data-Name-3 or Integer-3.
4. A setting of COLUMN 1 is assumed for screen descriptions that specify the LINE clause but omit the COLUMN clause.
5.
a. if no previous screen item has been defined, LINE 1 COLUMN 1 of the screen is assumed.
b. if a previous screen item has been defined, the line of that previous item and COLUMN PLUS 1 is assumed.
| Copyright (c) 2017 Veryant |
| Contact us |
|
Please share your comments on this manual or on any Veryant product documentation with the email button at the top left |