Component Management Message Syntax

Identifying Component Messages

All Serena XML component management messages have syntax that tells ChangeMan ZMF to perform a task against a component rather than some other object. In all such messages, the name attribute in the <service> takes the value "cmponent", as follows:

<service name="CMPONENT">

...

Tip

Note the abbreviated spelling of "cmponent" in the name attribute! This value is truncated because ChangeMan ZMF limits name attributes to eight bytes in length.

In addition, a component management task takes a value in the name attribute of the <scope> tag that is consistent with work at the level of individual components. For example, any Serena XML component message with a name attribute of "service" in the <scope> tag is a component-only, component-level task. For example:

<service name="cmponent">
<scope name="service">

Other purely component-level name attributes for the <scope> tag include "ssv_ver", "history", "gen_desc", "chg_desc", and the like.

Component tasks performed at a higher level of aggregation — such as the package level — indicate their higher-level scope in the <scope> tag. For example, attribute values such as "pkg_src" or "pkg_lod" broaden the scale of a component management function to include the components of an entire package as a group. At the same time, these attributes exclude any shared components that reside in packages not named in the request. This behavior classifies such requests as package-level component tasks rather than componentonly tasks — even though, for technical reasons, they are performed by the low-level component service.

For the purposes of this manual, then, syntax such as the following identifies a package-level component function rather than a component-only function:

<service name="CMPONENT">
<scope name="PKG_SRC">

Such tasks are discussed in the package management topic.