Re: [foxboro] ICCDRVR.tsk - GET script problem

I've never been able to get partial wildcarding to work with iccprt, i.e.,

iccprt -n "12*:*" -o /tmp/blah -p


would not get any compounds, even those beginning with "12".  [The comment 
about shell globbing is probably correct, but it has surprisingly never 
caused me issues when I left out the quotes.]  Having said that, though, I 
can omit the -n and successfully get entire CPs, on all my CPs, on both my 
I/A systems.  I wonder if maybe your workfile is corrupted on that CP or 
something.  Did you try dumping every compound in that CP individually to 
see if there is an offender?  Using getpars to dump them out to a list and 
then a simple for loop in a shell script should make that a 
not-too-tedious process.


Corey Clingo
BASF Corporation






"Dimitris Legakis" <legourasj@xxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/19/2007 04:09 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
Re: [foxboro] ICCDRVR.tsk - GET script problem







iccprt -p -n "12*:*" -o file.txt CP000B
did start to create the file.txt, but I still have the same problem. The
file was increasing endlessly and after the interruption I found many 
blocks
repeating too many times.

The main problem I need to resolve is the endless increase of the output
file that happens every time i run GET script or iccprt:
eg.
OPEN CP000B ALL TMP
GET *:* SUBSET *
*
END
CLOSE
EXIT

and when i run:
iccprt -p -n "12*:* -o file.txt CP000B

Note that the very same scripts work perfectly on other CPs.




 
 
_______________________________________________________________________
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: