       TRANSMISSION TESTING OF ALL BT DEVICES ON A ROUTE.

! TMRTTRAN.TXT Version 1.4      21/11/97
! V 1.0 21/07/94 Ralph Smith    Initial version
! V 1.1 02/11/94 Charlie Danger Updated references
! V 1.2 06/12/94 Ralph Smith    Updated notes on /66 usage.
!                               Script file version 2.9 modifications noted.
!                               Previous versions note added.
!                               Setup TMRT note added.
! V1.3 03/04/95  Charles Danger Added notes under "TESTING A FEW DEVICES ONLY"
!                               Previous versions notes added.
! V1.4 21/11/97  Nick Roots     TCARS.TXT changed TO TCARS.LST and moved
!                               ROUTE.GIV and TCARS.LST to OZTERM\LOCAL

  Created by: Ralph Smith, Richmond EMG,  ph  03 820 1099, fax 03 866 6633
              21 July 94.

  Updated by: Charles Danger, OSS-CW (Perth) Ph. 09 491 5841, Fax 09 481 2274
              03 Apr 95.

            ͻ
               TMRTTRAN.CMD requires OZTERM 6.1Q or later.   
            ͼ
   ͻ
     IMPORTANT: Do NOT use this file in /66 sites until the APT is at   
     level 6B or higher with patch TR3841293M4599 loaded in block BT6.  
     Usage at a level below 6B can lead to the following occurring.     
     The TMRT leaves some (100/600) devices in TEST state requiring the 
     use of TEST SYSTEM by NASS to release them. This was a problem in  
     /36 last year, but was fixed. A SYSTEM EVENT (SE10872) has been    
     raised and the /66 patch has been released, but it is not loaded   
     at all sites as of 05/12/94.                                       
   ͼ

The OZTERM 6.1Q TMRTTRAN.CMD script file was created because of inadequacies
in the AXE TMRT and to provide enhancements. It provides superior logging of
the results for each BT device on an outgoing route. It also logs faulty
devices in a separate file for easy identification.


INSTALLATION
------------
   ͻ
     IMPORTANT: This PMB release version 2.9 of TMRTTRAN.CMD is not     
     compatible with previous releases of TMRTTRAN.CMD.  The directory  
     structure has been changed as has the layout of the TCARS.LST      
     file. Earlier versions of TCARS.LST can be utilized by moving the  
     TCARS phone number to column 30 for the area code and column 33    
     for the local number. Characters starting at column 44 are not     
     utilized by the script file and can contain any local information  
     deemed desirable.                                                  
   ͼ

There are 4 files associated with this procedure :
        TMRTTRAN.CMD    the OZTERM script file for TMRT control
        TMRTTRAN.TXT    (this file)
        TCARS.LST       Sample ASCII text file containing TCARS numbers
        ROUTE.GIV       Sample file for nodes with multiple GIV routes with
                        the same LRDC but different TCARS for each route.

The latter three files should be found under subdirectory \OZTERM\TEXT, while
TMRTTRAN.CMD is located under subdirectory \OZTERM\CMDS\PMB.

TCARS.LST should be edited to include TCARS numbers for sites in the
control area.

ROUTE.GIV should be edited to include TCARS numbers for sites with multiple
GIV routes to the same LRDC with different TCARS numbers.  It can be deleted
at sites without multiple GIV routes.

Note: Please ensure that the SAME COLUMN POSITIONS and format are used in the
      TCARS.LST and ROUTES.GIV files. Any information starting at column 44
      is not used by the script file and is inserted on a local needs basis.

FILE NAMING
-----------
Files created by the command file are placed in a subdirectory based on
the name of the originating node (e.g. C:\PMB_RTNE\TRAK\ when calling from
TRAK).  The resultant files use the route name as the filename with various
extensions appended to it.

The naming format of the files is as follows.  I will use OSYRAN1 as the route
being tested from TRAK as an example.

        Device file     C:\PMB_RTNE\TRAK\OSYRAN1.DEV
        Retest file     C:\PMB_RTNE\TRAK\OSYRAN1.DO
        Result file     C:\PMB_RTNE\TRAK\OSYRAN1.DUN
        Faulty file     C:\PMB_RTNE\TRAK\OSYRAN1.FLT

The function of each of these files is explained in the next section.


TESTING A ROUTE
---------------
The user is requested to enter the name of the ROUTE to be tested and whether
to use the TCARS number listed for that route in the accompaning TCARS.LST file
or use a number that will be entered.

The operator may choose to use the number in the TCARS.LST file or enter a
number manually.  If the stored number is to be used, the complete route name
is searched for in the ROUTE.GIV file first, if the file exists.  If the route
name is found there, the TCARS number is extracted from that file.  If the
route name is not found in the ROUTE.GIV file (or the file does not exist),
the LRDC is extracted from the route name and the TCARS.LST file is searched
for the LRDC.  If the LRDC is not found with a TCARS number, manual input of
the TCARS number is requested.

Testing may be inhibited if required during any specified period (default from
08:30 to 10:30 - this period is used for planned TMRT transmission runs in
Melbourne South nodes).  The actual time testing is inhibited is three minutes
either side of the specified inhibit period.

The file also suspends testing from 23:50 to 00:10 as the TMRT block does not
allow testing with a single measuring program on more than one day.

The upper and lower transmission limits may also be edited (default settings
are : Lower Limit = -7dB, Upper Limit = -5dB).

A subdirectory, using the NODE name the PC is connected to, is created if not
already existing, and the file names set up ready for the TMRT run.

It then proceeds to log a  STRDP:R=xxxxxxx;  printout to a device file
(xxxxxxx.DEV), in the previously created subdirectory, to obtain the devices
on the route.  The state of each device is then checked with STDEP:DEV=BTx-xxxx;
If the device is blocked, it is noted as such in the result file.  If the
device is busy it is noted as such in the result file and also placed in the
retest file.  If the device is idle a TRAN type TMRT run is performed on the
device to the TCARS number selected.  The resultant printout is analysed and
if successful the device and its transmission levels are recorded in the result
file (xxxxxxx.DUN).

e.g.
    NATIONAL TRANSMISSION/TRAFFIC MEASURING PROGRAM RESULT

    MP     FCODE
    99

    DATE    TIME  TPL   DBS  DBN  R       RTD DEV
    941026  1057  0003       -9           NO

    MT    FT    SWM      BNB
    TRAN  NO             034821299

    CALLS  SUCC  CONG  BUSY  FAIL  FDEV  RM
    1      1     0     0     0     0     0

    INDIVIDUAL RESULT/TRANSMISSION

    DEV      DBLF  DBLB

    BT7-257  - 6   - 6
    END

If the call was unsuccessful or the device was not IDLE this is also recorded
in the result file.

If the printout is not satisfactory, due to the test failing because:
   * The device was seized and in use for the duration of the test period
   * The printout had no results (SE 09735 has been issued for this problem)
        * The TMRT failed ,
the device is recorded in the redo file xxxxxxx.DO and is retested when all of
the route's devices have had a call attempt.

If the printout includes a FAULT CODE, the device is recorded in the
xxxxxxx.FLT file as such.  FAULT CODE 9 can be caused by no polarity reversal
on answer, as well as the other causes listed in the printout description.
This fact is noted in the xxxxxxx.FLT file, after the device is recorded with
the fault code, every time that a FAULT CODE 9 is detected.

Devices that fall outside the transmission levels specified are recorded in the
faulty file xxxxxxx.FLT.  Devices that are not IDLE, BUSY or INCO are also
recorded in this faulty file.

When the device file has been processed, it is deleted and the retest file is
renamed to become the device file which is then processed. This continues until
all the non-blocked devices have been tested once each.


INCONCLUSIVE TESTS
------------------
Some printouts in /36 do not contain any meaningful results. ie. No Faultcode,
and no "CALLS  SUCC  CONG  BUSY  FAIL  FDEV  RM" section.

eg.

    WO      RCMXF1D4D---   930902   TW-2      TIME 930908 1130  PAGE    1
    NATIONAL TRANSMISSION/TRAFFIC MEASURING PROGRAM RESULT

    MP     FCODE
    99

    DATE    TIME  TPL   DBS  DBN  R       RTD DEV
    930908  1127  0003       -9           NO

    MT    FT    SWM      BNB
    TRAN  NO             5295299

    END

SE 09735 has been created for this problem in /36 and the fix should appear in
ISU 335T479.  The release date for this is not known to me.  I do not know if
this problem occurrs in /66.

The device is placed in the redo file and tested again later.  "HAD AN
INCONCLUSIVE TEST (REFER TO SE9735)" is also written into the result file.


TESTING A FEW DEVICES ONLY
--------------------------
If it is desired to only test some of the devices on a route, (e.g. after fixing
some faults) a STDEP:DEV=BTx-first dev&&-last dev; command can be logged to the
device file and the script file run using the existing device file.  Select
option "Use existing device file" from the menu (!! Note: This option is NOT
used to re-do the devices in the STRDP print generated by selecting the option
"Log route devices and start TMRT transmission run").

MAKE SURE THAT THE REDO FILE FOR THAT ROUTE, IF THERE IS ONE, IS DELETED FIRST.


INTERRUPTED TESTING
-------------------
If a test has to be interrupted for any reason, pressing the ESC key one or
more times will interrupt OZTERM transmitting the script file.  If it is then
desirable to recommence testing from the last device tested the following must
be performed :
       * Inspect the result file and note the last device tested.
       * Edit the device file and delete all BTx- lines from the start of the file
    down to and including the the line containing the last device tested.
The script file can then be restarted using the existing device file.

NOTE: The retest file, if there is one, becomes the device file when all devices
in the device file have been tested.


MISCELLANEOUS NOTES
-------------------
 * For guidance in setting up TCARS or a TMRT refer to TP 01401(N)
   "TMRT Calibration and Network Application".

                    ***************************************

RECENT CHANGES TO THE TRANSMIT FILE
-----------------------------------

VERSION 3.3
* Renmaed TCARS.TXT to TCARS.LST and moved ROUTE.GIV and TCARS.LST to new
  OZTERM\LOCAL directory

VERSION 3.2
* Restored handling of device file as per notes above.
  (i.e. removed last modification)

VERSION 3.1
* Correction - condition check for empty list was in wrong position in code.
* Set Levels option accepts any key other than 'R' and 'Q' as Yes.
* Device heading in redo file was not written if "Use existing device file"
  option was selected.
* Re-arranged file handling to preserve initial device file

VERSION 3.0
* Correction - first BT in list was missed in TMRT run.

VERSION 2.9
* Modified length of TCARS number from 12 digits to 10 digits.

VERSION 2.8
* Various updates including Destination Path for the output/input files to
  ensure compatibility for Periodic Maintenance Binder.
* Combination of editable fields into one window for ease of user input.

VERSION 2.70
* Extended the number of digits able to be entered manually from 7 to 10.
* Further implementation of LOCAL.DAT root drive and directory.
* Fixed screen problems encountered when the LRDC is not in the TCARS.TXT file.
* Caters for multiple routes to different GIV stages using the same LRDC but
  different TCARS numbers.

VERSION 2.60
* Using the existing log file procedure simplified.
* The device file is erased when the run is completed.
* Problems with the redo file caused by increasing the device string size fixed.
* Inconclusive test result file string modified.

VERSION 2.51
* Device string size increased to allow testing of BTARK3 devices at MacKay OMG
* TRT directory set using LOCAL.DAT root drive and directory.

VERSION 2.50
* FAULT CODE 6 devices are retested later.

VERSION 2.4
* Multiple call attempts are logged in the fault file.
* Special comments for FAULT CODE 9 results added.

VERSION 2.3
* Handling of FAULT CODES was improved.

VERSION 2.1 AND 2.2
* Faulty devices are now placed in a separate fault file.
* Tests that do not produce a result, for whatever reason, are now redone,
  rather than placed in the faultfile.
* Setting of transmission limits was added.
* Suspension of testing during MELBOURNE SOUTH scheduled run period as an
  option was added.
* Creation of separate subdirectory for each originating node was added.
* Issues EXACP to determine originating nodes area code. Previous versions
  only catered for 03 nodes, DROX and CRHC.
* Increased information displayed on screen during testing.
* Identification of ORIGINATING node was added to the result and fault files.
* Change back to the original directory at the end of the run was added.
