ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/adddstrte.htm

390 lines
17 KiB
HTML

<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Add Distribution Route (ADDDSTRTE)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="ADDDSTRTE.Top_Of_Page"></a>
<h2>Add Distribution Route (ADDDSTRTE)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#ADDDSTRTE.PARAMETERS.TABLE">Parameters</a><br>
<a href="#ADDDSTRTE.COMMAND.EXAMPLES">Examples</a><br>
<a href="#ADDDSTRTE.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="ADDDSTRTE"></a>
<p>The Add Distribution Route (ADDDSTRTE) command allows you to add an entry to the distribution services routing table. The routing table determines which distribution queue receives a distribution on its way to a particular destination.
</p>
<p>Distributions are routed to distribution queues based on service levels. One or more service levels must be specified for each routing table entry. Your system will not route distributions for service levels you have not configured. Normally, all service levels routed to the same destination use the same distribution queue. However, the user can configure several distribution queues for one destination based on distribution service levels.
</p>
<p>System names, group names, and distribution queue names are translated to the graphic character set and code page 930 500, using the job's coded character set identifier (CCSID).
</p>
<p><b>Restrictions:</b>
</p>
<ul>
<li>This command is shipped with public *EXCLUDE authority, and the QPGMR and QSYSOPR user profiles have private authorities to use the command.
</li>
</ul>
<ul>
<li>An error occurs if a distribution route specifying a SystemView distribution services (SVDS) type of distribution queue includes another type of distribution queue (such as SNA distribution services (SNADS) or VM/MVS bridge (RPDS)).
</li>
</ul>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="ADDDSTRTE.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDDSTRTE.SYSNAME"><b>SYSNAME</b></a></td>
<td valign="top">System name</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="3">Required, Positional 1</td>
</tr>
<tr>
<td valign="top">Element 1: System name</td>
<td valign="top">
<i>Character value</i>, *ANY</td>
</tr>
<tr>
<td valign="top">Element 2: System group</td>
<td valign="top">
<i>Character value</i>, *ANY</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDDSTRTE.FAST"><b>FAST</b></a></td>
<td valign="top">Fast service level</td>
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Distribution queue name</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Hop count</td>
<td valign="top">
1-255, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDDSTRTE.STATUS"><b>STATUS</b></a></td>
<td valign="top">Status service level</td>
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Distribution queue name</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Hop count</td>
<td valign="top">
1-255, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDDSTRTE.DATAHIGH"><b>DATAHIGH</b></a></td>
<td valign="top">Data high service level</td>
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Distribution queue name</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Hop count</td>
<td valign="top">
1-255, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#ADDDSTRTE.DATALOW"><b>DATALOW</b></a></td>
<td valign="top">Data low service level</td>
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Distribution queue name</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Hop count</td>
<td valign="top">
1-255, <b><u>*NETATR</u></b></td>
</tr>
<tr>
<td valign="top"><a href="#ADDDSTRTE.TEXT"><b>TEXT</b></a></td>
<td valign="top">Text</td>
<td valign="top"><i>Character value</i>, <b><u>*BLANK</u></b></td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="ADDDSTRTE.SYSNAME"></a>
<h3>System name (SYSNAME)</h3>
<p>Specifies the system name and group name of the remote system that is the destination for this routing table entry.
</p>
<p>You can specify a maximum of 8 characters for the system name and a maximum of 8 characters for the group name.
</p>
<p>*ANY can be specified for the system name. When <b>SYSNAME(*ANY group)</b> is specified, any system in the group can be the destination for the routing table entry. Only one *ANY is allowed for each group in the routing table and is used to resolve a distribution destination that does not match a specific system name, but matches a group name.
</p>
<p>*ANY can be specified for the group name only if *ANY is also specified for the system name. Only one <b>SYSNAME(*ANY *ANY)</b> entry is allowed in the routing table and is used to resolve a distribution destination that does not match any other routing table entries.
</p>
<p>This is a required parameter.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDDSTRTE.FAST"></a>
<h3>Fast service level (FAST)</h3>
<p>Specifies the distribution queue and maximum hop count to the destination system for fast service level distributions. The fast service level is the highest priority service level.
</p>
<p>The maximum hop count is the maximum number of times in a SNADS network that a distribution can be routed (hop) between systems at the SNADS level, including the hop to the final destination system. The maximum hop count does not include the hops made by advanced peer-to-peer networking (APPN) routing. If the maximum number of hops is exceeded, the distribution is ended and an error message is sent to the user who originally sent the distribution. Maximum hop count provides a means to prevent a distribution from looping indefinitely among systems.
</p>
<p>The possible <b>distribution queue</b> values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>No distribution queue is specified for distributions requiring a fast service level. Distributions requiring fast service cannot be routed using this routing table entry.
</dd>
</dl>
<dl>
<dt><b><i>distribution-queue-name</i></b></dt>
<dd>Specify the name of the distribution queue to which distributions using this service level and routing entry are sent. The distribution queue must already exist and cannot be a DLS (document library services) type of queue.
</dd>
</dl>
<p>The possible <b>maximum hop count</b> values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The system network attributes value for the maximum hop count is used. You can display the current system value using the Display Network Attributes (DSPNETA) command.
</dd>
<dt><b><i>hop-count</i></b></dt>
<dd>Specify the maximum hop count. Valid values range from 1 through 255.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDDSTRTE.STATUS"></a>
<h3>Status service level (STATUS)</h3>
<p>Specifies the distribution queue and maximum hop count to the destination system for status service level distributions. The status service level is used for network status and other feedback information.
</p>
<p>The maximum hop count is the maximum number of times in a SNADS network that a distribution can be routed (hop) between systems at the SNADS level, including the hop to the final destination system. The maximum hop count does not include the hops made by advanced peer-to-peer networking (APPN) routing. If the maximum number of hops is exceeded, the distribution is ended and an error message is sent to the user who originally sent the distribution. Maximum hop count provides a means to prevent a distribution from looping indefinitely among systems.
</p>
<p>The possible <b>distribution queue</b> values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>No distribution queue is specified for distributions requiring a status service level. Distributions requiring status service cannot be routed using this routing table entry.
</dd>
</dl>
<dl>
<dt><b><i>distribution-queue-name</i></b></dt>
<dd>Specify the name of the distribution queue to which distributions using this service level and routing entry are sent. The distribution queue must already exist and cannot be a DLS (document library services) type of queue.
</dd>
</dl>
<p>The possible <b>maximum hop count</b> values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The system network attributes value for the maximum hop count is used. You can display the current system value using the Display Network Attributes (DSPNETA) command.
</dd>
<dt><b><i>hop-count</i></b></dt>
<dd>Specify the maximum hop count. Valid values range from 1 through 255.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDDSTRTE.DATAHIGH"></a>
<h3>Data high service level (DATAHIGH)</h3>
<p>Specifies the distribution queue and maximum hop count to the destination system for data high service level distributions. The data high service level is used for high priority data traffic.
</p>
<p>The maximum hop count is the maximum number of times in a SNADS network that a distribution can be routed (hop) between systems at the SNADS level, including the hop to the final destination system. The maximum hop count does not include the hops made by advanced peer-to-peer networking (APPN) routing. If the maximum number of hops is exceeded, the distribution is ended and an error message is sent to the user who originally sent the distribution. Maximum hop count provides a means to prevent a distribution from looping indefinitely among systems.
</p>
<p>The possible <b>distribution queue</b> values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>No distribution queue is specified for distributions requiring a data high service level. Distributions requiring data high service cannot be routed using this routing table entry.
</dd>
</dl>
<dl>
<dt><b><i>distribution-queue-name</i></b></dt>
<dd>Specify the name of the distribution queue to which distributions using this service level and routing entry are sent. The distribution queue must already exist and cannot be a DLS (document library services) type of queue.
</dd>
</dl>
<p>The possible <b>maximum hop count</b> values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The system network attributes value for the maximum hop count is used. You can display the current system value using the Display Network Attributes (DSPNETA) command.
</dd>
<dt><b><i>hop-count</i></b></dt>
<dd>Specify the maximum hop count. Valid values range from 1 through 255.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDDSTRTE.DATALOW"></a>
<h3>Data low service level (DATALOW)</h3>
<p>Specifies the distribution queue and maximum hop count to the destination system for data low service level distributions. The data low service level is used for most data traffic.
</p>
<p>The maximum hop count is the maximum number of times in a SNADS network that a distribution can be routed (hop) between systems at the SNADS level, including the hop to the final destination system. The maximum hop count does not include the hops made by advanced peer-to-peer networking (APPN) routing. If the maximum number of hops is exceeded, the distribution is ended and an error message is sent to the user who originally sent the distribution. Maximum hop count provides a means to prevent a distribution from looping indefinitely among systems.
</p>
<p>The possible <b>distribution queue</b> values are:
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>No distribution queue is specified for distributions requiring a data low service level. Distributions requiring data low service cannot be routed using this routing table entry.
</dd>
</dl>
<dl>
<dt><b><i>distribution-queue-name</i></b></dt>
<dd>Specify the name of the distribution queue to which distributions using this service level and routing entry are sent. The distribution queue must already exist and cannot be a DLS (document library services) type of queue.
</dd>
</dl>
<p>The possible <b>maximum hop count</b> values are:
</p>
<dl>
<dt><b><u>*NETATR</u></b></dt>
<dd>The system network attributes value for the maximum hop count is used. You can display the current system value using the Display Network Attributes (DSPNETA) command.
</dd>
<dt><b><i>hop-count</i></b></dt>
<dd>Specify the maximum hop count. Valid values range from 1 through 255.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDDSTRTE.TEXT"></a>
<h3>Text (TEXT)</h3>
<p>Specifies the text that briefly describes the object.
</p>
<p>The possible values are:
</p>
<dl>
<dt><b><u>*BLANK</u></b></dt>
<dd>No text is specified.
</dd>
<dt><b><i>'description'</i></b></dt>
<dd>Specify a maximum of 50 characters of text enclosed in apostrophes.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDDSTRTE.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Adding an Entry for an Adjacent System</b>
</p>
<p>
<pre>
ADDDSTRTE SYSNAME(SYSTEMA GROUPA) FAST(SYSTEMA)
STATUS(SYSTEMA)
DATAHIGH(SYSTEMA) DATALOW(SYSTEMA)
</pre>
</p>
<p>This command adds a routing table entry for a system that is directly connected to this system (via a physical advanced program-to-program communications (APPC) connection or a logical APPN connection). The distribution queue is given the same name as the destination system. The hop count defaults to the system default value.
</p>
<p><b>Example 2: Adding a Generic Routing Table Entry</b>
</p>
<p>
<pre>
ADDDSTRTE SYSNAME(*ANY GROUPNM1) FAST(SYSTEMA)
STATUS(SYSTEMA)
DATAHIGH(SYSTEMA) DATALOW(SYSTEMA)
</pre>
</p>
<p>This command adds a routing table entry for all systems in system group GROUPNM1. The distribution queue SYSTEMA is used to route distributions to all systems in the group.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDDSTRTE.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF8801</b></dt>
<dd>Document library services (*DLS) queue &amp;1 not allowed in routing table.
</dd>
<dt><b>CPF8802</b></dt>
<dd>Distribution queue &amp;1 was not found.
</dd>
<dt><b>CPF8807</b></dt>
<dd>Error occurred while using QSNADS journal.
</dd>
<dt><b>CPF881E</b></dt>
<dd>Distribution route contains combination of distribution queues that is not allowed
</dd>
<dt><b>CPF881F</b></dt>
<dd>System group name cannot be blank for distribution route
</dd>
<dt><b>CPF8815</b></dt>
<dd>Routing table entry &amp;1 &amp;2 not found.
</dd>
<dt><b>CPF8831</b></dt>
<dd>Entry &amp;1 &amp;2 already exists in routing table.
</dd>
<dt><b>CPF8837</b></dt>
<dd>System name/Group &amp;1 &amp;2 in use by another distribution services function.
</dd>
<dt><b>CPF8849</b></dt>
<dd>Queue &amp;1 in use by another distribution services function.
</dd>
<dt><b>CPF9845</b></dt>
<dd>Error occurred while opening file &amp;1.
</dd>
<dt><b>CPF9846</b></dt>
<dd>Error while processing file &amp;1 in library &amp;2.
</dd>
<dt><b>CPF9847</b></dt>
<dd>Error occurred while closing file &amp;1 in library &amp;2.
</dd>
<dt><b>CPF9899</b></dt>
<dd>Error occurred during processing of command.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDDSTRTE.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>