Page History
...
Further important information about the CALL_FUNCTION activity is provided under the following headings later in these notes:
LANSA programming considerations for the called function
Calling a function in the same system and partition as LANSA Composer
Calling a function in another LANSA system or partition
Function calls executed through the LANSA Composer Request Server
You should also refer to:
Appendix F. The LANSA Composer Request Server
If you experience difficulties getting your function call to work through the LANSA Composer Request Server, please refer to:
Troubleshooting the LANSA Composer Request Server
INPUT Parameters
LANSACONFIG: Optional
...
Refer to the description of the EXCHANGE RDML command in the LANSA product documentation for further information on exchanging information via the exchange list.
| Anchor | ||||
|---|---|---|---|---|
|
The following LANSA programming considerations apply to the way in which the called function must be defined:
...
Depending on all the requirements, these considerations may sometimes necessitate that your programming staff write functions specifically for the purpose. However, even if this is necessary, the functions can frequently be simple "stub" functions that call other existing functions in the LANSA application.
| Anchor | ||||
|---|---|---|---|---|
|
If you want to call a function that is available in the same LANSA system and partition as LANSA Composer, you only need to specify the function name in the FUNCTION parameter, and any values to be exchanged with the function in the EXCH01 ... EXCH07 parameters. You do not need to specify values for the LANSACONFIG, PROCESS or SYNCHRONOUS parameters (nor the deprecated LANSASYS and PARTITION parameters).
...
Functions called in this way must be defined with FUNCTION OPTIONS(*DIRECT).
| Anchor | ||||
|---|---|---|---|---|
|
You can call a function that is available in a different LANSA system and/or partition than LANSA Composer on the same or a different server system. To do this, you should:
...
Such requests offer greater flexibility, including the ability to call the required function through a specified process (instead of with *DIRECT) and synchronously or asynchronously processing the request. These types of function calls will execute through the LANSA Composer Request Server, and some special considerations apply.
| Anchor | ||||
|---|---|---|---|---|
|
The CALL_FUNCTION activity will seek to execute the function call through the LANSA Composer request server if any of the following are true:
You specify a LANSA system configuration name using the LANSACONFIG parameter
Info (OR on IBM i servers only, the values specified for the LANSASYS and PARTITION parameters identify a LANSA system and/or partition that is not the same as for the LANSA Composer system.)
- You specify a process name (other than *DIRECT) in the PROCESS parameter.
- You specify a value other than YES for the SYNCHRONOUS parameter.
...