IBM Support

What is the nodelock file?

Question & Answer


Question

What is the role of nodelock file found under DB2 installation path license subdirectory?.

Cause


This is a temporary file created when adding or changing a DB2 UDB product license using the db2licm command. This file is only used when db2licm is running when registering the DB2 product license key.

The nodelock file could be found in the following locations:
Windows XP and Windows 2003
        X:\Documents and Settings\All Users\ApplicationData\IBM\DB2\<DB2 copy name>\license.
Windows Vista, Windows 7, Windows 2008 or later
        X:\ProgramData\IBM\DB2\<DB2 copy name>\license
Where 'X:' is the system drive.
On all other platforms the nodelock file is located in the installation path of this product in the license directory.

Linux/UNIX:
<installation path>/license/nodelock
Example: /opt/ibm/db2/V9.7/license/nodelock

Re-apply the DB2 connect license using db2licm -a <license file name>
Note: This step generates new nodelock file

Verify that the license is permanent using db2licm -l

Then try the connection to DB2 zos, you should now be able to connect to DB2 z/OS database successfully

Verify if the DB2 Connect license is permanent using db2licm -l command.
For example: C:\Program Files\IBM\SQLLIB\BIN>db2licm -l
Product name: "DB2 Connect Unlimited Edition for zSeries"
License type: "Client Device"
Expiry date: "Permanent"
Product identifier: "db2consv"
Version information: "9.7"

Here is an example on how to resolve a connectivity problem:

Remove the license
For example: db2licm -r <product identifier>
Product identifier:
db2consv (DB2 Connect Enterprise Edition)
db2conpe (DB2 Connect Personal Edition - applicable for DB2 V9.5, 9.7,and 10.1)

Re-apply the DB2 Connect license using db2licm utility
db2licm -a <license file name>

Then see if you are able to connect to the DB2 z/OS database.

If you still experience SQL1598N during DB2 z/OS connectivity, please use the above steps to resolve the error, sometimes the nodelock file may be corrupt, the license will not be found even though db2licm -l shows permanent, so you can rename the nodelock file to nodelock.bak  and recreate using db2licm -a.

Answer


If the DB2 UDB license update is processed successfully using db2licm -a command, the temporary file nodelock will be created.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"OTHER - Uncategorised","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1;10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 November 2020

UID

swg21416347

Page Feedback