1) I have a server job in DS 8.5 that reads records from a file, passing a field to a sub-job using UtilityRunjob() in a transformer. It has crashed once in a while, but the parent job returns a green/clean status. Is there a way to trap the error if the sub-job fails?
2) I'd prefer not to use the UtilityRunjob to call a sub-job with a parameter generated from SQL or file. Is there a best-practice for doing such a process in a parallel job or sequence ? I saw some notes about using USERSTATUS, but one of the notes said that wasn't suitable for a parallel job.
thanks,
Capturing an error when using UtilityRunjob()
Moderators: chulett, rschirm, roy
1) I don't recall but the docs say "Runs the specified job and returns statistics from the job run" and "The statistics are returned in an array". I would start by looking at what the 'statistics' show when the called job fails.
2) Have you looked into a looping Sequence job?
2) Have you looked into a looping Sequence job?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers