Note: This PI was mistakenly assigned to PI 109702, apparently without knowledge that it had an existing PI. Therefore, PI 539359 was inactivated 02/2008. Note that this accession record is incomplete. For more information on this accesssion, please see the record for PI 109702. (RRK, 02/2008)