How does EMANATE deal with Gets, GetNexts, and Sets when different rows of a table are in different subagents?

This depends very much on what sort of message it is: • Keep in mind that for each MIB object for which there are multiple subagents, the master agent has a priority-sorted list of subagents which have that object. €¢ When a Get request arrives at the master agent, each subagent which has a matching object database entry is asked (in order of priority), "Do you have this instance?" The value returned by the first subagent that responds affirmatively is returned in the response.

€¢ When a GetNext request arrives at the master agent, all subagents which have that object are asked, "What is the next instance you have after this OID?" When all responses from subagents have arrived, the lexicographically smallest object is returned. €¢ If a Set request arrives at the master agent, it calls the test methods for each subagent which has that object, and the first subagent that returns a non-fatal error status "wins".

Again, they are checked in priority order. More.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.