IBM Support

LO40621: CLIENT BUILD NOT UPDATING IN PERSON DOCUMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • In one specific case, the customer ran an agent to clear out the
    client build
    info in all person documents.  We removed the DYNINFOCR_... line
    from the
    notes.ini an changed the Setup= line to "620000" (telling the
    client to
    reupgrade the design of local DBs), and ran DCC, but the client
    build
    information never populates in the person document.
    Furthermore, a request to
    update the client build info is never generated in the admin4
    database, leaving
    us to believe this is a DCC problem.  The customer has reported
    that this
    method works fine for 7.0.x clients.  The customer has 8.0,
    8.0.1, and 8.0.2
    clients in his environment, and it does not work for any of
    them.  The
    "InstalLType" line has existed in all the notes.inis for the
    machines we have
    tested with.
    
    I am able to reproduce this.
    
    STEPS TO REPRODUCE:
    
    1) Clear out the client build info in your person doc, via this
    agent (found in
    TN 1289067 )
    
    field ClientType:="";
    field CIntMachine:="";
    field CIntPltfrm:="";
    field CIntBld:="";
    
    2) Remove the DYNINFOCR line from your notes.ini, and change
    Setup= to "620000"
    3) Launch your client and ensure DCC runs (run it manually)
    
    No matter how many times you launch and run DCC, a request will
    never appear in
    the admin4 DB to update the client build info in the person
    document
    

Local fix

  • None known at this time.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# ALAS7S6SHB.
    The problem was caused by a user error or user
     misunderstanding.
    

APAR Information

  • APAR number

    LO40621

  • Reported component name

    NOTES/DOMINO 7X

  • Reported component ID

    5724E6200

  • Reported release

    802

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-19

  • Closed date

    2011-05-19

  • Last modified date

    2011-05-19

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 May 2011