As part of the test design inspection (TDI), 
you must inspect the appropriate entry
in the trace matrix.

look for v05_trace.lis in 
ebsr3:[fpdtest.trace.b717-200.LIS]

any errors or missing entries should be reported to me.

but - you can fix them yourselves:

tim made a COM file to automatically insert
all info in the [.ADD]*.TRC to the trace matrix daily:
 
ebsr3:[fpdtest.trace.b717-200.ADD]


* 
HELP
Main Cluster Trace Report




How to update the TRACE database:

Generate the .TRC file

Copy the .TRC�file to EBSR3:[FPDTEST.TRACE.proj.ADD]

Execute the file SET_PROTECTION.COM

-- that is all, the trace database will get updated the next time Main_Cluster_Trace_Report
is run








TRC FILE FORMAT



Below is an example of an ideal TRC file.



Example .TRC file:


proj MD95 

zpd_xx0010 v00_anchor_1_from_dss 

zch_xx0090 v00_anchor_2_from_dss 

ioct_1_deu_adis_out v00_anchor_3_from_dss 




* The project in this example is designed as a comment
only.







The format for the .TRC file should always be:

TEST_ANCHOR space space space DSS_ANCHOR

* One space is required, several spaces improve readability

* uppercase or lowercase does not matter

* DO�NOT�USE�TABS












TRC FILENAMING



USERNAME#.TRC 



TRC Filenaming convention. The only file naming concern is that the
files do not all end up with the same name. To avoid this problem use USERNAME#.TRC
where "#" is a number unique for each file (# can be 1-5 characters).













when you have time,
please review the matrix and send me a list
of testids that do not belong in the MD95 trace matrix.
that is, testids from other programs not used in MD95.
(for example, any ppd_at007x we are not using this time)
i will delete them.
we can clean up as we go, or we can do it all at the
end of the project when we have everything in ACM.
either way, it has to be completely accurate.

(i added all testids from -600 and md90 to this tracematrix.
 i understand that some of these testids will not be used
 in MD95, but i added them anyway as a reminder.
 it will remind us to look for old tests 
 instead of making a new one.)


TRACE

> 2) For tests already inspected should be maintain a local copy of the trace
> list and update it as and when inspections are done and send you the list
> every week. Is that ok.
no.
please send me a list of testids you wish to add (ADD.TRC)
and another list of testids you wish to delete (DELETE.TRC)
in the format of 
TEST ID    SRD_ANCHOR
TEST ID    SRD_ANCHOR
TEST ID    SRD_ANCHOR
TEST ID    SRD_ANCHOR

example: this is the ADD.TRC i will run today:

ppd_bk0010  v05_bank_angle_limit
ppd_fp0010  v05_fpa_symbol
ppd_fp0011  v05_fpa_target