OpenTP1 Version 7 Programming Guide
8.6.1 MCF sample directory configuration
The MCF sample is divided into an MCF basic section and a communication protocol section. The figure below shows the directories containing the MCF sample.
Figure 8-11 Configuration of directories for MCF sample
Directories subordinate to the $DCDIR/examples/mcf/ directory are listed below with a brief explanation.
- aplib/
- Directory that contains MHP sample
- conf/
- Directory that contains system definition sample
- psv/cmlib/
- Directory that contains MCF main function sample
- protocol/
- Directory that contains sample specific to the communication protocol supporting product
- The following directories are placed under the protocol/ directory:
- Directory that contains MHP and SPP samples
- Directory that contains the system definition
- Directory that contains the MCF main function
- Organization of this subsection
- (1) Contents of mcf/aplib/ directory
- (2) Contents of conf/ directory
- (3) Contents of psv/cmlib/ directory
- (4) Contents of protocol/ directory
(1) Contents of mcf/aplib/ directory
Files in the mcf/aplib directory are listed below with a brief explanation.
- c/
- Directory that contains MHP source files (in the C language). MHP main function (mhp.c) and MHP service function (apl.c) are stored here.
- cobol/
- Directory that contains MHP source files (in the COBOL language). MHP main function (mhp.cbl) and MHP service function (ap.cbl) are stored here.
- dml/
- Directory that contains MHP source files (in the COBOL language with DML). MHP service function (ap.cbl) is stored here.
For the contents of the above programs, see the coding example shown in the applicable OpenTP1 Programming Reference manual.
(2) Contents of conf/ directory
Files in the mcf/conf/ directory are listed below with a brief explanation.
- abc_mngr
- Sample MCF manager definition
- abc_ua_c
- Sample common definition of MCF communication configuration definition. This definition is for OSAS/UA protocol.
- abc_ua_d
- Sample protocol-specific definition of MCF communication configuration definition. This definition is for OSAS/UA protocol.
- psvr_psvr_cmn
- Sample common definition of MCF communication configuration definition. This definition is for application starting definition.
- psvr_psvr_dta
- Sample application starting definition of MCF communication configuration definition.
- abc_apli
- Sample MCF application definition
- mcfu01
- Sample MCF system service information definition. This definition is the contents of the MCF communication process (for OSAS/UA).
- mcfu02
- Sample MCF system service information definition. This definition is the contents of the application communication process.
For the contents of the above definitions, see the definition sample shown in the manual OpenTP1 System Definition.
(3) Contents of psv/cmlib/ directory
Directories subordinate to the mcf/psv/cmlib/ directory are listed below with a brief explanation.
- ansi/
- Sample MCF main function for application starting process (in ANSI C and C++ style)
- c/
- Sample MCF main function for application starting process (in K&R C style)
For the contents of the above MCF main functions, see the definition sample shown in the manual OpenTP1 Operation. For the MCF main function for MCF communication service, see the files in the mcf/protocol/cmlib/ directory.
(4) Contents of protocol/ directory
Samples for each communication protocol supporting product are stored in the protocol/ directory. The name of the protocol/ directory depends on the communication protocol supporting product. The correspondence between the protocol/ directory names and the product names is as follows:
HDLC: TP1/NET/HDLC
HNANIF: TP1/NET/HNA-NIF
OSITP: TP1/NET/OSI-TP
TCPIP: TP1/NET/TCP/IP
XMAP3: TP1/NET/XMAP3
X25: TP1/NET/X25
For the contents of each directory, see the applicable OpenTP1 Protocol manual.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.