For a Windows NT operating system, event logs that are collected during use of JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system) can be displayed using Event Viewer. You should check the following events that are displayed in the source column in Event Viewer:

• Software Distribution
  This event log is collected during use of JP1/Software Distribution Manager or JP1/Software Distribution Client (relay system).
  
• Netmdm Utility
  This log contains execution results from JP1/Software Distribution commands.
  

By selecting Select Computer in the Log menu of Event Viewer, you can also check events on other hosts on which Windows NT is running. For details about how to operate Event Viewer, see either the Windows NT documentation or help files.

Numbers (event IDs) that are displayed in the event column of Event Viewer are associated with message IDs. These numbers have the following meanings:

Table 6-8 Event IDs and their meanings (JP1/Software Distribution Manager and JP1/Software Distribution Client (relay system))

Event ID	Description
0-999	Windows NT interface
1000-1999	TCP/IP-related
7000-7999	Installation-related
8000-8999	Relay-related
10000-19999	Managing server-related
30000-39999	Client alert-related

Double-clicking an event in the Event Viewer window produces the display of detailed explanations on each event. For example, if a system error occurs due to a disk space shortage on the managing server or the relay system, a message indicating a disk space shortage is displayed in the Event Viewer system log. In this case, you should allocate enough disk space by deleting files that are no longer needed, and rerun the job.

For some events, memory dump information may be output in the event details. If you contact Hitachi regarding a JP1/Software Distribution error, please provide this information along with any other pertinent information.

For event log messages that are output by JP1/Software Distribution, see 7.1 Lists of event log messages.

JP1/Software Distribution also collects a log in a MAIN.LOG file, using the following file format:

Figure 6-4 Format of the MAIN.LOG file

The message type and function type that are displayed in the MAIN.LOG file have the following meanings:

Table 6-9 Main.log file message types (JP1/Software Distribution Manager and JP1/Software Distribution Client (relay system))

Message type	Meaning
Informational	Information message
Warning	Warning message
Error	Error message

Table 6-10 Main.log file function types (JP1/Software Distribution Manager and JP1/Software Distribution Client (relay system))

Function type	Meaning
Setup	JP1/Software Distribution Manager and JP1/Software Distribution Client (relay system) setup-related
TCP/IP	TCP/IP interface
System	Windows NT interface
Server	JP1/Software Distribution event

When using a relational database, JP1/Software Distribution collects a log in a file called RDBSRV.LOG. If the remote installation manager is installed in a host separate from the managing server, the RDBSRV.LOG file can be checked from either host.

For message numbers and error levels that are displayed in the log, see the manual for relational database system administrators.

The RDBSRV.LOG file has the following format:

Figure 6-5 Format of the RDBSRV.LOG file

If an error occurs during the use of the inventory viewer, an RDBMS error message is output to an INVODBC.log file. When the size of the INVODBC.log file grows to 400 kilobytes, the file is renamed as INVODBC.logn (where n is either 1 or 2), and a new log file is created. The old log files are saved up to two generations. The date and time when a log was output in the log file can be identified in terms of the date and time that are displayed next to a line number.

When you execute the dcmamtin, dcmamtwc, or dcmamtrc command for AMT Linkage, the DCMAMT.LOG file log is acquired. The DCMAMT.LOG file format is as follows:

Figure 6-6 Format of the DCMAMT.LOG file

The following table lists and explains the message text strings that may be output to the DCMAMT.LOG file when the dcmamtin command is executed.

Table 6-11 Message texts output to the DCMAMT.LOG file when the dcmamtin command is executed

Type	Message	Meaning
Informational	dcmamtin START	Command execution has started.
Informational	file=xxx	System configuration file specified in the /f argument
Informational	host=xxx	Host name specified in the /H argument
Informational	ipaddress=xxx	IP address specified in the /I argument
Informational	dcmamtin RETURN=xx END	The command terminated with return code xx.
Error	The input file can't be opened.	The input file cannot be opened. Check the input file specified in the argument.
Error	The input file format is invalid.	The input file is invalid. Check the description format of the input file.
Error	Arguments are invalid.	Check the command's arguments.
Error	The output file can't be opened.	The output file cannot be opened. Check the output file specified in the argument.
Error	System error occurred.	A system error occurred. Check the command execution environment.
Error	Access error occurred. Host=xxx	Connection error occurred. The specified host may not support AMT or may not exist on the network. Also, Enterprise may be specified for the Provision model of AMT.
Error	Authentication error occurred. Host=xxx	An authentication error occurred. Check the AMT management user name and password of the specified host.

The following table lists and explains the message text strings that may be output to the DCMAMT.LOG file when the dcmamtwc command is executed.

Table 6-12 Message texts output to the DCMAMT.LOG file when the dcmamtwc command is executed

Type	Message	Meaning
Informational	dcmatmwc START	Command execution has started.
Informational	file=xxx	Name of the file specified in the /f argument that is output from the CSV output utility.
Informational	profilename=xxx	Name of the wireless profile specified in the /n argument.
Informational	The profile is deleted.	Indicates that the /r argument was specified.
Informational	mode=xxx	Indicates that the /w argument was specified.
Informational	priority=xxx	Priority of the wireless profile specified in the /p argument.
Informational	SSID=xxx	SSID specified in the /i argument.
Informational	Communication Method=xxx	Communication method specified in the /s argument.
Informational	Encryption Method=xxx	Encryption method specified in the /e argument.
Informational	Key=xxx	Key specified in the /k argument.
Informational	dcmamtwc RETURN=xx END	The command terminated with return code xx.
Error	The input file can't be opened.	The input file cannot be opened. Check the input file specified in the argument.
Error	The input file format is invalid.	The input file is invalid. Check the description format of the input file.
Error	Arguments are invalid.	Check the command's arguments.
Error	System error occurred.	A system error occurred. Check the command execution environment.
Error	Access error occurred. Host=xxx	A connection error occurred. The specified host may not support AMT or may not exist on the network. Also, Enterprise may be specified as the Provision model of AMT.
Error	Authentication error occurred. Host=xxx	An authentication error occurred. Check the AMT management user name and password for the specified host.

The following table lists and explains the message text strings that may be output to the DCMAMT.LOG file when the dcmamtrc command is executed.

Table 6-13 Message texts output to the DCMAMT.LOG file when the dcmamtrc command is executed

Type	Message	Meaning
Informational	dcmamtc START	Command execution has started.
Informational	host=xxx	Host name specified in the /h argument.
Informational	ipaddress=xxx	IP address specified in the /i argument.
Informational	BIOS configuration started.	Client BIOS configuration has started.
Informational	IDER session is opened.	Client diagnostic program has started.
Informational	dcmamtrc RETURN=xx END	The command terminated with return code xx.
Error	Socket error occurred.	A socket error occurred. Check if the SOL driver is installed on the client.
Error	Failed to open IDER session.	The IDE redirection connection failed. Check if the file is on the floppy disk.
Error	The SOL session has already been opened.	A new SOL connection cannot be established, because one has already been established.
Error	The IDER session has already been opened	A new IDE redirection connection cannot be established, because one has already been established.
Error	Client PC is up	The client is running. Turn off the power to the client.
Error	Arguments are invalid.	Check the command's arguments.
Error	System error occurred.	A system error occurred. Check the command execution environment.
Error	Access error occurred. Host=xxx	A connection error occurred. The specified host may not support AMT or may not exist on the network. Also, Enterprise may be specified for the Provision model of AMT.
Error	Authentication error occurred. Host=xxx	An authentication error occurred. Check the AMT management user name and password of the specified host.

When you store operation information (suppress history and operation history) acquired by JP1/Software Distribution in the database, logs are output to the MONRST.LOG file. The MONRST.LOG file format is as follows.

Figure 6-7 Format of the MONRST.LOG file

The following table lists and explains the message text strings that may be output to the MONRST.LOG file when operation information acquired by JP1/Software Distribution is stored in the database.

Table 6-14 Message texts output to the MONRST.LOG file when operation information is stored in the database

Type	Message	Meaning
Information	START:Store data at a specified time	Time-specified database storage processing has started.
Information	END:Store data at a specified time	Time-specified database storage processing has ended.
Information	START:Store data at a fixed interval	Interval-specified database storage processing has started.
Information	END:Store data at a fixed interval	Interval-specified database storage processing has ended.
Information	START:dcmmonrst xx	Command execution with argument xx specified has started.
Information	END:dcmmonrst xx	Command execution with argument xx specified has ended.
Information	Time=xx:xx#1	Start time for time-specified database storage processing.
Information	Interval=xx#1	Interval at which operation information is to be stored in the database. The unit is days for time-specified storage processing and hours for interval-specified storage processing.
Information	Preservation=xx#1	Retention days for the operation information stored in the database
Information	Start=YYYYMMDD#1	Date specified in the /s argument
Information	End=YYYYMMDD#1	Date specified in the /e argument
Information	Clear=YYYYMMDD#1	Date specified in the /c argument
Information	Directory=xxxx#1	Operation history backup directory name specified in the /d argument
Information	Host=xxxx#1	Host name specified in the /H argument
Information	IPAddress=xxx.xxx.xxx.xxx#1	IP address specified in the /I argument
Information	Operation history from xxxx	Storing of operation history from the xxxx operation history storage directory has started.
Information	Suppress history from RDB	Storing of suppress history has started.
Information	xxxx/yyyy#2	Number (xxxx) of directories and hosts whose storage processing has been completed out of the total number (yyyy) of directories and hosts subject to storage processing
Information	Directory=xxxx#2	Name of directory whose storage processing has been completed
Information	Host=xxxx#2	Name of host whose storage processing has been completed
Information	Inserted=xxxx#2	Number of new operation logs stored
Information	Total=xxxx	Number of operation logs contained in the Microsoft SQL Server or Oracle database after storage processing was performed
Information or Warning	Total=xxxx/yyyy	Total estimated number (yyyy) of operation information items that can be stored, based on the number (xxxx) of operation information items stored in the Embedded RDB after storage processing was performed and the size of the database file. If xxxx is 80% or more of yyyy, Warning is displayed. In such a case, upgrade the database and extend the capacity of the software operation monitoring log file. The database capacity must be extended by at least 10% of the existing size. In order to avoid a database access error, do not re-organize the database.
Error	STOP:Error occurred	An error occurred during storage processing. Check the command's return code and event log.

#1

Any combination of these items is output as a single message.

#2

Any combination of these items is output as a single message.