5.3 UNIX-specific Messages

This section explains messages that are specific to Solaris and Linux

Event ID	Category	Message	Action
DSA0543E	Error	Bad data received from command '%1': %2	[Meaning] This message is output when the output results of a command are in an unexpected format. %1: Command name %2: Error message [Action] Take any appropriate action that can be determined from the error message. This message is also output if the middleware to be managed is stopped. To control information collection behavior according to the operation mode of jobs or clusters, refer to "sqcMdPolicy (Temporary Policy Change Command)" and perform a temporary policy change. In cases other than these, collect the maintenance information and contact a systems engineer.
DSA0557W	Warning	Bad data received from command '%1': %2	[Meaning] This message is output when the output results of a command are in an unexpected format. %1: Command name %2: Error message [Action] Collect the maintenance information and contact a systems engineer.
DSA0600E	Error	Scripting error detected at line %1 in script '%2': %3	[Meaning] A TIS scripting error occurred. %1: Line number %2: Script name %3: Error message [Action] Collect the maintenance information and contact a systems engineer.
DSA0601E	Error	Invalid SampleStart record: %1	[Meaning] SampleStart record is not correct. %1: Record [Action] Collect the maintenance information and contact a systems engineer.
DSA0604E	Error	There is no troubleshooting route code for default group %1	[Meaning] Error in troubleshooting definition. %1: Group name [Action] Collect the maintenance information and contact a systems engineer.
6330	Error	Syntax error was found inside definition file.(file=%1, line=%2)	[Meaning] The definition file has syntax errors. %1: File name %2: Line number [Action] Correct the definition file. If no problem is found with the definition file, collect the maintenance information and contact a systems engineer.
6331	Error	Error occurred so stopped.(detail=%1, errno=%2)	[Meaning] An error occurred. %1:Details %2: Error code [Action] Collect the maintenance information and contact a systems engineer.
6332	Warning	Log can not be analyzed so it was ignored. (detail=%1, log=%2)	[Meaning] Failed to analyze log file. %1:Details %2: Log file name [Action] The log format may not be correctly defined in the definition file. Check it and make any necessary corrections. The Interstage log may be corrupt. Check it and take any necessary actions. If the problem is not solved by the above action, collect the maintenance information and contact a systems engineer.
6333	Information	Definition file has been changed so it was reloaded.	[Meaning] The definition file is changed so it was reloaded. [Action] No action is necessary.