bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Platform > WebLogic Integration > DI Topics > Translating Data > Supported Data Types |
Translating Data
|
Supported Data Types
WebLogic Integration supports the following data types:
This section describes them.
MFL Data Types
Table A-1 lists the MFL data types supported by WebLogic Integration. These types are specified in the type attribute of a FieldFormat element.
COBOL Copybook Importer Data Types
The following table lists the COBOL data types and the support provided by the Importer.
Support for these data types is limited. Data presented in either of the following formats is converted to an unsigned four-byte integer type:
Data presented in the following formats generates errors:
In these samples, pic9(5) can be substituted for pic x(5).
The following table defines the three levels of support for these data types.
Some vendor-specific extensions are not recognized by the importer. Any copybook statement that conforms to ANSI standard COBOL, however, is parsed correctly by the importer. The importer's default data model, which is based on the IBM mainframe model, can be changed in the Format Builder to compensate for the endian nature of characters set and data.
When importing copybooks, the importer may identify fields generically, although those fields can easily be identified as specific data types. For this reason, the copybook importer creates comments for each field found in the copybook. This information is useful when you are editing the MFL data, helping you to improve upon the formats used in the original copybook. For example, suppose an original copybook contains the following entry:
05 birth-date picxx/xx/xx
After the copybook is imported, this entry is shown in a field of type EBCDIC with a length of 8. Close inspection reveals that this entry is intended as a date that can be formatted in either of the following ways:
C Structure Importer from Importing Metadata
The C struct importer does not parse files containing anonymous unions, bit fields, or in-line assembler code. The following samples of unsupported structures are taken from the preprocessor output of a hello.c file that contained a #include <windows.h> statement:
#line 353 "e:\\program files\\microsoft visual studio\\vc98\\include\\winnt.h"
typedef union_LARGE_INTEGER{
struct {
DWORD LowPart;
LONG HighPart;
};
struct {
DWORD LowPart;
LONG HighPart;
} u;
#line 363 "e:\\program files\\microsoft visual studio\\vc98\\include\\winnt.h"
LONGLONG QuadPart;
} LARGE_INTEGER
typedef struct_LDT_ENTRY {
WORD LimitLow;
WORD BaseLow;
union {
struct {
BYTE BaseMid;
BYTE Flags1;
BYTE Flags2;
BYTE BaseHi;
} Bytes;
struct
DWORD BaseMid : 8;
DWORD Type : 5;
DWORD Dpl : 2;
DWORD Pres : 1;
DWORD LimitHi : 4;
DWORD Sys : 1;
DWORD Reserved_0 : 1;
DWORD Default_Big : 1;
DWORD Granularity : 1;
DWORD BaseHi : 8;
} Bits;
} HighWord;
} LDT_ENTRY, *PLDT_ENTRY;
_inline ULONGLONG
_stdcall
Int64ShrlMod32(
ULONGLONG Value,
DWORD ShiftCount
)
{
_asm {
mov ecx, ShiftCount
mov eax, dword ptr [Value]
mov edx, dword ptr [Value+4]
shrd eax, edx, cl
shr edx, cl
}
}
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |