  what is TP_SERVER? 
 The Question is:
 
What is the TP_SERVER process actually used for and is it necessary to run
on the system?
 
 The Answer is:
    With VMS V5.4 a few new processes can be seen via the SHOW SYSTEM command.
 
    One, TP_SERVER, may take some CPU cycles from you, if you haven't seen
    and acted upon a startup OPCOM message and/or the Release Notes.
    It is used to by DecDTM to manage distributed transactions.
    (System services SYS$START_TRANS[w], SYS$END_TRANS[w],...)
 
    If you don't use TP_SERVER, you can inhibit it's creation with the
    following line in SYLOGICALS.COM:
 
          $ define/system/exec sys$decdtm_inhibit true
 
    On boot, TP_SERVER looks for a journal file, normally found in
    SYS$SYSTEM, (but the location is pointed to by the SYS$JOURNAL logical)
    called  SYSTEM$nodename.LM$JOURNAL. If the journal file is not found,
    it will look again every 15 seconds until it is found.
 
    This is regardless of whether you are using TP_SERVER for anything at all.
 
    On systems where TP_SERVER is not being used, you can stop TP_SERVER's
    CPU cycle-grabbing by issuing the following command:
 
          $ MCR LMCP CREATE LOG SYSTEM$nodename.LM$JOURNAL/SIZE=100
 
    If you are using TP_SERVER, via RMS Journalling, RDB or DBMS, please
    see their documentation in combination with the VMS V5.4 Release Notes
    and New Features Manual for sizing information. Otherwise, 100 blocks
    is the minimum size.
 
    This file must be created for all members of a cluster and will be used
    immediately tha TP_SERVER recognises its existence in a maximum of 15
    seconds after creation. TP_SERVER will thenceforth cease using your CPU
    to go look for a file that isn't there. No reboot is needed.
 
