| Summary | Information on how to configure the number of times the Adapter attempts to call otma_openx(). |
|---|---|
| Article Number | 29377 |
| Environment | Orbix Mainframe 6.3, Patch ORBM-405 All supported platforms |
| Question/Problem Description | Orbix Mainframe IMS Adapters using OTMA invoke the operation "otma_openx()" on IBM's OTMA API when establishing a connection with IMS. It is possible to configure how this connection attempt is managed. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | ORBM-405 |
| Cause | Under some, rare circumstances, if IMS control region is cancelled while IMS OTMA Adatper is starting, the Orbix Adapter may launch without a connection to IMS and without logging an error message. This article describes a way to change the above behaviour. |
| Resolution | Patch ORBM-405 for Orbix Mainframe 6.3 provides the configuration variable: plugins:ims_otma:open_attempts This specifies how often the adapter attempts to call otma_openx() on IBM's OTMA API. By default, this is set to "3". If the otma_openx() call does not respond, the adapter will retry the call every 10 seconds, for the number of times specified by the new "open_attempts" configuration variable. If the adapter is unable to establish the connection in this time, the following message is displayed in the adapter's log: (IT_MFA:40) E - Timeout on call to otma_openx() |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 29 February 2012 |
|---|---|
| Last Modified: | 14 February 2013 |
| Last Published: | 29 February 2012 |
| First Published date: | 29 February 2012 |
#Orbix
#KnowledgeDocs
