Referring to my (3) question (shown below in attached email).....

I see the Table2 "_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine  
calls the Table2 "ocStbHostAnalogVideoTable_row_prep()" routine.  I attached 
this code below for reference:


static int
_mfd_ocStbHostAnalogVideoTable_object_lookup(netsnmp_mib_handler *handler,
                                             netsnmp_handler_registration
                                             *reginfo,
                                             netsnmp_agent_request_info
                                             *agtreq_info,
                                             netsnmp_request_info
                                             *requests)
{
    int             rc = SNMP_ERR_NOERROR;
    ocStbHostAnalogVideoTable_rowreq_ctx *rowreq_ctx =
        netsnmp_container_table_row_extract(requests);

    
DEBUGMSGTL(("internal:ocStbHostAnalogVideoTable:_mfd_ocStbHostAnalogVideoTable_object_lookup",
 "called\n"));

    /*
     * get our context from mfd
     * ocStbHostAnalogVideoTable_interface_ctx *if_ctx =
     *             (ocStbHostAnalogVideoTable_interface_ctx 
*)reginfo->my_reg_void;
     */

    if (NULL == rowreq_ctx) {
        rc = SNMP_ERR_NOCREATION;
    }

    if (MFD_SUCCESS != rc)
        netsnmp_request_set_error_all(requests, rc);
    else
        ocStbHostAnalogVideoTable_row_prep(rowreq_ctx);

    return SNMP_VALIDATE_ERR(rc);
}                               /* _mfd_ocStbHostAnalogVideoTable_object_lookup 
*/


I am assuming I should update the Table2 "ocStbHostAnalogVideoTable_row_prep()" 
routine to have an "int" return value and then update the Table2 
"_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine (shown above) to add 
the following "rc=" text to the "ocStbHostAnalogVideoTable_row_prep()" routine 
call (shown below):

        rc = ocStbHostAnalogVideoTable_row_prep(rowreq_ctx);
 
Is this all which is required to process a MFD_SKIP value returned from the 
row_prep routine?



Need Help <[EMAIL PROTECTED]> wrote:
3) You indicate that the "Table2_row_prep()" routine will be called for each 
row in Table1.  This is fine, since I can check whether the  current row 
actually relates to Table2 easily by checking the "type" value defined in 
"Table1".  If the row is not related to Table2, then you indicate I should 
return MFD_SKIP.  Yes, this seems straightforward, however (and you probably 
know I would be asking this), what changes must I make to the table interface 
code of each of the secondary tables in order for them to handle the new 
MFD_SKIP return value?   Actually by "interface code" do you mean the 
"xxxxx_interface.c" files need to be updated, or are you referring to some 
other code file which would need to be updated?



       
---------------------------------
Boardwalk for $500? In 2007? Ha! 
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to