Advanced tab

Select the Advanced tab and complete the Resource options:

Resources Add – click New to define communication protocol resources. The ODL Resource Info dialog box appears.
- Debug – allows more verbose debug information to be written to the ODL log. If you select this option, increase the Log Limit size on the General tab.
- Name – enter a resource name. If you are using TCP or Telnet, enter the name you assigned to the clcomm object when developing the AIM.
- Type – select the communication protocol used by this application—TCP, Telnet, or TTY.
Tohost/Fromhost – create a file that records all data going into the endpoint application and all data coming out.
- Limit (KB) – defines the size of the Tohost/Fromhost file. The default of 10240 (10MB) is suggested for optimum performance.
- Depth – defines the number of copies of the log file that e-Biz Impact maintains. The default setting of 2 indicates that when the first file reaches the limit setting, it switches to a second file. When that file reaches the limit setting, it switches back to the first file, overwriting all data stored in that file.
What displays in the remainder of the window depends on your selection for the Type option.
TCP Mode (displays for TCP or Telnet) – select:
- Connect – for an AIM connecting to a socket.
- Listen – the AIM accepts only one connection; it stops listening for new connections while the initial connection is in progress. Listening does not restart once the connection progress stops, unless it has been explicitly directed to do so with a call to the restart method of the communication object (comm.restart()).
- Listen Up – the AIM does not stop listening for new connections. Therefore, you can initiate a second connection, but it is not accepted until the first connection is closed.
- Adopt – used in conjunction with Multisrv applications for multiple connections.
TCP Connect (displays for TCP or Telnet) – if you selected Connect for TCP Mode, enter a host and port. If you selected Listen or Listen Up, enter only a port. If you selected Adopt, leave these fields blank.
TTY Settings (displays only for TTY) – select COM Port and leave the properties selected to accept the defaults, or unselect a property and choose an alternate value from the drop-down lists to meet your specific system requirements. You can also select Device to use a logical device. See Table 4-1.

Not all TTY combinations are valid. Settings are restricted by the underlying operating system device drivers and hardware devices.

**Table 4-1: TTY settings**
Property	Description
COM Port	Value must be greater than zero. This value is appended to a platform-specific prefix (COM for Windows and /dev/tty on UNIX) to create a device name of COMn or /dev/ttyN.
Device	The full device name; for example, `COM1` or `/dev/tty01`.
Baud	Select the baud rate from the drop-down list. If on you are on AIX, the value must be less than 38400.
Parity	Select the parity value from the drop-down list. The Mark and Space values are not supported on HP-UX.
Data Bits	Select 5, 6, 7, or 8.
Stop Bits	Select the stop bits value. A value of 2 works with a 6, 7, and 8 data bit value, but not with a data bit value of 5.
Xon/Xoff	This key controls the XON/XOFF software flow control protocol. Off and None disable the XON/XOFF protocol for both inbound and outbound data. On and Both enable the protocol in both directions. To set inbound and outbound independently, use In to enable inbound and Out to enable outbound.
CTS	Select Handshake to enable inbound hardware flow control.
RTS	Select True to enable outbound hardware flow control.
DTR	Specifies the data terminal ready (DTR) flow control. Select On to enable the DTR line and Off to disable the DTR line.
InDSR (Windows NT only)	Specifies whether the communications driver is sensitive to the state of the data set ready (DSR) signal. Select True to ignore bytes received, unless the DSR modem input line is high.
OutDSR	Select True to suspend output. Select False to monitor the DSR signal for output flow control.

External Libraries – use this option when the code within the ODL makes calls to custom C or C++ code through a bridged library created using BIDL.

Name – enter the alias name, which the user-defined name for the custom collection of C or C++ functions.
Library – enter the actual library file name. (<file name>.<file name_extension>).

Click Add to add the library to the list. Click Delete to remove a selected library from the list. Click Modify to change the name of a selected library.

Custom Keys – to configure custom keys, which can be inserted in the ODL configuration file, click New. Custom keys are defined in groups.

New – configure and add a new custom keys group.
Edit – reconfigure the selected custom key group. Alternatively, you can double-click the custom key group to edit.
Delete – deletes the selected Custom Key group.

Each group is configured through the Custom Keys Info form, using the following attributes:

Name – enter the key-value group.
Key – enter a name for a specific key for this group.
Value – enter the value of the specific key.

Use clGetConfig in an ODL application to retrieve a value from the application configured custom keys as generated by the Configurator. See Chapter 2, “Bridge Functions,” in the e-Biz Impact ODL Guide.

The Debugging options allow more verbose messages to be written to the ODL application xlog. Use these options primarily when the ODL application is using SFM functionality. Select:

Tran – to write transaction information into xlog.
Engine – to write ODL engine information into xlog.
Protocol – to write protocol information to xlog.

Click Apply.