if a log in was not required no the process continues via connector b to fig2 a to repeat these steps for other partitions or service processors if a log in is required yes then the program will log out of the currently scanned partition service processor by using the windows api call wnetcancelconnection2 which is initiated at step 214 which is continued via connector b to fig2 a referring now to fig3 which begins with start bubble 301 actions are performed for each partition service processor process 302 an inquiry is then made diamond 303 to determine if this partition is a voyager or clearpath partition this is done by looking at the operating system type ostype in the partitioninformation record for that partition a value of u201c 4 u201d indicates voyager and a value of u201c 7 u201d indicates clearpath these values are internal representations in the database based on how the partition was defined to the system programmatically the constants cosvoyager and cosclearpath are used to check for these values if the partition type is something other than voyager or clearpath no the process continues to step 306 to check if there is another partition service processor if the partition is of type voyager or clearpath yes in inquiry 303 the process continues to step 304 where a process to store the partitionnumber the computername the systemnumber and the lastsample from the partitioninformation record into a new class object clsvoyager this class object then gets added to a collection of partitions colpartitions this partition collection is represented by step 185 in fig1 an inquiry is then made at step 306 to check if there are more partitions to step through if there are.