This ION has been written to assist with the introduction of TST onto your system. It only explains some details of the process and should be used in conjunction with the following manuals :-

HANDBOOK 1: MAINTAINING THE SYSTEM  
SAM REFERENCE MANUAL  

Total System Teleservice (TST) enables Fujitsu Services to diagnose and reply to system problems electronically. As a result this will reduce the time taken to resolve problems. Evidence may be submitted via File Transfer Facility (FTF). For sets of evidence that are greater than 100Kb in size, the File Transfer Facility should only be used across an ISDN or DSL link. 

Paper evidence can be specified within TST, however a paper Product Report Form must be supplied with any submitted paper evidence.      

The "Switch On" of TST can only be done after the application of the enabling repair XR/A/0010.2. You can request this repair via the normal SAM retrieval mechanism. 

Note - XR/A/0010 is pre-applied at OpenVME Version 5.  

The method for initialisation of TST can be found in OptICL for Trimetra as follows:

• For OVME up to versions 4 see section  F32 of System Management.
  
  
• For OVME version 5 and above see section 2.17.4 of OpenVME Handbook 1 : Maintaining the System

As part of this initialisation a new user (:TRANSMAN) is introduced. Filestore associated with :TRANSMAN is used to secure evidence prior to transmission to Fujitsu Services. It is strongly recommended that this filestore should not be in ICLMAINTCT.  

An EPR reference is the same format as that of a paper PRF ie mmmm/xnnn where:

• mmmm is your 3 or 4 character MDB prefix
• xnnn is the unique reference number.

Please see ION L26 (Resource Retrieval of Filestore Solutions), as TST uses the same FTF service. Note that if the service is already set up on your system you will still be required to have additional parameters included. i.e. :-

PROPOSE_RESUMPTION = Y
CHECKPOINT_INTERVAL = 48128

Once you have submitted the evidence to Fujitsu Services, the existing progress updates will continue.

The following points should also be noted :-

1. The transmission of evidence can result in all available FTCOPIERs being used. Hence, it is recommended that TST be run at quiet periods.
   
   
2. SAM TAILORING - After enabling TST, clients should login to SAM and, in turn, select the following options from the menus presented-
   
   
   • SAM Management
   • Teleservice Log facilities
   • Set the Teleservice Log details
   
   
   The field marked "Progress MSR to Completion following a final reply?" should be changed from "Y" to "N". This will enable an EPR to be re-opened should this be necessary. Clients using SERVMAN, however, should not make this change, but should, instead, tailor SERVMAN to trap the "FINAL REPLY". See also ION P47 on submitting further evidence.
   
   
3. The EPR/MSR Fingerprint is transmitted to Fujitsu Services by the normal SAM ADI link.
   
   
4. There are some changes to the procedure for handling Auto MSRs. The evidence should be submitted with the Support Request using the TST facilities ( Progress MSR Option 12 ). This will normally be via FTF where ISDN or DSL diagnostics links are in use. Magnetic tape is another option, though it is now non preferred. See reference -
   
   
   • HANDBOOK 1: MAINTAINING THE SYSTEM Section 3.5.1 Processing Automatically raised problems with TST
   
   
   
5. There is no requirement to raise an EPR for a software problem covered by an Auto MSR.
   
   
6. Further evidence may be appended to the evidence set of an Auto MSR if required.
   
   
7. Please note that all your core loadsets must be at currently supported version of OVME before TST is switched on.