InputOutputMessage
Use this element to define messages for REQUEST-RESPONSE operations if the input and output messages are of the same type.
Note: In the InputOutputMessage
both request and response message definitions
come from a single COBOL source. Because of this, the XsdSpecOut schema
specification for the namespace will be ignored for theresponse schema.
Contained by
OperationContains
Attributes
Table 1 shows the attributes for InputOutputMessage.
Fields | Description |
---|---|
Attribute: importFile
Valid values: See Description Required?: Yes (unless the -s command line option is specified) Default value: See Description |
Specifies the file name that contains the data
definition to be used in creating the Web service operation message
types. Note: Only COBOL data definitions are supported and are subject
to the restrictions that are specified in the online help.
The default value is: The name provided in the xsebatch command line parameter -s. |
Attribute: nativeTypeName
Valid values: See Description Required?: No Default value: See Description |
Specifies the name of the data type that is
to be imported from the importFile, such as DFHCOMMAREA for a CICS® COBOL application. An error
message is generated on the console if a parse of the importFile does
not identify the nativeTypeName as a valid data type. The default value is: For COBOL, the name of the first available level 01 data item name. |
Example
<InputOutputMessage name="PhoneBookMsg" importDirectory="."
importFile="Ex01z.cbl" nativeTypeName="input-msg">
<RedefinesArray>
<RedefineSelection redefine="input-msg.redParent.redefd"
useRedefinition="input-msg.redParent.redefd2"/>
</RedefinesArray>
<ItemSelectionArray>
<ItemSelection itemName="input-msg.redParent"/>
<ItemSelection itemName="input-msg.in-extn"/>
<ItemSelection itemName="input-msg.in-zip"/>
<ItemSelection itemName="input-msg.in-ll"/>
</ItemSelectionArray>
</InputOutputMessage>