To create a UAP that does not use the MCF simulator, follow the same procedure as for a job UAP. See the manual OpenTP1 Programming Guide for details.
To create a UAP that uses the MCF simulator, use the simulation functions library provided by the online tester. The creation procedure differs depending on whether TP1/Message Control is cataloged in the Resource Manager.
If TP1/Message Control is not cataloged in the Resource Manager, link the UAP to the online tester's MCF simulation functions library (libmuto.a) rather than to the TP1/Message Control library (libmcf.a).
Specify -lmuto to link the UAP to the MCF simulation functions library. There is no need to specify -lmcf to link the UAP to the TP1/Message Control library.
For a UAP created in COBOL or in a data manipulation language (DML), specify -lmuto instead of -lmcf in the same way.
If TP1/Message Control is cataloged in the Resource Manager, link the UAP first to the MCF simulation functions library (libmuto.a) and then to the TP1/Message Control library (libmcf.a).
The command for compiling a UAP that uses the MCF simulator is shown below.
cc -go example exmain.c exsv1.c exsv2.c ex_sstb.c |
cc -go example exmain.c exsv1.c exsv2.c ex_sstb.c |