Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Automation Script Lock Elements/Force Lock Elements | Admin/Owner Group and Other Users

Solved888 views19th January 2024automate automation scipt Force Lock elements Lock elements
3
Vikas Choudhary [DevOps Member]556 25th October 2023 3 Comments

Hello Dojo Community,

I was going through DataMiner Automation videos course. Please help me on below scenarios

  1. Is there any way where Admin/Owner can check, how many automation script currently running for DMA or particular element or services by some other users manually or through automation.
  2. is there any screen/way where Admin/Owner can check which element is locked by which process or script, In case script is not able to release lock or due to any dead lock situation, lock didn’t get release automatically. so that admin can release the lock forcefully from that script or can stop script if required.
  3. If Admin/Owner run script with Lock Element option or Force Lock Element options, Other user can’t take force lock on elements if admin already running the script with lock option, even other user selected force lock option but it should not allow?
  4. if particular script finishing task in approx. 1 min and during execution if script locking the elements, any option or way where Admin can configured unlock elements time? for example if script expected to complete in 1 min and admin can put 2 mins unlock for those elements(if lock is not released by that time, even script completed or failed)
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th January 2024
Vikas Choudhary [DevOps Member] commented 26th October 2023

Hello Dojo Community,

Please guide me on my questions

Thanks

Vikas Choudhary [DevOps Member] commented 27th October 2023

Hello Dojo Community,

Please guide me. your help & support are truly appreciated.

Thanks

Vikas Choudhary [DevOps Member] commented 30th October 2023

Hello Dojo Community,

Please help on above scenarios.

Thank you

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
2
Thomas Ghysbrecht [SLC] [DevOps Enabler]4.84K Posted 30th October 2023 3 Comments

Hi Vikas,

  1. You can check what scripts are currently running using the SLNet Client Test Tool. There is a procedure in the DataMiner Docs that shows you how to see these scripts and how to abort one if needed: https://docs.dataminer.services/user-guide/Reference/DataMiner_Tools/SLNetClientTest_tool/SLNetClientTest_tool_advanced_procedures/SLNetClientTest_aborting_running_script.html
  2. There is no built-in overview currently available as far as I know. You can always check who is locking an element by opening it in Cube. At the bottom, a banner should explain who is locking the current element (if any). You can also see this when you go to the ‘General Parameters’ page which you can find on the left sidebar of an element card. The first two general parameters will display whether the element is locked and who is locking it. Since these are parameters on an element (65000 & 65002), you could create an ad-hoc GQI data source that retrieves these parameter values for the elements you are interested in. This data source can then be used in a dashboard or low-code app to have a nice overview.
  3. The last user who executed a script that uses an element, and has selected the ‘Force Lock’ option will be the owner of the lock. Regardless of any other condition. That seems to be the current behavior. I don’t believe it is possible to prevent a normal operator from forcing a lock when executing an automation script.
  4. There is currently no time limit configurable on a lock. You could set a lower timeout time on a script to prevent it from keeping a lock for too long.

In general, an administrator always has the power to force-take a lock. So there is little risk when a script or user is accidentally locking an element for too long.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th January 2024
Vikas Choudhary [DevOps Member] commented 31st October 2023

Dear Thomas,

Thank you very much for the thorough and detailed explanation.

On Point #3:- When the Admin/Owner is running a significant script on any element(s) with lock, other operators cannot use the Force Lock option until the Admin’s script has completed its execution. is it plan in upcoming release?

Thomas Ghysbrecht [SLC] [DevOps Enabler] commented 31st October 2023

Hi Vikas, I just checked with the team and we are currently not planning on changing the current behavior. We understand the use case you mention but expect other use cases that would still require the force lock to be available as an operator. We will however keep this in mind when changes are made to the locking behavior in the future.

Vikas Choudhary [DevOps Member] commented 31st October 2023

Thank you Thomas

Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs