ADELIA |
VADELIA |
|
WADELIA |
|
(I) |
(I) (S) |
(I) (S) |
Section for use
All
Syntax
PLACE ViewName SeriesTransactionNum Parameter
PLACE ViewName SeriesWindowNames Parameter
SeriesTransactionNum |
→ |
SeriesTransactionNum TransactionNum |
| None |
||
SeriesWindowNames |
→ |
SeriesWindowNames WindowName |
| None |
||
Parameter |
→ |
*NO_MR | *MR | None |
Description
This instruction reads the file record associated with the view ViewName by the data flow and:
If the record exists:
the screen data is transferred to the corresponding file fields (those linked by the data flow).If the record does not exist:
the file fields are reset to blank, zero or *LOVAL, and the screen data is transferred to the corresponding file fields (those linked by the data flow).
The transaction numbers SeriesTransactionNum are optional. The system takes all the screen fields which are in the transactions mentioned in the instruction or, by default, those of the transaction which correspond to the validation block (where the instruction is), to generate the file field loading instructions.
With VADELIA programs, this instruction replaces transaction numbers with window names SeriesWindowNames.
This instruction must be followed by the CLASSIFY instruction.
This instruction can only be used on views used in the data flow.
Notes:
- The STORE instruction is equivalent to the PLACE and CLASSIFY instructions.
- The PLACE instruction can only be used if there was previously a PRESENT instruction (Adelia or Visual Adelia and Adelia Web context) for the view.
Important note: If the file associated with the view is specified having non-unique keys, the records are read via direct access (the system saves the sequence number upon PRESENT; see the "CPF4101 Error System" message.
The *MR parameter allows you to generate read implicit management rules that are linked to the entity corresponding to the view, even if the program is generated without the option to generate implicit management rules.
The *NO_MR parameter allows you not to generate read implicit management rules that are linked to the entity corresponding to the view, even if the program is generated with the option to generate implicit management rules.
Example
******************
VALIDATION 02
******************
ZORDER_DATE = &DATE6_FORMAT('MDY';'YMD';ZORDER_DATE)
PLACE ORDERS
*
ORDER_DATE = *DATE
ORDER_USER = *USER
CLASSIFY ORDERS
*
MANAGE_SFL 2
PLACE ORDER_LINES
ORD_LIN_DATE = *DATE
ORD_LIN_USER = *USER
CLASSIFY ORDER_LINES
END_MANAGE_SFL