Changing IDMIF Files with Resynchronizations
and Pragma Statements

You can add, change, or delete any part of an IDMIF file in any of the following ways:

• Replace the entire MIF file with a new one by using the full resync parameter:

  //FullResync<1>

• Use an agent resynchronization to replace all MIF file parts that were created by a certain agent.

  //ResyncAgent<1>

• Replace the given class within the MIF (if a value of 0 is specified). Or, if the value is 1, replace the values that were created by the agent within the given class.

  //ResyncClass<ClassName><1>

• When you use no history IDMIF files (*.nhm), you can also add, delete, and change groups within the IDMIF file by using pragma statements.

Pragma statements are messages to Inventory Data Loader that can be inserted into SMS IDMIF files. You can use pragma statements to direct Inventory Data Loader to add new groups, change groups, or delete groups within IDMIF files.

Pragma statements are used only with no history MIF files (*.nhm), not with MIF files (*.mif).

You might find the following three pragma statements especially useful when you use no history MIF files within SMS:

• Add pragma
  This statement adds a group to an existing instance of an architecture within the SMS site database. Other instances of the architecture are not affected unless an IDMIF file is submitted for them.

  Pragma = "sms:add"

• Update pragma
  This statement replaces the information currently stored about a group in a certain instance of an architecture with the information in the current IDMIF file. This pragma statement appears as follows:

  Pragma = "sms:update"

  ---

  Note   If you use the Update pragma statement, the group must exist within the instance of the architecture you specify with the SMS site database. Otherwise, the entire architecture is resynchronized.

  ---

• Delete pragma
  This statement deletes the group from this instance of the architecture. Deleting the top-level group causes the entire architecture to be deleted. This pragma statement appears as follows:

  Pragma = "sms:delete"

  ---

  Note   No spaces should be placed between the elements of the pragma statements or the delta header statements.

  ---

The following pragma statement is sometimes found in SMS 2.0 MIFs, but it is not necessary with the SMS site database and is not typically used in SMS:

Pragma = "sms:lookup"

Pragma statements can apply to any group within the MIF file. You insert them in the following location within any group:

Start Group           Name = "Equipment"          ID = 1          Class = "Equipment"          Key = 3,5          <pragma statement inserted here>          Start Attribute

The following table provides strategies for the three most common tasks you will perform when working with custom MIF files.

Table 10.2 Strategies for Common IDMIF File Tasks

You can change or delete groups within an IDMIF file instance by modifying the MIF file as described in the following procedure. After you modify the MIF file, place it in the target directory on the client:

%Windir%\MS\SMS\Idmifs

  To replace a value in an IDMIF file

1. Prepare an IDMIF file that includes the change you want. Use your name or another identifier as the agent ID. You can modify the IDMIF file that originally created the value, or you can create a new IDMIF file that changes whatever values you want modified.
2. In the IDMIF file, add a Resync or a pragma statement. If you want to replace the entire architecture, use the following comment:

//FullResync<1>

To replace an attribute class, use the following comment:

//ResyncClass<ClassName><1>

To replace everything in the architecture for the unique ID that was added by this agent, use the following comment:

//ResyncAgent<1>

Or, you can use a pragma statement for no history MIF files, as described earlier.

3. Place the IDMIF file in the target directory on the client:

   %Windir%\MS\SMS\Idmifs

   For example:

   copy test.mif c:\%Windir%\MS\SMS\Idmifs