1cimmof(1) cimmof(1)
2
6 cimmof - compile MOF files into the CIM Repository
7
9 cimmof -h | --help
10 cimmof --version
12 cimmof [ -w ] [ -E ] [ -uc ] [ -aE | -aV | -aEV ] [ -I path ]
14 [ -n namespace ] [ --namespace namespace ] [ --xml ]
15 [ --trace ] [ mof_file ... ]
16 Remarks
18 Only a superuser or user with write access to the default or specified
19 namespace can run the cimmof command to compile MOFs in the CIM Reposi‐
20 tory.
21 Superclasses must be compiled before subclasses, else the compile will
23 fail.
24 It is strongly recommended that MOF files include all necessary sub‐
26 classes, so they can compile properly even if certain classes are not
27 in the CIM Repository.
28
30 The cimmof command is the command line interface to the Managed Object
31 Format (MOF) Compiler. The MOF Compiler is a utility that compiles MOF
32 files (using the MOF format defined by the DMTF CIM Specification) into
33 CIM classes and instances that are stored in the CIM Repository.
34 The cimmof command can be used to compile MOF files at any time after
36 installation. If no input file is specified, stdin is used as the
37 input.
38 The MOF Compiler requires that the input MOF files be in the current
40 directory or that a fully qualified path be given. To simplify the
41 specification of multiple MOF files in the cimmof command line, the MOF
42 Compiler allows compiling from files containing a list of MOF files
43 using the include pragma (as shown below).
44 #pragma include ("application.mof")
46 #pragma include ("server.mof")
47 MOF files using the include pragma must be in the current directory or
49 in a directory specified by the -I command line option.
50 The -n option can be used to specify a R namespace in which the CIM
52 classes and instances will be compiled. If this option is not speci‐
53 fied, the default R namespace is root/cimv2 (with the exception of
54 provider registration schemas).
55 For provider registration schemas, if the -n option is not specified,
57 the default R namespace is root/PG_InterOp. If -n option is specified,
58 the R namespace specified must be root/PG_InterOp, otherwise, the error
59 message "The requested operation is not supported." is returned. For
60 provider MOFs, the R namespace specified must match one of the names‐
61 paces specified in the PG_ProviderCapabilities class schema definition.
62 Options
64 The cimmof command recognizes the following options:
65 -aE Allow Experimental Schema changes.
67 -aEV Allow both Experimental and Version Schema
69 changes.
70 -aV Allow both Major and Down Revision Schema
72 changes.
73 -E Syntax check only
75 -h, --help Display command usage information.
77 -I path Specify the path to included MOF files. This
79 path may be relative or absolute.
80 If the input MOF file has include pragmas and the
82 included files do not reside in the current
83 directory, the directive must be used to specify
84 a path to them on the cimmof command line.
85 -n Override the default CIM Repository namespace.
87 The namespace specified must be a valid CIM
88 namespace name. For the definition of a valid
89 CIM namespace name, refer to the Administrator's
90 Guide. For provider registration schemas, the
91 namepace specified must be root/PG_InterOp.
92 --namespace Override the default CIM Repository namespace.
94 The namespace specified must be a valid CIM
95 namespace name. For the definition of a valid
96 CIM namespace name, refer to the Administrator's
97 Guide. For provider registration schemas, the
98 namepace specified must be root/PG_InterOp.
99 --trace Trace to file (default to stdout)
101 -uc Allow update of an existing class definition.
103 --version Display CIM Server version.
105 -w Suppress warning messages.
107 When compiling the MOF files, if there are CIM
109 elements (such as classes, instances, properties,
110 or methods) defined in the MOF files which
111 already exist in the CIM Repository, the cimmof
112 command returns warning messages. The -w option
113 can be used to suppress these warning messages.
114 --xml Output XML only, to stdout. Do not update reposi‐
116 tory.
117
119 The cimmof command returns one of the following values:
120 0 Successful completion
122 1 Error
123 When an error occurs, an error message is written to stderr and an
125 error value of 1 is returned.
126
128 The cimmof command requires that the CIM Server is running. If an
129 operation requires more than two minutes to be processed, the cimmof
130 command prints a timeout message and returns an error value.
131
133 Error trying to create Repository in path localhost:5988: Cannot con‐
134 nect to: localhost:5988 Failed to set DefaultNamespacePath.
135 The CIM Server is not running. Start the CIM Server with the
137 command and re-run cimmof .
138 If the MOF Compiler detects an error in the MOF file while parsing the
140 file, a parsing error is returned with the line number of the MOF file
141 containing the error.
142 Operation cannot be carried out since the specified superclass does not
144 exist.
145 The MOF Compiler compiled a MOF file with superclasses that were
147 not in the CIM Repository.
148 For a list of possible error messages that may be returned, refer to
150 the Chapter on WBEM messages in the Administrator's Guide.
151
153 Compile a MOF file into the default namespace in the CIM Repository,
154 issue the cimmof command with no options.
155 cimmof processInfo.mof
157 Compile the MOF files into the "root/application" namespace.
159 cimmof -nroot/application test1.mof test2.mof
161 Compile the MOF file defined in the directory ./MOF with the name CIM‐
163 Schema25.mof, and containing include pragmas for other MOF files also
164 in the ./MOF directory.
165 cimmof -w -I./MOF MOF/CIMSchema25.mof
167 Display Usage Info for the cimmof command.
169 cimmof -h
171
173 cimserver(1).
174 cimmof(1)