Neoview Messages Manual (R2.2)

Both files are in the load directory /opt/tandem/genus/gel/log/load.
Execution completed with warnings. Bad records rejected on source.
Cause The task completed with warnings—records were rejected at the source when the
data was being read from either a file, name pipe, or JMS queue.
Recovery This is an informational message only. No corrective action is needed. The rejected
records are in a file with a name in this format:
task_name.task_instance_name.input.bad
This file is located in the load directory /opt/tandem/genus/gel/log/load.
Execution completed with warnings. Bad records rejected on target.
Cause The task completed with warnings—records were rejected at the target when the
data was being loaded by SQL.
Recovery This is an informational message only. No corrective action is needed. The rejected
records are in a file with a name in this format:
task_name.task_instance_name.sql.bad
This file is located in the load directory /opt/tandem/genus/gel/log/load.
Execution completed with error.
Cause The gelserver stopped execution because one or more worker threads encountered
an error. Previous errors in the log provide details about the error.
Recovery Check the previous errors in the task instance log file.
Execution completed with success.
Cause The task completed successfully.
Recovery This is an informational message only. No corrective action is needed.
Execution failed.
Cause The task completed unsuccessfully. This failure can occur if the reader or writer
shared-library (mentioned in gelserver.config.xml file) is incorrect. Previous errors in
the log provide details about the error.
Recovery Check the previous errors in the task instance log file.
Linux Gelserver Messages 377