Cool Solutions

Quickfinder tips


May 20, 2006 1:39 pm





For the last few weeks (since the Wednesday of Brainshare in fact) I have been working on an issue that has been very quickfinder intensive. Quickfinder, for those that don’t know, is the process that runs in the POA that indexes all the mail and documents so that searches perform more quickly. In fact, a DMS system is handicapped without quickfinder as no searches will complete.

Watching a POA index a post office is a little hypnotic, along the same lines as a bad B movie or, dare I say it, American Idol – you find yourself just sitting and staring at the thing when there are loads better things you can be doing – but these switches make the pain a little more bearable.

/qfnousers – Skips indexing of user databases, so each run will only index the libraries in the post office

/qfnopreproc – Skips the preprocessing, though if you are indexing libraries you probably don’t want to add this switch

/qfnolibs – Skips libraries – very useful if you only want to index the users


0 indexes 1000 items at a time

1 indexes 500 items on a low priority thread, and skips if less than 3 new items

2 indexes 1000 items on a medium priority thread and does all items

3 indexes 2000 items on a high priority thread and does all items

99 indexes 11000 items at a time on a high priority thread – this is the one that I use the most, as it means that the indexing will be done in the least amount of time.

/qfdeleteold – Deletes the old indexes and starts a complete reindex



These last two go hand in hand – you specify the start and end FID that you want to index – this is great if you only want to index a single user. TIDs say that you need to specify the FID in reverse, but that’s not true. My FID is DA0, so if I wanted to index only my database I would specify DA0 on both switches.

When the QF index is running you will see a database name and a number in parentheses, eg USERDAO.DB (14563). This number is the number of items in the database left to index, so on qflevel 2 it would take 15 complete QF runs to complete and, depending on your QF settings this can take over 2 weeks. With qflevel 99, it would be done in 2 runs, or 2 days with the same settings that you may already have. The more times that qf runs per day the quicker this whole process will complete.

What I do when working on qf problems is create a seperate POA instance with it’s own startup file and add the relevent qf switches in it – this means that I can start and stop that POA without impacting users.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:Tony Vissoc

    Do I have to create a POA object for this, or can I just launch a POA with the appropriate switches on the server?

  2. By:Alex Evans

    Well, just back from 2 weeks vacation in Blighty so I am a bit behind on my responses. The best option is to have a new POA object for the 2nd POA and add the /name- in both startup files.

  3. By:Ed

    Who knows where I should be asking this question, but here I go. Sounds funny and there
    is probably not an answer but if one wanted to change how the font of an outgoing email
    was, how would one set it up so it defaults to that style from that point on?

    Thanks in advance,

    Ed (

  4. By:Ron van Herk

    The blog isn’t the place for general questions, but is mainly to comment on issues that where mentioned on the blog. For questions like this it’s probably best to have a look at the support forums

    There are different categories for the different products, either with http or nntp access

  5. Hi Alex,

    I tend to use /qflevel=999 which (as I understand it) reverts to pre GW6.5 behaviour – it indexes each mailbox until done (i.e. nolimit).

    I don’t know what priority “999” runs at (any chance you could ask ?).

    Obviously in 6.5 and above the developers wanted to ensure QF indexing runs were predictable in timeframe (max of 500 items * number of mailboxes)
    but I prefer to have a predictable outcome (fully indexed) at the expense of unpredictable timeframe. 🙂

    Of course – running the QF indexer more than once per day also helps – before start of work, and after daily maintenance upkeep (i.e. after trash is emptied)
    normally fits.

    With GW7 the attachments can also be searched as well, so that may increase the indexing load too – 1 message, 3 attachments = 4 items maybe ?