Filter
Top Products
The class of service mapping table allows for the conversion of non-native COS
names to native COS names and vice versa. Non-native networks using the same
COS names as the extended border node’s native network need not have a COS
mapping table defined. If only some of the non-native COS names differ from the
native COS names, then only those that differ should be configured in a COS
mapping table.
A given COS mapping table may apply to a single or multiple non-native networks.
You may configure multiple COS mapping tables as necessary.
There are limits on the number of non-native network names used in COS mapping
tables. These limits vary according to the model router you have. See Table 38 on
page 191 for the configuration command detail. Limits have been set to allow as
much flexibility as possible in various environments. The ability of the router to
handle the specification of many COS mapping tables, each with many non-native
network names and COS name pairs, is limited by the availability of configuration
nonvolatile memory, router memory, and APPN shared memory. See “APPN Node
Tuning” on page 38 for a discussion of the APPN tuning parameters which control
the amount of APPN shared memory.
COS mapping table name
is the first prompt. As with the analogous name for
routing lists, this parameter is not used by the operational code. It’s purpose is to
allow you to refer to a specific COS mapping table so that you can modify or delete
it. Different COS mapping tables must have different names, but a given COS
mapping table may have an identical name as a routing list.
Non-native CP
name(s) are prompted for next. These are use to specify the
non-native network(s) that this COS mapping table applies to.
As with LU names in a routing list, you may prematurely terminate any of the FQCP
names at any point with a trailing wildcard “*” . This allows you to specify a range of
non-native FQCP names in one or more non-native networks. You may not imbed a
wildcard in the middle of a FQCP name.
One COS mapping table in the extended border node may have a standalone
wildcard “*” as one of the non-native CP names. Such a table is known as the
default COS mapping table
, and will be the table used by the extended border node
whenever no other table has a CP name that matches the non-native network.
COS name pairs
are the final part of configuring a COS mapping table. Here you
are prompted for one or more pairs of COS names. Each COS name pair consists
of a native COS name followed by the corresponding COS name used in the
non-native network.
The extended border node uses this table to translate from native to non-native
networks and vise versa. If you need to map multiple native COS names into a
common non-native COS name you should configure one COS name pair for each
possible mapping. Similarly you may need to map multiple non-native COS names
into a common native COS name, and that too can be accomplished by configuring
a COS name pair for each possible mapping. If there are multiple possible
mappings in a table the extended border node will use the first exact mapping
found.
Each COS mapping table may have one COS name pair where the non-native COS
name is a wildcard “*” . This is the
default COS mapping
entry for that table, and it
is used to translate all unrecognized non-native COS names into a single native
APPN
Chapter 1. APPN 35