Author Topic: Using RECORD RANGE on Trigger  (Read 1186 times)

DDP021

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
Using RECORD RANGE on Trigger
« on: September 12, 2019, 06:05:12 AM »
We ran into an interesting issue...We have mainframe data that has no constant value on every page to base a trigger off of....We decided to use the word Account: but it can fall anywhere between lines 1, 6....So we set up the trigger with a record range ((TYPE=GROUP,RECORDRANGE=(1,6))....That seemed to work...However, the users started reporting that on some pages were "missing"...What we found is, the missing pages have less than 6 lines and were being attached to the next index on the data file.  It appears this is due to the RECORD RANGE parameter.  If the page contains less than 6 lines it throws the indexing off.  When we manually edited the pages that had 5 lines or less and just inserted blank likes so it was more than 5, indexing worked.  We notified the application that they need to edit any page to ensure they all have 6 lines or more.  Just checking to see of anyone knows of anything else that can be done from a CMOD perspective on the Indexer?