An OLTP View class is an external class definition in which a standard OLTP Buffer description is loaded. This description is used to specify the attributes and format to be used to send an OLTP transaction request to an external server. It is also used by an instance of a class that defines the format of the response to be received from an external server.
Set up the OLTP View Class as an external class. The relevant properties for this class are described later in this subsection.
An OLTP Buffer description file is loaded or reloaded when the OLTP View Class is built, and either:
The file is not loaded correctly. Build the selected class.
The file has changed from the previous file loaded. This is detected automatically by a date/timestamp mismatch, or by a comparison with the previously loaded file.
Restrictions on the OLTP View Class
OLTP Buffer descriptions can be imported into a client <<segment>>. It is your responsibility to provide the View descriptions. The following restrictions apply to the OLTP View Class:
Maximum total length of the buffer described is 65 characters
OLTP Type must be X_COMMON or X_C_TYPE
OLTP Subtype is user-defined
Attribute names in the View description are truncated to 18 characters
Lowercase is converted to uppercase
Underscore (_) is converted to hyphen (-)
An X_COMMON View can contain attributes of any of the following data types:
char
short
long
Note: The standard data type char represents non-translatable data. It is transferred between client and service without regard for the character-sets used by the supporting systems. Communications between MCP based computers and Windows operating systems, UNIX, or OS 2200 based computers produces unexpected results due to the mix of EBCDIC and ASCII character sets. The data type chartranslate should be used for communication between these hosts; however, its use and View definition are not standardized on the different architectures.To communicate across architecture boundaries, modify the View files for MCP based applications, to set the flag value to 1. (This is set by default in Agile Business Suite-generated View files).
An X_C_TYPE View can contain attributes of any X_COMMON data type, as well as any of the following data types:
carray
string
int
float
double
For an MCP based application, arrays of carray or string type are not available.
On MCP based hosts, there is a current limit of 270 attributes. On other architectures, the screen size limits the number of attributes you can have in the View class.
For an MCP based application, the OLTP View class is treated as being part of the GLOBAL Subsystem.
The following restrictions apply to OLTP View class attributes:
They are excluded from the GLI file.
Numeric items in View descriptions do not contain DECIMALS; data attributes. You are responsible for correctly interpreting the value of numeric items in OLTP View classes.
Note: OLTP View classes are defined in Developer. Developer does not enforce all of the host-specific restrictions listed above.
OLTP View Classes
Define your OLTP View classes using the <<ispec>> properties in Developer.
OLTP View Class Properties
The OLTP View Class properties are described in the following list:
Interface Type
Select OltpView to define the class as an OLTP View Class.
Synchronize File
Enter the external file name of the View definition. Use the browse button to select the View definition file.
The requirements for this file are described in “Restrictions on the OLTP View Class”, earlier in this section.
View Name
Use this field to enter the externally known OLTP Subtype name of the View.
Note: For MCP based applications, the view name might be up to 16 characters. To prevent view names exceeding this limit, ensure your application names are restricted to nine characters.
View Type
Select X_COMMON to specify that the View description has an OLTP type of X_COMMON. This is the default.
Select X_C_TYPE to specify that the View description has an OLTP type of X_C_TYPE.
SynchronizeState
The SynchronizeState property is set to True if the OLTP Buffer description file needs to be loaded. This happens if the file has changed since it was last loaded.
Select this check box and transmit to load your OLTP Buffer description file. After loading, you can view any errors by accessing the OLTP View Load Inquiry screen, as described in the following subsection.
Note: If you do not load the OLTP Buffer description file, it is loaded at build time. However any AUTO; logic commands requiring this file are flagged as syntax errors.