This form of the INPUT statement is used to perform input
processing using a map layout that has been created using the Natural map
editor.
Map layouts can be used in two ways:
the program does not provide a parameter list;
the program does provide a parameter list
(operand1).
INPUT
[WINDOW='window-name']
[WITH-TEXT-option]
|
||
| [MARK-option] | ||
| [ALARM-option] | ||
[USING] MAP map-name [NO ERASE]
|
||
|
|
operand1
|
|
NO PARAMETER |
||
This document covers the following topics:
For an explanation of the symbols used in the syntax diagram, see Syntax Symbols.
The following requirements must be met when INPUT USING MAP
is used without parameter list:
The map-name must be specified
as an alphanumeric constant (up to 8 characters).
The map used in this manner must have been created prior to the compilation of the program which references the map.
The names of the fields to be processed are taken dynamically from the map source definition at compilation time. The field names used in both program and map must be identical.
All fields to be referenced in the INPUT statement must
be accessible at that point.
In structured mode, fields must have been previously defined (database fields must be properly referenced to processing loops or views).
In reporting mode, user-defined variables may be newly defined in the map.
When the map layout is changed, the programs using the map need not be recataloged. However, when array structures or names, formats/lengths of fields are changed, or fields are added/deleted in the map, the programs using the map must be recataloged.
The map source must be available at program compilation; otherwise the
INPUT USING MAP statement cannot be compiled.
Note:
If you wish to compile the program even if the map is not yet
available, specify NO PARAMETER: the INPUT USING MAP
can then be compiled even if the map is not yet available.
By specifying the names of the fields to be processed within the program
(operand1), it is possible to have the
names of the fields in the program differ from the names of the fields in the
map.
The sequence of fields in the program must match the map sequence. Please note that the map editor sorts the fields as specified in the map in alphabetical order by field name. For more information, see the map editor description in your Natural Editors documentation.
When the layout of the map is changed, the program using the map need not be recataloged. However, when field names, field formats/lengths, or array structures in the map are changed or fields are added or deleted in the map, the program must be recataloged.
A check is made at execution time to ensure that the format and length of the fields as specified in the program match the fields as specified in the map. If both layouts do not agree, an error message is produced.
Operand Definition Table:
| Operand | Possible Structure | Possible Formats | Referencing Permitted | Dynamic Definition | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
map-name
|
C | S | A | U | yes | no | ||||||||||||||
operand1
|
S | A | A | U | N | P | I | F | B | D | T | L | C | yes | yes | |||||
Syntax Element Description:
| Syntax Element | Description |
|---|---|
INPUT
WINDOW='window-name' |
INPUT WINDOW='window-name'
Option:
This option is described under
Syntax 1
of the |
WITH
TEXT/MARK/ALARM-options
|
WITH TEXT/MARK/ALARM Options:
These options are described under Syntax 1 of
the |
USING
MAP map-name
|
USING MAP Clause:
The The execution of the |
NO ERASE |
NO ERASE Option:
This option is described under Syntax 1 of the
|
operand1
|
Field Specification:
A list of database fields and/or user-defined variables. The fields must agree in number, sequence, format, length and (for arrays) number of occurrences with the fields in the referenced map; otherwise, an error occurs. When the content of a database field is modified as a result of
|
You can change the input mode with the session parameter
IM.
In forms mode (profile/session parameter
IM=F), Natural will
display all output text of the map layout on the terminal field by field
according to the positioning parameters. This permits the user to enter data on
a field by field basis. When all data are entered, the hardcopy output is
produced exactly as it would have appeared on the screen.
In forms mode, entering %R permits the operator to retype
the entire form in case of an error. The input is processed as in the first
execution of the INPUT statement.
In keyword/delimiter mode (profile/session parameter
IM=D), data can be
entered using keywords or positional input values.
- General Validation Rules
Data entered in keyword/delimiter mode are validated as for screen mode. An error message will be returned if an attempt is made to enter more characters than defined for a field.
If the
INPUTstatement is to be processed in keyword/delimiter mode on a buffered (3270-type) terminal or a workstation, all data to be assigned to oneINPUTstatement must be entered on one screen. ENTER is only to be used when all data to theINPUTstatement have been entered.- Keyword Input
Using keyword input, the terminal operator may enter data for the individual fields using the prompting text that, in forms mode, would have been displayed before the value as a keyword to identify the field. The keyword must be followed by the input assign character (
IAparameter), followed immediately by the data. Any spaces following the assign character are taken as data up to the delimiter character (IDparameter). A delimiter character is not required after the last data element. Keyword data for the different fields may be entered in any order separated by the delimiter character. If the operator types in a keyword which is not defined in theINPUTstatement, an error message will be returned. Data need not be entered for all input fields. Fields for which no data are entered are set to blank for alphanumeric fields and zero for numeric and hexadecimal fields.A keyword and the corresponding input field must be on the same logical line. If their aggregate length exceeds the line size, adjust the line size (
LSparameter) accordingly so that keyword and field fit onto one line.- Indexed Input
Using indexed input, the terminal operator may enter data for the individual input fields using their ordinal values prefixed with a percent character (%). This index specification must be followed by the input assign character (
IAparameter), followed immediately by the data.Indexed data for the different fields may be entered in any order separated by the delimiter character (
IDparameter). If the specified ordinal value does not correspond to that of any existing input field, an error message will be returned. Data need not be entered for all input fields. Fields for which no data are entered are set to blank for alphanumeric fields and zero for numeric and hexadecimal fields.- Positional Input
Using positional value input, the terminal operator enters only data for all input fields separated by the currently defined input delimiter character (
IDparameter). The sequence of fields for input must correspond to the sequence of the fields in theINPUTstatement.The user may switch from positional to keyword input by entering a number of values in positional input separated by the delimiter character and then switching to keyword mode for selected fields by specifying keywords in front of the values.
After a keyword has been used to position to a field, any non-keyword input following the keyword will be processed as positional input to be assigned to fields following the previously selected field in the
INPUTstatement.- Example of Keyword, Indexed and Positional Input
If you execute the following program
***** Program PGM1 ***** DEFINE DATA LOCAL 1 #F1 (A10) 1 #F2 (A10) 1 #F3 (A10) END-DEFINE INPUT (IP=ON) / 'FLD1' #F1 / 'FLD2' #F2 / 'FLD3' #F3 WRITE 'FLD1' #F1 / 'FLD2' #F2 / 'FLD3' #F3 ENDfrom the command line with any of the following commands, assuming the comma (
,) is used as the delimiter character
keyword input indexed input positional input positional input combined with keyword positional input combined with keyword combined positional and indexed input you will always receive the following output
FLD1 AA FLD2 FLD3 CC
Data elements that have been placed in the Natural stack via a
FETCH,
RUN or
STACK statement will be
processed by the next INPUT statement encountered for
execution.
The INPUT statement will process the data in
keyword/delimiter mode as described above.
If data elements are not available to fill all input fields, fields will be filled with blank/zero depending on the field format. If more data elements are specified than input fields exist, the remaining data are ignored.
When a field is filled with data from the stack, the field attributes do not apply to the data.
The Natural system variable *DATA may
be referenced to determine the number of data elements currently available in
the Natural stack.
The following topics are covered below:
A data record is read for each line containing one or more
AD=A and/or
AD=M fields, and the data contained in the record are assigned to
the appropriate field (or fields).
Input data fields are assumed to be contiguous. Unless the delimiter
character is used, input data must be entered in the exact length according to
the internal definition of the field. For numeric fields, space must be allowed
for a sign (if SG=ON) and decimal point when
appropriate.
Data may optionally be entered using the delimiter character to separate the values of the individual fields. In this case, data need not be entered in the exact number of positions according to the internal definition but are processed from left to right beginning in position 1. The rules for data entry are the same as described under Entering Data in Response to an INPUT Statement. In addition, the assign character may be used to skip a field.
Keyword/delimiter mode, when used in batch mode, functions the same as keyword/delimiter mode as used for stack input.
