chg-map

4.100 chg-map

Use this command to add or modify an entry in the Mated Application Part (MAP) table. A MAP table entry consists of a mate PC/SSN, its attributes, and an Alternate Routing Indicator Mate MRN Set and MRN point code.

Note:

A mate point code defines an adjacent signaling point, which is considered the mated signal transfer point (STP) to the system. See the Notes section for additional information on multiplicity modes.

Note:

The GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI) feature must be enabled before an Alternate RI Mate for a MAP Set can be provisioned.

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.

Note:

The mrnset and mrnpc parameters indicate whether an Alternate RI Mate search is performed in the MRN table if all of the point code/subsystem number combinations provisioned in a given MAP Set are unavailable or congested.

pc (mandatory)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

pca

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

pc/pca/pci/pcn/pcn24 /pcn16 (mandatory): Primary remote point code.

pci (mandatory)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pcn (mandatory)

ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn24 (mandatory)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

pcn16 (mandatory)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000---127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000---31

ssn (mandatory)

Subsystem number.

Range:: 2 - 255

eswt (optional)

Entity set weight. The weight assigned to each PC/SSN in a weighted entity set.

Note:

This parameter cannot be specified when adding PC/SSNs to a weighted entity set or when modifying RC or weight values for an individual PC/SSN.

Range:: 1 - 99, none
none —Changes a weighted entity set to a non-weighted entity set.

force (optional)

This parameter must be specified to modify the rc parameter and the srm, mrc, or wt parameter in the same command.

Modification of the srm, mrc, or wt parameter depends on the parameter's current multiplicity state, which depends on the RC value. Changing the rc parameter value can change the multiplicity state, which can cause the srm, mrc, or wt parameter value to become invalid.

Range:: yes

grp (optional)

The concerned point code broadcast list (CSPC) group name. The CSPC is a group of point codes that should be notified of the subsystem status. A different CSPC group can be assigned to each mated PC/SSN. For ANSI, the EAGLE broadcasts SSP or SSA to the mate subsystem only if the mate’s point code is provisioned as part of the CSPC group to receive an SSP or SSA.

Range:: ayyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters; none —Disassociates a concerned point code broadcast list group from the given mate application
Default:: Current value.

grpwt (optional)

Group weight. The weight assigned to each PC/SSN in a weighted RC group.

Note:

This parameter cannot be specified when adding PC/SSNs to a weighted entity set or when modifying RC or weight values for an individual PC/SSN.

Range:: 1 - 99

mapset (optional)

MAP set ID.

Range:

1 - 36000, dflt

dflt —Default MAP set

Default:

dflt -if the Flexible GTT Load Sharing feature is not enabled

No change to current value—if the Flexible GTT Load Sharing feature is enabled

materc (optional)

Mate relative cost. The RC assigned to the mate PC/SSN that is being added to the entity set. The system determines the multiplicity mode based on the RC values (rc and materc parameters) of the subsystem.

Range:: 0 - 99
Default:: Current value.

mpc (optional)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

mpca

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001–005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006–255.

The point code 000-000-000 is not a valid point code.

Default:

000

mpc/mpca/mpci/mpcn/mpcn24/mpcn16 (optional): Mate remote point code.

mpci (optional)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

Default:: 000

mpcn (optional)

ITU national point code in the format of a 5-digit ITU number (nnnnn). The prefix subfield indicates a spare point code (prefix-nnnnn).

Range:

s-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

Default:

00000

mpcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

msa—000–255

ssa—000–255

sp—000–255

Default:: 000

mpcn16 (optional)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000---127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000---31
Default:: 000

mrc (optional)

Message routing under congestion. This parameter specifies whether Class 0 messages to the specified PC/SSN are routed to the next preferred mode/subsystem when that PC/SSN is congested.

Range:

yes
no

Default:

No change to the current value

mrnpc (optional)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:: mrnpca
Default:: 000

mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24/mrnpcn16 (optional): Alternate RI Mate point code.

mrnpci (optional)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Default:: 0-000-0

mrnpcn (optional)

Default:: 00000

mrnpcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Default:: 000

mrnpcn16 (optional)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000--127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un--000--127; sna--000--15; mna--000--31

Default:: 000

mrnset (optional)

Alternate RI Mate MRN Set ID. The MRN Set where the Alternate RI Mate search is performed.

Range:: 1 - 3000, dflt
dflt —default MRN Set

Note:
If the mrnpc parameter is specified, and the mrnset parameter is not specified, then the value for the mrnset parameter is automatically set to dflt.
Default:: No change to the current value

mssn (optional)

Mated subsystem number. The SSN that acts as a backup if the SSN fails.

Range:: 2 - 255
Default:: Current value.

mwt (optional)

Mate point code weight. The weight assigned to the PC/SSN that is being added to a weighted entity set.

Range:: 1 - 99

rc (optional)

Relative cost. The RC assigned to a specified PC/SSN. The EAGLE determines the multiplicity mode based on the relative costs (the rc and materc parameters) of the subsystem.

Range:: 0 - 99
Default:: Current value.

srm (optional)

Subsystem routing messages. This parameter specifies whether subsystem routing messages (SBR, SNR) are transmitted between the mated applications.

This value can be provisioned in any of the multiplicity modes, but its value only affects traffic if the multiplicity mode is DOM or COM. See the Notes section for more information on multiplicity modes.

Range:

yes
no

Default:

Current value.

sso (optional)

Subsystem status option. This parameter specifies whether the PC/SSN initiates a subsystem test when a RESUME is received for the PC.

Range:

on: prohibited
off: allowed

Default:

Primary—no change

Mate, if entered— off

thr (optional)

Threshold. The in-service threshold assigned to each PC/SSN in a weighted entity set or RC group.

This parameter cannot be specified when adding PC/SSNs to a weighted entity set or RC group or when modifying RC or weight values for an individual PC/SSN.

If this parameter is not specified, a value of 1% is assigned to each weighted PC/SSN.

Range:: 1 - 100

wt (optional)

Weight. The new weight assigned to the primary PC/SSN.

Range:: 1 - 99

Example

This example enters 1 into the MAP table and adds it to the same group as 1. Because 1 already exists in the MAP table, the rc parameter is not used.

chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40

This example enters 1 into the MAP table, and adds it to the same group as 1. Because 1 has a lower relative cost than 1, it is placed into the group in relative cost order.

chg-map:pc=1-1-0:ssn=10:mpc=1-1-2:mssn=10:materc=30

This example changes the relative cost for the specified PC/SSN pair:

chg-map:pc=1-1-0:ssn=10:rc=20

This example changes the concerned PC broadcast list group name for the specified PC/SSN pair:

chg-map:pc=1-1-0:ssn=10:grp=abc

This example changes the ITU-I spare point code entry s-1-12-2 and adds the spare mate point code entry s-2-23-3 in the map table:

chg-map:pci=s-1-12-2:ssn=10:rc=10:mpci=s-2-23-3:mssn=20:materc=10

This example turns ON the SSO option for PC 1-1-0 and SSN 10.

chg-map:pc=1-1-0:ssn=10:sso=on

This example turns OFF the SSO option for PC 1-1-0 and SSN 10.

chg-map:pc=1-1-0:ssn=10:sso=off

This example does not change the current value of the SSO option for the primary or the mate.

chg-map:pc=1-1-0:ssn=10:rc=10

This example turns ON the SSO option for primary and mate.

chg-map:pc=1-1-0:ssn=10:mpc=3-3-3:mssn=2:sso=on

This example turns OFF the sso option for primary and mate.

chg-map:pc=1-1-0:ssn=10:mpc=4-4-4:mssn=2:sso=off

This example does not change the current value for the SSO option for the primary. The SSO option is turned OFF for the mate, because the mate is specified but the sso parameter is not specified (the default is OFF for the mate when the mate is specified).

chg-map:pc=1-1-0:ssn=10:mpc=5-5-5:mssn=2

This example changes the ITU-I spare s-1-12-2 entry and adds the spare mate point code s-2-23-3 entry in the map table.

chg-map:pci=s-1-12-2:ssn=10:rc=10:mpci=s-2-23-3:mssn=20:materc=10

This example adds a new PC/SSN 1 in the existing MAP set 362.

chg-map:pc=1-1-1:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362

This example adds a new PC/SSN 1-1-3/15 to the same load-sharing group in the default MAP set to which 1-1-1/15 belongs.

chg-map:pc=1-1-1:ssn=15:mpc=1-1-3:mssn=15:materc=40:mapset=dflt

This example changes the RC of 1-1-1/10 in existing MAP set 362 to 20.

chg-map:pc=1-1-1:ssn=10:rc=20:mapset=362

This example changes a non-weighted shared or non-weighted combined entity set to a weighted shared or weighted combined entity set.

chg-map:pc=1-1-1:ssn=10:eswt=30

This example changes a non-weighted shared or non-weighted combined entity set to a weighted shared or weighted combined entity set. The example also sets a threshold value and changes the weights of all of the PC/SSNs in the entity set.

chg-map:pc=1-1-1:ssn=10:eswt=30:thr=50

This example changes a weighted shared or weighted combined entity set to a non-weighted shared or non-weighted combined entity set.

chg-map:pc=1-1-1:ssn=10:eswt=none

This example assigns a weight value to each PC/SSN in an RC group within a weighted entity set.

chg-map:pc=1-1-1:ssn=10:grpwt=20

This example assigns a threshold value to each PC/SSN in an RC group within a weighted entity set.

chg-map:pc=1-1-1:ssn=10:thr=70

This example assigns weight and threshold values to each PC/SSN in an RC group within a weighted entity set.

chg-map:pc=1-1-1:ssn=10:grpwt=20:thr=70

This example changes the weight of an existing PC/SSN in a weighted entity set.

chg-map:pc=1-1-1:ssn=10:wt=20

This example changes the weight of PC/SSN 1 and adds PC/SSN 1-2-1/10 to an existing weighted entity set.

chg-map:pc=1-1-1:ssn=10:wt=50:mpc=1-2-1:mssn=10:materc=20:mwt=30

This example adds PC/SSN 1-3-2/10 to an existing non-weighted entity set.

chg-map:pc=1-1-1:ssn=10:mpc=1-3-2:mssn=10:materc=20:mwt=10

This example changes the RC value and turns on MRC of an existing PC/SSN in a weighted entity set.

chg-map:pc=1-1-1:ssn=10:rc=30:mrc=yes:force=yes

This example changes the RC value and turns on SRM of an existing PC/SSN in a weighted entity set.

chg-map:pc=1-1-1:ssn=10:rc=30:srm=yes:force=yes

This example changes the RC value and the weight of an existing PC/SSN in a weighted entity set.

chg-map:pc=1-1-1:ssn=10:rc=30:wt=20:force=yes

This example changes the Alternate RI Mate (MRNSET and MRNPC) in an existing MAP set.

chg-map:mapset=362:pc=1-1-1:ssn=10:mrnset=1:mrnpc=1-1-2

Example for 16 bit PC:

chg-map:pcn16=1-1-1:ssn=10:rc=20:wt=30:mpcn16=1-2-3:mssn=10:materc=20:mwt=20:thr=40

Dependencies

At least one optional parameter must be specified.

The specified remote PC must exist in the MAP table.

The Spare Point Code Support feature must be enabled before an ITU-I or ITU-N spare point code can be specified.

The specified SSN must exist for the specified remote PC.

If a subsystem is configured for a subsystem number (SSN) value in the SS-APPL table, then the specified MAP table entry for that subsystem must be a valid point code type for that subsystem. The following point code types are not valid for the indicated subsystems:

For the INP subsystem, the True Point code cannot be an ITU-I point code.
For the AIQ, ATINPQ, VFLEX, and EIR subsystems, the True Point code cannot be an ITU-N24 point code.

The mate PC/SSN cannot be the same as the primary PC/SSN.

If the PC value is an ITU type (pci/pcn/pcn24/pcn16), the srm=yes parameter cannot be specified.

The apca and pcn24/pcn16 parameters cannot be specified for the same MAP set. The pci and pcn parameters cannot be specified for the same MAP set if the MAP set contains a true point code.

The ANSI/ITU SCCP Conversion feature must be enabled before the network type of the CPC broadcast group can be different from the network type of the point code.

The mated PC/SSN must not already exist in the MAP table.

The DPCs of the primary subsystem and the mate subsystem must be full PCs.

The Route table must be accessible.

The format of the pcn or mpcn parameter must match the format assigned with the npcfmti parameter of the chg-stpopts command.

If the mpc parameter is specified, the mssn and materc parameters must be specified.

A maximum of 128 mated applications is allowed per MAP set.

The sso parameter cannot be specified with a PC that is the system true PC.

A true PC can have only one mate.

A true PC cannot be routed to itself.

The RPC3 table must be accessible.

The Site Identification table must be accessible.

If the mssn or materc parameter is specified, the mpc parameter must be specified.

The PC must already exist in the CPC group.

The specified CSPC broadcast list group name must already exist.

If the mpc parameter is specified, then the mssn parameter must be specified.

The number of MPC Subsystem entries must not exceed the table capacity.

A maximum of 1024 unique remote point codes are allowed.

If a remote MPC is specified, then the remote MPC must exist in the Routing table.

If the Flexible GTT Load Sharing feature is not enabled, then the mapset parameter must not be specified. If the Flexible GTT Load Sharing feature is enabled, then the mapset parameter must be specified.

The specified MAP set must exist in the database.

The specified PC/SSN/MAP set must already be provisioned in the MAP table.

The EAGLE true PC can be provisioned only in the default MAP set.

The MAP table must be accessible.

The Weighted GTT Loadsharing feature must be turned on before the wt, mwt, eswt, grpwt, or thr parameters can be specified.

If the eswt, grpwt, or thr parameter is specified, the mpc parameter cannot be specified.

If the eswt, grpwt, and thr parameters are specified, the rc, wt, mrc, srm, sso, and grp parameters cannot be specified.

The eswt and grpwt parameters cannot be specified together in the command.

If the eswt=none parameter is specified, the thr parameter cannot be specified.

If the mwt parameter is specified, the mpc parameter must be specified.

The mpc parameter value must be a full point code.

If the mpc parameter is specified for a weighted entity set, the mwt parameter must be specified.

If the mpc parameter is specified for a non-weighted entity set, the mwt parameter cannot be specified.

The eswt=none parameter cannot be specified for a non-weighted entity set.

The grpwt and thr parameters cannot be specified for a non-weighted entity set.

If the chg-sid:pctype=ansi command is entered, a value of ni=000 cannot be specified.

If the chg-sid:pctype=ansi command is entered, and a value of ni=001 – 005 is specified, a value of nc=000 cannot be specified.

The mate point code in the command cannot exceed the maximum number of entries in the MAP table.

The MAP table contains the maximum number of possible entries for the specified True Point Code. Maximum entries for the ANSI, ITU-I, and ITU-N point codes are:

ANSI—2 (ANS41 AIQ and LNP), 4 (ANSI41 AIQ, ATINPQ, INP, and V-FLEX)
ITU-I—4 (ANSI41 AIQ, ATINPQ, EIR, and V-FLEX)
ITU-N—5 (ANSI41 AIQ, ATINPQ, EIR, INP, and V-FLEX)

Note:

LNP is mutually exclusive with ATINPQ and V-FLEX, unless the Dual ExAP Config feature is enabled.

The true point code in the entity set must be the primary PC/SSN for that entity set. The rc parameter value for the specified point code cannot be changed, and a new point code cannot be added that causes the true point code to no longer be the primary PC/SSN.

If the pc parameter value is a true point code, the subsystem must have a lower RC than all other mated subsystems in the RC group.

If the mpc parameter value is a true point code, the subsystem must have a lower RC than all other mated subsystems in the RC group.

The eswt, grpwt, and thr parameters cannot be specified for solitary or dominant entity sets.

The AINPQ, EIR, INP, or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpcn parameter can be a true point code.

The force=yes parameter must be specified before the rc parameter can be specified in the same command with the srm, mrc, or wt parameter.

The force parameter can be used only to specify the rc parameter and the srm, mrc, or wt parameter in the same command.

If the pcn or mpcn parameter is specified, then the format of the parameter must match the format dictated by the chg-stpopts:npcfmti command.

The values specified for the pc and mpc parameters cannot be associated with proxy point codes.

The EIR or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpci parameter can be a true point code.

The LNP, V-Flex, EIR, or INP feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpca parameter can be a true point code.

The GTT LS ARI feature must be enabled before the mrnset and mrnpc parameters can be specified.

The value specified for the mrnpc parameter must be a full point code.

The value specified for the mrnset parameter must already exist in the MRN table.

The MRN table is corrupt or cannot be found.

The point codes and alternate RI Mate point codes must have compatible network types as shown:

ITUI, ITU-N, ITU-I spare, ITU-N-spare—ITUI, ITU-N, ITU-I spare, ITU-N-spare
ANSI—ANSI
ITUN-24—ITUN-24
ITUN-16---ITUN-16

The value specified for the mrnpc parameter must already exist in the specified MRN Set.

If the mrnset parameter is specified, then the mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24/mrnpcn16 parameter must be specified.

If the eswt, grpwt, or thr parameter is specified, then the mrnpc parameter cannot be specified.

The mrnset parameter cannot be specified if the MAP Set specified by the mapset parameter contains a True Point Code.

The chg-map command will reject provisioning of local subsystem for ITUN16 SID, so that ITUN16 MSUs will not be forwarded to Local Subsystems.

Notes

When the ANSI/ITU SCCP Conversion feature is enabled, the Concerned Point Code (CSPC) Group’s network type can be of a different network than the mated application’s network type. For example, the mated application’s network type could be ANSI and the CSPC Group could be ITU or mixed with ANSI, ITU, and ITUN concerned point codes.

Multiplicity Modes

For the -map commands, an entity set consists of a group of PC/SSNs that are used for traffic distribution, and an RC group consists of PC/SSNs within an entity set that have the same RC. In loadsharing mode, an entity set contains 1 RC group. In combined loadsharing/dominant mode, an entity set can contain multiple loadsharing groups.

Note:

For dominant and combined loadsharing/dominant modes, the PC/SSN in the MAP table where traffic distribution initializes is determined by the result of GTT translation and is referred to as the preferred PC/SSN. The preferred PC/SSN may not be the lowest cost entry.

The EAGLE supports the following multiplicity modes for nodes/subsystems:

When a PC/SSN pair is not replicated, the pair is in solitary (SOL) mode. The subsystem acts as the only application, with no backup. If this subsystem fails, messages routed to it are discarded and SCCP management returns “Subsystem Unavailable” messages to the originator.
A group of replicated PC/SSN pairs are in dominant (DOM) mode if each PC/SSN pair in the group has a unique RC. The preferred PC/SSN acts as the primary subsystem while the higher cost systems act as backups.
A group of replicated PC/SSN pairs are in load sharing (SHR) mode if each PC/SSN pair in the group has the same RC. All messages are evenly distributed at the SCCP level to all nodes/subsystems in the group. If failure occurs, the non-affected subsystem assumes the load of its failed mate.
The combined load sharing/dominant (COM) mode supports a combination of load sharing and dominant mode. A group of PC/SSN pairs are in COM mode when at least two of the PC/SSN pairs have the same RC and another node subsystem in the group has a different RC.

The sso parameter changes the initialization of the subsystem status (“prohibited” or “allowed”) for PC/SSN MAP entries. The system previously marked the subsystem status “allowed” (OFF) for each PC/SSN entry. The sso option marks the subsystem status “prohibited” for each entry that has sso=on. This causes the EAGLE to generate an SST to the remote PC when an MTP-RESUME is received. Upon reception of an SSA, the subsystem status is marked “allowed”.

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).

When the Flexible GTT Load Sharing feature is turned on, MAP Load-Sharing Sets are supported. Each MAP set is identified by a new mapset parameter.

When the Weighted GTT Loadsharing feature is turned on, weighted entity sets and RC groups are supported, and threshold values can be assigned to each PC/SSN in a weighted entity set.

Output

chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362


    tekelecstp 11-03-22 12:29:22 EST  EAGLE 44.0.0
    chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362
    Command entered at terminal #4.
    CHG-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    CHG-MAP: MASP A – COMPLTD 
;

chg-map:pc=1-1-1:ssn=100:mrc=no:srm=no


    tekelecstp 11-03-22 12:29:22 EST  EAGLE 44.0.0
    chg-map:pc=1-1-1:ssn=100:mrc=no:srm=no
    Command entered at terminal #4.
    CHG-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
    CAUTION: THE VALUE OF SRM IS EFFECTIVE WHEN MULT IS COM OR DOM AND
    THE VALUE OF MRC IS EFFECTIVE WHEN MULT IS DOM.
    CHG-MAP: MASP A - COMPLTD 
;

Related Topics