NX_MINOR_VER value after RU 19 update
search cancel

NX_MINOR_VER value after RU 19 update


Article ID: 275610


Updated On:


CA Service Management - Service Desk Manager CA Service Desk Manager


After the version update from 17.3.12 to 17.3.19 the value of the variable @NX_MINOR_VER was modified from 3 to 2.  How can this be addressed and are there any lasting consequences to this change?


Release : 17.3 RU17 - RU19
Component:  CA Service Desk Manager


There is a known issue with some of the older 17.3 RU updates, between RU 17 to RU19, where the NX_MINOR_VER value is changed to "2" when it should be a "3".  The issue does not present in the earlier RU updates or the more recent RU releases, from RU22 onwards.

The nature of the issue is relatively benign as it merely is a representation of the version number in place and does not affect overall product operation.


Run the following commands in options manager to correct the given variable "NX_MINOR_VER" in NX.env

pdm_options_mgr -c -s MINOR_VER -v 3 -a pdm_option.inst

To avoid losing the change when you run pdm_configure, run the same command with -t option as follows:

pdm_options_mgr -c -s MINOR_VER -v 3 -a pdm_option.inst -t

The above will set the NX_MINOR_VER setting in NX.env correctly.  The lack of "NX" prefix on the above variable is intentional.  This is also the correct method to modify the NX.env rather than perform a direct change to the file.

In the install.properties, modify the file with a text editor and change:


to read as:


You will need to recycle SDM Services for the above changes to take effect.


Additional Information

As in any such changes, please test in a non-prod instance before making the changes in prod, and perform backups of the original files.