LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

Arguments Applicable to -t group
The following is a list of valid arguments for -t group:
<group_name>
Required argument. Specifies the POSIX textual style group name
for the new group entry. <group_name> is a required argument.
It must follow all command line options and must precede the
<atr>=<value> parameters if provided. This group name must
conform to HP-UX group name requirements. For more information,
refer to man page group(4) for group name requirements.
-g <gidNumber>
Optional. Specifies the group ID number. If the specified gidNumber
already exists in the directory server, ldapugadd does not add the
new entry and return an error status, unless the -F option is
specified.
If you do not specify this argument, ldapugadd provisions a new
group ID number by randomly selecting a value from the
gidNumber range specified by the ldapugadd -D -g
<min_gid>:<max_gid> command. If ldapugadd randomly
selects a gidNumber that is already in use on the LDAP directory
server, ldapugadd randomly selects another gidNumber and tries
again until it finds an unused gidNumber or exhausts retry attempts.
Retry attempts are limited to 90% of the range of available
gidNumbers (specified with -D -g <min_gid>:<max_gid>).
-x <domain>
Optional. Specifies the group's domain name. Use this option to
specify the ${domain} value that can be used in the template file.
If you do not specify this value, the domain name is created by
using the first dc component of the new group's distinguished
name. If the distinguished name does not contain any dc
components, and the ${domain} variable is specified in the
template file, ldapugadd generates an error.
-M <member>
Optional. Defines initial group membership by adding the specified
user accounts as members. If you specify more than one member,
you must separate each account name by a comma. No white space
is allowed between or within account names. Use of -M requires
that the specified user’s account is already defined in the LDAP
directory server, unless the -F option is specified. When you use
the -F option, the user's group membership is defined using the
memberUid attribute, regardless of the attribute mapping
configuration defined by the LDAP-UX configuration profile. Use
of the -F option is not recommended, and will not succeed if the
directory server does not support the memberUid attribute.
The ldapugadd tool follows the same membership syntax as
defined by the LDAP_UX configuration profile attribute mapping.
Specifically, if the LDAP-UX has mapped the RFC 2307 group
membership attribute, memberUid, to a DN-based membership
attribute such as member or uniqueMember, then ldapugadd
defines membership using the DN of the specified user. If the
memberUid attribute has been mapped to more than one attribute
type, ldapugadd uses the first attribute defined by the mapping.
NOTE: If the ldapugadd tool can only add members that follow
a static membership syntax (such as memberUid, member and
uniqueMember) to a group. The ldapugadd tool will fail if the
only mapping defined by the LDAP-UX configuration profile uses
a dynamic group membership syntax (such as memberURL).
-c <comment> Optional. Specifies a comment that is stored in the description
attribute as defined by RFC 2307. LDAP-UX does not support
192 Command, Tool, Schema Extension Utility, and Migration Script Reference