We are currently using DS 4.2 sp6. I noticed that the Job Error Log has a lot of useful information in the warning messages (SESSION|WORKFLOW|DATAFLOW) but the error messages only have the dataflow.
Since we use a third party tool to monitor the logs and alert us, it would be helpful if the error messages contained the same information as the warnings.
Is there a way to customize what gets written to the logs when an error occurs other than putting our own custom errors in? I’ve tried to look through the installation path but was unable to find any type of config file to modify and didn’t see anything in CMC either. Similarly the admin guides didn’t provide any useful information concerning this.
More complex answer is that you could implement Try-Catch blocks on all your jobs (this is a best practice in any case), set current object to the database and then have your catch print whatever you want into the Trace Log. Then your third party software can parse what it needs from the Trace Log. I do something like this today in my job_end script to pass custom error messages up through try catch blocks (because globals lose scope when you raise an exception.
$var_Errr_Mess = sql('ds_Utility',
'Select var_Value From tbl_Job_Parm ' ||
'Where var_Varb = \'$var_Mess_Errr_Glob\' ' ||
' and int_Proc = {$int_Proc_Glob}');
It’s really worth your time in the long run for troubleshooting problems that make it into production, at least in my experience.
(BOB member since 2005-09-16)