To enable Enterprise Server to use IMS Connect, you must create a custom listener. 
- Click the Listeners tab in Enterprise Server Administration. 
 
-  Click Add. 
 
-  Enter a unique name for the new listener. 
 
- From the Endpoint Protocol drop-down list, choose TCP . 
 
- Enter an appropriate port for IMS Connect in the Endpoint Address text box. 
 
- Select a Supported Conversation Type of Custom and enter mfcs-ims-connect in the text box. 
 
- Optionally, add trace details in the Configuration Information text box, for example: 
[Trace]
trace=y
data-trace=all
allmax=255
 
- Click Add. 
 
Note: 
The following IMS features are supported by Enterprise Server: 
- Conversational (SPA) and non-conversational transactions that do not use the IMS SETO functionality 
 
- Support for IMS commands 
 
- Security for all IMS Connect listeners 
 
- The following IBM-supplied I/O exits: 
-  HWSIMSO0 '*IRMREQ*' Yes 
 
- HWSIMSO1 '*IRMRE1*' Yes 
 
- HWSSMPL0 '*SAMPLE*' Yes (unmodified - same as HWSIMSO0) 
 
- HWSSMPL1 '*SAMPL1*' Yes (unmodified - same as HWSIMSO1) 
 
- HWSJAVA0 '*HWSJAV*' No 
 
- HWSCSLO0 '*HWSCSL*' No 
 
No exit screening configuration is provided.  
- The return MOD name control 
 
-  Persistent, non-persistent and transactional socket control 
 
- End-to-end ASCII flows 
 
There is limited support for flow control and Syncpoint/Commit controls 
The following are not supported: 
- Modified Sample I/O exits or target resolution exits 
 
- The return OTMA headers control 
 
- UTF and UCS codesets 
 
- The Translate control 
 
- The IRM timer 
 
- The One Message and One Message No Wait" controls 
 
- The Auto Flow and no Auto Flow controls 
 
- Asynchronous and unsolicited output to an IMS Connect client