OpenTP1 Version 7 System Definition
To set the network communication definitions, use a text editor to create the definition source files and create the definition object files from the definition source files. Register these definition object files in the OpenTP1 system.
To specify the name of a definition object file, use the appropriate format shown in Tables 4-1 and 4-2. Use the definition commands shown in Tables 4-1 and 4-2 to register the file names beforehand.
For details about the definition source files, see 5. Network Communication Definitions.
For the method of creating the definition object files, see 4.3 Creation of definition object file.
Table 4-1 Names of files where network communication definitions are registered (1)
Definition name | Number of definition source files | Definition object file name#1 | Definition command name to be specified (definition name) |
---|---|---|---|
MCF manager definition | 1 for each definition | $DCCONFPATH/_mu......#2 | dcsvstart -m (system service configuration definition) |
MCF communication configuration definition | 2 for each definition | $DCCONFPATH/_mu......#2 | mcfmcname -s (MCF manager definition) |
MCF application definition | 1 for each definition | $DCCONFPATH/any | mcftenv -a (MCF communication configuration definition) |
Table 4-2 Names of files where network communication definitions are registered (2)
Definition name | Definition file name (full path name) | Definition command name to be specified (definition name) |
---|---|---|
System service information definition | $DCDIR/lib/sysconf/ definition-file-name#1 | mcfmcname -s (MCF manager definition) |
System service common information definition | $DCDIR/lib/sysconf/ mcf#2 | There is no definition command to be specified. |
MCF performance verification trace definition | $DCCONFPATH/_mc | There is no definition command to be specified. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.