Basic log messages related to the operation of a client are output to the USER_CLT.LOG file for each PC. When checking the operation of a client, this file is the first source of information that you should refer to. This file contains brief messages about the start and termination of each process. If processing fails, the cause of the error is also output to this file.

The following operations can have information output to the USER_CLT.LOG file:

• Starting and termination of a product or process
• Log on and off
• Receipt of a job execution request
• Polling
• Receiving and executing a job
• Downloading a package
• Uploading a file
• Automatic registration in the system configuration information
• Addition to and deletion from an ID
• Packaging
• Internal errors and application exceptions

For details about file formats and messages, see 7.2 Lists of basic client log messages.

The log for the entire JP1/Software Distribution Client (client) is produced in the event log for Windows NT and in the MAIN.LOG file.

(a) Checking Windows NT event logs

For Windows NT operating system, event logs that are collected during the use of JP1/Software Distribution Client (client) can be displayed using Event Viewer. You should check the event that is indicated as Software Distribution in the source column of Event Viewer. You can also check events on other hosts on which Windows NT is running by selecting Select Computer in the Log menu of Event Viewer. For details about how to use Event Viewer, see the Windows NT documentation or Help files.

The numbers (event IDs) that are displayed in the event column of Event Viewer correspond to message IDs, and they have the following meanings:

Table 6-15 Event IDs and their meanings (JP1/Software Distribution Client (client))

Event ID	Description
0-999	Windows NT interface
1000-1999	TCP/IP-related
5000-5999	Setup-related
6000-6999	Packaging-related
7000-7999	Installation-related
60000 and above	User output

Double-clicking an event in the Event Viewer window displays detailed information about the event.

Some events produce memory-dump information in the event details. When contacting Hitachi regarding a JP1/Software Distribution Client (client) error, please provide this information along with other pieces of relevant information.

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

(b) Checking the MAIN.LOG file

JP1/Software Distribution Client (client) produces a message log for each PC in the MAIN.LOG file, in the following file format:

Figure 6-8 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-16 MAIN.LOG file message type (JP1/Software Distribution Client (client))

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

Table 6-17 MAIN.LOG file function type (JP1/Software Distribution Client (client))

Function type	Meaning
Package	Packaging (an error within JP1/Software Distribution Client)
Install	Installing (an error within JP1/Software Distribution Client)
Setup	Installing in GUI installation mode (an error within JP1/Software Distribution Client)
TCP/IP	TCP/IP interface
System	Windows NT interface
User	User log (output from the LogFile function of installation script)
Server	Relaying (an error within JP1/Software Distribution Client)

Syntax errors and runtime errors from installation scripts and collect scripts are collected in the SCRIPT.LOG file for each PC. Because the contents of this log are also output to the log (the MAIN.LOG file) for the entire JP1/Software Distribution Client (client), you should check the MAIN.LOG file when checking how the installation script log relates to the JP1/Software Distribution Client (client) log. The SCRIPT.LOG file has the following format:

Script syntax check starting message

Figure 6-9 Format of the SCRIPT.LOG file (script syntax check starting message)

Script execution starting message

Figure 6-10 Format of the SCRIPT.LOG file (script execution starting message)

Script syntax error message

Figure 6-11 Format of the SCRIPT.LOG file (script syntax error message)

When the user outputs a log by using the LogFile function of an installation script, the contents of the log are collected in the USER.LOG file for each PC. Because the contents of this log are also output to the log (the MAIN.LOG file) for the entire JP1/Software Distribution Client (client), you should check the MAIN.LOG file when checking how the installation script log relates to the JP1/Software Distribution Client (client) log. The USER.LOG file has the following format:

Figure 6-12 Format of the USER.LOG file

When client connection destinations are automatically set or changed by an information file for higher connection destinations, log is collected in the USER.LOG file for each PC. The USER.LOG file has the following format:

Figure 6-13 Format of the USER.LOG file

The messages that are displayed and their meanings are summarized as follows:

Message	Meaning
Match smallest-IP-address-largest-IP-address: Change old-connection-destination: old-connection-destination-product-type -> new-connection-destination: new-connection-destination-product-type	The connection destination for the client was successfully changed.
Match smallest-IP-address-largest-IP-address: No Changed existing connection-destination: existing-connection-destination-type	The connection destination that is already specified matches the definition in the information file for higher connection destinations. The connection destination is not changed.
No Match IP Address List, No Changed existing connection-destination: existing-connection-destination-type	The client IP address is not in the definition range of the information file for higher connection destinations. The connection destination is not changed.
Not exist No. item-sequence Value: LineNo line-number	An item-sequence item is not specified in the line-number line of the information file for higher connection destinations. The definition in the line is invalid.
IP Address is not available:"specified-value" :LineNo line-number	An invalid IP address is specified in the line-number line of the information file for higher connection destinations. The definition in the line is invalid.
Higher manager value is over 64 character:"specified-value" :LineNo line-number	A value containing more than 65 characters is specified in the line-number line of the information file for higher connection destinations. The definition in the line is invalid.
Connection type value is not "netmdm" or "netmdmw":"specified-value" :LineNo line-number	A value other than netmdm or netmdmw is specified as a connection destination product type in the line-number line of the information file for higher connection destinations. The definition in the line is invalid.
Match smallest-IP-address-largest-IP-address: Change Multicast IP Address old-multicasting-address -> new-multicasting-address	The client's multicasting address was changed normally.
Match smallest-IP-address-largest-IP-address: No Changed Multicast IP Address multicasting-address	The multicasting address that is already specified matches the definition in the information file for higher connection destinations. The multicasting address is not changed.
Multicast IP Address is not available:"multicasting-address":LineNo line-number	An invalid multicasting address is specified in the line-number line of the information file for higher connection destinations. The definition in the line is still valid, but the multicasting address specification is invalid.
Multicast IP Address is under 224.0.0.0:"specified-value" :LineNo line-number	A multicasting address with a value less than 224.0.0.0 is specified in the line-number line of the information file for higher connection destinations. The definition in the line is still valid, but the multicasting address specification is invalid.
Multicast IP Address is over 239.255.255.255:"specified-value" :LineNo line-number	A multicasting address with a value greater than 239.255.255.255 is specified in the line-number line of the information file for higher connection destinations. The definition in the line is still valid, but the multicasting address specification is invalid.
Use Option "MultiBoard Environment": Not Execution	Set multiple network adapters is selected in the client setup; connection destinations cannot be changed automatically.
Use Option "Auto Change higher manager by instructions to execute job": Not Execution	Automatically set the higher system that sent an execution request as a connection destination is selected in the client setup; connection destinations cannot be changed automatically.