This procedure is used to add a dominant mated application to the database.

The only parameters that can be specified with this procedure are the primary point code, primary subsystem number, mate point code, and mate subsystem number. The EAGLE relative cost parameters cannot be specified in this procedure. When the mated application is added to the database with this procedure, the relative cost value for the primary point code and subsystem is defaulted to 10. The relative cost value for the mate point code and subsystem is defaulted to 50. This creates a dominant mated application with only two entries.

This procedure uses the EAGLE commands rtrv-map, rtrv-ctrl-feat, rtrv-dstn, and chg-db. For more information on provisioning mated applications, refer to one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide.

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, or mapset, wt, mwt, thr, mrnset, or mrnpc parameters of the EAGLE’s ent-map command, the subsystem assigned to the mated application is the LNP, INP, V-Flex, ATINPQ, AIQ, or EIR subsystem, or you wish to create another type of MAP group or MAP set, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

Mated application groups in the EAGLE database can contain up to 32 entries, the primary point code, and up to 31 mate point codes. SEAS allows the user to configure only two entries for each MAP group. To add more entries to the MAP group, up to 30, after performing this procedure, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands. The rc and materc parameters must be specified with the EAGLE’s chg-map command. The maximum number of mated application entries that can be provisioned in the EAGLE is 1024, 2000, or 3000, depending on the quantity that is enabled.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE rtrv-map output, by default the mated application is assigned to the default MAP set. To assign a mated application to a MAP set other than the default MAP set, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

A proxy point code cannot be assigned to any point code that will be assigned to a mated application.

Sheet 2 of 2

This procedure is used to remove a mated application from the database. This procedure uses the EAGLE commands rtrv-feat, rtrv-ctrl-feat, rtrv-ss-appl, dlt-map, and chg-db. For more information on this procedure, see “Removing a Mated Application” in Database Administration - GTT User's Guide.

If you wish to use the pci, pcn, pcn24, all, mapset, or mrnset parameters of the EAGLE’s dlt-map command, perform the “Removing a Mated Application” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayed from the SEAS terminal. Performing this procedure removes only mated application entries in the default MAP set. To remove entries from a MAP set other than the default MAP set, perform the “Removing a Mated Application” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The output from the EAGLE command rtrv-ctrl-feat shows whether or not the Flexible GTT Load Sharing feature is enabled.

The EAGLE's point code and subsystem can be assigned to the mated application. If the mated application contains EAGLE's point code and the subsystem shown in Table 4-1, perform the “Removing a Mated Application” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

This procedure is used to change an existing mated application in the database. The only parameters that can be specified in this procedure are the primary point code, primary subsystem number, mate point code, and mate subsystem number. The EAGLE relative cost parameters cannot be specified in this procedure. When the mated application is added to the database with this procedure, the relative cost value for the primary point code and subsystem is defaulted to 10. The relative cost value for the mate point code and subsystem is defaulted to 50. This creates a dominant mated application with two entries.

If you wish to use the pci, pcn, pcn24, mpci, mpcn, mpcn24, srm, grp, mrc, rc, materc, sso, mapset, eswt, wt, mwt, grpwt, thr, mrnset, or mrnpc parameters of the EAGLE’s chg-map command, or if the subsystem assigned to the mated application is the LNP, EIR, V-Flex, ATINPQ, AIQ, or INP subsystem, perform any of the procedures from Database Administration - GTT User's Guide that are shown in Table 4-2 using the SEAS FLOW-THRU command with the EAGLE commands.

If you plan to change the existing MAP group to another type of MAP group, perform the Changing the Mated Application Type procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The mate point code cannot be changed to the EAGLE’s true point code.

This procedure uses the EAGLE commands chg-db and rtrv-dstn. For more information about changing a mated application, refer to the procedures from Database Administration - GTT User's Guide that are shown in Table 4-2on this procedure, see “Changing a Mated Application” in Database Administration - GTT User's Guide.

No new entries can be added to a mated application group with this procedure. Mated application groups in the EAGLE database can contain up to 32 eight entries, the primary point code, and up to 31 seven mate point codes. SEAS allows the user to configure only two entries for each MAP group. To add more entries to the MAP group, up to 30 six, perform one of the “Provisioning a Mated Application” procedures in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands. The rc and materc parameters must be specified with the EAGLE’s chg-map command. The maximum number of mated application entries that can be provisioned in the EAGLE is 1024, 2000, or 3000, depending on the quantity that is enabled.

If the Flexible GTT Load Sharing feature is enabled, only entries in the default MAP set are displayed from the SEAS terminal. Performing this procedure changes only mated application entries in the default MAP set. To change entries in a MAP set other than the default MAP set, perform any of the procedures from Database Administration - GTT User's Guide that are shown in Table 4-2 using the SEAS FLOW-THRU command with the EAGLE commands

The output from the EAGLE command rtrv-ctrl-feat shows whether or not the Flexible GTT Load Sharing feature is enabled.

A proxy point code cannot be assigned to any point code that will be assigned to a mated application.

This procedure is used to add a global title translation to the database. This procedure uses the EAGLE commands rtrv-ctrl-feat, rtrv-feat, chg-feat, rtrv-card, rtrv-tt, rtrv-gtt, rtrv-dstn, rtrv-gttsel, and chg-db. For more information on this procedure, see “Adding a Global Title Translation” in Database Administration - GTT User's Guide.

The following parameters of the EAGLE’s ent-gtt command are not supported by SEAS: typei, typeis, typen, typens, typen24, pci, pcn, pcn24, ttn, xlat, gtmodid , force, mrnset, mapset, loopset, or cggtmod.

SEAS does not support hexadecimal digits as the value of the global title address parameter. If you wish to use any of these parameters, or use hexadecimal digits as the value for the global title address parameter, perform the “Adding a Global Title Translation” procedure in Database Administration - GTT User's Guide using the SEASFLOW-THRU command with the EAGLE commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLErtrv-gtt output, and the routing indicator of the global title translation is G (the EAGLE value GT), by default, the global title translation is assigned to the default MRN set. To assign the global title translation to an MRN set other than the default MRN set, perform the “Adding a Global Title Translation” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLErtrv-gtt output, and the routing indicator of the global title translation is D (the EAGLE value SSN), by default, the global title translation is assigned to the default MAP set. To assign the global title translation to a MAP set other than the default MAP set, perform the “Adding a Global Title Translation” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The EAGLE XLAT parameter does not have a SEAS equivalent. When global title translations are configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, all mandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE parameters and values shown in Table 4-3.

The RC parameter of the SEAS ADD-GTT command is not supported by the EAGLE. While the RC parameter must be specified with the SEAS ADD-GTT command, the RC parameter is discarded when the SEASADD-GTT command is processed by the EAGLE.

A proxy point code cannot be assigned to any point code that will be assigned to a global title translation.

Sheet 2 of 6

Sheet 3 of 6

Sheet 4 of 6

Sheet 5 of 6

Sheet 6 of 6

This procedure is used to remove a global title translation from the database. This procedure uses the EAGLE commands rtrv-tt, rtrv-gtt, rtrv-feat, rtrv-gttset, rtrv-gta, rtrv-gttapath, and chg-db. For more information on this procedure, see “Removing a Global Title Translation” in Database Administration - GTT User's Guide.

If you wish to use the typei, typeis , typen, typens , typen24, or ttn parameter of the EAGLE’s dlt-gtt command, perform the “Removing a Global Title Translation” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

The DPC and SSN parameters of the SEAS DLT-GTT command are not supported by the EAGLE. While these parameters must be specified with the SEAS DLT-GTT command, these parameters are discarded when the SEAS DLT-GTT command is processed by the EAGLE.

Sheet 2 of 2

This procedure is used to change an existing global title translation in the database. This procedure uses the EAGLE commands rtrv-gtt, rtrv-mrn, rtrv-map, rtrv-tt, rtrv-dstn, rtrv-feat, rtrv-ctrl-feat, rtrv-gttsel, and chg-db. For more information on this procedure, see “Changing a Global Title Translation” in Database Administration - GTT User's Guide.

The following parameters of the EAGLE’s chg-gtt command are not supported by SEAS: typei, typeis, typen, typens, typen24, pci, pcn, pcn24, ttn, xlat, gtmodid, force, mrnset, mapset, split, loopset, or cggtmod. SEAS does not support hexadecimal digits as the value of the global title address parameter. If you wish to use any of these parameters or use hexadecimal digits as the value for the global title address parameter, perform the “Changing a Global Title Translation” procedure in Database Administration - GTT User's Guide using the SEAS FLOW-THRU command with the EAGLE commands.

If the Flexible GTT Load Sharing feature is enabled, shown by the MRNSET field in the EAGLE rtrv-gtt output, and the routing indicator of the global title translation is G (the EAGLE value GT), the global title translation can be changed in this procedure only if the global title translation is assigned to the default MRN set. All the attributes of the global title translation can be changed except for the following:

• The MRNSET value cannot be changed.
• The routing indicator value cannot be changed.
• If the point code is changed, the new point code must be assigned to the default MRN set.

If the Flexible GTT Load Sharing feature is enabled, shown by the MAPSET field in the EAGLE rtrv-gtt output, and the routing indicator of the global title translation is D (the EAGLE value SSN), the global title translation can be changed in this procedure only if the global title translation is assigned to the default MAP set. All the attributes of the global title translation can be changed except for the following:

• The MAPSET value cannot be changed.
• The routing indicator value cannot be changed.
• If the point code is changed, the new point code must be assigned to the default MAP set.

The EAGLE XLAT parameter does not have a SEAS equivalent. When global title translations are configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, all mandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE parameters and values shown in Table 4-4.

A proxy point code cannot be assigned to any point code that will be assigned to a global title translation.

The DPC, SSN and NRC parameters of the SEAS CHG-GTT command are not supported by the EAGLE. While these parameters must be specified with the SEAS CHG-GTT command, these parameters are discarded when the SEAS CHG-GTT command is processed by the EAGLE.

The range of global title addresses assigned to a global title translation can be extended or reduced to create a new range of global title addresses. The range can be extended so long as the new range of global title addresses does not overlap an existing range of global title addresses. The range can be reduced so long as the new end global title address parameter value is not smaller than the global title address parameter value.

For example, a global title translation contains this range of global title addresses: 9194600000 - 9194603000. The range of global title addresses can be extended to 9194604500 by specifying an end global title address value of 9194604500 parameter with the SEAS CHG-GTT command. However, if another range of global title addresses begins with the value 9194604000, the end global title address value of 9194604500 cannot be specified with the SEAS CHG-GTT command as the new range created with the end global title address value of 9194604500 would overlap the range of global title addresses beginning with the value 9194604000. In this situation, the maximum value for the end global title address value would be 9194603999.

Using the same example, the range of global title addresses can be reduced to 9194600000 - 9194601500 by specifying the end global title address value of 9194601500 with the SEAS CHG-GTT command. The new range must lie inside of the original range. You cannot create the range 9194595000 - 9194600000 by specifying the end global title address value of 9194595000 parameter with the SEAS CHG-GTT command.

Sheet 2 of 8

Sheet 3 of 8

Sheet 4 of 8

Sheet 5 of 8

Sheet 6 of 8

Sheet 7 of 8

Sheet 8 of 8