Re: omset should never be used for application purposes

One should generally use /opt/fox/bin/tools/omsetimp instead of omset.

The caveat with it is that it eliminates broadcasts by placing the compound
name and the corresponding address in the IMPORT table.

The IMPORT table is 100 entries by default and it can be filled.

The IMPORT table usage can be monitored by using 'show_params'.

The size of the IMPORT table can be increased by following the procedure
described either of the following manuals:

*       B0193MJ - 50 Series Configurable Operating System and 
*       B0193ND - System Administration Guide for 50 Series Systems (Solaris
2.X)



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:   Sieling, Marcel [SMTP:[EMAIL PROTECTED]]
        Sent:   Tuesday, March 20, 2001 6:50 AM
        To:     'Foxboro DCS Mail List'
        Subject:        crontab issues and other useful information

        Hi,

                >I  reset accumulators  as follows by adding the following
                >line to the the scheduler cron table
                >               1 6 * * *  /opt/fox/bin/tools/omset -v -b T
        <COMPUND_NAME>:<ACCUM_NAME>.RESET
                >You will need to write  an application to clean up the cron
                >logs periodically to conserve disk space.

        Let me make two notes on this statements:

        1.) omset should never be used for application purposes, if it can
be
        avoided. The use of omset (omcrt, omdel, omfnd, omget etc.) produces
        Broadcast Messages on the Nodebus, which can very easily overload
the
        system, especially in large systems, because Broadcasts are sent to
all
        stations.

        2.) The cron logs can be kept from growing if output is sent to some
device
        or file or /dev/null in the crontab. Of course then you can't look
at them
        anymore to investigate in case of problems. But often this is a nice
        solution for every days work and only in case of problems you change
the
        redirection to a file. Since cron is running the cron jobs in a
bourne
        shell, the appropriate statement would look like this:

                >               1 6 * * *  /opt/fox/bin/tools/omset -v -b T
        <COMPUND_NAME>:<ACCUM_NAME>.RESET >/dev/null 2>&1 &

        In case you want to see only errors and not the regular messages try
this:

                >               1 6 * * *  /opt/fox/bin/tools/omset -v -b T
        <COMPUND_NAME>:<ACCUM_NAME>.RESET >/dev/null
        2>/usr/tmp/my_phantastic_logfile &



        BTW: Did you know, where the dust in long used computers is coming
from?

        Well, it's pretty simple and obvious: All data being sent to
/dev/null ist
        being transformed into thermal energy, because it can not disappear
from the
        world without being transformed to something else. Now (as every
physics
        student knows) thermal energy corresponds to mass with the famous
equation
        E=mc^2 from Albert Einstein. So all the thermal energy is
transformed to
        mass and that's where the dust in computers comes from. ;-))

        Now you know. ;-)

        PS: Don't tell my boss I'm wasting time writing such emails. ;-))

        best regards -

        Marcel Sieling
        Systems Technologies

        FOXBORO Deutschland GmbH
        Heerdter Lohweg 53 - 55
        40549 Duesseldorf
        Tel.:    +49 (0)211 5966-171
        Fax:     +49 (0)211 5966-104
        Mobile:  +49 (0)172 2673077
        E-Mail:  [EMAIL PROTECTED]
        http://www.foxboro-deutschland.de
        Private Home: http://www.powerslider.de

        > -----Urspr�ngliche Nachricht-----
        > Von:  Freddy Why [SMTP:[EMAIL PROTECTED]]
        > Gesendet am:  Freitag, 16. M�rz 2001 10:36
        > An:   Foxboro DCS Mail List
        > Betreff:      RE: Accumulator Block
        > 
        >               Loyd,
        > 
        >               I  reset accumulators  as follows by adding the
following
        > line to the the scheduler cron table
        >               1 6 * * *  /opt/fox/bin/tools/omset -v -b T
        > <COMPUND_NAME>:<ACCUM_NAME>.RESET
        >               You will need to write  an application to clean up
the cron
        > logs periodically to conserve disk space.
        >               The above works for 50 series server , for 20 series
the
        > application 'omset' is in directory /usr/fox/bin/tools
        > 
        >               Regards,
        > 
        > 
        >               Freddy Why
        > 
        >               AFH Devers - Engineering Services South Africa
        >               A division of Protea Data Systems
        > 
        > 
        >               Email Address: [EMAIL PROTECTED]
        > <mailto:[EMAIL PROTECTED]> 
        >               Website: http://www.protea.co.za
<http://www.protea.co.za>  
        > 
        >               Telephone Number:
        >               (+27) (11) 719-5750 (Direct)
        >               (+27) (11) 719-5700 (Switchboard)
        >               (+27) (82) 7747845  (Mobile)
        >               (+27) (11) 887-8757 (Fax)
        > 
        >               Address:
        >               26 Sixth Street, Wynberg, Sandton
        >               P.O.Box 707, Bramley, 2018
        > 
        > The information transmitted is intended only for the person or
entity to
        > which it is addressed and may contain confidential and/or
privileged
        > material.  Any review, retransmission, dissemination or other use
of, or
        > taking of any action in reliance upon, this information by persons
or
        > entities other than the intended recipient is prohibited.   If you
        > received
        > this in error, please contact the sender and delete the material
from any
        > computer.
        > 
        > 
        > 
        >                               -----Original Message-----
        >                               From:   Heath, Graham
        > [SMTP:[EMAIL PROTECTED]]
        >                               Sent:   Friday, March 16, 2001 10:15
AM
        >                               To:     'Foxboro DCS Mail List'
        >                               Subject:        RE: Accumulator
Block
        > 
        >                       suggest using the TIM command which returns
the
        > number od seconds since
        >                       Midnight date I say RTFM.
        > 
        >                       regds
        > 
        > 
        > 
        >                       -----Original Message-----
        >                       From: Loyd Greer [mailto:[EMAIL PROTECTED]]
        >                       Sent: 15 March 2001 1:31
        >                       To: Foxboro DCS Mail List
        >                       Subject: Accumulator Block
        > 
        > 
        >                       Hi to the list.
        >                                I would like to clear (reset) an
        > accumulator block at 0600 every
        >                       day with the system clock or TOD. If this
can be
        > done, I would appreciate
        >                       any suggestions on how to do it.
        > 
        >                            Thanks in advance
        >                            Also thanks to Joe Gale for help on a
Weather
        > Station Display.
        >                            Loyd Greer
        >                            Great Lakes Chem.
        > 
        > 
        >       
        >
-----------------------------------------------------------------------
        >                       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]
        > 
        >
-----------------------------------------------------------------------
        > 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]

-----------------------------------------------------------------------
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]

Reply via email to