A Checklist for the Programmers

All application programmers in CICS under z/OS environment must check the checklist.

  • The first TIBCO EMS API call must be a successful tibcoemsConnection_Create – if unsuccessful, the transaction does not have a CEET Work Thread, without which no TIBCO EMS API calls can be processed.
  • The tibemsConnection_SetExceptionListener API is automatically done for the Work Thread when it is first started, so this API is available to the user transaction. Consequently, it is important that transactions make sure the first tibcoemsConnection_Create is the one they use to receive messages. In this situation, the Work Thread can pass status back to the transaction for Connection disruptions. If the transaction issues tibcoemsConnection_Create for other URLs, they will not be monitored, because only one tibemsConnection_SetExceptionListener is issued for the first URL tibcoemsConnection_Create.

For details on the TIBCO EMS API, see TIBCO Enterprise Message Service C & COBOL API Reference.

Batch Applications

Execution – The TIBCO EMS API uses the TCP/IP socket interface. Most installations require a SYSTCPD DD statement in the execution JCL. Contact the TCP/IP support personnel of your organization for additional details.