The implementation of the JSM_BINDSCRIPT activity provides predefined binding fields and working lists.

In your LANSA Integrator binding solution, you must exclusively use the pre-defined binding fields and working lists.  It will not be possible for your LANSA Composer Processing Sequence to provide or receive values to the binding solution unless the solution uses the pre-defined binding fields and working lists.

The pre-defined binding fields, including the fields defined in the pre-defined working lists, are all defined as alphanumeric and maximum length of 256.  Note that all processing sequence variables are untyped, so this definition is appropriate for LANSA Composer.

Of course, the data items used in your LANSA Integrator binding solution may be of a variety of data types such as integers, dates, date and timestamps, and so on.  However, the mapping to and from the pre-defined binding fields will provide an acceptable representation in both directions for most cases.  You may need to pay attention in your LANSA Composer solution to how you format the values in any processing sequence variables used as inputs to the solution, to be sure that the mapping is successful.

Binding Fields

There are twenty-six pre-defined binding fields that may be used, with the following directives, to "bind" processing sequence variable names to the fields used in your LANSA Integrator binding solution:

Receive binding field values from processing sequence variables

Write binding field values to processing sequence variables

These are the pre-defined binding fields that you must use in your binding solutions for all non-list data items:

DXBINDF0A

DXBINDF0N

DXBINDF0B

DXBINDF0O

DXBINDF0C

DXBINDF0P

DXBINDF0D

DXBINDF0Q

DXBINDF0E

DXBINDF0R

DXBINDF0F

DXBINDF0S

DXBINDF0G

DXBINDF0T

DXBINDF0H

DXBINDF0U

DXBINDF0I

DXBINDF0V

DXBINDF0J

DXBINDF0W

DXBINDF0K

DXBINDF0X

DXBINDF0L

DXBINDF0Y

DXBINDF0M

DXBINDF0Z

Binding Lists

There are six predefined binding working lists that may be used, with the following directives, to "bind" processing sequence variable list names to the working lists 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

These are the pre-defined working lists (and the fields that each contains) that you must use in your binding solutions:

DXBINDL1A

Contains nine (9) fields named DXBINDF1A through DXBINDF1I.

DXBINDL2A

Contains nine (9) fields named DXBINDF2A through DXBINDF2I.

DXBINDL2B

Contains eighteen (18) fields named DXBINDF2A through DXBINDF2R.

DXBINDL3A

Contains nine (9) fields named DXBINDF3A through DXBINDF3I.

DXBINDL3B

Contains eighteen (18) fields named DXBINDF3A through DXBINDF3R.

DXBINDL3C

Contains twenty-six (26) fields named DXBINDF3A through DXBINDF3Z.

Note that working lists of several dimensions are provided – of nine, eighteen, and twenty-six fields.  For optimal performance, your LANSA Integrator binding solution should use the smallest list that is able to provide or receive all the required data items.