Re: [foxboro] Deleted Tags

...described in CAR 990568 is an interesting issue (and even more
interesting response)  
related to your question regarding deleted source blocks involved in
peer-to-peer connections:

CAR 990568:

ISSUE:
OM Peer to Peer point connections not releasing.  There appears to be a
problem with peer to peer CBP connections between CP's and AW51
Integrators
that do not release when either the source block or compound is deleted.
This is true whether the source connection originates in the CP or the
AW51
Integrator.  This condition has been monitored by using the som and rsom
utilities against the stations.  The CP's are running V4.2.3.  The AW51
Integrator is running V6.1 with the large control station image.  (The
large control station image is being tested to verify that more than 300
Local connections are possible.)  The number of entries in the peer to
peer
OM lists finally update after the source and sink stations are
restarted.

RESPONSE:
11/08/99 - Response from TAC:
This is a duplicate of 990565 whose response is:
Workaround:
To prevent this problem from happening the following procedure must be
adhere to
   ADD/REMOVE PEER_TO_PEER PROTOCOL PROCEDURE:
A correct procedure for adding and removing peer_to_peer connections
from
he OM open_var_list:
1. In the SOURCE/SERVER station NEVER delete a source block from the
database that has active peer_to_peer connections.
2. In the SOURCE/SERVER station - Add the new source block to the
database,
leave the old block in the database for now.
 . In the SYNC/CLIENT station ALWAYS Modify the peer_to_peer connection
path name to the new source block before deleting the unwanted source
block
from the SOURCE/SERVER station.  This will result in a delete message
being
sent to the SOURCE/SERVER.  The SOURCE/SERVER will then free up the old
connection entry in the OM open_var_list.  When the SYNC/CLIENT station
is
checkpointed by closing the ICC/ICCAPI session, the new peer_to_peer
linkage will be resolved in both stations.
4. In the SOURCE/SERVER station now delete the unwanted block.  Since it
now has no active peer_to_peer connections, there is no need to modify
the
OM open_var_list.  Thus, no permanent deleted entry remains in the list.
Action:
The peer-to-peer 'dropout' connection happened because the SOURCE
station
deleted the wrong Object Manager open variable entry.  The SYNC station,
while in the process of deleting another peer-to-peer connection, sent
an
incorrect Object Manager open variable index value to the SOURCE
station.


Richard Massitti  
Ingénieur en Instrumentation  
Raffinerie de Montréal-Est  
Produits Shell Canada Ltée  
_______________
Tél.: 514-640-3506  
Fax: 514-640-3284  



-----Message d'origine-----
De : Timothy.Teindl /Internet/dd.RFC-822=Timothy.Teindl@xxxxxxxxxxxxxxx
[mailto:Timothy.Teindl@xxxxxxxxxxxxxxx]
Envoyé : 31 mai, 2002 10:04
À : Foxboro /Internet/dd.RFC-822=Foxboro@xxxxxxxxxxxxx
Objet : [foxboro] Deleted Tags




Hello,
I was wondering if there was a tool to tell all the places a tag has
been
connected to. I know that by looking at the Station Block on FoxSelect
you
can monitor the Peer to Peer Status including Total Points and Points
Deleted. But if a tag is going to more than one CP, and the tag is then
deleted, how do you find all the other places the tag was going? (In
order
to clean up the data base) Our AW is running 50 series Unix.
Thanks...Tim

  
  
_______________________________________________________________________
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
  



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