NonStop SOAP 4.1 User's Manual

Table 10 Valid AlignmentRule setting for existing COBOL services that use DDL generated
header files
AlignmentRule settingDDL settingCOBOL option
evenC00CALIGNDefault
shared2CFIELDALIGN_MATCHED2Default
shared2C_MATCH_HISTORIC_TALDefault
shared8SHARED8Default
Table 11 Valid AlignmentRule setting for existing COBOL services that does not use DDL
generated header files
AlignmentRule settingCOBOL option
evenDefault
datatypeAll elements marked as SYNC
NOTE: For C and COBOL services that do not include DDL generated header files, use the
SOAPAdminCL tool with -fs option.
• The responseType parameter setting determines the processing of BLANK response elements.
If the parameter is set to strict, then the NonStop SOAP 4 server builds the XML response,
according to the service definition, even if BLANK elements are present. If the parameter is
set to lenient, then the NonStop SOAP 4 server does not create the BLANK elements and
builds the minimal size XML response.
In C services, all bytes of an element filled with the null character (\0) denote a BLANK element.
In COBOL services, all bytes of an alphabetic, alpha-edited, or alphanumeric element filled
with spaces, or all bytes of a numeric or numeric-edited element filled with zero denote a
BLANK element.
An entity is considered optional if:
◦ The corresponding DDL field is marked with a @SOAP_OPTIONAL comment tag
◦ It is an element in WSDL, minOccurs value is set to 0
◦ It is an attribute in WSDL, use="optional" is set
The following table lists the display behavior for different responseType parameter and
BLANK element settings.
Table 12 Displaying BLANK element in response XML
responseType set to lenientresponseType set to strictBLANK element is
NoNoOPTIONAL
NoYesMANDATORY
NoNoGreater than minOccurs and less
than maxOccurs
NoYesGreater than minOccurs and less
than OccDependON
NoYesLess than minOccurs
NOTE: If an optional element or attribute is omitted in XML request, BLANK value is sent.
The services.xml File 185