[foxboro] how to really omset STRINGs from dmcmd

All knowing and all wise Alex,

you wrote:
> Can be implemented as

[ahem] your statements are not QUITE syntactically correct. ;-) To =
prevent
all others from trial and error experiences here is the correct syntax,
tested on an AW70 with FoxView (should work on all other FWs on Solaris =
and
Windows as well) (be careful with the nested "'" and """ signs):

#!/bin/sh
#
# replace the following with the name of your DM
DMNAME=3DBKA911
#
echo "This is the first message"
/usr/local/pref -${DMNAME} DMCMD 'msglin "This is the first message"'
sleep 2
echo "This is the second message"
/opt/fox/bin/tools/omsetimp -s "msglin \"This is the second message\""
${DMNAME}DMCMD

yours faithfully

Marcel Sieling
Systems Technologies

Invensys Systems GmbH
Emanuel-Leutze-Str. 11
40547 Duesseldorf
Germany
Tel.:      +49-211-5966-302
Fax:      +49-163-99-5966302=20
Mobile:  +49-163-5966302
Email: mailto:marcel.sieling@xxxxxxxxxxxxxxxx
Homepage: http://www.foxboro-deutschland.de


> -----Urspr=FCngliche Nachricht-----
> Von: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] Im Auftrag von Johnson,=20
> Alex (Foxboro)
> Gesendet: Samstag, 29. Januar 2005 14:04
> An: foxboro@xxxxxxxxxxxxx
> Betreff: Re: [foxboro] how to omset STRING block from dmcmd
>=20
>=20
> True. That's good advice.
>=20
> /usr/local/pref -$DMNAME DMCMD "Setting $CBP"
>=20
> Can be implemented as
>=20
> /opt/fox/bin/tools/omsetimp -s "Setting $CBP" ${DMNAME}DMCMD
>=20
> ${DMNAME}DMCMD expands to something like 'WP0001DMCMD' which=20
> is the name of the OM variable checked by DM/FV to look for commands.
>=20
>=20
> Regards,
> =20
> Alex Johnson
> Invensys Process Systems
> Invensys Systems, Inc.
> 10707 Haddington
> Houston, TX 77043
> 713.722.2859 (voice)
> 713.722.2700 (switchboard)
> 713.932.0222 (fax)
> ajohnson@xxxxxxxxxxx
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of john kinsley
> Sent: Friday, January 28, 2005 10:42 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] how to omset STRING block from dmcmd
>=20
> I believe the pref command is a broadcast so if you're using=20
> omsetimp to reduce broadcasts, you probably don't want to use=20
> the pref command either.
>=20
> John Kinsley
> Saudi Aramco
> P&CSD/PCD/PASU
> Phone:  966-3-873-0952
>=20
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson,=20
> Alex (Foxboro)
> Sent: Thursday, January 27, 2005 4:28 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] how to omset STRING block from dmcmd
>=20
> Display Manager or FoxView
>=20
> If FoxView, which release?
>=20
> The alias function in FV will probably be the simplest
> solution to your
> problem, i.e., it allows you to build quite complicated
> generic overlays.
>=20
>=20
> If you need to set a string C:B.P, do this:
>=20
> dmcmd run /opt/fox/bin/tools/omsetimp -s "<value>" C:B.P
>=20
> where
>    <value> is the string value to set. If it holds blanks,
> use the quotes
>            shown. Otherwise, they are optional.
>    C:B.P   is the parameter to change.
>=20
> Normally, this line is placed in a script with other lines.=20
>=20
> You have two types of scripts: Shell Scripts and DM scripts
>=20
> DM Scripts
>=20
> dmcmd script
> dmcmd run /opt/fox/bin/tools/omsetimp -s $P8 C:B.P
>=20
> or something similar
>=20
>=20
> Alternatively, you have a Shell Script
>=20
> Assume the script is myScript and it is stored in=20
> /opt/MyScripts. It should read something like:
>=20
> #!/bin/sh
> mkdir -p /opt/MyScripts/logs
> LOG=3D/opt/MyScripts/logs/`basename $0`
> exec >$LOGS 2>&1
>=20
> DMNAME=3D$1
> VALUE=3D"$2"
> CBP=3D"$3"
>=20
> /usr/local/pref -$DMNAME DMCMD "Setting $CBP"=20
/opt/fox/bin/tools/omsetimp -s "<value>" C:B.P
>=20
>=20
> You would invoke the script as:
>=20
> dmcmd run /opt/MyScripts/myScript $DMNAME "<value>" C:B.P
>=20
>=20
>=20
>=20
> Regards,
> =20
> Alex Johnson
> Invensys Process Systems
> Invensys Systems, Inc.
> 10707 Haddington
> Houston, TX 77043
> 713.722.2859 (voice)
> 713.722.2700 (switchboard)
> 713.932.0222 (fax)
> ajohnson@xxxxxxxxxxx
>=20
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Liptock,=20
> Sheri A - Eastman
> Sent: Wednesday, January 26, 2005 5:16 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] how to omset STRING block from dmcmd
>=20
> OOPS, should have mentioned that "=3D3D P8 string" works to
> store the =3D
> string
> in the P8 variable.  But because I have 20 tanks on one
> display then I
> cannot use P8 to subsequently display/update the graphic  --=20
> because all 20 tanks go to the same string (ie, product name)=20
> which is wrong.  But I do have 20 STRING blocks.  So I tried=20
> to send the contents of P8 to a specific STRING.VALUE, but=20
> not working.
>=20
>=20
> -----Original Message-----
> From: Liptock, Sheri A - Eastman=3D20
> Sent: Wednesday, January 26, 2005 4:32 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] how to omset STRING block from dmcmd
>=20
>=20
> Hi,
>=20
> Need action of an object to set the .VALUE of a string
> block.
>  "=3D3D3D" or "subst" DO NOT appear to work. =3D3D20
> However omset from $prompt does, but would prefer dmcmd to
> set the
> string.
>=20
> Please help, anyone.  Thanks very much.  I have talked with=20
> several at TAC and they proposed the omset script. =3D20 =3D20=20
> ____________________________________________________________
> ___________
> 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=20
> http://www.thecassandraproject.org/disclaimer.html
> =3D20
> foxboro mailing list:
> http://www.freelists.org/list/foxboro
> to subscribe:         =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe:      =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
> =20
> =20
> ____________________________________________________________
> ___________
> 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=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro=20
> mailing list:
> http://www.freelists.org/list/foxboro
> to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
> =20
> =20
> ____________________________________________________________
> ___________
> 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=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro=20
> mailing list:
> http://www.freelists.org/list/foxboro
> to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>=20
> =20
> =20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process Systems (formerly The Foxboro Company). Use=20
> the info you obtain here at your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro=20
> mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to=20
> unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
> =20
> =20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process Systems (formerly The Foxboro Company). Use=20
> the info you obtain here at your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro=20
> mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to=20
> unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>=20
 
 
_______________________________________________________________________
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: