dcmuidi.exe (batch input of user inventories)

This section explains the dcmuidi command, which inputs multiple user inventory items to the managing server from a CSV-formatted file. You can execute this command on the managing server for JP1/Software Distribution Manager. A parameter file is not used with this command.

Organization of this section: (1) Function; (2) Format; (3) Arguments; (4) Return codes; (5) Notes; (6) Example

(1) Function

This command connects to the managing server on the local computer and inputs multiple user inventories created in a CSV-formatted file in a single operation.

To create the user inventories, prepare a CSV-formatted file based on the user inventory information template, using the CSV output utility or dcmcsvu command. The file format is the same as the user inventory information template.

An example of a prepared CSV file is shown as follows:

[Figure]

When you execute the dcmuidi command, the entries in the file are checked against existing user inventories in the managing server, using either the host name, IP address or host ID, according to whichever is used as the ID key for operations. If user inventories already exist on the managing server for a particular host, the new information from that host is entered.

This means that you cannot enter new user inventories for a host that is not already registered in the system configuration of the managing server.

(2) Format

(3) Arguments

/if
In CSV-formatted-input-file, specify the full path of the input file.
/LC
Specify ON or OFF to indicate whether the command's processing is to continue after logging off from Windows when Task Scheduler or JP1/AJS is used to execute commands in the background.
- ON
  Continues command processing even after logging off from Windows.
- OFF
  Forcibly terminates command processing once Windows is logged off.
This argument is effective when the command is executed from a service under any of the following OSs:
- Windows 2000
- Windows XP
- Windows Server 2003 (excluding Windows Server 2003 (IPF))
Do not specify /LC ON when you execute the command from the command prompt, because in this case the command is executed as a foreground program.
You can use a registry setting to specify whether command processing is to continue after Windows is logged off. For details about the registry setting, see 4.6 Registry settings (JP1/Software Distribution Manager) in the manual Setup Guide.
Note that operation may differ depending on the combination of the /LC specification and the registry setting. For details, see 4.28 Command operation at logoff that depends on a registry setting and logoff option.

(4) Return codes

The following explains the return codes that the dcmuidi command may return:

Code	Meaning	Action
0	Normal termination. No matching host exists, or there were no changes to the user inventories.	None.
2	Invalid value in command argument.	Check the value in the command argument.
3	Error during connection or access to managing server.	Check that the managing server and database server are running and that all settings are correct.
4	Open error occurred in the CSV-formatted input file.	Check the file path.
12	Other errors occurred.	Check the event log. Possible causes include a system error, invalid data in the CSV file, or a processing denied error.

If JP1/Base is linked to manage JP1/Software Distribution users, see 1.3.3 Setting for executing commands.

(5) Notes

Note the following points when inputting user inventories from a CSV-formatted file using the dcmuidi command:

Before executing batch input, ensure that no Get system information from client jobs are running. In the case of batch input of user inventory while a Get system information from client job is running, the database may be updated by the information acquired by the Get system information from client job.
When performing the batch input, update the client information too. If you do not update the client information, the information collected from the clients at execution of a Get system information from client job is reflected in the database.
The system does not check the following at input of a CSV-formatted file:
- Whether the value entered for a list item is included in a selection item
- Whether any invalid characters are entered in text-input items that have character restrictions
- Whether values are entered for required items
- Whether the higher and lower selection items are correctly related in hierarchical items
If an invalid value has been entered in the data sent to a client, that item is displayed as a blank field when the client user enters user information. In hierarchical items, if the value entered in a higher item is invalid, the lower items will all be blank fields.
When deleting unnecessary information from a CSV-formatted file, delete the information in row units (client units). If the host name, IP address, or host identifier column (item) is deleted, an error occurs.

(6) Example