Rational Developer for System z, Version 7.6

XML and PL/I type compatibility

In order for your mapping selection to be valid, the PL/I elementary items and XML elements you are trying to match must have similar (compatible) types. In other words, the PL/I data class or category of the mapped item should match the data category of the XML elements. For example, a PL/I numeric item should only be matched with an XML element which could be described by a built-in numeric XML schema type.

Table 1 and Table 2 describe the relationship between PL/I data classes and categories and the XML Schema types.

Table 1. Mapping of Built-In Primitive XML Types to PL/I Data Attributes
XML Datatype PL/I Data Attribute Default Request Conversion (See Note 1) Default Response Conversion (See Notes 1 and 2)
string CHARACTER, GRAPHIC, WIDECHAR, BIT memConvert, = memConvert, =
boolean CHARACTER, WIDECHAR memConvert, = memConvert, =
string PICTURE memConvert, PICSEC, = memConvert, =
boolean PICTURE memConvert, PICSEC, = memConvert, =
string FLOAT, FIXED = =
boolean FIXED = =
float FLOAT = =
double FLOAT = =
decimal FIXED = =
duration CHARACTER, GRAPHIC, WIDECHAR N/A N/A
dateTime CHARACTER, GRAPHIC, WIDECHAR N/A N/A
time CHARACTER, GRAPHIC, WIDECHAR N/A N/A
date CHARACTER, GRAPHIC, WIDECHAR N/A N/A
gYearMonth CHARACTER, GRAPHIC, WIDECHAR N/A N/A
gYear CHARACTER, GRAPHIC, WIDECHAR N/A N/A
gMonthDay CHARACTER, GRAPHIC, WIDECHAR N/A N/A
gDay CHARACTER, GRAPHIC, WIDECHAR N/A N/A
gMonth CHARACTER, GRAPHIC, WIDECHAR N/A N/A
hexBinary BIT, GRAPHIC, WIDECHAR memConvert, = memConvert, =
base64Binary CHARACTER, GRAPHIC, WIDECHAR N/A N/A
anyURI CHARACTER, GRAPHIC, WIDECHAR N/A N/A
QName CHARACTER, GRAPHIC, WIDECHAR N/A N/A
NOTATION CHARACTER, GRAPHIC, WIDECHAR N/A N/A
Note:
  1. The functions: memConvert and PICSEC are build-in functions provided by the PL/I compiler. The function: = is a normal PL/I assignment statement.
  2. The mapping tools do not enforce matching rules for user-defined simple XML schema types that are derived by constraint. For example, if for a base="int", the user defined type has a constraint of minInclusive value="-99" it may not be possible to enforce the minInclusive constraint.
Table 2. Mapping of Built-In Derived XML Types to PL/I Data Attributes
XML Datatype PL/I Data Attribute Default Request Conversion (See Note 1) Default Response Conversion (See Notes 1 and 2)
normalizedString CHARACTER, GRAPHIC, WIDECHAR N/A N/A
token CHARACTER, GRAPHIC, WIDECHAR N/A N/A
language CHARACTER, GRAPHIC, WIDECHAR N/A N/A
IDREFS CHARACTER, GRAPHIC, WIDECHAR N/A N/A
ENTITIES CHARACTER, GRAPHIC, WIDECHAR N/A N/A
NMTOKEN CHARACTER, GRAPHIC, WIDECHAR N/A N/A
NMTOKENS CHARACTER, GRAPHIC, WIDECHAR N/A N/A
Name CHARACTER, GRAPHIC, WIDECHAR N/A N/A
NCName CHARACTER, GRAPHIC, WIDECHARl N/A N/A
ID CHARACTER, GRAPHIC, WIDECHAR N/A N/A
IDREF CHARACTER, GRAPHIC, WIDECHAR N/A N/A
ENTITY CHARACTER, GRAPHIC, WIDECHAR N/A N/A
integer CHARACTER, WIDECHAR memConvert, = memConvert, =
nonPositiveInteger CHARACTER, WIDECHAR memConvert, = memConvert, =
negativeInteger CHARACTER, WIDECHAR memConvert, = memConvert, =
long CHARACTER, WIDECHAR memConvert, = memConvert, =
int CHARACTER, WIDECHAR memConvert, = memConvert, =
short CHARACTER, WIDECHAR memConvert, = memConvert, =
byte CHARACTER, WIDECHAR memConvert, = memConvert, =
nonNegativeInteger CHARACTER, WIDECHAR memConvert, = memConvert, =
unsignedLong CHARACTER, WIDECHAR memConvert, = memConvert, =
unsignedInt CHARACTER, WIDECHAR memConvert, = memConvert, =
unsignedShort CHARACTER, WIDECHAR memConvert, = memConvert, =
unsignedByte CHARACTER, WIDECHAR memConvert, = memConvert, =
positive-Integer CHARACTER, WIDECHAR memConvert, = memConvert, =
integer PICTURE memConvert, PICSEC, = memConvert, =
nonPositiveInteger PICTURE memConvert, PICSEC, = memConvert, =
negativeInteger PICTURE memConvert, PICSEC, = memConvert, =
long PICTURE memConvert, PICSEC, = memConvert, =
int PICTURE memConvert, PICSEC, = memConvert, =
short PICTURE memConvert, PICSEC, = memConvert, =
byte PICTURE memConvert, PICSEC, = memConvert, =
nonNegativeInteger PICTURE memConvert, PICSEC, = memConvert, =
unsignedLong PICTURE memConvert, PICSEC, = memConvert, =
unsignedInt PICTURE memConvert, PICSEC, = memConvert, =
unsignedShort PICTURE memConvert, PICSEC, = memConvert, =
unsignedByte PICTURE memConvert, PICSEC, = memConvert, =
positive-Integer PICTURE memConvert, PICSEC, = memConvert, =
integer FIXED = =
nonPositiveInteger FIXED = =
negativeInteger FIXED = =
long FIXED = =
int FIXED = =
short FIXED = =
byte FIXED = =
nonNegativeInteger FIXED = =
unsignedLong FIXED = =
unsignedInt FIXED = =
unsignedShort FIXED = =
unsignedByte FIXED = =
positive-Integer FIXED = =
Note:
  1. The functions: memConvert and PICSEC are built-in functions provided by the PL/I compiler. The function: = is a normal PL/I assignment statement.
  2. The mapping tools do not enforce matching rules for user-defined simple XML schema types that are derived by constraint. For example, if for a base="int", the user defined type has a constraint of minInclusive value="-99" it may not be possible to enforce the minInclusive constraint.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)