User Defined Variables
Posted: Mon Apr 18, 2005 8:54 am
Hi All,
( using Version 7.5 on solaris 2.8 )
I have a situation where I need to handle a dynamicly changing value thru-out the life cycle of a sequence job.
My job reports progres to some QA tables, along the way it records business significant points and/or processing sections so I'll be able to address them from another process flow and generate reports on them as well.
The thing is I'm trying to simplify my job design by using the automatically handle activities that fail check box in the sequence job's properties tab.
so I have 2 seperate flows:
1. the process itself.
2. the exception flow when one is caught.
The thing is that while in the first flow I'll occasionally invoke an open section job activity stating section 1 started then some processing then section 1 finished then section 2 started , section 2 finished and so on till the end of this run.
In the 2nd flow - handling the exception, how can I capture the fact that some activity failed inside a certain section?!
I thought of using user variable stage and modify it along the way, but I noticed that the stage name is also part of the user variables name if I want to pass it as a parameter value to my section failed activity.
After searching this forum and even reaching back to Oliver's List !!! I came to the conclusion that a possible solution lies in the use of common variable/s and routines.
I would apreciate any other ideas you might have to solve this issue.
Thanks in advance for your time,
( using Version 7.5 on solaris 2.8 )
I have a situation where I need to handle a dynamicly changing value thru-out the life cycle of a sequence job.
My job reports progres to some QA tables, along the way it records business significant points and/or processing sections so I'll be able to address them from another process flow and generate reports on them as well.
The thing is I'm trying to simplify my job design by using the automatically handle activities that fail check box in the sequence job's properties tab.
so I have 2 seperate flows:
1. the process itself.
2. the exception flow when one is caught.
The thing is that while in the first flow I'll occasionally invoke an open section job activity stating section 1 started then some processing then section 1 finished then section 2 started , section 2 finished and so on till the end of this run.
In the 2nd flow - handling the exception, how can I capture the fact that some activity failed inside a certain section?!
I thought of using user variable stage and modify it along the way, but I noticed that the stage name is also part of the user variables name if I want to pass it as a parameter value to my section failed activity.
After searching this forum and even reaching back to Oliver's List !!! I came to the conclusion that a possible solution lies in the use of common variable/s and routines.
I would apreciate any other ideas you might have to solve this issue.
Thanks in advance for your time,