How to: |
A channel is created to listen for the IMS Event and process the event document. A channel that is configured using the REQUEST or REQUEST_ACK (Acknowledgment) synchronization type does not return data to the IMS application, and may be associated with one or more ports. Specifying multiple ports means that the document will be written to each port. A channel that uses the REQUEST_RESPONSE synchronization type may only be associated with a single port. If the channel converts Copybook formatted request messages to XML, a PreParser must be configured. If the channel converts XML to Copybook formatted response messages, then a PreEmitter must be configured.
When using a REQUEST/RESPONSE configuration, input and output data must be either both Copybook or XML formatted.
To create a channel:
The following image shows the Channels node highlighted in the left pane.
The Add Channel dialog box opens.
The TCP Listener dialog box opens where you provide parameters to specify values for the protocol you will use with the channel, as shown in the following image.
The following table lists and describes the properties in the Basic tab.
Property |
Description |
---|---|
Port Number |
Port number where your IMS connection node listens for Events generated by IMS. |
Host/IP Binding |
Name or IP address of the host computer where the IMS application region is running. |
Synchronization Type |
Choose one of the following:
|
Is Length Prefix |
For IMS events that return data, which is not in XML format. The TCP/IP event application must prefix the data with a 4-byte binary length field when writing data to the TCP/IP port. |
Is XML |
For IMS events that return data in XML format. No preparser is required. |
Is Keep Alive |
Maintains continuous communication between the Event transaction and the channel. |
The following table lists and describes the properties in the PreParser tab.
Property |
Description |
---|---|
Location of COBOL Data Description |
Path to the COBOL description of the layout sent by IMS. For more information, see Sample Requests, Schemas, and COBOL File Descriptions. |
Remote Codepage |
Select the code page from the drop-down menu. Cp500 is the default value. |
Use data structure information from COBOL |
When this parameter is selected, the Event creates request and response documents including COBOL group levels (for example, 05, 10, 20, and others). You must select this parameter when COBOL input or output descriptions contain the COBOL OCCURS or REDEFINES statement. |
Accept multiple records in COMMAREA |
When this parameter is selected, multiple COMMAREA records are read by the PreParser. Otherwise, any data in excess of the COBOL definition is truncated. |
The following table lists and describes the properties in the PreEmitter tab.
Note: Specify a PreEmitter only when using the REQUEST_RESPONSE synchronization type.
Property |
Description |
---|---|
Location of COBOL Data Description |
Path to the COBOL description of the layout returned to IMS. |
Remote Codepage |
Select the code page from the drop-down menu. Cp500 is the default value. |
Use data structure information from COBOL |
When this parameter is selected, the Event creates request and response documents including COBOL group levels (for example, 05, 10, 20, and others). You must select this parameter when COBOL input or output descriptions contain the COBOL OCCURS or REDEFINES statement. |
The following image shows the newly created IMSChannel under the Channels node in the left pane.
An X over the icon indicates that the channel is currently disconnected. You must start the channel to activate your Event configuration.
To edit a channel:
The Edit Channel dialog box opens.
To delete a channel:
The channel disappears from the list in the left pane.