Tuxedo
0

File Formats, Data Descriptions, MIBs, and System Processes Reference

 Previous Next Contents View as PDF  

DM_ROUTING Section

This section provides information for data-dependent routing of local requests using FML32 typed buffers to one of several remote TOP END systems offering the same resource. This description applies only to domain gateways of type TOPEND.

Entries within the DM_ROUTING section have the following form:

ROUTING_CRITERIA_NAME required_parameters

where ROUTING_CRITERIA_NAME is the identifier name assigned to the ROUTING parameter for the particular resource entry in the DM_IMPORT section. ROUTING_CRITERIA_NAME must be 15 characters or less in length.

Required TEDG parameters for the DM_ROUTING section

FIELD = identifier

Specifies the name of the routing field, which may contain up to 30 characters. It is assumed that the value of this parameter is a field name identified in an FML field table (for FML32 buffers). The FLDTBLDIR32 and FIELDTBLS32 environment variables are used to locate FML field tables. If a field in an FML32 buffer is used for routing, the number of the field must be less than or equal to 8191.

RANGES = "string[1..4096]"

Specifies the ranges and associated remote domain access point names for the routing field. string must be enclosed in double quotes. The format of string is a comma-separated ordered list of pairs, where each pair consists of a range and a remote domain access point separated by a colon (:); for example,
RANGES = "MIN-1000:b01,1001-3000:b02,*:b03".

A range is either a single value (a signed numeric value or a character string enclosed in single quotes), or a range of the form lower - upper (where lower and upper are both signed numeric values or character strings in single quotes). Note that the value of lower must be less than or equal to the value of upper.

To embed a single quote in a character string value (as in O'Brien, for example), you must precede it with two backslashes (O\\'Brien).

The value MIN can be used to indicate the minimum value for the data type of the associated FIELD: for strings and carrays, it is the NULL string; for character fields, it is 0; for numeric values, it is the minimum numeric value that can be stored in the field.

The value MAX can be used to indicate the maximum value for the data type of the associated FIELD: for strings and carrays, it is effectively an unlimited string of octal-255 characters; for a character field, it is a single octal-255 character; for numeric values, it is the maximum numeric value that can be stored in the field. Thus, the value of the string "MIN - -5" is the set of all numbers less than or equal to -5 and the value of the string "6 - MAX" is the set of all numbers greater than or equal to 6. The meta-character * (wildcard) in the position of a range indicates any values not covered by the other ranges previously seen in the entry. Only one wildcard range is allowed per entry and it should be listed last (ranges following it are ignored).

The routing field can be of any data type supported in FML. A numeric routing field must have numeric range values and a string routing field must have string range values. String range values for string, carray, and character field types must be placed inside a pair of single quotes and cannot be preceded by a sign. Short and long integer values are a string of digits, optionally preceded by a plus or minus sign. Floating point numbers are of the form accepted by the C compiler or atof(3): an optional sign, then a string of digits optionally containing a decimal point, then an optional e or E followed by an optional sign or space, followed by an integer.

When a field value matches a range, the associated remote domain access point identifies the remote domain to which the request should be routed. A remote domain access point value of "*" indicates that the request can go to any remote domain known by the gateway group.

BUFTYPE = "type1[:subtype1[,subtype2 . . . ]][;type2[:subtype3[, . . . ]]] . . ."

is a list of types and subtypes of data buffers for which this routing entry is valid. For TOP END domain gateways, the type is restricted to FML32. No subtype can be specified for type FML32. This parameter is required.

If the field value is not set (for FML32 buffers), or does not match any specific range and a wildcard range has not been specified, an error is returned to the application process that requested the execution of the remote resource.

 

Back to Top Previous Next
Contact e-docsContact BEAwebmasterprivacy