CA Tuesday Tips: NX_SREL_BLOCKS_TIMEOUT x SDM 12.7

[Sandra_Antunes]

Hey there,

Recently it has been indicated the usage of NX_SREL_BLOCKS_TIMEOUT = 30 to address problems related to locks:

CA Tuesday Tip - How do I get rid of all these locks??

CA found out that SDM 12.7 doesn't use this specific variable. CA is fixing this problem so CA Service Desk recognizes NX_SREL_BLOCKS_TIMEOUT.

In the meantime, for SDM 12.7, this one should be used:

NX_DEBUG_SREL_BLOCKS=30

Note SDM should be recycled so the change works.

Thanks!

Sandra Antunes

[System]

Thanks for the valuable info Sandra!

Sandra_Antunes wrote:

Hey there,

Recently it has been indicated the usage of NX_SREL_BLOCKS_TIMEOUT = 30 to address problems related to locks:

CA Tuesday Tip - How do I get rid of all these locks??

CA found out that SDM 12.7 doesn't use this specific variable. CA is fixing this problem so CA Service Desk recognizes NX_SREL_BLOCKS_TIMEOUT.

In the meantime, for SDM 12.7, this one should be used:

NX_DEBUG_SREL_BLOCKS=30

Note SDM should be recycled so the change works.

Thanks!

Sandra Antunes

[Sandra_Antunes]

Sandra_Antunes:

Hey there, Recently it has been indicated the usage of NX_SREL_BLOCKS_TIMEOUT = 30 to address problems related to locks: [url=https://communities.ca.com/web/ca-service-management-global-user-community/message-board/-/message_boards/view_message/101093097?&#p_19]CA Tuesday Tip - How do I get rid of all these locks??[/url] CA found out that SDM 12.7 doesn't use this specific variable. CA is fixing this problem so CA Service Desk recognizes NX_SREL_BLOCKS_TIMEOUT. In the meantime, for SDM 12.7, this one should be used: NX_DEBUG_SREL_BLOCKS=30 Note SDM should be recycled so the change works. Thanks! Sandra Antunes

After some time, for SDM 12.7 we have a fix available that makes CA SDM use NX_SREL_BLOCKS_TIMEOUT in place of NX_DEBUG_SREL_BLOCKS.
This fix is avaialbe in Cumulative Fix 2 for SDM 12,7, recently released:

(28)    CGI TIME OUT WHILE VIEWING A TICKET
Related Problem Number: USRD 1717
 

Important: SDM 12.9, as for SDM 12.7, natively uses NX_DEBUG_SREL_BLOCKS. To keep compatibility with the variable usage, you should open a case with CA Support and request the fix for it.

Have a great week!

Sandra

 

 

[Kyle_R]

Thanks Sandra,

Great tip.

Some context around when you might use this variable. Customers who have seen "white pages" returned - that is, the header banners of SDM, but a white pane with no information in it - while using SDM may benefit from this variable.

Or as a preventative measure for locks that are not identifiable through System Locks or which do not clear from the bop_cmd "unblock" command.

Not all cases are addressed by this variable, but a good many are. There can also be different causes of lock failure. Please log an issue with CA Support if you experience similar symptoms.

Thanks, Kyle_R.

 

 

 

[Kyle_R]

Here are two key documents on the variable, for reference:

 

Unable to enable NX_SREL_BLOCKS_TIMEOUT on CA Service Desk Manager

 

CGI TIME OUT WHILE VIEWING A TICKET

 

They are both relevant for ITSM 14.1 as well with the variable "NX_SREL_BLOCKS_TIMEOUT = 30".

 

TIP: Make sure you update:

• ALL SDM servers.
• The /NX.env and the /pdmconf/NX.env_nt.tpl

 

Remember, that the form "NX_SREL_BLOCKS_TIMEOUT" is the "default, correct" form and should be used on every version of SDM which is patched up to recent code lines (this includes ITSM 14.1).

 

The only time that you needed to use "NX_DEBUG_SREL_BLOCKS" was on those versions which were not patched to included "NX_SREL_BLOCKS_TIMEOUT". But once your system is patched (see those links above), then you may revert to only using the default form.

 

Thanks, Kyle_R.