DCC doesn't work when Location document contains malformed MailServer field
The Dynamic Client Configuration (DCC) component does not work when the Location document's MailServer field data is stored in abbreviated format. This field's data must be in canonical format to allow DCC to operate correctly.
You notice that Dynamic Client Configuration (DCC) tasks like updating the client information in person documents and pulling down updated policy information do not work for some clients. Why does this occur?
This has been identified as a product defect under APAR LO65938 (SPR BJGY8PBKA4).
Diagnosing the problem
DCC requires the home server to be stored in canonical format in the MailServer field of the current Location document. Code in the local address book template will always display this value in abbreviated format, so it is necessary to review the document properties of the document to see the actual stored value in the MailServer field.
A valid value will contain the canonical separators. For example, "CN=Server/O=IBM" will work. Invalid values will be stored without the canonical separators. For example, "Server/IBM" will not work. Additionally, IP addresses and DNS host names are not valid values for this field.
Resolving the problem
Editing and re-saving problematic Location documents should re-save the value in canonical format. Additionally, code can be written and provided to users in a button or as part of the PostOpen event of the database script to programmatically store the value in the correct format. If you see this issue occur repeatedly in the environment, the most likely cause is custom or third-party code that manipulates this field and stores the data in the incorrect format.