Command Reference

DEREGISTER

Deregisters the DB2 server from the network directory server.

Authorization

None

Required Connection

None

Command Syntax

>>-DEREGISTER----+-------------+---+-----+---------------------->
                 '-DB2 SERVER--'   '-IN--'
 
>-----+-NWBINDERY--USER--username--+---------------------+-------------------+>
      |                            '-PASSWORD--password--'                   |
      '-LDAP--NODE--nodename----+------------------------------------------+-'
                                '-USER--username--+---------------------+--'
                                                  '-PASSWORD--password--'
 
>--------------------------------------------------------------><
 

Command Parameters

IN
Specifies the network directory server from which to deregister the DB2 server. Valid values are: NWBINDERY for a NetWare bindery, and LDAP for an LDAP (Lightweight Directory Access Protocol) directory server.

USER username
For NWBINDERY, this is the user ID to log into the network server. The user ID must have SUPERVISOR or Workgroup Manager security equivalence. The user name must be provided when deregistering from the NetWare directory server, and is the user ID to log into the NETWARE server. For LDAP, this is the user's LDAP distinguished name (DN). The LDAP user DN must have sufficient authority to delete the object from the LDAP directory. The user name is optional when deregistering in LDAP. If the user's LDAP DN is not specified, the credentials of the current logon user will be used.

PASSWORD password
Account password.

NODE nodename
The node name is the value that was specified when the DB2 server was registered in LDAP.

Usage Notes

This command can only be issued for a remote machine when in the LDAP environment. When issued for a remote machine, the node name of the remote server must be specified.

The DB2 server is automatically deregistered when the instance is dropped.

See Also

REGISTER

UPDATE LDAP NODE.


[ Top of Page | Previous Page | Next Page ]