Re: [foxboro] ICCDRVR.tsk - GET script problem
- From: "Jeremy Milum" <jmilum@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 19 Apr 2007 02:24:10 -0500
On 4/19/07, Dimitris Legakis <legourasj@xxxxxxxxxxx> wrote:
> Actually I have tried many variations of the iccprt script including the one
> you propose. The only one that could work is:
> iccprt -p 12GHC01:* file.txt CP000B
> Which extracted all parameters of all blocks in the compound 12GHC01.
strange as that should not work like that. let me check the docs....
(i am not sure how this will format)
**********
Usage: iccprt [-p] [-n compound[:block]] [-o outputfile] <station>
-n compound and/or block list to be reported (wildcards are valid);
default is for all compounds.
-o output file to which report will be redirected; default is to console.
-p generate report on compound and/or block PARAMETERS rather than
compound and/or block ORDER.
<station> is the Control Station or volume to be reported.
***********
so I don't think that running it like you did would work since you did
not specify the -n parameter, leaving it off all together (along with
any wildcards or comp:block specifications) should return the
parameters for every comp:block in the CP
alas, i am not at work and cannot verify all this, but I can see about
it tomorrow. I am sure others will chime in before that and show where
I have gone astray ;)
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
