problem in tool when checking the access of Index elements
Hello,
Iam having an Index element which is also an OBJECT for an NOTIFICATION-TYPE object. And Iam having the MAX-ACCESS of this Index element as "accessible-for-notify". The smilint tool gives an warning that "Index element should be not-accessible", which is wrong for this case. So an extra check should be put for this also.
Regards, Vivekanandan.V *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************
HI,
You can not have an index object with access of accessible-for-notify.
At 11:56 AM 4/5/2002 +0530, Vivekanandan V wrote:
Hello,
Iam having an Index element which is also an OBJECT for an NOTIFICATION-TYPE object. And Iam having the MAX-ACCESS of this Index element as "accessible-for-notify". The smilint tool gives an warning that "Index element should be not-accessible", which is wrong for this case. So an extra check should be put for this also.
Regards, Vivekanandan.V
Regards, /david t. perkins
Hi,
Then whether a check for this can be added in the smilint tool. Presently the tool is not giving an error, if Iam having an Index object with an access of "access-for-notify".
Regards, Vivekanandan.V
-----Original Message----- From: libsmi-admin@ibr.cs.tu-bs.de [mailto:libsmi-admin@ibr.cs.tu-bs.de]On Behalf Of David T. Perkins Sent: Friday,April 05,2002 1:31 PM To: vivekav@future.futsoft.com; libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] problem in tool when checking the access of Index elements
HI,
You can not have an index object with access of accessible-for-notify.
At 11:56 AM 4/5/2002 +0530, Vivekanandan V wrote:
Hello,
Iam having an Index element which is also an OBJECT for an NOTIFICATION-TYPE object. And Iam having the MAX-ACCESS of this Index element as "accessible-for-notify". The smilint tool gives an warning that "Index element should be not-accessible", which is wrong for this case. So an extra check should be put for this also.
Regards, Vivekanandan.V
Regards, /david t. perkins
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to libsmi-request@ibr.cs.tu-bs.de !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.
*************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************
Hi!
(a)
Vivekanandan> [...] The smilint tool gives an warning that Vivekanandan> "Index element should be not-accessible", [...]
(b)
Vivekanandan> [...] Presently the tool is not giving an error, if Iam Vivekanandan> having an Index object with an access of Vivekanandan> "access-for-notify".
I am confused. Which one is true, (a) or (b)?
(a) should be true, and it is for me.
Or do you just mean the severity of the message should be increased?
-frank
Hi,
Sorry for the confusion!!!!! The tool is giving error properly if an Index element is having access of "access-for-notify".
Thanks & Regards, Vivekanandan.V
-----Original Message----- From: libsmi-admin@ibr.cs.tu-bs.de [mailto:libsmi-admin@ibr.cs.tu-bs.de]On Behalf Of Frank Strauss Sent: Friday,April 05,2002 3:08 PM To: vivekav@future.futsoft.com Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] problem in tool when checking the access of Index elements
Hi!
(a)
Vivekanandan> [...] The smilint tool gives an warning that Vivekanandan> "Index element should be not-accessible", [...]
(b)
Vivekanandan> [...] Presently the tool is not giving an error, if Iam Vivekanandan> having an Index object with an access of Vivekanandan> "access-for-notify".
I am confused. Which one is true, (a) or (b)?
(a) should be true, and it is for me.
Or do you just mean the severity of the message should be increased?
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to libsmi-request@ibr.cs.tu-bs.de !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.
*************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************
participants (3)
-
David T. Perkins -
Frank Strauss -
Vivekanandan V