Generation of the data flow in SQL access mode
Note: When the logical entity has a default logical server, the instructions related to the entity will automatically be assigned to the logical server.
In the example below, <S1> is the default logical server of ENTITY1, and <S2> is the default logical server of ENTITY2.
Typical structure
* For the window BEGIN_STD_DFL <S1> CHAIN_SQL ENTITY1 *COND(ACCESS_FIELD1=:HOST_VAR1 AND ....) <S1> INSERT_STD ENTITY1 INSERT_STD END_STD_DFL * For a list BEGIN_STD_DFL CLEAR_LST <window.object:list_prop> <S2> LOADING_LST LDG_ENTITY2 <S2> INSERT_STD ENTITY2 <S2> INSERT_STD <S2> INSERT_ELT <window.object:list_prop> <S2> END_LOADING_LST END_STD_DFL |
The condition for the CHAIN_SQL instruction generated depends on the access path specified.
As regards the host variables of the SQL condition, those taken into account are:
The first Input/Output screen field whose origin is the logical property defined in the entity's access.
The first screen field whose original logical entity is different from the entity processed, but has the same original conceptual property.
The field of the entity which constitutes the access.
Click below for further information about: