<!DOCTYPE REFENTRY PUBLIC "-//Sun Microsystems//DTD DocBook V3.0-Based SolBook Subset V2.0//EN" [
<!--ArborText, Inc., 1988-1999, v.4002-->
<!ENTITY meta-info SYSTEM "meta-info.sgm">
<!ENTITY options-common SYSTEM "options-common.sgm">
<!ENTITY synopsis-common SYSTEM "synopsis-common.sgm">
<!ENTITY Date "22 Dec 2004">
<!ENTITY SectDesc "User Commands">
<!ENTITY Software "J2EE SDK 1.4">
<!ENTITY arch "generic">
<!ENTITY copyright "Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved">
<!ENTITY % commonents SYSTEM "smancommon.ent">
%commonents;
<!ENTITY % booktitles SYSTEM "booktitles.ent">
%booktitles;
<!ENTITY Dash "&ndash;">
]>
<?Pub UDT _bookmark _target>
<?Pub Inc>
<refentry id="set-1">
<refmeta><refentrytitle>set</refentrytitle><manvolnum>1</manvolnum>&meta-info;
</refmeta>
<refnamediv><indexterm><primary sortas="set">set &mdash; sets the values of
attributes</primary></indexterm><indexterm><primary sortas=" sets the values of attributes">
sets the values of attributes &mdash; set</primary></indexterm><refname>set
</refname><refpurpose>sets the values of attributes</refpurpose></refnamediv>
<refsynopsisdiv><title>&synp-tt;</title>
<cmdsynopsis><command>set</command>&synopsis-common;
<arg choice="plain"><replaceable>attributename=value</replaceable></arg>
</cmdsynopsis></refsynopsisdiv>
<refsect1><title>&desc-tt;</title>
<para>Sets the values of one or more configurable attribute.</para>
<para>An application server dotted name uses the &ldquo;<literal>.</literal>&rdquo;
(period) as a delimiter to separate the parts of a complete name. This is
similar to how the &ldquo;<literal>/</literal>&rdquo; character is used to
delimit the levels in the absolute path name of a file in the UNIX file system.
The following rules apply while forming the dotted names accepted by the <command>
get</command>, <command>set</command> and <command>list</command> commands.
Note that a specific command has some additional semantics applied.</para>
<itemizedlist>
<listitem><para> A <literal>.</literal> (period) always separates two sequential
parts of the name.</para></listitem>
<listitem><para>A part of the name usually identifies an application server
subsystem and/or its specific instance. For example: web-container, log-service,
thread-pool-1 etc.</para></listitem>
<listitem><para>If any part of the name itself contains a <literal>.</literal>
(period), then it must be escaped with a leading <literal>\</literal> (backslash)
so that the &ldquo;<literal>.</literal>&rdquo; does not act like a delimiter.
</para></listitem>
<listitem><para>The top level switch for any dotted name is <option>&Dash;monitor
</option> or <option role="nodash">&Dash;m</option> that is separately specified
on a given command line. The presence or lack of this switch implies the selection
of one of the two hierarchies for appserver management: monitoring and configuration.
</para>
<para>If you happen to know the exact complete dotted name without any wildcard
character, then <command>list</command> and <command>get</command>/<command>
set</command> have a little difference in their semantics:<itemizedlist>
<listitem><para>The <command>list</command> command treats this complete dotted
name as the complete name of a parent node in the abstract hierarchy. Upon
providing this name to <command>list</command> command, it simply returns
the names of the immediate children at that level. For example, <command>
list server.applications.web-module</command> will list all the web modules
deployed to the domain or the default server.</para></listitem>
<listitem><para>The<command> get</command> and <command>set</command> commands
treat this complete dotted name as the fully qualified name of the attribute
of a node (whose dotted name itself is the name that you get when you remove
the last part of this dotted name) and it gets/sets the value of that attribute.
This is true if such an attribute exists. You will never start with this case
because in order to find out the names of attributes of a particular node
in the hierarchy, you must use the wildcard character <literal>*</literal>.
For example, <command>server.applications.web-module.JSPWiki.context-root
</command> will return the context-root of the web-application deployed to
the domain or default server.</para></listitem>
</itemizedlist></para></listitem>
<listitem><para>If you are using the Enterprise Edition of the Application
Server, then "<classname>server</classname>" (usually the first part of the
complete dotted name) can be replaced with the name of a particular server
instance of interest (e.g., <classname>server1</classname>) and you'll get
the information of that server instance, remaining part of the dotted name
remaining the same. Note that the dotted names that are available in such
other server instances are those from the monitoring hierarchy because these
server instances don't have a way to expose the configuration hierarchy.</para>
</listitem>
</itemizedlist>
<para>The <command>list</command> command is the progenitor of navigational
capabilities of these three commands. If you want to <command>set</command>
or <command>get</command> attributes of a particular application server subsystem,
you must know its dotted name. The <command>list</command> command is the
one which can guide you to find the dotted name of that subsystem. For example,
to find out the modified date (attribute) of a particular file in a large
file system that starts with <literal>/</literal>. First you must find out
the location of that file in the file system, and then look at its attributes.
Therefore two of the first commands to understand the hierarchies in appserver
are: <command>* list *</command> and <command>* list "*" <option>&Dash;monitor
</option></command>. The sorted output of these commands is typically of the
following form:</para>
<informaltable frame="topbot">
<tgroup cols="2" colsep="0" rowsep="0">
<?PubTbl tgroup dispwid="7.56in">
<colspec colname="COLSPEC0" colwidth="20.22*"><colspec colname="COLSPEC1"
colwidth="79.78*">
<thead>
<row rowsep="1"><entry><para>Command</para></entry><entry><para>Output</para></entry>
</row>
</thead>
<tbody>
<row><entry><para><command>list *</command></para></entry><entry><para><itemizedlist>
<listitem><para><classname>default-config</classname></para></listitem>
<listitem><para><classname>default-config.admin-service</classname></para>
</listitem>
<listitem><para><classname>default-config.admin-service.das-config</classname></para>
</listitem>
<listitem><para><classname>default-config.admin-service.jmx-connector.system
</classname></para></listitem>
<listitem><para><classname>default-config.admin-service.jmx-connector.system.ssl
</classname></para></listitem>
<listitem><para><classname>default-config.availability-service</classname></para>
</listitem>
<listitem><para><classname>default-config.availability-service.jms-availability
</classname></para></listitem>
<listitem><para><classname>default-config.diagnostic-service</classname></para>
</listitem>
<listitem><para><classname>default-config.ejb-container</classname></para>
</listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>default-config.http-service.http-listener.http-listener-1
</classname></para></listitem>
<listitem><para><classname>default-config.http-service.http-listener.http-listener-2
</classname></para></listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>default-config.iiop-service</classname></para>
</listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>default-config.java-config</classname></para></listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>domain</classname></para></listitem>
<listitem><para><classname>domain.clusters</classname></para></listitem>
<listitem><para><classname>domain.configs</classname></para></listitem>
<listitem><para><classname>domain.resources</classname></para></listitem>
<listitem><para><classname>domain.resources.jdbc-connection-pool.DerbyPool
</classname></para></listitem>
<listitem><para><classname>domain.resources.jdbc-connection-pool._CallFlowPool
</classname></para></listitem>
<listitem><para><classname>domain.resources.jdbc-connection-pool._TimerPool
</classname></para></listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>server</classname></para></listitem>
<listitem><para><classname>server-config</classname></para></listitem>
<listitem><para><classname>cerver-config.admin-service</classname></para>
</listitem>
<listitem><para><classname>server-config.admin-service.das-config</classname></para>
</listitem>
<listitem><para><classname>server-config.admin-service.jmx-connector.system
</classname></para></listitem>
<listitem><para><classname>server-config.admin-service.jmx-connector.system.ssl
</classname></para></listitem>
<listitem><para><classname>server-config-availability-servicce</classname></para>
</listitem>
<listitem><para><classname>server-config.availability-service.jms-availability
</classname></para></listitem>
<listitem><para><classname>server-config.diagnostic-service</classname></para>
</listitem>
<listitem><para><classname>server-config.ejb-container</classname></para>
</listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>server.log-service</classname></para></listitem>
<listitem><para><classname>server.log-service.module-log-levels</classname></para>
</listitem>
<listitem><para><classname>. . . </classname></para></listitem>
<listitem><para><classname>server.session-config</classname></para></listitem>
<listitem><para><classname>server.session-config.session-manager</classname></para>
</listitem>
<listitem><para><classname>server.session-config.session-manager.manager-properties
</classname></para></listitem>
<listitem><para><classname>server.session-config.session-manager.store-properties
</classname></para></listitem>
<listitem><para><classname>server.session-config.session-properties</classname></para>
</listitem>
<listitem><para><classname>server.thread-pools</classname></para></listitem>
<listitem><para><classname>server.thread-pools.thread-pool.thread-pool-1</classname></para>
</listitem>
<listitem><para><classname>server.transaction-service</classname></para></listitem>
<listitem><para><classname>server.web-container</classname></para></listitem>
<listitem><para><classname>server.web-container-availability</classname></para>
</listitem>
</itemizedlist></para></entry></row>
<row><entry colname="COLSPEC0"><para><command>list <option>&Dash;monitor</option>
*</command></para></entry><entry colname="COLSPEC1"><para><itemizedlist>
<listitem><para><classname>server</classname></para></listitem>
<listitem><para><classname>server.applications</classname></para></listitem>
<listitem><para><classname>server.applications._JWSappclients</classname></para>
</listitem>
<listitem><para><classname>server.applications._JWSappclients.sys\.war</classname></para>
</listitem>
<listitem><para><classname>server.applications.adminapp</classname></para>
</listitem>
<listitem><para><classname>server.applications.admingui</classname></para>
</listitem>
<listitem><para><classname>server.connector-service</classname></para></listitem>
<listitem><para><classname>server.http-service</classname></para></listitem>
<listitem><para><classname>server.http-service.server</classname></para></listitem>
<listitem><para><classname>server.jms-service</classname></para></listitem>
<listitem><para><classname>server.jvm</classname></para></listitem>
<listitem><para><classname>server.orb</classname></para></listitem>
<listitem><para><classname>server.orb.connection-managers</classname></para>
</listitem>
<listitem><para><classname>server.resources</classname></para></listitem>
<listitem><para><classname>server.thread-pools</classname></para></listitem>
</itemizedlist></para></entry></row>
</tbody>
</tgroup>
</informaltable>
<para>Consequently, the <command>list</command> command is the entry point
into the navigation of the application server's s management hierarchies.
Take note of the output of the <command>list</command> command:</para>
<itemizedlist>
<listitem><para>The output lists one element per line.</para></listitem>
<listitem><para> Every element on a line is a complete-dotted-name of a management
component that is capable of having attributes. Note that none of these lines
show any kind of attributes at all.</para></listitem>
</itemizedlist>
<para>The output of the<command>list</command> command is a list of dotted
names representing individual application server components and subsystems.
Every component or subsystem is capable of having zero or more attributes
that can be read and modified.</para>
<para>With the<command>list</command> command you can drill down through the
hierarchy in a particular branch of interest. For example, if you want to
find the configuration of the <command>http-listener</command> of the domain
(the default server, whose ID is "<classname>server</classname>"). Here is
how you could proceed on a UNIX terminal:</para>
<informaltable frame="topbot">
<tgroup cols="3" colsep="0" rowsep="0">
<?PubTbl tgroup dispwid="7.72in">
<colspec colname="COLSPEC2" colwidth="7.13*"><colspec colname="COLSPEC3" colwidth="37.93*">
<colspec colname="COLSPEC4" colwidth="53.95*">
<thead>
<row rowsep="1"><entry><para>ID</para></entry><entry><para>Command</para></entry>
<entry><para>Output/Comment</para></entry></row>
</thead>
<tbody>
<row><entry><para>1</para></entry><entry><para><command>list "*" | grep http
| grep listener</command></para></entry><entry><para><orderedlist>
<listitem><para><classname>default-config.http-service.<?Pub _newline>http-listener.http-listener-1
</classname></para></listitem>
<listitem><para><classname>default-config.http-service.<?Pub _newline>http-listener.http-listener-2
</classname></para></listitem>
<listitem><para><classname>server-config.http-service.<?Pub _newline>http-listener.admin-listener
</classname></para></listitem>
<listitem><para><classname>server-config.http-service.<?Pub _newline>http-listener.http-listener-1
</classname></para></listitem>
<listitem><para><classname>server-config.http-service.<?Pub _newline>http-listener.http-listener-2
</classname></para></listitem>
<listitem><para><classname>server-http-service.http-listener.admin-listener
</classname></para></listitem>
<listitem><para><classname><replaceable>server.http-service.http-listener.http-listener-1
</replaceable></classname></para></listitem>
<listitem><para><classname>server.http-service.http-listener.http-listener-2
</classname></para></listitem>
</orderedlist></para></entry></row>
<row><entry colname="COLSPEC2"><para>2</para></entry><entry colname="COLSPEC3"><para>
To find the listener that corresponds to the default <command>http-listener
</command> where the web applications in the <filename>domain/server</filename>
are deployed:</para><para><orderedlist>
<listitem><para>Examine the dotted name starting with item number 7 in above
output.</para></listitem>
<listitem><para>Use the <command>get</command> command as shown in its usage.
</para></listitem>
</orderedlist>For example, <command>get server.<?Pub _newline>http-service.http-<?Pub _newline>listener.http-<?Pub _newline>listener-1.*
</command> will return <?Pub _newline>all the attributes of the <?Pub _newline><command>
http-listener</command> in context.</para></entry><entry colname="COLSPEC4"><para>
server.http-service.http-listener.http-listener-1.acceptor-threads = 1<?Pub _newline>server.http-service.http-listener.http-listener-1.address
= 0.0.0.0<?Pub _newline>server.http-service.http-listener.http-listener-1.blocking-enabled
= false<?Pub _newline>server.http-service.http-listener.http-listener-1.default-virtual-server
= server<?Pub _newline>server.http-service.http-listener.http-listener-1.enabled
= true<?Pub _newline>server.http-service.http-listener.http-listener-1.external-port
=<?Pub _newline>server.http-service.http-listener.http-listener-1.family =
inet<?Pub _newline>server.http-service.http-listener.http-listener-1.id =
http-listener-1<?Pub _newline>server.http-service.http-listener.http-listener-1.port
= 8080<?Pub _newline>server.http-service.http-listener.http-listener-1.redirect-port
=<?Pub _newline>server.http-service.http-listener.http-listener-1.security-enabled
= false<?Pub _newline>server.http-service.http-listener.http-listener-1.server-name
=<?Pub _newline>server.http-service.http-listener.http-listener-1.xpowered-by
= true</para></entry></row>
</tbody>
</tgroup>
</informaltable>
<para>Making use of both <command>list</command> and <command>get</command>
commands, it is straightforward to reach a particular component of interest.
</para>
<para>To get the monitoring information of a particular subsystem you must:
</para>
<orderedlist>
<listitem><para>Use the <command>set</command> command to set an appropriate
monitoring level for the component of interest.</para></listitem>
<listitem><para>Obtain the various information about the JVM that the application
server domain is running.</para></listitem>
</orderedlist>
<informaltable frame="topbot">
<tgroup cols="3" colsep="0" rowsep="0">
<?PubTbl tgroup dispwid="7.68in">
<colspec colname="COLSPEC0" colwidth="7.33*"><colspec colname="COLSPEC1" colwidth="38.15*">
<colspec colname="COLSPEC2" colwidth="53.54*">
<thead>
<row rowsep="1"><entry><para>ID</para></entry><entry><para>Command</para></entry>
<entry><para>Output/Comment</para></entry></row>
</thead>
<tbody>
<row><entry><para>1</para></entry><entry><para><command>list server* | grep
monitoring</command></para></entry><entry><para>server-config.monitoring-service<?Pub _newline>server-config.monitoring-service.module-monitoring-levels<?Pub _newline>server.monitoring-service<?Pub _newline>server.monitoring-service.module-monitoring-levels
</para><para>Note that this is the <command>list</command> command. It only
shows the hierarchy, nothing else. Using the '|' and "grep" narrows down the
search effectively. Now, you can choose <classname>server.monitoring-service
</classname> to set the attributes of various attributes that can be monitored.
</para><para>This is the configuration data because this setting will be persisted
to the server's configuration store.</para></entry></row>
<row><entry colname="COLSPEC0"><para>2</para></entry><entry colname="COLSPEC1"><para><command>
get server.monitoring-service.*</command></para></entry><entry colname="COLSPEC2"><para>
You can try the number of attributes that are presently available with monitoring
service. Here is the output: </para><para>No matches resulted from the wildcard
expression. This is because this fully dotted name does not have any attributes
at all. Logically, you try the next one and that is: <command>server.monitoring-service.module-monitoring-levels
</command>. Again, use the wildcard character to get ALL the attributes of
a particular component.</para></entry></row>
<row><entry colname="COLSPEC0"><para>3</para></entry><entry colname="COLSPEC1"><para><command>
get server.monitoring-service.<?Pub _newline>module-monitoring-levels.*</command></para></entry>
<entry colname="COLSPEC2"><para>server.monitoring-service.module-monitoring-levels.<?Pub _newline>connector-connection-pool
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>connector-service
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>ejb-container
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>http-service
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>jdbc-connection-pool
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>jms-service
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>jvm
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>orb
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>thread-pool
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>transaction-service
= OFF <?Pub _newline>server.monitoring-service.module-monitoring-levels.<?Pub _newline>web-container
= OFF </para><para>The JVM monitoring is at a level OFF. It must be changed
in order to make the JVM monitoring information available. The other valid
values for all the monitoring level are: LOW and HIGH. use the <command>set
</command> command to set the value appropriately.</para></entry></row>
<row><entry colname="COLSPEC0"><para>4</para></entry><entry colname="COLSPEC1"><para><command>
set server.monitoring-service.<?Pub _newline>module-monitoring-levels.<?Pub _newline>jvm=HIGH
</command></para><para>There is no space before or after the = sign.</para></entry>
<entry colname="COLSPEC2"><para>server.monitoring-service.module-monitoring-levels.jvm
= HIGH</para><para>Now, the JVM information can be obtained using the <command>
get</command> command and monitoring switch. But remember , when you switch
to the monitoring hierarchy, start with the <command>list</command> command
again. </para></entry></row>
<row><entry colname="COLSPEC0"><para>5</para></entry><entry colname="COLSPEC1"><para><command>
list --monitor * | grep jvm</command></para></entry><entry colname="COLSPEC2"><para>
server.jvm <?Pub _newline>server.jvm.class-loading-system <?Pub _newline>server.jvm.compilation-system <?Pub _newline>server.jvm.garbage-collectors <?Pub _newline>server.jvm.garbage-collectors.Copy <?Pub _newline>server.jvm.garbage-collectors.MarkSweepCompact <?Pub _newline>server.jvm.memory
server.jvm.operating-system <?Pub _newline>server.jvm.runtime server.jvm.thread-system <?Pub _newline>server.jvm.thread-system.thread-1 <?Pub _newline>.
. . <?Pub _newline>server.jvm.thread-system.thread-793823 <?Pub _newline>server.jvm.thread-system.thread-793824 <?Pub _newline>server.jvm.thread-system.thread-793825 <?Pub _newline>server.jvm.thread-system.thread-793826 <?Pub _newline>server.jvm.thread-system.thread-793827 <?Pub _newline>server.jvm.thread-system.thread-9
</para><para>The JRE 1.5.0 monitorable components are exposed in an elegant
manner. This is what you see when connected by the JConsole.  Now, to know
more about the class-loading system in the JVM, this is how you'll proceed.
</para><para>Note that now you are interested in the attributes of a particular
leaf node. Thus the command is <command>get</command> not <command>list</command>.
</para></entry></row>
<row><entry colname="COLSPEC0"><para>6</para></entry><entry colname="COLSPEC1"><para><command>
get <option>&Dash;monitor</option> server.jvm.class-loading-<?Pub _newline>system.*
</command></para></entry><entry colname="COLSPEC2"><para>server.jvm.class-loading-system.dotted-name
= server.jvm.class-loading-system <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-count
= 7328 <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-description
= No Description was available <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-lastsampletime
= 1133819508973 <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-name
= LoadedClassCount? <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-starttime
= 1133819131268 <?Pub _newline>server.jvm.class-loading-system.loadedclasscount-unit
= count <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-count
= 10285 <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-description
= No Description was available <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-lastsampletime
= 1133819508972 <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-name
= TotalLoadedClassCount? <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-starttime
= 1133819131268 <?Pub _newline>server.jvm.class-loading-system.totalloadedclasscount-unit
= count <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-count
= 2957 <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-description
= No Description was available <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-lastsampletime
= 1133819508973 <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-name
= UnloadedClassCount? <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-starttime
= 1133819131268 <?Pub _newline>server.jvm.class-loading-system.unloadedclasscount-unit
= count</para><para>You cansee that 10285 is the total number of classes loaded
by the Virtual Machine. Whereas, 2957 is number of classes unloaded, since
it was started.  ,Similarly, you can explore attributes of the other subsystems
as well.</para></entry></row>
</tbody>
</tgroup>
</informaltable>
</refsect1>
<refsect1><title>OPTIONS</title>
<variablelist termlength="medium">&options-common;
<?Pub Caret></variablelist></refsect1>
<refsect1><title>OPERANDS</title>
<variablelist termlength="medium">
<varlistentry><term><replaceable>attributename=value</replaceable></term>
<listitem><para>identifies the attribute name and its value. See the <emphasis>
Reference</emphasis> for a listing of the available attribute names.</para>
</listitem></varlistentry>
</variablelist></refsect1>
<refsect1><title>&exam-tt;</title>
<example>
<title>Using <command>set</command></title>
<screen>asadmin> <userinput>set --user admin --passwordfile password.txt --host localhost 
--port 4848 server.transaction-service.automatic-recovery=true</userinput>

</screen>
</example>
</refsect1>
<refsect1><title>EXIT STATUS</title>
<variablelist termlength="medium">
<varlistentry><term>0</term><listitem><para>command executed successfully
</para>
</listitem></varlistentry>
<varlistentry><term>1</term><listitem><para>error in executing the command
</para>
</listitem></varlistentry>
</variablelist></refsect1>
<refsect1><title>&also-tt;</title>
<para><link linkend="get-1"><citerefentry><refentrytitle>get</refentrytitle>
<manvolnum>1</manvolnum></citerefentry></link>, <link linkend="list-1"><citerefentry>
<refentrytitle>list</refentrytitle><manvolnum>1</manvolnum></citerefentry></link></para>
</refsect1>
</refentry>
<?Pub *0000026388>
