Re: [foxboro] Operator action journal auto start at boot up

oops, an error in my example ;

the system uses 
   dmtlist=OJLOG
not
   gctlist=OJLOG

That is the OJLOG variable is created per
Display Manager, not per Workstation

WCR
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of William C Ricker
Sent: Friday, December 07, 2001 5:02 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Operator action journal auto start at boot up



Which in a practical sense means

   gctsize=14

   I will make a variable.  It will be a Text
   variable ( the 't' in 'gctsize says that ) and I
   want it to be 14 characters ling.

   gctlist=OJLOG

   Make the text variable ( again the first 't' in 
   gctlist ) now and call it OJLOG.  Make one copy
   for all DM's in this workstation (the 'gc' in 
   'gclist )

Another place you might use, for example:

   dmtlist=OPNAM

   Make the text variable ( again the first 't' in 
   gctlist ) now and call it OJLOG.  Make one copy
   for each DM in this workstation (the 'dm' in 
   'dmlist )

There are other permutations, 'amtlist' makes variables
per alarm manager, 'gcllist' makes long type variables
per workstation, gcflist makes float type variables 
per workstation, and so forth.

For practical examples, look at the file somebody else 
mentioned in this discussion, 
'/usr/fox/wp/data/wp51_glbls.all'.  Most of the display 
and alarm HI variables are created and initialised there.

Oh, and when you look around in that file, remember that 
also sets up the read-only variable set, too.  They don't
have the 'gctsize'/'gctlist', or similar constructs.


W C Ricker
FeedForward, Inc.
Marietta GA

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of
Richard.Massitti@xxxxxxxx
Sent: Friday, December 07, 2001 4:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Operator action journal auto start at boot up



=2E..rather our ''read-write'' variable is OJLOG ...sorry about that

 -----Message d'origine-----
De :    Richard.Massitti /Internet/dd.RFC-822=3DRichard.Massitti@xxxxxxxx =
[mailto:Richard.Massitti@xxxxxxxx] =20
Envoy=E9 :      07 d=E9c., 2001 16:11
=C0 :   foxboro /Internet/dd.RFC-822=3Dfoxboro@xxxxxxxxxxxxx
Objet : Re: [foxboro] Operator action journal auto start at boot up


Hello Ken :

From  FoxDoc (oh, sorry...I mean Invensys Doc) B0193DF,  Rev K  - Displa=
=3D
y Manager Commands, Chapter 11 under =3D20

''wp51_gbls.* File Syntax''

it alludes to the need to specify the name and size of a read-only varia=
=3D
ble.  In our case, the read-only variable is ''OJLOG'' and we want to di=
=3D
sable, enable, etc. it .

Excerpt from FoxDoc :

The syntax of a read-only variable specification is:

     XXXXXX=3D3D<value>

     where

          XXXXXX is the name of the variable

          <value> is the value to be assigned to the variable. <value> c=
=3D
an be blank.

Specifying a read-write variable requires two pieces of information: the=
=3D
 size of the variable and its name.

     gctsize=3D3D<size>

     where

          gctsize is a reserved word, indicating the size (in characters=
=3D
) of the read-write variable.

          <size> is the size (in characters) of the next set of read-wri=
=3D
te variables. The maximum size is 255.

The syntax of a read-write variable is:

     dmtlist=3D3D<variable(s)> =3D20

     where

          dmtlist is a reserved word, indicating that a list of read-wri=
=3D
te variables follows

          <variable(s)> is a list of read-write variable names. A separa=
=3D
te variable is created for each configured display
          manager name. The maximum length of the variable name is eight=
=3D
 characters.

Best regards,
Richard

 -----Message d'origine-----
De :    Ken.E.Moore /Internet/dd.RFC-822=3D3DKen.E.Moore@xxxxxxxxxxx [mail=
to=3D
:Ken.E.Moore@xxxxxxxxxxx] =3D20
Envoy=3DE9 :    07 d=3DE9c., 2001 15:33
=3DC0 : foxboro /Internet/dd.RFC-822=3D3Dfoxboro@xxxxxxxxxxxxx
Objet : Re: [foxboro] Operator action journal auto start at boot up


Thanks for all the replies,

Can you decode the entries:

gctsize=3D3D14

dmlist=3D3DOJLOG

What does what to what?

thanks

Ken Moore
NSCC
Woodruff, SC






"William C Ricker" <wcricker@xxxxxxxxxxxxxxx>@freelists.org on 12/07/200=
=3D
1
02:01:42 PM

Please respond to foxboro@xxxxxxxxxxxxx

Sent by:  foxboro-bounce@xxxxxxxxxxxxx


To:   <foxboro@xxxxxxxxxxxxx>
cc:
Subject:  Re: [foxboro] Operator action journal auto start at boot up



(Richard, The e-mail system is throwing extra
characters into your messages (the '3D' that
shows up after every '=3D3D' sign.)

As such, it should look like this)

> Try :
>
> OJLOG=3D3DDLP01, Ehist01  (you have this already)
> gctsize=3D3D14            (add this with no spaces
>                           within the statement)
> dmtlist=3D3DOJLOG         (add this with no spaces
>                           within the statement)


However, at least since 6.1, the 'gctsize' and 'dmlist'
lines are in the tail end of file 'wp_51glbls.all',
which is the Foxboro def's, processed before the
file 'init.user'.  As such, I'd have thought that
this variable creation step shouldn't be needed.

That being said, however, we tested it on a 6.2
AW51 (just did it).  Without the 'gctsize' and
'dmtsize', the variable is not changed to what's
in the 'init.user' file; rather it retains what's
in the standard definition ( OLOG=3D3DDLP00,Dqualdb ).

Learn something new every day.

Also seems in out test we see that the D or  E preceeding
the printer name or historian name is operating
to cause Disable or Enable, so use of a fake printer
or historian name is'nt indicataed.  Just use D to
disable, and E to enable.

Any questions about how the string should form
up can be answered by setting the options like
you want then using the 'OperActJournal' pick
under the 'Config' menu.  Then use the VT100
mode and type 'pref -DMNAME OJLOG' to see how
it built the string.  Copy this into the
init.user file.


W C Ricker
FeedForward, Inc.
Marietta, GA


___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave




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=
=3D

offence.  Please delete if obtained in error and email confirmation to t=
=3D
he
sender.

=3D2D- No attachments (even text) are allowed --
=3D2D- Type: application/octet-stream
=3D2D- File: $RFC822.eml


 =3D20
 =3D20
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave

 =20
 =20
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: