! TEST_POS.TXT  Version 1.0     16/07/96
! V1.0  16/07/96  Initial version.  Nick Roots

              AXE Test Position Files


                     Introduction

The AXE Test Position files have been released to aid
testing of AXE customer services.  An AXE Test Position is
initiated to provide a metallic link to the customers line
to utilise specific tests, eg check for service dial tone.

The files listed below have been provided to enable the user
to automatically initiate Test Position data when connecting
to an AXE Exchange.  There is also an option to manually
initiate the data via Function Key 4 after connection to an
AXE Exchange.


                     Description

In the CLS LAN environment the operator is asked (when
running Ozterm for the first time) if they wish to setup
the AXE Test Position data.  This question is only asked
once.  If they choose "No", no data is setup.  If they
choose "Yes" they are then asked to supply a Test Position
telephone number.  This is the phone service that the Exchange
will call when a test is requested which requires a "metallic"
connection.  This data is saved in the NOC.DAT file and stored
in the users working directory, and the PC's LAN directory if
running Ozterm on a CLS LAN.

The operator is then asked if they want the Test Position
data automatically initiated every time they connect to
an AXE Exchange.  If they answer "No" the Test Position
data is NOT initiated on connection to the Exchange.
Function Key 4 is loaded with a script file to manually
initiate the data if required.  If they answer "Yes" the
Test Position data is initiated every time they connect to an
AXE Exchange.  This data is saved to the NOC.USR file and
stored in the user's home directories.

The disconnection script files will check to see if a Test
Position has been initiated in the Exchange.  If there
has, the data is automatically ended, regardless of
whether the data was automatically initiated or manually
initiated via Function Key 4.

If you want to change your existing data, you can run
the script file NOC_WRT.CMD which is in the OZTERM\CMDS
directory.  This file will work for both CLS and non-CLS
environments.


                     Ozterm Files

In the Ozterm Program Directory:

GET_NOC.BAT   DOS Batch file used to retrieve the NOC.DAT
              and NOC.USR files in the CLS environment.
WRT_NOC.BAT   DOS Batch file used to write the NOC.DAT and
              NOC.USR files in the CLS environment.


In the User's Ozterm Working Directory:

NOC.DAT       Stores the Test Position phone number.
NOC.USR       Stores the users preference for automatic
              initiation.
TESTPOS.CHK   Temporary file for storing the currently
              initiated Test Position data.


In the CLS User's Ozterm Configuration Directory:

NOC.FLG       Records whether the user has been asked about
              Test Position data.
NOC.USR       Stores the users preference for automatic
              initiation. This file is copied to the current
              Working directory for CLS users.


In the Ozterm Command File Directory:

NOC_CHK.CMD   Script file used to check for NOC.FLG and
              retrieve the NOC.DAT and NOC.USR files if
              operating in a CLS environment.
NOC_WRT.CMD   Script file used to create the NOC.DAT and
              NOC.USR files in both non-CLS and CLS
              environments.
TPOSCON.CMD   Script file run from Function Key 4 for
              manual Test Position initiation.
TPOSCON.INC   Script file run from CONNECT.CMD for
              automatic Test Position initiation.
TPOSDISC.CMD  Script file run from DISCONNT.CMD for
              automatic Test Position removal.
