Top
Systemwalker Operation Manager  Message Guide
FUJITSU Software

3.8.2 Text Messages That Are Output during Import Processing

This section explains the messages that are output to the following text file when information is imported.

Systemwalker Operation Manager client installation directory\MPWALKER.JM\mpjmc1\work\jmimpexp\impinfo.txt

The Cancel button was clicked, so processing terminated after xx items were completed out of yy items.

[Description]

Import processing was interrupted after xx out of yy items because the Cancel button was clicked while the import information file was being generated.

[Parameter]

xx: Number of items processed

yy: Total number of items

[User Response]

No action required.

The file could not be imported because the file name is more than 256 bytes.

[Description]

The file could not be imported because the name of the CSV file was longer than 256 bytes long.

[User Response]

Make sure the name of each CSV file is no more than 256 bytes.

The CSV file could not be imported because the read process failed.

[Description]

The CSV file could not be read.

[User Response]

Check whether the specified CSV file exists.

The specified CSV file could not be imported because of invalid contents for Systemwalker Operation Manager.

[Description]

The specified CSV file could not be imported because it was not the right kind of file. This message is output when the CSV file contains neither job net information nor group information.

[User Response]

Specify either a job net definition CSV file or a group definition CSV file.

An internal file could not be generated during import processing.

[Description]

An internal file could not be generated during the import processing. This message is output when a batch file that is used for server operations fails to be generated on the client.

[User Response]

Check whether the following directory has write attributes.

<Systemwalker Operation Manager client installation directory>\MPWALKER.JM\mpjmcl\work\jmimpexp

Sending the CSV files to the server during import processing failed.

[Description]

Sending a CSV file to the server failed during import processing. This message is output when a file that is used for server operations cannot be sent from the client to the server.

[User Response]

Check the network environment to see if the client can connect to the Systemwalker Operation Manager server.

Registration of the CSV files during import processing failed.

[Description]

Registering a CSV file failed during import processing. This message is output when a batch file for server operations fails to execute from the client.

[User Response]

Execute the import again.

Could not get import information because reading of the execution result file failed.

[Description]

Reading the execution result file failed, and so import information could not be obtained. This message is output when the information that needs to be written to the import information file cannot be obtained because the execution result file cannot be read on the server.

[User Response]

Check the network environment to see if the client can connect to the Systemwalker Operation Manager server.

Command xxx terminated normally.

[Description]

The command that registers CSV files on the server has terminated normally.

[Parameter]

xxx: Command name

[User Response]

No action required.

Command xxx terminated abnormally during import processing.

[Description]

The command that registers CSV files on the server has terminated abnormally.

[Parameter]

xxx: Command name

[User Response]

Check the other messages that are output at the same time as this message.

The import process terminated abnormally. (0xXXXXXXXX)

[Parameter]

0xXXXXXXXX: Detailed error code

When the detailed error code is less than 0x40000000:

[Description]

The group or job net information in the CSV file is incorrect.

[User Response]

Check that the specified CSV file can be converted correctly using the jobschcsvtodef command.

When the detailed error code is 0x40000000 or more:

[Description]

Processing was interrupted because an error occurred during communication or because the script execution environment on the server is incorrect.

[User Response]

Check that the communication environment is correct and that the connected Systemwalker Operation Manager server is operating normally.

In the case of a UNIX server, also check that the shell environment is operating normally.