1.  INTRODUCTION

   1.01   This Practice is an introductory document for DMS-100 Fam-
          ily  system  maintenance  personnel.   It provides general
   information about the the maintenance system  and  describes  the
   fundamentals  of  Maintenance  and  Administration Position (MAP)
   usage.  The MAP components, its interface with  the  DMS  system,
   and its operation is described in 297-1001-110.


   PURPOSE

   1.02   This Practice describes:

   o   the  maintenance  system structure and terminology as it per-
       tains to the DMS-100 Family.

   o   descriptions of MAP displays and their meanings

   o   use of the MAP in regard to

       Ä   entering commands
       Ä   system responses to commands


   APPLICATION

   1.03   The information in this document applies to  offices  that
          have Batch Change Supplement (BCS19) release software.  It
   also applies to offices that have a software release greater than
   BCS19, unless it is re-issued.

   1.04   Software applicable to a specific DMS-100 Family office is
          identified by a BCS release number and by Northern Telecom
   (NT)  Product  Engineering Codes (PEC).   The significance of the
   BCS number and the PEC  is  described  in  297-1001-450  (section
   450/32) and in the Office Feature Record D-190.

   1.05   A  display  of  the  BCS number and PEC for the NT feature
          packages available in a specific office can be obtained by
   entering the command string:

           DSU;INFORM LIST;LEAVE

   at a Maintenance and Administration Position (MAP).   (NTP)  edi-
   tions   with   respect  to  a  given  BCS  release  is  given  in
   297-1001-001.


   REVISION HISTORY

   1.06   For this release (02.03) the NODISP option  of  the  MAPCI
          command has been added.

                                                              Page 6

                                               PRACTICE 297-1001-520
                                                      RELEASE: 02.03

   REFERENCES

   1.07   References  listed  as  prerequisites are essential for an
          understanding of this Practice.  Those listed  as  inform-
   ative  contain  detailed  information concerning other items men-
   tioned in this Practice, but are not essential.   References  are
   inserted at the appropriate places in the text.

   Note:    The documents listed may exist in more than one version.
   See 297-1001-001 to determine the release  code  of  the  version
   compatible with a specific release of software.


   Prerequisite References

   DOCUMENT
   NUMBER        TITLE

   297-1001-100  System Description
   297-1001-106  Maintenance System DMS
   297-1001-110  Maintenance and Administration Position (MAP)
   297-1001-513  Input/Output Devices MMI Description


   Informative References

   DOCUMENT
   NUMBER        TITLE

   297-1001-001  Master Index of Practices
   297-1001-120  Equipment Identification
   297-1001-129  Input/Output System Reference Manual
   297-1001-814  Operational Measurements Reference Manual
   297-1001-453  Network Management System Reference Manual
   297-1001-471  Service Analysis Reference Manual
   297-1001-500  Switch  Maintenance  Performance Oriented Practices
                 (POP)
   297-1001-511  Central Control MMI Description
   297-1001-512  Central Message Controller MMI Description
   297-1001-513  Input/Output Devices MMI Description
   297-1001-514  Network Maintenance and MMI Description for Network
                 Modules
   297-1001-515  Peripheral Modules MMI Description
   297-1001-516  Trunk Maintenance Reference Manual
   297-1001-517  External Alarms - MMI Description
   297-1001-519  Call Processing Display System (CPSYS)  MMI  Refer-
                 ence Manual
   297-1001-528  Common  Channel Signaling System Maintenance Refer-
                 ence Manual
   297-2101-516  Lines Maintenance Reference Manual
   297-1001-112  Modular Documentation System



                                                              Page 7

                                               PRACTICE 297-1001-520
                                                      RELEASE: 02.03

   COMMAND FORMAT CONVENTIONS

   1.08   In this Practice, a uniform system of notation is used  to
          illustrate  system  commands and responses.   It shows the
   order in which command elements appear, the punctuation, and  the
   options.    Where the conventions are not used, an explanation is
   given in the text.

   CAPITAL letters or     show constants, commands, or keywords that
   special characters     the system  accepts when entered  as writ-
                          ten.

   lowercase letters      show  a  user-  or  system-supplied  para-
                          meter. Definitions are given for each par-
                          ameter.

   Brackets [ ] or Ú  ¿   enclose  optional  parameters. A  vertical
                   ³  ³   list enclosed  in brackets  means that one
                   À  Ù   or more of the parameters may be selected.

   Underlined parameter   is a default. If no choice is entered, the
                          system acts as though the underlined para-
                          meter had been entered.

   Underscore connecting  means the words  are to be treated  as one
   words                  item, for example, pm_type or #_one_two.

   ooo                    indicates repeated steps or items.

   In addition, the following conventions are used.

   n (lowercase n)        is a number from 0 to 9.

   a (lowercase a)        is a letter from A to Z.

   h (lowercase h)        is a hexadecimal integer from 0 to F.








                                                              Page 8

                                               PRACTICE 297-1001-520
                                                      RELEASE: 02.03