Top
Systemwalker Operation Manager  Message Guide
FUJITSU Software

3.15 Messages of Systemwalker Script Standard Output

This section explains the messages of Systemwalker script standard output.

swotclsh: 129 Bad parameter.

[Description]

An incorrect parameter has been specified at the startup.

[System Action]

Does not execute the script.

[User Response]

Specify a correct startup parameter and restart the script.

swotclsh: 130  Insufficient memory.

[Description]

There is not enough memory to execute the command.

[System Action]

Does not execute the script.

[User Response]

Contact your system administrator.

[System Administrator Response]

Close unnecessary applications.

swotclsh: 131 Failed to get installation path.

[Description]

Could not execute the command because acquisition of the Systemwalker installation path failed.

[System Action]

Does not execute the script.

[User Response]

Contact your system administrator.

[System Administrator Response]

Reinstall Systemwalker since it may not have been installed correctly.

swotclsh: 132 Failed to start process. (process=%1)

[Description]

Failed to start the execution file (%1).

[Parameter]

%1: The name of the failed process

[System Action]

Does not execute the script.

[User Response]

Contact your system administrator.

[System Administrator Response]

Reinstall Systemwalker since it may not have been installed correctly.

swotclsh: 133 Failed to get status of process. (process=%1, pid = %2)

[Description]

Failed to obtain the status of the started process.

[Parameter]

%1: The name of the process whose status could not be obtained

%2: The ID of the process whose status could not be obtained

[System Action]

The script has been started successfully and may be running now. Terminates swotclsh.

[User Response]

No action is required since the script has been stated successfully. If the message frequently appears, contact your system engineer.

[System Administrator Response]

When reproducing the symptom, contact a Fujitsu's system engineer with the script you created.

swotclsh: 134 Failed to open file. (file name=%1)

[Description]

Failed to open the file (%1).

[Parameter]

%1: The name of the path to the file that could not be opened.

[System Action]

Whether the script has been executed is unknown. Terminates swotclsh.

[User Response]

Contact your system administrator.

[System Administrator Response]

Check whether access rights for the file indicated in this message and the directory in which the file exists have been granted and remove the cause of the access failure.

swotclsh: 135 Failed to read file. (file name=%1)

[Description]

Failed to load the file (%1).

[Parameter]

%1: The name of the path to the failed file

[System Action]

Whether the script has been executed is unknown. Terminates swotclsh.

[User Response]

Contact your system administrator.

[System Administrator Response]

When the file indicated in this message exists, remove the cause of the access failure by working on the file.

swotclsh: 136 Internal operation abnormality occurred. (error code=%1)

[Description]

An error occurred in the internal operation.

[Parameter]

%1: The detailed code that indicates the location of the error.

[System Action]

Whether the script has been executed is unknown. Terminates swotclsh.

[User Response]

Based on the following information, check whether the script has been executed:

  • Script trace

    The trace is stored in the following directory by default.

    [Windows version]

    Systemwalker Operation Manager installation directory\MpWalker.JM\mpfwtco\trc

    [UNIX version]

    /var/opt/FJSVfwtco/trc

    Or, it is stored in a location specified on trace obtaining processing within script. See the Systemwalker Operation Manager Reference Guide for script trace.

  • Script output information

    This information is output to the destination you specified when describing processing that outputs information to a file or standard output within script. If there is no information output processing, nothing is output.

No action is required when the script has already been executed but if not, execute it. If the symptom frequently occurs, contact a Fujitsu's system engineer.

[System Administrator Response]

When reproducing the symptom, contact a Fujitsu's system engineer with the script you created.