The following limits, ranges, and dependencies that apply to the configuration of applications for OLTP have not already been described:
There is no special provision for Security.
There is no special provision for Internationalization/Localization.
No automatic OLTP buffer version control is provided.
Data conversions between ASCII and EBCDIC are transparently performed.
Resolution of data format differences between integer (long and short) and floating point data formats is transparently performed.
OLTP buffer types X_COMMON and X_C_TYPE are supported for imported buffer definitions.
All X_COMMON and COBOL compatible X_C_TYPE data types are supported within OLTP View class definitions.
The distribution of the description of Service and View descriptions throughout the user network is the responsibility of the user.
(MCP environment) Reports cannot use the full OLTP 2PC facilities. A COMS restriction requires OLTP programs to use COMS DIRECT interface, which is not available for batch programs. A Report might only be OLTP-capable if the application is also OLTP-capable.
(MCP environment) The system software supports OLTP within a single host, from Release 41.2 onwards. (Multiple-host OLTP is currently scheduled for in a later System software release.)
(MCP environment) The OLTP software requires the DMS II DASDL options: REAPPLYCOMPLETED and INDEPENDENTTRANS. Agile Business Suite enforces this requirement.