Article 137109 of comp.os.vms:
Path: nntpd.lkg.dec.com!depot.mro.dec.com!mrnews.mro.dec.com!news
From: Scott Hamilton <scott>
Newsgroups: comp.os.vms
Subject: Re: Monitoring FTAM
Date: 4 Jan 1996 15:13:09 GMT
Organization: Digital Equipment Corp.
Lines: 20
Message-ID: <4cgqq5$du1@mrnews.mro.dec.com>
References: <375CDBB319C@pdcfs1.pdc.nhs.gov.uk>
NNTP-Posting-Host: moonbase.uvo.dec.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 1.12 (X11; I; OSF1 V3.2 alpha)
X-URL: news:375CDBB319C@pdcfs1.pdc.nhs.gov.uk

It's part of FTAM itself. Try the following;

	$ define osif$trace_enable ftam-pci,acse-pci,presentation-pci,session
	$ define osif$trace sys$login:ftam_trace.dat
	$ dir/applic=ftam node::"blah blah blah"
	$ ftrace :== $osif$ositrace
	$ ftrace sys$login:ftam_trace.dat 

	If you need to check the lower layers use the Common Trace Facility
	you'll need the NET$TRACEALL identifier granted to your username
	then simply try

	$ trace
	CTF> start/live ositp

	or whatever tracepoint takes your fancy...

	Hope this helps
	  Scott.