The code that is generated for a Logical View is in the program body or in the elementary levels that are run by PERFORM. This code contains the standard processing for the implementation of the services in the Logical View. This standard processing is associated with only one Logical View. To add a specific processing, you must then insert it relatively to a standard processing of the Logical View. It is inserted after the automatically generated tag or associated condition.
The information that you enter, except the action type, is identified in the Macro code as:
REF=Processing type Category Service Elementary processing
Processing types | Comments | Associated fields |
---|---|---|
BEGV: Logical View beginning | No comment | Action type |
CCNX: Connect to database | No comment | Action type |
CHKD: Check data | The Data Elements that are called in the Logical View are checked. The data that the user enters is checked and an error is sent if the input is erroneous. | Data Element code, Category, Action type |
CHUP: Check and update | This processing carries out the following actions:
|
Service, Category, Action type |
CLOS: Close | This processing closes the indexed files of the Logical View. You must specify the file code (Data Structure code). | File code, Action type |
DCNX: Disconnect from database | No comment | Action type |
ENDV: Logical View ending | No comment | Action type |
ERRV: Logical View errors | This processing manages the errors on a service request. | Action type |
LOCK: Lock | This processing blocks data update to avoid simultaneous updates. It prevents inconsistencies. | Action type |
OPEN: Open | This processing opens the indexed files of the Logical View. You must specify the file code (Data Structure code). | File code, Action type |
SELC: Selection | This processing carries out the following actions:
|
Service, Category, Action type |
TRDT: Transfer View to Segment | This processing transfers data from the Logical View to the Segments. | Category, Action type |
TRER: Errors transfer | This processing transfers the errors when a second-level Business Component is called. You must indicate the code of the Segment where the error can be detected | Segment code, Action type |
TRVW: Transfer Segment to View | The second-level Business Component transfers the data from the Segment to the Logical View. | Category, Action type |
UNLK: Unlock | No comment | Action type |
USER: User service | This processing runs a special service that
is not a selection service or a check and update service. You can
create a user service, for example, to count the number of persons
who put in an order or to describe a print service. The Business Component retrieves, through the communication area, the name and code of the user service that is requested by the client. |
User service code, Action type |
For a processing type SELC: Selection, you can insert a specific processing in the service SRVA: Selection service.
You can parameterize the service to identify it in various use contexts. To do so, enter a $ symbol followed by a digit or a letter directly in the field.
The elementary processing is run by PERFORM from the Logical View level. You can specify in which elementary processing you want to insert the specific processing.
You can parameterize the elementary processing to identify it in various use contexts. To do so, enter a $ symbol followed by a digit or a letter directly in the field.
You can parameterize the category to identify it in various use contexts. To do so, enter a $ symbol followed by a digit or a letter directly in the field.
In the Macro code, the positioning of this specific processing is identified by ACTION=*A. In the Business Component code, it is identified by @BEFORE.
In the Macro code, the positioning of this specific processing is identified by ACTION=*P. In the Business Component code, it is identified by @AFTER.
In the Macro code, the positioning of this specific processing is identified by ACTION=*P. In the Business Component code, it is identified by @REPLACE.