Depends on what you are trying to do. If you want to the change to survive a
reboot, it must be reflected in the checkpoint file.
What are you doing that requires the use of setpars?
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 4:29 PM
To: Foxboro DCS Mail List
Subject: RE: HLBL REF.
After speaking with our former application engineer, I agree that
the
setpars is not what we want to do.
We currently only use the "setpars" tool after an unusual event, it
is not
used on a routine basis, the display
with the call button is not nomally accessible.
Do you recommend running a checkpoint after every use of the setpars
tool?
Ken Moore
NSCC
"Johnson, Alex (Foxboro)" <[EMAIL PROTECTED]>
@lists.TheCassandraProject.org> on 07/09/2001 13:23:44
Please respond to "Foxboro DCS Mail List"
<[EMAIL PROTECTED]>
Sent by: <[EMAIL PROTECTED]>
To: Foxboro DCS Mail List <[EMAIL PROTECTED]>
cc:
Subject: RE: HLBL REF.
Setpars is a pretty powerful tool. I hope you are very careful with
its
use.
It will make changes to the CP that are not reflected in the
checkpoint
file
or the workfile.
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 9:52 AM
To: Foxboro DCS Mail List
Subject: RE: HLBL REF.
It is a Unix script, currently called via a foxview button , I
would
like
to include this in the sequence logic if possible.
The script utilizes the "setpars" tool found in
/opt/fox/bin/tools.
Ken Moore
NSCC
"Jones, Charles R. (Chuck)" <[EMAIL PROTECTED]>
@lists.TheCassandraProject.org> on 07/09/2001 11:59:08
Please respond to "Foxboro DCS Mail List"
<[EMAIL PROTECTED]>
Sent by: <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'"
<[EMAIL PROTECTED]>
cc:
Subject: RE: HLBL REF.
If the operators can interact with the process, I recommend
putting
GDEV
blocks to AUTO (then WAIT 2 seconds for the block to see it)
right
before
you use each one. It is the only way to be sure that the GDEV
will
be in
the correct auto/manual state when you need it to be. If you
are
going to
change state on several GDEVs, then you can put them all to
AUTO
followed
by
only one WAIT statement.
If you want to call the script that you have already written,
then I
am
going to have flex a few thoughts to remember how to do that.
Depending on
how you wrote the UNIX script, I believe that it may be a more
efficient
use
of resources to rewrite it in HLBL. Is it a UNIX script, PERL,
C
code, or
--Heaven forbid-- JAVA? (I am assuming UNIX.) Does the script
use
Object
Manager calls or API calls?
I'm curious now. Does any one know if HLBL is the most
efficient
use of
resources in this case? Does anyone know how to call an
external
script
from within HLBL?
Chuck Jones
Refinery Automation Technologist
A.E. Staley Mfg. Co. -- Lafayette South Plant
765.477.5324 - Office | 765.420.4431- Pager
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 5:17 AM
To: Foxboro DCS Mail List
Subject: RE: HLBL REF.
Thanks for the input,
I have a script that places all GDEV blocks in auto. How would
you
use this
in HLBL. I would like to place all GDEV's in auto at the
beginning
of the
Sequence Logic.
thanks in advance
Ken Moore
NSCC
This e-mail and any files transmitted with it are confidential
and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you are not the intended recipient or the person responsible
for
delivering the e-mail to the intended recipient, be advised
that you
have
received this e-mail in error, and that any use, dissemination,
forwarding,
printing, or copying of this e-mail is strictly prohibited. If
you
have
received this e-mail in error, please notify the TLNA HELPDESK
at
800-404-2436 or e-mail [EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro
Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to
hold
the
list sponsor(s) blameless for any and all mishaps which might
occur
due to
your application of information received from this mailing
list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is
for
the
intended recipient only. Access, disclosure, copying,
distribution,
or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email
confirmation
to the
sender.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro
Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to
hold
the
list sponsor(s) blameless for any and all mishaps which might
occur
due to
your application of information received from this mailing
list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to hold
the
list sponsor(s) blameless for any and all mishaps which might occur
due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for
the
intended recipient only. Access, disclosure, copying, distribution,
or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation
to the
sender.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to hold
the
list sponsor(s) blameless for any and all mishaps which might occur
due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
