HP 3000 Manuals HP 3000 Manuals
Data Division (cont.)
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The BELL Clause |
| |
|Function |
| |
|The BELL clause causes an audible alarm to occur each time the item |
|containing the clause is displayed. In order to cause the audible |
|alarm to sound when the clause is accepted, you must define the |
|BELL clause in General Format 5 of the ACCEPT statement: the |
|alarm will not sound if you define the BELL clause in the Screen |
|Description Entry and then use General Format 4 of the ACCEPT |
|statement. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. This clause is allowed only with elementary items. |
| |
|2. BELL and BEEP are equivalent. (MF) |
| |
| |
|General Rule |
| |
|The BELL clause causes an alarm to occur each time the item containing|
|the clause is accepted or displayed. |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The BLANK Clause |
| |
|Function |
| |
|During a DISPLAY operation, each subsidiary item within a screen-name |
|is displayed according to source sequence. When an item with BLANK |
|LINE is encountered, the line is cleared to spaces from the beginning |
|of the line to the end of the line. The cursor remains in the |
|same position as before the BLANK LINE was actioned. When an |
|item with BLANK SCREEN is encountered, the entire screen is |
|cleared to spaces and the cursor repositioned to line 1, column |
|1. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. The BLANK SCREEN clause can be specified in any screen |
| description entry. |
| |
|2. The BLANK LINE clause can be specified only for elementary |
| items. |
| |
| |
|General Rules |
| |
| |
| |
|1. The BLANK SCREEN clause is executed before DISPLAY of a screen |
| data item, no matter where it appears. If the clause is |
| specified, all the screen is cleared and the cursor is placed at |
| line 1, column 1. |
| |
|2. When BLANK LINE is specified, blanking begins at column 1 of |
| the line specified for the screen data element in whose |
| description it is included and continues through the end of the |
| line. |
| |
|3. If neither the BLANK nor the ERASE clause is specified, |
| only the particular character positions corresponding to |
| the screen data element are modified when the element is |
| displayed. The rest of the screen content remains the |
| same. |
| |
|4. The BLANK SCREEN clause causes the screen to return to its |
| default foreground and background colors. For additional |
| effects, if the screen item is subject to a FOREGROUND-COLOR or |
| BACKGROUND-COLOR clause, see the sections on those clauses. |
| |
|5. The BLANK clause is ignored in an ACCEPT statement. |
| |
|6. The erasing is done before the item is displayed. |
| |
|7. When the BLANK SCREEN clause is used, only color options |
| (foreground-color and background-color) should be used on |
| the same screen. Other attributes will be accepted but |
| ignored. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The BLANK WHEN ZERO Clause in the Screen Section Function |
| |
|The BLANK WHEN ZERO clause causes the blanking of a screen item when |
|its value is zero. |
| |
|General Format |
| |
| BLANK WHEN ZERO |
| |
|Syntax Rule |
| |
|This clause is allowed only with input, output and update fields that |
|are numeric or numeric-edited. |
| |
|General Rule |
| |
| |
| |
|1. The BLANK WHEN ZERO clause causes the blanking of a screen item |
| when its value is zero. |
| |
|2. This clause has no effect when the cursor is in the field, that |
| is the contents of the field are always displayed, even if zero, |
| if this is the current input field. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The BLINK Clause |
| |
|Function |
| |
|The BLINK clause causes the screen item to blink when it appears on |
|the screen. |
| |
|General Format |
| |
| BLINK |
| |
|Syntax Rules |
| |
| |
| |
|1. The BLINK clause is allowed with any screen item. |
| |
|2. If the BLINK clause is specified at group level, it applies to |
| all suitable subordinate elementary items. |
| |
| |
|General Rule |
| |
|The BLINK clause causes the screen item to blink when it appears on |
|the Screen. |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The COLUMN Clause |
| |
|Function |
| |
|The COLUMN clause specifies the column at which the screen item starts|
|on the screen. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. Identifier-l must be an unsigned numeric integer and must contain|
| a value greater than zero and less than 256. |
| |
|2. Integer-l must be unsigned, greater than zero and less than |
| 256. |
| |
|3. PLUS and "+" are equivalent. |
| |
|4. Omitting the NUMBER option results in a default value of |
| +1. |
| |
|5. COLUMN 1 is assumed for screen descriptions which specify the |
| LINE clause but omit the COLUMN clause. |
| |
|6. The COLUMN clause can be specified with any elementary |
| item. |
| |
|7. COL is an abbreviation for COLUMN. (MF) |
| |
| |
|General Rules |
| |
| |
| |
|1. The COLUMN clause specifies the column in which the screen |
| item is to appear on the screen in an ACCEPT or DISPLAY |
| operation. |
| |
|2. If the COLUMN clause has an identifier or an integer but does not|
| specify PLUS, "+" or "-", the clause gives an absolute |
| column number. Column 1 is the column number specified |
| in the AT phrase of the statement. If the AT phrase is |
| not specified, then column 1 is the first column on the |
| screen. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
| |
| |
|3. If PLUS, "+" or "_" is specified in the COLUMN clause, then the |
| column number is relative to that at which the preceding screen |
| item ends, regardless of whether or not the statement displays |
| the preceding item on the screen. This depends on the |
| current effective length of that item at run-time, derived |
| from its PICTURE, VALUE and SIZE clauses. The counting |
| of column numbers restarts at a level 01 item at column |
| 1. |
| |
|4. If a Screen Description contains neither a LINE or COLUMN clause,|
| and the item is not a level 01 item, COLUMN+1 is assumed. The |
| item then starts immediately following the preceding item in the |
| Screen Section. |
| |
|5. If a COLUMN position is specified that is off the screen, |
| wraparound occurs to the next (or previous) line. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The CONTROL Clause |
| |
|Function |
| |
|The CONTROL clause allows attributes associated with a screen section |
|item to be defined at run-time. |
| |
|General Format |
| |
| [CONTROL IS identifier-1] |
| |
|Syntax Rules |
| |
| |
| |
|1. This clause is allowed with any screen item. |
| |
|2. If this clause is specified at group level, it applies to all |
| elementary subordinate items. |
| |
|3. Identifier-1 must be an alphanumeric data item. The maximum |
| permitted size of the item is PIC X(65535). |
| |
|4. Attributes specified in identifier-1 override any statically |
| defined attributes. |
| |
|5. CONTROL statements must not be nested. |
| |
|6. Identifier-1 must not be subject to an OCCURS clause. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|General Rules |
| |
| |
| |
|1. The attributes which can be specified in the CONTROL clause are a|
| subset of the screen section syntax as shown below. |
| |
________________________________________________________________________
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
| |
| |
|2. If identifier-1 contains spaces, the statically defined |
| attributes are used for any accept or display of the item. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The ERASE Clause |
| |
|Function |
| |
|The ERASE clause clears part of the line or the screen starting at the|
|cursor position. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rule |
| |
|The ERASE clause can be specified only for elementary items. |
| |
|General Rules |
| |
| |
| |
|1. When ERASE EOL is specified, blanking begins at the line and |
| column coordinates specified for the screen data element in whose|
| description it is included and continues through the end of the |
| line. |
| |
|2. When ERASE EOS is specified, blanking begins at the line and |
| column coordinates specified for the screen data element in whose|
| description it is included and continues through the end of the |
| screen. |
| |
|3. If neither the BLANK nor the ERASE clause is specified, |
| only the particular character positions corresponding to |
| the screen data element are modified when the element is |
| displayed. |
| |
|4. The clause is ignored in an ACCEPT operation. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The FOREGROUND-COLOR Clause |
| |
|Function |
| |
|The FOREGROUND-COLOR clause specifies the foreground color of the |
|screen item. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. FOREGROUND-COLOR and FOREGROUND-COLOUR are equivalent. |
| |
|2. This clause is allowed with any screen item. |
| |
|3. If this clause is specified at group level, it applies to all |
| elementary subordinate items. |
| |
|4. Integer-1 must be a value from 0 to 7. |
| |
| |
|General Rules |
| |
| |
| |
|1. This clause is only available for use with a color screen. |
| |
|2. Integer-1 or identifier-1 specifies the foreground color of the |
| screen item. The colors and their corresponding values |
| are: |
| |
| |
| 0 black |
| 1 blue |
| 2 green |
| 3 cyan |
| 4 red |
| 5 magenta |
| 6 brown or yellow |
| 7 white |
| |
| |
|3. If this clause is not specified, the foreground color defaults to|
| white. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
| |
| |
|4. to one that does, then when the screen item is displayed by a |
| DISPLAY statement the specified color becomes the default |
| foreground color. It remains the default foreground color until |
| either another screen item with this combination of options |
| is displayed (whether in the same DISPLAY statement or |
| another), or a Format 3 DISPLAY statement with both options is |
| executed. |
| |
|5. If the HIGHLIGHT clause is also specified, foreground colors are |
| brightened and lightened; for example on some hardware, black can|
| become grey and brown can become yellow. However, this does not |
| apply to the BLANK SCREEN clause. |
| |
|6. Identifier-1 must be an unsigned numeric integer and should |
| contain a value between 0 and 7. Any value higher than 7 |
| will be divided by 8 and the remainder used as the color |
| value. |
| |
|7. Identifier-1 must not be subject to OCCURS clauses. |
| |
|8. Whether a value of 6 in integer-1 or identifier-1 produces brown |
| or yellow depends on the terminal hardware. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The FULL Clause |
| |
|Function |
| |
|The FULL clause specifies that the operator must either leave the |
|screen item completely empty or fill it entirely with data. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. The FULL clause is valid only in input and update fields and |
| group item. |
| |
|2. If this clause is specified at group level, it applies to all |
| suitable subordinate elementary item. |
| |
|3. FULL and LENGTH-CHECK are equivalent. (MF) |
| |
| |
|General Rules |
| |
| |
| |
|1. The FULL clause is effective during the execution of any |
| ACCEPT statement that causes the screen item to be accepted |
| provided the cursor enters the screen item at some time during |
| the ACCEPT operation. Until this clause is satisfied, |
| terminator keystrokes are rejected. If the item is fixed-format |
| numeric-edited, the cursor is repositioned to the decimal point |
| position. |
| |
|2. If the screen item is alphanumeric, then to satisfy this clause, |
| either the entire item must contain only spaces or prompt |
| characters, or the first and last character positions must |
| contain non-space, non-prompt characters. |
| |
|3. If the screen item is free-format numeric or free-format |
| numeric-edited, then to satisfy the clause, either the |
| resultant value must be zero, or both the first and last |
| character positions must contain non-space, non-prompt |
| characters. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
| |
| |
|4. If the screen item is fixed-format numeric-edited, then to |
| satisfy the clause either the value must be zero or there must be|
| no digit positions in which zero-suppression has taken |
| effect. |
| |
|5. The FULL clause has no effect on fixed-format numeric or on |
| numeric-edited screen items that have no zero- suppression |
| positions. |
| |
|6. For update fields, the FULL clause can be satisfied by initial |
| data as well as operator-keyed data. |
| |
|7. The FULL clause can not be effective if a function key is used to|
| terminate the ACCEPT operation. (See your COBOL System Reference|
| for details of configuration options.) |
| |
|8. An error message can be configured for display on the screen if |
| the FULL clause is not satisfied. (See your COBOL System |
| Reference for details of configuration options.) |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) |
| |
|The GRID Clause |
| |
|Function |
| |
|The GRID clause causes each character of the screen item to have a |
|vertical line on its left-hand side when the item appears on the |
|screen. Each line is within the character-position. |
| |
|General Format |
| |
| GRID |
| |
|Syntax Rules |
| |
| |
| |
|1. The GRID clause can be used with any screen item. |
| |
|2. If the GRID clause is specified at group level, it applies to all|
| suitable subordinate elementary items. |
| |
|3. If this clause is used on a system that does not support |
| characters with vertical left-hand lines it has no effect. |
| |
| |
|General Rule |
| |
|The GRID clause causes each character of the screen item to have a |
|vertical line on its left-hand side when the item appears on the |
|screen. Each line is within the character-position. |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The HIGHLIGHT Clause |
| |
|The HIGHLIGHT clause causes the screen item to appear in high |
|intensity mode when it appears on the screen. |
| |
|General Format |
| |
| HIGHLIGHT |
| |
|Syntax Rules |
| |
| |
| |
|1. This clause is valid for input, output, update or literal |
| fields. |
| |
|2. If the HlGHLlGHT clause is specified at group level, it applies |
| to all suitable subordinate elementary items. |
| |
| |
|General Rule |
| |
| |
| |
|1. If the FOREGROUND-COLOR clause is a]so specified, the HIGHLIGHT |
| clause causes the foreground colors to become brighter and |
| lighter; for example on some hardware, black can become grey and |
| brown can become yellow. |
| |
|2. This does not apply to the blank screen clauses. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The JUSTIFIED Clause in the Screen Section |
| |
|Function |
| |
|The JUSTIFIED clause specifies non-standard positioning of data within|
|a screen item when data is either moved to it or entered into |
|it. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. JUST is an abbreviation for JUSTIFIED. |
| |
|2. The JUSTIFIED clause is allowed only with input, output and |
| update fields. |
| |
| |
|General Rules |
| |
| |
| |
|1. If the screen item is an output or update field, when data is |
| moved to it from the sending item, the JUSTIFIED clause is |
| applied according to the normal rules for MOVE. |
| |
|2. If the screen item is an input or update field, when the |
| accepting of data into it has terminated, the JUSTIFIED clause |
| causes the data entered to be moved right by the number of |
| character positions occupied by prompt characters, and the left |
| of the field to be padded with spaces. This is done before the |
| data is moved to the receiving item. This does not occur if data|
| is not entered. |
| |
|3. If the screen item has a SECURE clause, the effect on the |
| data is the same as it would be without the presence of |
| the SECURE clause, but this effect does not appear on the |
| screen. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) |
| |
|The LEFTLINE Clause Function |
| |
|The LEFTLINE clause causes the leftmost character of the screen |
|item to have a vertical line on its left-hand side when the |
|item appears on the screen. The line is within the character- |
|position. |
| |
|General Format |
| |
| LEFTLINE |
| |
|Syntax Rules |
| |
| |
| |
|1. The LEFTLINE clause can be used with any screen item. |
| |
|2. If the LEFTLINE clause is specified at group level, it applies to|
| all suitable subordinate elementary items. |
| |
|3. If this clause is used on a system that does not support |
| characters with vertical left-hand lines it has no effect. |
| |
| |
|General Rule |
| |
|The LEFTlINE clause causes the leftmost character of the screen item |
|to have a vertical line on its left-hand side when the item appears on|
|the screen. The line is within the character-position. |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The LINE Clause |
| |
|Function |
| |
|The LINE clause specifies the line at which the screen item starts on |
|the screen. |
________________________________________________________________________
General Format
Click here to view figure.
________________________________________________________________________
|(MF) (XOPEN) |
| |
|Syntax Rules |
| |
| |
| |
|1. Identifier-l must be an unsigned numeric integer and must contain|
| a value greater than zero and less than 256. |
| |
|2. Integer-1 must be unsigned, greater than zero and less than |
| 256. |
| |
|3. PLUS and "+" are equivalent. |
| |
|4. Omitting the NUMBER option results in a default value of |
| +1. |
| |
|5. The current line is assumed for screen descriptions which omit |
| the LINE clause. |
| |
|6. The LINE clause can be specified with any elementary item. |
| |
| |
|General Rules |
| |
| |
| |
|1. The LINE clause specifies the line on which the screen |
| item is to appear on the screen in an ACCEPT or DISPLAY |
| operation. |
| |
|2. If the LINE clause has an identifier or an integer but does not |
| specify PLUS, "+" or "-", the clause gives an absolute line |
| number. Line 1 is the line number specified in the AT phrase of |
| the statement. If the AT phrase is not specified, then line 1 is|
| the first line on the screen. |
| |
|3. If PLUS, "+" or "-" is specified in the LINE clause, then the |
| line number is relative to that at which the preceding |
| screen item ends, regardless of whether or not the statement |
| displays the preceding item on the screen. This depends on |
| the current effective length of that item at run-time, |
| derived from its PICTURE, VALUE and SIZE clauses. The |
| counting of line numbers restarts at a level 01 item at line |
| 1. |
| |
|4. If a Screen Description contains neither a LINE or COLUMN clause,|
| and the item is not a level 01 item, COLUMN +1 is assumed. The |
| item then starts immediately following the preceding item in the |
| screen section. |
| |
|5. If a LINE position is specified that is off the screen, the |
| ACCEPT or DISPLAY is truncated. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The LOWLIGHT Clause |
| |
|Function |
| |
|The LOWLIGHT clause specifies that the field is to appear on the |
|screen with the lowest intensity. |
| |
|General Format |
| |
| LOWLIGHT |
| |
|Syntax Rule |
| |
|The LOWLIGHT clause can be specified only for an elementary screen |
|description entry. |
| |
|General Rule |
| |
|The LOWLIGHT clause specifies that the field is to appear on the |
|screen with the lowest intensity. |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The OCCURS Clause in the Screen Section Function |
| |
|The OCCURS clause eliminates the need for separate entries for |
|repeated screen items and supplies information required for the |
|application of subscripts or indices. |
| |
|General Format |
| |
| OCCURS integer-1 TIMES |
| |
|Syntax Rules |
| |
| |
| |
|1. This clause is allowed only with input, output and update fields |
| and with group items. |
| |
|2. If OCCURS clauses apply to the screen item, then the same number |
| of OCCURS clauses, specifying the same number of occurrences, |
| must apply to the receiving item. These OCCURS clauses must not |
| include the DEPENDING phrase. |
| |
|3. If OCCURS clauses apply to the screen item, either the same |
| number of OCCURS clauses, specifying the same number of |
| occurrences, or no OCCURS clauses at all, must apply to the |
| sending item. These OCCURS clauses must not include the |
| DEPENDING phrase. |
| |
| |
|General Rules |
| |
| |
| |
|1. In a Screen Description which is subject to an OCCURS clause, the|
| LINE and COLUMN clauses apply to each individual table |
| entry. Thus either the LINE or the COLUMN clause should |
| specify relative positioning, because if they both specify |
| an absolute position every entry will appear in the same |
| place. |
| |
|2. If the screen item is an output field, and no OCCURS clauses |
| apply to the sending item, then in a DISPLAY operation the |
| contents of the sending item are moved to every occurrence of the|
| screen item. An elementary item that is fully subscripted is |
| deemed to have no OCCURS clauses applying to it. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
| |
| |
|3. If the screen item is an update field, or it is an output field |
| with OCCURS clauses applying to the sending item, then in a |
| DISPLAY operation the contents of each occurrence of the sending |
| item are moved to the corresponding occurrence of the screen |
| item. |
| |
|4. If the screen item is an update or input field, then in an ACCEPT|
| operation the data entered into each occurrence of the screen |
| item is moved to the corresponding occurrence of the receiving |
| item. |
| |
________________________________________________________________________
________________________________________________________________________
|(MF) (XOPEN) |
| |
|The OVERLINE Clause |
| |
|Function |
| |
|The OVERLINE clause causes every character of the screen item to have |
|a horizontal line above it when the item appears on the screen. The |
|line is within the character-position. |
| |
|General Format |
| |
| OVERLINE |
________________________________________________________________________