! SULTAN.TXT    Version 1.0     19/11/96

                 Description of 'SULTAN.CMD' - Version 2.4
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The SULTAN.CMD command file has been developed to allow the automatic checking
all data associated with the AXE SAI/MRT. It will produce up to three files
which have the following naming convention and uses :-

1.      lncd_month.txt  - this file list all sultan robots and their associated
                          data for a particular node and it's associated
                          LSS-A/D and RSS-D's. Any discrepenies in the data for
                          a particular robot will be indicated using a convention                          explained in the following section entited Explanation
                          of Exceptions. May be found in the "pmbdir\sultan"
                          directory, which is created by SULTAN.CMD
2.      res_month.txt   - this file concatinates all lncd_month.txt files into
                          one file so a quick scan can be done of all nodes
                          checked. Any subsequent runs are appended to this file.
                          This file may be found in the "pmbdir\sultan" directory
                          which is created by SULTAN.CMD
3.      lncd_month.err  - this file contains only those robots that have data
                          errors. These files are stored in the "discrep" sub
                          directory. These files can be found in the
                          "pmbdir\sultan\discrep" directory which is created by
                          SULTAN.CMD

One common situation is the appropriation for customers use, of sultan monitor
and revertive call lines. To enable monitor and revertive call lines that have
been reallocated to customers to be easily detected, a standard category has
been allocated to them. This category, while allowing the sultan machines to
function correctly, will be unacceptable for normal customers use. Changes to
the sultan line category will therefore be an indication the lines have been
reallocted.

Although it is possible to identify the sultan monitor line by command, the
same situation is not true for the revertive line. It is therefore necessary
to enter it in the exchange EXPOP data of main stream nodes using the
following format:-

  DEVICE POSITION
  EMG          EQ               POS
               SAI-26           REDK-418-2-G      <- SAI number with LRD & pos
                                REVERTIVE-3101045 <- revertive line number
                                MRT-3B            <- MRT number


In the case of /69 rurals the data is entered in the EXROP table using the
following format:-

  ROUTE DATA
  R        ROUTE PARAMETERS
  REVERT   SNB=642111
  END

The MRT number can be obtained from the local sultan support group.

Explanation of Exceptions
~~~~~~~~~~~~~~~~~~~~~~~~~
Following is a list of the possible causes for exeptions generated by the
SULTAN script file.

1.  An "?????" in the SAI column means that no SAI device is specified for the
    the EMG. Compare the EXAIP & EXAOP prints with the EXEGP print.

2.  No_SNB in the Mon SNB column indicates that a monitor number is not
    specified for the SAI. Check the EXSAP print.

3.  SNB_Err in the Mon SNB column indicates that the monitor number specified in
    the EXSAP print is an invalid number. This is most likely caused by a 10 digit'
    number being specified as either 7 or 9 digits.

4.  A Mon SNB number prefixed by a number of question marks indicates that the
    number is specifed without the area code in the EXSAP print in \66 sites.

5.  An NC in the Mon SCL column indicates that the monitor number is not
    connected.

6.  ?????? in the Mon SCL column indicate the monitor line category is
    incorrect. This is a good indication that the monitor line has been
    taken for a customers line.

    Mandatory Monitor line categories are:-
                                          TSU-1, LTE-2, BOC-1, TCL-12, SCH-1,
                                          CBA-5(/29 & /66), CBN-5(/36 & 69)

7.  No-TP in the IO column means the SNB number could not be matched with a BNB
    number in the EXTPP print.

8.  When scanning the IO column check that AT devs and not TW devs are
    specified in \66 - \29 sites.

9.  BNB_Err in the TP BNB column means the test position BNB is specified
    incorrectly. Most likely no area code specified in \29 - \66 sites.

10. No_BNB in the TP BNB column means that the SNB specified in the EXSAP print
    could not be matched with a BNB in the EXTPP print.

11. SNB_Err in the Rev SNB column indicates the revertive line number is not
    specified correctly. This may be due to it not being specified in the EXpOP /
    EXrOP data correctly.

12. ?????? in the Rev SCL column indicates the revertive line category is
    not specified correctly. This is most likely caused by the revertive line
    being given to a customer.
    Mandatory Revertive line categories are:-
                                           TSU-1, BIC-1, LTE-2, TCL-12, SCH-1,
                                           CBA-5(/29 & /66), CBN-5(/36 & 69)
    See SULTAN.TXT for explanation of errors.
