The following JSM Binding Script directives require you to specify the Processing Sequence variable list names that will provide or receive the entries and values for the JSM binding working lists that you used in your LANSA Integrator binding solution:
Receive binding list values from processing sequence variable lists
Write binding list values to processing sequence variable lists
To do this, select the appropriate script line and click the Edit Bindings button. Depending on which type of directive you are using, a window like one of those shown will be displayed.
The implementation of the JSM_BINDSCRIPT activity provides six (6) predefined binding working lists. These are the working lists that you should have used in your LANSA Integrator binding solution. The pre-defined working lists are listed in:
Binding Fields and Working Lists
The top part of the window lets you choose which of these working lists you wish to bind to Processing Sequence variable lists. You should make your choice according to the list you actually specified in your LANSA Integrator binding solution.
The rest of the window shows the pre-defined field names according to the working list you have chosen (you can scroll the window to see all of them). Against each of the pre-defined working list fields that you actually used in your LANSA Integrator binding solution, you should type the name of a Processing Sequence variable list that will provide or receive the binding field values.
When you enter the Processing Sequence variable list names, note the following:
- LANSA Composer displays the Processing Sequence variable list names with the leading ampersand (&) character, but you do not have to type it.
- Processing Sequence variable list names may be up to twenty (20) characters, must begin with A through Z, and may consist of A through Z, 0 through 9 and the underscrore (_) character.
- Processing Sequence variable lists are implicitly defined simply by using them. You need to be careful that the variable list names that you use do not conflict with variables that may already be used for other purposes in the Processing Sequence containing the JSM_BINDSCRIPT activity.
It should be clear that you cannot simply assign Processing Sequence variable list names to arbitrary working list fields, but instead, you must do so with reference to the working list's usage in the actual LANSA Integrator binding solution that you are using. You will, therefore, need to make reference to the actual LANSA Integrator binding solution while completing these bindings.
It is not mandatory that you bind every working list field used in your LANSA Integrator binding solution to a processing sequence variable list. Indeed, if the values are not required in or from a processing sequence variable list, then you can optimize performance by omitting the binding for that binding list field.
For more information about Processing Sequence variables, refer to the following topic: