Where a user-specified OLTP buffer is not available to pass a response from an OLTP Server to its Client, a predefined OLTP buffer is used. This buffer has the following format (View description):
OLTP Type is X_COMMON
OLTP Subtype is LINCdefaultwarn
A single attribute LINC_MESSAGE (15 characters)
This standard view contains data formatted as follows:
VIEW LINCdefaultwarn
#type X_COMMON
#used internally for replies and error conditions
char LINC_MESSAGE - 15 1 - -
#Edit A
END
In addition to the attribute, the standard OLTP application result value is used to identify the type of result being returned from the server.
| Value | Type of Result |
|---|---|
| 0 | Warning message. Glb.Status is set to (*****). |
| 1 | Good transaction response, with no data. |
| 2 | Fatal error message. The OLTP flag TPFAIL is set. The Client receives a TPSVCFAIL error. |
The LINC_MESSAGE attribute provides the value to be returned to user logic in Glb.HubStatus, identifying the particular error condition. Refer to the Agile Business Suite Programming Reference Manual for more information on Glb.HubStatus settings.
Note: Any OLTP buffer with a null message is recognized by a Client as a valid response to a TRANSACTION; WRITE command, with no data returned. However, the Server value in Glb.Error cannot be returned by this method, and Glb.Error is assumed to be spaces.
The following table shows the file or element that contains the View for the LINCdefaultwarn buffer for the various OLTP platforms.
| Host | View file name |
|---|---|
| MCP environment | NGEN28/OLTPVIEW/DEFAULT ON pack (where pack is the Dictionary pack for Runtime) |