For the most part, the use of Gateway-Library functions in CICS, IMS TM, and MVS is the same. The minor differences that exist are discussed in Table 1-1 and noted in the reference pages for the affected functions.
Function  | 
Difference between CICS, IMS TM, and MVS  | 
|---|---|
TDINFRPC TDSTATUS  | 
The action taken when the communication state (COMM-STATE) is TDS-RESET can differ between CICS, MVS and the IMS TM implicit API: 
  | 
TDINIT  | 
The first argument differs between CICS and IMS TM: 
  | 
TDSETPT  | 
Used with IMS TM only, to indicate the type of IMS TM transaction.  | 
TDSNDDON  | 
Value of CONN-OPTIONS in CICS, MVS, and the IMS TM explicit API can be set to TDS-ENDREPLY in long-running transactions. TDS-ENDREPLY cannot be used under the IMS TM implicit API. To learn how to simulate long-running transactions in the implicit API, see “Long-running transactions”.  | 
TDINFACT TDSETACT  | 
Accounting records are written to different logs under CICS, IMS TM, and MVS: 
  | 
TDINFLOG TDINFSPT TDLSTSPT TDSETLOG TDSETSPT TDWRTLOG  | 
Trace records are written to different logs under CICS, IMS TM, and MVS: 
  |