Specify whether or not this table (and any of its associated indexes) should be opened with the option to share an open data path.
Note that this value only affects the way that the OAM (and hence RDML applications) open the table at run time. To actually get the physical table and indexes defined to the operating system as SHARE(*YES) or SHARE(*NO) for the benefit of external application programs, refer to the 3.6.20 CRTPF and CHGPF Parameter.
Default = NO (unchecked/not selected).
- This option relates to the opening of the table's open data path when used in OAMs and *DBOPTIMISE programs.
- This option does not relate to the creation or changing of the database table attributes.
- IBM i: This table attribute applies to IBM i databases only.
- IBM i: Despite the fact that IBM recommends data path sharing as one of the fundamental design considerations for efficient applications, the default for LANSA created tables is NO (UNCHECKED or unselected). That is, do not share open data paths. The reason for this is that the OAM concept implicitly emulates an open data path, because one active OAM is shared by all RDML functions (within a job) that are accessing a table.
- IBM i: Generally use option NO (UNCHECKED/not selected). That is do not share an open data path, except in the special situation where the table is only being used as a 'joined record format' for data that is dynamically created by the IBM OPNQRYF (open query file) command.