6.1.13 JP1/Script event logs

JP1/Script outputs event logs according to the status. The user can also use the MessageEventLog command to specify output of event logs.

Table 6-6 lists and describes the event IDs and event logs that are output. The information output source is JP1/Script.

Table 6‒6: Event IDs and logs
Event ID	Type	Event log	Output information^#1
`1`	Information	Information log at the beginning of script execution	`Script execution has started. (script-file-name)`
`2`	Information	Information log at the end of script execution	`Script execution has finished. (script-file-name)`
`3`	^#2	User-specified log using the `MessageEventLog` command	Message specified in the `MessageEventLog` command
`4`	Information	Information log for the execution of Script Launcher	`The Script launcher is not running on the Remote Desktop service client.`
	Warning	Warning log for the execution of the JP1/Script service, Script Launcher service, or Script Launcher	Warning message (error message)
	Error	Error log for the execution of the JP1/Script service, Script Launcher service, or Script Launcher	`JP1/Script may be installed incorrectly. Reinstall JP1/Script.`
			`The contents of the automatic start information file are invalid. Remake the automatic start information file.` (`automatic-start-information-file-name`)
			`The Script Launcher service is already running. Script Launcher cannot be started.`
			`Script Launcher is already running. The Script Launcher service cannot be started.`
			`The startup account for the Script Launcher service is not a local system account. The Script Launcher service cannot be started.`
			`A logon user name is not specified in the startup parameter for the Script Launcher service. The Script Launcher service cannot be started.`
			`The NetExec thread for the Script Launcher service cannot be started because the content of the policy file limited to the NetExec command is invalid. Re-create the policy file limited to the NetExec command and restart the Script Launcher service. (file-name)`
			An error message for the error that occurred.
`5`	Warning	Warning log at execution of the `ExitWindows` command	`The ExitWindows (type-of-shutdown-operation-specified-in-the-command) command was executed. (script-file-name)`
`5`	Warning	Warning log at execution of the `ExitWindows` command	`Executing the ExitWindows command failed.` (`function-name`, `error code`)
`6`	Warning	Warning log for unsuccessful issuance of an event to JP1/IM or JP1/Base	`An error occurred in a JP1/Integrated Manager function. (JP1/IM-or-JP1/Base-function-name::` `JP1/IM-or-JP1/Base-function-error-condition-code)`
`7`	Information	Information log at execution of the `TerminateProcess` command	`The TerminateProcess (Id=process-ID-specified-in-the-command) command was executed. (script-file-name)`
`8`^#3	Information	Information log at the beginning and end of the JP1/Script service, Script Launcher service, and Script Launcher execution	`The Script Launcher will now start. (date` `time` `elapsed-time-since-system-startup)`
			`The Script Launcher will now end. (date` `time` `elapsed-time-since-system-startup)`
			`The NetExec thread of the Script Launcher will now start. (date` `time` `elapsed-time-since-system-startup)`
			`The NetExec thread of the Script Launcher will now end. (date` `time` `elapsed-time-since-system-startup)`
			`The Script Terminate Control Launcher was executed. (date` `time` `elapsed-time-since-system-startup)`
			`The JP1/Script service will now start. (date` `time` `elapsed-time-since-system-startup)`
			`The JP1/Script service will now end. (date` `time` `elapsed-time-since-system-startup)`
			`The NetExec thread of the JP1/Script service will now start. (date` `time` `elapsed-time-since-system-startup)`
			`The NetExec thread (which limits users who can execute the NetExec command) for the JP1/Script service will now start. (date time elapsed-time-since-system-startup)`
			`The NetExec thread of the JP1/Script service will now end. (date` `time` `elapsed-time-since-system-startup)`
			`The File Mapping Object Control thread of the JP1/Script service will now start. (date time elapsed-time-since-system-startup)`
			`The File Mapping Object Control thread of the JP1/Script service will now end. (date time elapsed-time-since-system-startup)`
			`The Script Launcher service will now start. (date time elapsed-time-since-system-startup)(execution-account-name)`
			`The Script Launcher service will now end. (date time elapsed-time-since-system-startup)(execution-account-name)`^#5
			`The NetExec thread for the Script Launcher service will now start. (date time elapsed-time-since-system-startup)`
			`The NetExec thread (which limits users who can execute the NetExec command) for the Script Launcher service will now start. (date time elapsed-time-since-system-startup)`
			`The NetExec thread for the Script Launcher service will now end. (date time elapsed-time-since-system-startup)`
`16`	Error	Error log at startup of multiple scripts	`The specified script file has already been started. (script-file-name)`
`17`	Warning	Warning log at forced termination of a script	`Forcibly terminated the JP1/Script process. (script-file-name)`
`18`	Warning	Warning log at script termination due to timeout	`Terminated the JP1/Script process because a timeout occurred. (script-file-name)`
`19`	Information	Information log at script termination due to a syntax error	`Script execution has finished. Syntax error occurred. (script-file-name)`
`96`	Warning	Warning log when the JP1/Script service is not running at startup of script execution	`The execution result will not be output to the analysis/execution trace file because the JP1/Script service is not running.\nAlso, execution of the Message, EntryStartUp, or CancelStartUp command, or the global variable operation command will result in an error.\nStart the JP1/Script service, and then perform execution. (script-file-name)`
`98`^#4	Error	Error log when no analysis trace or execution trace (`/SPALV(0)` or `/SPXLV(0)` specified) is output	`User name:` `user-name-at-script-execution` `Script file name:` `script-file-name` `The following error occurred.` `Line-number-of-the-error` line; `error-message-for-the-error-that-occurred`
`99`	Error	Error log at the beginning of script execution	An error message for the error that occurred.

#1

Italic letters indicate a placeholder whose contents depend on the log. date, time, and elapsed-time-since-system-startup are displayed in the formats yyyy/mm/dd, hh:mm:ss.ss, and in milliseconds, respectively.

#2

The event type specified by the MessageEventLog command.

#3

To suppress output of this event log, set the registry key as follows:

Registry key

HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\JP1/Script\SPTF\SPV

Value name

CommandLine(character-string)

Value datatype

REG_SZ

Value

/NOEVLOG(8)

When the setting takes effect

The setting takes effect the next time the JP1/Script service, the Script launcher, or the Script launcher service is started.

#4

To output this error to the event log, set the registry key as follows:

Registry key

HKEY_CURRENT_USER\SOFTWARE\HITACHI\JP1/Script\SPTX

Value name

ErrorEventLog

Value datatype

REG_DWORD

Value

1: The error is output to the event log.

Other than 1: No error is output to the event log.

When the setting takes effect

The setting takes effect the next time the script file is executed.

#5

When an error occurs on startup of the Script Launcher service, an event log entry is output without an execution account name.

Of these event logs, you can suppress output of non-error event logs. To specify output suppression, see If you choose Command Line: in 6.2.2(4) /NOEVLOG (or /noevlog).

To Page Top