Problems in creating OU and O

Question

I've 2 scenarios which I don't how to handle:
Suppose I have a department in an organisation that have many smaller sub-department & these sub-departments may have groups within them (so sort like nesting), how do I create such entries?
For the top level department, I could do this:
dn: ou=ACC, o=abc.com.tw
objectClass: top
objectClass: organizationalUnit
ou: ACC
description: Accounts Department
Lets say I want to create a sub-department call payroll within this Accounts department, how should my LDIF be?
For my 2nd situation:
Usually, there'll be only 1 top level organisation like this:
dn: o=abc.com.tw
objectClass: top
objectClass: organization
o: abc.com.tw
Suppose this particular organisation is actually co-owned by two companies, like the Sun-Netscape Alliance. What can I do since now instead of one top level organisation, I've 2 or even more.
Any help or suggestion is greatly appreciated.

Answer 1

1) ou=Payroll,ou=ACC,o=abc.com.tw
I think you may be under the impression that ou, o, etc. are somehow significant, that they can only be used in certain levels of the tree. This is not so in LDAP, and especially iDS. Perhaps you are confused about DIT Structure Rules in X.500.
2) You can create up to 99 suffixes - each suffix would correspond to a top level organization.
You sure ask a lot of questions. Perhaps you should invest in an LDAP book. The one by Howes, Smith, and Good is quite good. After you read that, take a look at the iDS Admin Guide and the iDS Deployment Guide.