For initial LDAP server configuration, that’s about all that’s needed. It’s time to start the LDAP server virtual machine. It can be XAUTOLOGged, or you can directly log on to it. It starts up just like the other TCP/IP service virtual machines. When the LDAP process is started, it will issue several messages, some of which appear in Figure 2. Note the values coded in the configuration file and the message indicating the LDAP server is ready to accept requests.
If you use the TCP/IP NETSTAT command, you will see the LDAP server listening on port 389; this indicates the LDAP server is running properly.
LDAP implementations typically provide command line tools to maintain the back-end database(s). LDAP on z/VM is no different. The names are slightly different to fit into the CMS eight-character name standard. The tools are equivalent to those found on other platforms and work similarly.
Here are the commands typically used to maintain the LDAP back-end and their shorter CMS equivalents:
• ldapsearch: LDAPSRCH
• ldapadd: LDAPADD
• ldapmodify: LDAPMDFY
• ldapcompare: LDAPCMPR