Appendix B. Changes to the Interfaces (for Migrating from Version 6 or Earlier)

If you migrate from Version 6 or earlier of TP1/Message Control and the architecture is not 32-bit, you must check the C language source files. This appendix lists the changes to the interfaces from when migrating from Version 6 or earlier.

The following table provides an overview by interface of the changes that are explained in this appendix.

Table B-1 List of changes to the interfaces

Changed interfaceReference in the Version 7 manual
Message transmission interfacesdc_mcf_ap_info2. dc_mcf_ap_info
dc_mcf_ap_info_uoc2. dc_mcf_ap_info_uoc
dc_mcf_close2. dc_mcf_close
dc_mcf_commit2. dc_mcf_commit
dc_mcf_contend2. dc_mcf_contend
dc_mcf_execap2. dc_mcf_execap
dc_mcf_mainloop2. dc_mcf_mainloop
dc_mcf_open2. dc_mcf_open
dc_mcf_receive2. dc_mcf_receive
dc_mcf_rollback2. dc_mcf_rollback
dc_mcf_tempget2. dc_mcf_tempget
dc_mcf_tempput2. dc_mcf_tempput
dc_mcf_timer_cancel2. dc_mcf_timer_cancel
dc_mcf_timer_set2. dc_mcf_timer_set
User exit routinesUser exit routine that determines inheritance of timer-start messages 8. Function format of the user exit routine that determines whether to inherit the timer-start settings
MCF event interfaces8. Structure format of mcf event that reports discarding of a timer-start message (ERREVT4)
Coding example for the MHP service function7.3 Coding samples for message exchange configuration UAPs (MHP)
(2) MHP sample (service function)

The following sections explain the changes to the interfaces between Version 6 or earlier and Version 7. Changes are indicated by underlines.

Organization of this section
B.1 Message transmission interfaces
B.2 User exit routines
B.3 MCF event interfaces
B.4 Coding example for the MHP service function