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

NotifyType 220 vs NotifyType 336

Solved1.11K views25th November 2021Fillarray fillarray with collumn mediation protocol protocol.clear protocol.leave
4
Guilherme Gaspar [SLC] [DevOps Advocate]539 25th November 2021 0 Comments

NotifyType.NT_FILL_ARRAY_WITH_COLUMN (220)
vs
NotifyType.NT_FILL_ARRAY_WITH_COLUMN_ONLY_UPDATES (336)

What's the difference between them?

What's the history of 336? Is it related to the incorporation of Protocol.Clear and Protocol.Leave?

Guilherme Gaspar [SLC] [DevOps Advocate] Selected answer as best 25th November 2021

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
6
Laurens Moutton [SLC] [DevOps Enabler]8.78K Posted 25th November 2021 0 Comments

Hi,

To give an overview of the history: More than a decade ago the EPM (CPE) collectors were using NotifyProtocol NT_FILL_ARRAY_WITH_COLUMN (220) to fill in the data that was being polled in the frequency tables. But as the number of US and DS channels increased with the introduction of newer DOCSIS version this meant that the tables also needed to contain more rows and the processes could not handle the data load anymore at that moment in time. For this reason the NT_FILL_ARRAY_WITH_COLUMN_ONLY_UPDATES (336) got introduced as a more performant alternative for the notify 220: only the cells that changed got forwarded in the background and because of that there was an increase in the throughput as it could save out some locking (you still had to fill in the cell value in the notify, but if it was the same then it got filtered out in the background).

Later on, the internal locking in the DataMiner core software got rewritten and it could be improved in such a way that there was no difference anymore between the notify 220 and 336. So now there is no difference between notify 220 and 336, they're both the same.

This is something different with the protocol.Clear and protocol.Leave that got introduced later. With these items you indicate protocol.Clear = set the cell to not initialized, protocol.Leave = I don't know what the cell value is, but the value can stay as is. In the past when using the notify one had to fill in all the values even though they were to remain the same.

Do note that at this moment a protocol.Leave in the background will copy the current cell value and fills it in as if you would have filled it in the notify call, this result is then being forwarded to other processes like SLElement so that process is not aware if a protocol.Leave or a real value was specified. There were plans to ignore the .Leave cell but as far as I'm aware this is not implemented yet. In other words when executing a notify with a row containing protocol.Leave for all the columns will be better performance wise to leave out that row from the notify.

Laurens Moutton [SLC] [DevOps Enabler] Edited answer 25th November 2021
You are viewing 1 out of 2 answers, click here to view all answers.
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

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin