[foxboro] C:B refs in sequence blocks

Hi,
(My first posting to this group!)

I'am looking for a way to report all COMPOUND:BLOCK references within sequence 
blocks.
I have managed to do this for 'normal' sequence blocks by means of the sequence 
block compiler from a script (/opt/fox/ciocfg/topseq (or was is seqtop?)).
I copy my .s files to some ../tmp directory and run the pre-processor on these. 
This will create output files in this ../tmp directory of which one of them has 
the extension .e.
With the unix 'strings' command you get (as far as I can tell) a list of all 
used COMPOUND:BLOCKS within the compiled sequence block (including any included 
files).

My problem now is that I have not found a way yet to do the same trick for SFC 
sequence blocks.
I noticed that when compiling the block from within the SFC package the .e file 
is generated but automatically removed.
As I would like to automate this I would like to do this from within a script 
so I don't have to manually start the SFC package.

Anybody out there who could give me some hints?

Platform is AW51.

TIA,

P. Martens,
Total Raffinaderij Nederland NV.

ps:
I would like to add this info to a MS-Access based application which I wrote 
over the last couple of years.
This started of with having the complete CIOCFG of all our CP's available in 
MS-Access format.
Currently it includes compound:block references (usage) to all mimics, 
historians, trendscripts, advanced control files (DMCplus.oad files), all 
aimapi/foxapi usages and, recently, sequence blocks.
All this info is updated automatically once every day (or on request).
All CIOCFG parameter changes, block additions/deleting are logged (comparing 
with files of previous day).
IO tables are generated (including spares, as long as there is an ECB for the 
FBM)

This tool has proven to be very usefull as we can now run any kind of query we 
can think of!
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: