WebSphere Message Brokers
File: an07350_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:33:36

mqsicreatemsgdefs command

Supported platforms

  • Windows
  • Linux (x86 platform)

Purpose

The command generates message definition files (*.mxsd), according to a set of import options specified in an option file. The generated files are placed in the specified message set folder.

The mqsicreatemsgdefs command takes as a parameter a directory where source files of various types, for example, C and COBOL, are located (in addition to various other parameters) and invokes the appropriate operation based on the extensions to the files.

Note:
  1. Ensure that only the files that are required for the command to run exist in the directory and subdirectory structure you specify. One of the actions the mqsicreatemsgdefs command performs is to copy all the files in the directory and subdirectories into the workspace prior to creating the message definition. This could include any files not associated to the message definitions you are trying to create.
  2. You must specify the -data WorkspacePath parameter to specify the target workspace.

Syntax

Parameters

-p MessageSetProjectName
(Required) The name of the message set project. If the project does not exist, a new one is created.
-d Pathname of source files folder
(Required) The absolute or relative path name of the directory of definition files (source files).

All relevant files located in any sub folders under the source files folder are scanned and imported.

-data WorkspacePath
(Required) The path of the workspace in which your projects are created.

The workspace location is also the default location for projects. Relative paths are interpreted as being relative to the directory from which the command was started.

-base
(Optional) If a new message set is to be created, this is the existing message set project and message set, on which it is based.
-rmp
(Optional) Replaces the existing project of the same name.
-rmd
(Optional) Replaces an existing message definition file of the same name.
Note:
  1. If this flag is omitted, and a message definition file of the same name exists, you receive a warning.
  2. The location of the generated message definition file in the message set is determined by the target namespace.
-ns
(Optional) If a new message set is to be created, the message set is enabled for namespace support
-msg
(Optional) Creates messages from complex global elements
-opt xxx.xml
(Optional) The absolute or relative pathname of the options file. The options file can be one of the following types: If you do not specify a specific option, the default options file called mqsicreatemsgdefs.xml is used; see Default options file.

You can copy the default options file and customize it to create an options file for your environment.

-v
(Optional) Verbose report.
-log ReportFilePathname
(Optional) Absolute or relative path name of the report file. If omitted, the report is written to the default log file named mqsicreatemsgdefs.report.txt in the Eclipse current directory.

If you specify -log without the report file path name, or a path name that is not valid, the command issues an error message and stops.

Examples

The following example creates or uses the message set project newproject in the source file c:\myproject\source and replaces the existing message project and message definition files of the same name.

mqsicreatemsgdefs -p newproject -d c:\myproject\source -rmp -rmd
Related concepts
Message definition files
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:36

an07350_ This topic's URL is: