Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Ask Professor INI - Introducing Professor INI

Professor INI, Professor, IBM Lotus
Professor INI has been writing about Notes.ini variables since Notes/Domino 5. When he's not writing, Professor INI enjoys reading product documentation and perusing the Lotus knowledge base for tech notes.

Summary:  This column introduces Professor INI, who will put the NOTES.INI file and the variables it controls under the microscope, discussing documented -- and undocumented -- variables and when to use the INI settings . . . and when not to.

Date:  01 Nov 2000
Level:  Introductory

Activity:  3929 views
Comments:  

NOTES.INI-The very name conjures up images of long-ago days when system administrators knew their OS commands like a second language, and GUIs were for wimps. Nowadays, many things we used to do through NOTES.INI can be done more safely and easily within Domino and Notes. Even so, there are still a number of uses for NOTES.INI. These include:

  • Performance tuning
  • Accessing system and application parameters
  • Sharing information with agents and other code (for example API programs)

As you may have already discovered, finding complete information for all NOTES.INI variables is not always easy. The Domino and Notes documentation covers most of the more commonly used variables. Additional details can be found in Lotus Support's Lotus Notes Knowledge Base and technical articles published in Iris Today and elsewhere. But experienced users still come across new, undocumented variables now and then. And the existing literature on NOTES.INI may not provide all possible uses for all variables.

This column, "Ask Professor INI," will help bridge this gap in NOTES.INI information. We'll introduce new variables and examine in detail how to make better use of old ones. Each month we'll take a close look at one or two particularly useful variables and discuss ways they might help you. We'll also answer some of the questions that you and other readers submit regarding NOTES.INI variables. Our goal is to make you better informed about how and when to use NOTES.INI-and equally important, when not to use it.

To begin, let's look at a few common, basic questions concerning NOTES.INI in general.

Q. Everyone probably knows this already, but just so we all start on the same page-what exactly is NOTES.INI?

NOTES.INI is the initialization file (hence the ".INI") used by the program to set up a Domino server or Notes client. Each server and client has a NOTES.INI file. This includes partitioned servers running on the same machine; each has its own NOTES.INI. The file contains all the environment and preference settings for the client and server. These are stored within variables, of which several hundred exist. A number of variables are commonly used and are included in virtually all NOTES.INI files. Others are used less frequently and may not appear unless manually added. Some variables apply only to the server, others to the client, and some to both.

Q. I've heard you should never touch your NOTES.INI file. Is this true?

Frankly, that's not bad advice for many users, especially if you're relatively new. Even if you're experienced, you should modify NOTES.INI only when necessary (and ideally, while under the guidance of Lotus Support or a similarly qualified Notes/Domino professional). And you shouldn't edit NOTES.INI if there's another way to accomplish what you're trying to do-for example, by setting a preference within Notes. However, if you're an experienced Domino administrator or Notes user who works only with supported, documented variables and carefully observes all necessary precautions (see below), you can modify NOTES.INI without disrupting the operation of Domino or Notes.

Q. Why should I ever need to modify NOTES.INI? Can't I do everything I need through the Domino/Notes interface itself?

For the most part, this is true. However, there are a number of variables for which no corresponding UI exists. One example is ClockType, which sets 12 or 24-hour time on UNIX servers. Many of these represent newly introduced functionality, for instance PercentAvailSysResources for limiting the maximum percentage of system memory used by Domino.

Q. If I do decide to edit NOTES.INI, what's the safest way to do it?

For servers, the safest way to modify this file is through the NOTES.INI Settings tab in the Server Configuration document in the Domino Directory. This lets you add or change variables in the server's NOTES.INI file without having to open and edit the file itself-which could be dangerous if some or all of the file is accidentally changed or deleted. If you do choose to edit the file directly, be sure to create a backup copy you can restore if something goes wrong.

Q. What are some typical uses of NOTES.INI?

We asked Business Partners how they use NOTES.INI. A few said they don't, and emphasized our point above that NOTES.INI should only be modified when there's a very good reason. Others listed numerous uses for NOTES.INI, including:

  • Performance tuning. This is probably the most popular use of NOTES.INI. It certainly has the most documentation devoted to it. Many Domino administrators suspect there's some undiscovered NOTES.INI variable out there that would make their lives so much easier if they only knew about it. Others consider NOTES.INI a somewhat overrated tool for enhancing performance. Reality probably lies somewhere in between. Certainly no amount of NOTES.INI tweaking can compensate for an insufficiently configured, under-powered computer. But many administrators find variables such as NSF_Buffer_Pool_Size and Server_Session_Timeout useful tools for fine-tuning server performance. Other widely used performance variables include the AMgr series designed to control Agent Manager.
  • Configuring which server tasks to start up automatically. NOTES.INI offers two variables to do this: ServerTasks (for starting tasks at server startup) and ServerTasksAt (for starting tasks at a specified time). Both can help automate Domino administration, which is especially useful when a single administrator is responsible for multiple servers.
  • Storing information to share with agents and other code. Although there are often alternate ways of doing this, NOTES.INI is still used frequently for storing information to be shared by external agents and API programs, and sometimes across multiple databases. NOTES.INI can also store information that instructs an API program how to run-for example, which configuration database to read, what import/export libraries to use, and so on.
  • Accessing system and application parameters. NOTES.INI can be mined for system parameters such as mail file path and server identification/location. It can also provide application parameters such as time last accessed and duration of activity in a database.
  • Add-in menus. The variable AddInMenus instructs the Install program which add-in menus to read into Notes. For at least one Business Partner, this line is "essential."
  • Global information sharing. In earlier releases, NOTES.INI was often used to enforce a standard set of user preferences across an organization. Many administrators now find Profile documents a more convenient way to do this. But some still prefer NOTES.INI, finding it a more "global" tool for this task.
  • Controlling servlet actions. This is useful if there are simple access limits on each server. In some instances, using NOTES.INI to control servlets is faster and more reliable than using a configuration database.
  • Client vs. user based variables. Often, a single PC may be used by two or more users. NOTES.INI can help keep track of "machine" information as opposed to "user" information-for example, to determine whether an LSX is installed and updated, or whether some other component is configured.

Q. When I look at my NOTES.INI file, I see lots of variables that aren't described in the documentation. Why don't you document them?

There are a number of reasons a variable might not be described in the documentation, including:

  • It's unsupported. Some variables are intended for short-term internal use only. These variables may be added to or removed from the product without notice and are not intended for customer use. A number of DEBUG variables fall into this category. We strongly recommend you never work with undocumented variables unless instructed to do so by Lotus Support.
  • Customers should not modify it. Many variables are dynamic, used for on-the-fly storage of information. Examples include any variable preceded by a dollar sign ($). These variables should never be changed because doing so could disrupt or even crash Notes.
  • The information is unavailable. Even after weeding out unsupported and uneditable ones, there are still some perfectly good variables that should be documented but aren't. This can occur whenever a variable is added late in the product release cycle, after the documentation is complete. Obviously we try to minimize the number of such situations and correct them as quickly as possible, but we probably still have some useful variables missing from the documentation. "Ask Professor INI" will devote special attention to these variables, identifying and describing them as soon as we get the necessary information.

Q. What's the best source for NOTES.INI information?

For Business Partners, the most complete NOTES.INI information can be found in the Admin Best Practices (ABP) discussion database on server LPDP. Here is posted the latest NOTES.INI documentation, along with contributions added by Business Partners. The ABP includes numerous variables that don't appear in the product documentation, with considerably more information on their use.

For customers who don't have access to LPDP, the Domino Administration Help for R5 releases, which are viewable on-line, are the most complete references for NOTES.INI. These include a listing of supported variables, with sections describing how to edit NOTES.INI for performance tuning. In addition, Lotus Support's Lotus Notes Knowledge Base contains numerous Technotes on NOTES.INI variables and how to use them.

Q. Where does "Ask Professor INI" fit in?

This column's primary goal is to supplement the above sources of NOTES.INI information. Our monthly format lets us present the most up-to-date material possible. This will be especially convenient for introducing new variables added to the latest QMRs. We'll feature one or two variables each month, pulling together all available documentation on them into one convenient article. And we'll talk about new ways to use existing variables, presenting information beyond what has already been published. This will include real-world examples of how some variables are used and by whom.

Perhaps most importantly, we'll try to answer any questions you have about NOTES.INI in general or any variable in particular. For this column to be successful, we will rely heavily on your questions. These will allow us to collect and present NOTES.INI information of practical use to you and others within the Notes/Domino community, so all can better understand and use this valuable and important tool.


Resources

About the author

Professor INI has been writing about Notes.ini variables since Notes/Domino 5. When he's not writing, Professor INI enjoys reading product documentation and perusing the Lotus knowledge base for tech notes.

Report abuse help

Report abuse

Thank you. This entry has been flagged for moderator attention.


Report abuse help

Report abuse

Report abuse submission failed. Please try again later.


developerWorks: Sign in


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


Rate this article

Comments

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Lotus
ArticleID=12759
ArticleTitle=Ask Professor INI - Introducing Professor INI
publish-date=11012000
author1-email=
author1-email-cc=

Tags

Help
Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

For articles in technology zones (such as Java technology, Linux, Open source, XML), Popular tags shows the top tags for all technology zones. For articles in product zones (such as Info Mgmt, Rational, WebSphere), Popular tags shows the top tags for just that product zone.

For articles in technology zones (such as Java technology, Linux, Open source, XML), My tags shows your tags for all technology zones. For articles in product zones (such as Info Mgmt, Rational, WebSphere), My tags shows your tags for just that product zone.

Use the search field to find all types of content in My developerWorks with that tag. Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere). My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

Try IBM PureSystems. No charge.

Special offers