Add Distribution Route (ADDDSTRTE)

Where allowed to run: All environments (*ALL)
Threadsafe: No
Parameters
Examples
Error messages

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.

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.

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).

Restrictions:

Top

Parameters

Keyword Description Choices Notes
SYSNAME System name Element list Required, Positional 1
Element 1: System name Character value, *ANY
Element 2: System group Character value, *ANY
FAST Fast service level Single values: *NONE
Other values: Element list
Optional
Element 1: Distribution queue name Character value
Element 2: Hop count 1-255, *NETATR
STATUS Status service level Single values: *NONE
Other values: Element list
Optional
Element 1: Distribution queue name Character value
Element 2: Hop count 1-255, *NETATR
DATAHIGH Data high service level Single values: *NONE
Other values: Element list
Optional
Element 1: Distribution queue name Character value
Element 2: Hop count 1-255, *NETATR
DATALOW Data low service level Single values: *NONE
Other values: Element list
Optional
Element 1: Distribution queue name Character value
Element 2: Hop count 1-255, *NETATR
TEXT Text Character value, *BLANK Optional
Top

System name (SYSNAME)

Specifies the system name and group name of the remote system that is the destination for this routing table entry.

You can specify a maximum of 8 characters for the system name and a maximum of 8 characters for the group name.

*ANY can be specified for the system name. When SYSNAME(*ANY group) 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.

*ANY can be specified for the group name only if *ANY is also specified for the system name. Only one SYSNAME(*ANY *ANY) entry is allowed in the routing table and is used to resolve a distribution destination that does not match any other routing table entries.

This is a required parameter.

Top

Fast service level (FAST)

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.

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.

The possible distribution queue values are:

*NONE
No distribution queue is specified for distributions requiring a fast service level. Distributions requiring fast service cannot be routed using this routing table entry.
distribution-queue-name
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.

The possible maximum hop count values are:

*NETATR
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.
hop-count
Specify the maximum hop count. Valid values range from 1 through 255.
Top

Status service level (STATUS)

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.

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.

The possible distribution queue values are:

*NONE
No distribution queue is specified for distributions requiring a status service level. Distributions requiring status service cannot be routed using this routing table entry.
distribution-queue-name
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.

The possible maximum hop count values are:

*NETATR
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.
hop-count
Specify the maximum hop count. Valid values range from 1 through 255.
Top

Data high service level (DATAHIGH)

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.

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.

The possible distribution queue values are:

*NONE
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.
distribution-queue-name
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.

The possible maximum hop count values are:

*NETATR
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.
hop-count
Specify the maximum hop count. Valid values range from 1 through 255.
Top

Data low service level (DATALOW)

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.

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.

The possible distribution queue values are:

*NONE
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.
distribution-queue-name
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.

The possible maximum hop count values are:

*NETATR
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.
hop-count
Specify the maximum hop count. Valid values range from 1 through 255.
Top

Text (TEXT)

Specifies the text that briefly describes the object.

The possible values are:

*BLANK
No text is specified.
'description'
Specify a maximum of 50 characters of text enclosed in apostrophes.
Top

Examples

Example 1: Adding an Entry for an Adjacent System

ADDDSTRTE   SYSNAME(SYSTEMA GROUPA)  FAST(SYSTEMA)
            STATUS(SYSTEMA)
            DATAHIGH(SYSTEMA)  DATALOW(SYSTEMA)

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.

Example 2: Adding a Generic Routing Table Entry

ADDDSTRTE   SYSNAME(*ANY GROUPNM1)  FAST(SYSTEMA)
            STATUS(SYSTEMA)
            DATAHIGH(SYSTEMA)  DATALOW(SYSTEMA)

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.

Top

Error messages

*ESCAPE Messages

CPF8801
Document library services (*DLS) queue &1 not allowed in routing table.
CPF8802
Distribution queue &1 was not found.
CPF8807
Error occurred while using QSNADS journal.
CPF881E
Distribution route contains combination of distribution queues that is not allowed
CPF881F
System group name cannot be blank for distribution route
CPF8815
Routing table entry &1 &2 not found.
CPF8831
Entry &1 &2 already exists in routing table.
CPF8837
System name/Group &1 &2 in use by another distribution services function.
CPF8849
Queue &1 in use by another distribution services function.
CPF9845
Error occurred while opening file &1.
CPF9846
Error while processing file &1 in library &2.
CPF9847
Error occurred while closing file &1 in library &2.
CPF9899
Error occurred during processing of command.
Top