Page History
...
Specifies either the field(s) that are to be browsed from the record in the file or the name of a group that specifies the field(s) to be browsed.FROM_FILE
Refer to Specifying File Names in I/O Commands.
| WHERE |
|---|
Refer to Specifying Conditions and Expressions.
| WITH_KEY |
|---|
Refer to Specifying File Key Lists in I/O Commands.
| NBR_KEYS |
|---|
This parameter can be used in conjunction with the WITH_KEY parameter to vary the number of key fields that are actually used to browse records at execution time.
...
If a user field is nominated to receive the return code, it must be alphanumeric with a length of 2. Even if a user field is nominated the special field IO$STS will still be updated.
For values, refer to I/O Return Codes.
| IO_ERROR |
|---|
Specifies what action is to be taken if an I/O error occurs when the command is executed. An I/O error is considered to be a "fatal" error. Some examples are file not found, file is damaged, and file cannot be allocated. These types of errors stop the function from performing any processing at all with the file involved.
...
For further information refer also to Load Other File in the Visual LANSA Developers Guide.
...
Specifies whether the "next function" field should be shown on line 22 of the screen. The next function field is a facility that allows transfer between the functions in a process without the need to return to the process menu each time. Refer to The Function Control Table in the LANSA for i User Guide for details about "next function" processing.*PRO, which is the default value, indicates that the "next function" field should appear only when the process to which this function belongs has a menu selection style of "FUNCTION". If the process menu selection style is "NUMBER" or "CURSOR" then the next function field should not appear.
...