ADELIA |
|
|
|
|
(I/B) |
|
|
|
|
Section for use
INITIALIZATION, VERIFICATION, VALIDATION, BATCH PROCESSING, or any other interactive section when the transaction number is indicated.
Syntax
PRESENT ViewOrEntity Transaction Option
Transaction |
→ |
TransactionNum | None |
|
|
|
Option |
→ |
*FORCE | None |
Description
This instruction loads the file fields into the corresponding layout fields, after reading the file associated with the view View via the data flow.
If the *FORCE option is not mentioned and the previous attempt to read the view or the previous SQL read operation in the entity was unsuccessful (record not found), two things can happen:
fields are set to blank or zero if there is not any default value;
default value is moved into screen field wherever there is a default value.
In an interactive context:
If the transaction number is not mentioned after the guide word of the view, this instruction only affects the screen fields of the transaction where the instruction is.
If the transaction number is mentioned after the guide word of the view, the instruction affects the screen fields of the indicated transaction.
In a batch context: the instruction concerns the print fields associated with the view via the data flow.
This instruction is only applicable to views used by the data flow.
See also the PRINT_VIEWS instruction.
Example
Use with a view:
**********************
INITIALIZATION 02
**********************
CHAIN ORDERS
PRESENT ORDERS
CHAIN PAYMENTS
PRESENT PAYMENTS
*
* Note that PRESENT will blank out fields in case the order does not exist
*
MANAGE_SFL 2
* loading all order lines in subfile 2 and getting the item description
PRESENT ORDER_LINES
ZORDER_DATE = &DATE6_FORMAT('YMD';'MDY';ZORDER_DATE)
CHAIN ITEM
PRESENT ITEM
LAST_NUMBER = ZORDER_LINE_N
UPD_SFL
END_MANAGE_SFL
Use with an entity:
CHAIN_SQL ORDERS *COND(CORD_NUM = :ZORD_NUM)
PRESENT ORDERS