This function will unregister the Acl entry dynamically, This will delete the row registered in the Acl table by specifying the Acl community as argument to identify which row has to be deleted in the Acl table. Also, the host name and port number arguments has to be specified to identify in which port and port the master agent is running.

This function will unregister the manager entry dynamically, This will delete the row registered in the manager table by specifying the, host name and port as arguments to identify which row has to be deleted in the manager table. Also, the host name and port number arguments has to be specified to identify in which port and port the sub-agent is running.

This function is used to unregister a listener in the Agent Server. After successful deregistration, it will send UNREGISTRATION notification to its listeners and it can't be managed from the remote.

This function will unregister the subagent dynamically, This will delete the row registered in the proxy table by specifying the oid, context name and entry instance as arguments to identify which row has to be deleted in the proxy table. Also, the host name and port number arguments has to be specified to identify in which port and port the master agent is running.

This function will unregister the trap receiver entry dynamically, This will delete the row registered in the trap receiver table by specifying the agent host name and trap port as arguments to identify which row has to be deleted in the trap receiver table. Also, the host name and port number arguments has to be specified to identify in which port and port the master agent is running.

It will call UnsynchronizeResource() mehtod for all pointer which are in the Vector.

Unlocks channel for use again.

unlocks a session locked due to intrusion.

Compares each Entry's oid of the given Vector with varName. If both are matches then set FALSE for the rollBackFlag of the corresponding Entry.

It will search the given resource in the gv_rsrcLockTable, if it is there then it verify the given source with locked source, both are same then it will unlock the given rsrc.

It will remove the sync/lock of the given resource, so that the other user/thread can use the give resource which is locked in the SynchronizeResource() method. Before unlocking the resource it will verify whether both the given source and locked source are same just to make sure the same source is unlocking the resource.

It will updates entries for all api tables like authTable, proxyTable, trap forwarding & receiving, USM and VACM tables.

Update the changes of UpdateAgentAuthTableFile.

It will update the agent transport domain info. Since it is using UDP/IP or TCP/IP, it will update the socket descriptors variable like maxSockFd, fd_set, etc.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to Cli. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to CliCommIfcTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to CliTcpTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

It will update the client information. Based on the state of the client it may close the connection. The third argument is not required if MULTI_THREAD is defined.

Updates a row in a given table.

Updates a row in a given table.

Updates a row in a given table.

Increments both the gv_engineTime and gv_engintBootCnt depending upon the current system time.

In case of tcp new handle value for connection with subagent will be updated in the transport domain's handle of correspoding proxy entry. By doing this same connection will be used for the next request. Here domain will be identified by remote port and remote host of ipInfo

It will update the changes of ManagerTableFile.

It will find out the max sockFd of the given transport domain info.

Updates/Adds client information. While updating, it checks whether the time interval between any two continous requests by the client is greater than the gv_IntervalSec. If so, it resets the number of Requests to 0, otherwise increments the number of request by 1.

It will update the max socket descriptor value by searching in the proxy vector.

Update the changes of ProxyTable.

Validate the input for RowStatus.

Used to update the v3 security and access control related parameters based on the security model and access control model implemented. It will be called each time from the base loop.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to Selfmonitor. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to SessionTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from TL1 Security upon receiving the ED-CID-SECU command.Here,Keep Alive Timeout value will be updated for the server session whose transport provider matches the Channel ID whose timeout value was editted through the ED-CID-SECU command at run-time.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to SnmpNotificationLogTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to SnmpNotificationVarBindTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

Updates the changes of SnmpSet. If AGENT_FILE_TO_VECTOR is enabled then the corresponding textfile will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.

It will update the gv_snmpSysORLastChange value. So user has to call this method whererver he/she updating the SysOrOid value.

Updates the changes of System. If AGENT_FILE_TO_VECTOR is enabled then the corresponding textfile will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.

Update the changes of SnmpUsmUserTable.

Update the changes of SnmpVacmAccessTable.

Update the changes of SnmpVacmContextTable.

Update the changes of SnmpVacmSecurityToGroupTable.

Update the changes of SnmpVacmViewTreeFamilyTable.

If AGENT_FILE_TO_VECTOR is defined , it will write gateway NE entries into text file.Otherwise has to provide code to update records to external storage device.

If AGENT_FILE_TO_VECTOR is defined , it will write log records into text file.Otherwise has to provide code to update records to external device.

If AGENT_FILE_TO_VECTOR is defined , it will write security log records into text file.Otherwise has to provide code to update records to external device.

If AGENT_FILE_TO_VECTOR is defined , it will write security records into text file.Otherwise has to provide code to update records to external device.

It will update the give column Attribute value after resolving the table Entry. It is used for atomic set in mutli protocol agent.

It will update the thread resource, used to unblock or lock/unlock the mutex.

It will remove the given nodePtr from the table, before that it will take the timer notification from the nodePtr and update with its period value then add it to the timer service table.

Update the changes of Tl1CommIfcTable.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to Tl1CommandSecurityTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to Tl1OperationSecurityTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

Update the changes of Tl1TcpTable.

Update the changes of TrapReceiverTable.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwDocAccessTopNTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwDocBucketTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwDocBytesTopNTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwDocCtrlTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwDocLastNTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwRequestInTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwRequestOutTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwResponseInTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwResponseOutTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwServiceTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

This method will be called from the agent api after successful SET/GET/GET-NEXT operation, in order to update the original or user application's data structrue with the changes made to WwwSummaryTable. If FILE_TO_VECTOR is enabled then the corresponding text file will be updated here. If the storagetype is NoStorage then the user should call this method to update the changes done by the management.The user can also free the resources in this function if required.

Displays the help information of the WebNMS agent.

It will process the GET & GET-NEXT requests and send back the appropriate result.

It will process the SET requests and send back the modified result.

It will process the GET & GET-NEXT requests and send back the appropriate result.

It will process the SET requests and send back the modified result.