Skip to main content link. Accesskey S Skip to tab navigation link. Accesskey 1 Skip to sub navigation. Accesskey 2
  • Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Similar Entries

photo

If you're thinking o...

Blog:  Lotus Nut
Chris Whisonant
Updated 
RatingsRatings 1     CommentsComments 2
photo

How To Speed Up Your...

Blog:  Lotus Nut
Chris Whisonant
Updated 
RatingsRatings 4     No CommentsComments 0
photo

Easy Way To Manage A...

Blog:  Lotus Nut
Chris Whisonant
Updated 
RatingsRatings 1     No CommentsComments 0
photo

ikeyman Not Allowing...

Blog:  Lotus Nut
Chris Whisonant
Updated 
No RatingsRatings 0     CommentsComments 1
photo

Highly recommended f...

Blog:  Domino Diva
Kim Greene
Updated 
No RatingsRatings 0     No CommentsComments 0

+ Bookmarks

+ Archive

+ Links

+ Blog Authors  

Chad Scott

Domino job scheduler does not recognize new or updated program documents

Chad Scott |   | Tags:  administration | Comments (2)  |  Visits (734)
I ran into an issue this morning where new and modified program documents are not recognized by the Domino job scheduler. If I added, deleted, or modified a program document, I saw no change in the output from "show sched" on the console, and the program documents never ran. It turns out that this is behavior introduced by the set of NAMELookup fixes documented in Technote 1254752. The various NAMELookup flags are enabled using the notes.ini parameter DEBUG_ENABLE_UPDATE_FIX, which has the following default/maximum value by release:

  • 6.5.5 FP2 - 7.0.2: 0/8191
  • 7.0.3: 0/16383
  • 8.0 and 8.0.1: 8191/16383
  • 8.0.2: 8191/32767
  • 8.5: 32767/32767

These values enable flags that turn off unnecessary view rebuilds by functional area. For the program document issue, that flag is decimal value two, which means that if you are running any release of 8.x without the notes.ini parameter set or 6.5.5 FP2 or later with the notes.ini parameter set to a value that includes this flag, you will experience this issue. To work around the problem, you can remove the flag, which means subtracting two from the value of DEBUG_ENABLE_UPDATE_FIX in notes.ini. If the parameter is not there, you should set it to the maximum for your release minus two.
 No RatingsRatings 0

Comments (2)

photo
1 Sjaak Ursinus commented   Permalink No RatingsRatings 0

Chad

Thanks for sharing as we had already experienced this problem but couldn't really find a solution to it. Now we have :-D (our solution was to restart the server every time we played with program docs)

I have one question though where did you get the information from the default values and maximum allowable settings for the DEBUG_ENABLE_UPDATE_FIX ini parameter. Tried to find a knowledge base doc. But could only find the one which describes the values towards 8191 and not the ones above. Hope you can let me know that as well.

Thnx

photo
2 Chad Scott commented   Permalink No RatingsRatings 0

This information will be updated for existing Technotes that reference DEBUG_ENABLE_UPDATE_FIX, and a separate Technote documenting the specific problem should be published soon.

Add a Comment Add a Comment

Previous |  Main  | Next
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About