One more option, run the workflow in debugger mode as step-by-step execution.
Keep looking at the context viewer window after each activity for the variable you are looking for.
the context viewer will show you the value in each context items till the current activity being executed in that workflow.
To debug step by step in a huge flow is very painful. I would like to know all the building blocks where the var has been used.
In that case only option is the one Carl suggested in his reply.
Is that perl script supported and verified by BMC? I see that the last "aolint.pl" update was in 2014, is it still valid?
Also, I would prefer not to use third-party tools, I'd rather use a built-in BMD utility.
There are a number of things not "verified" by BMC, but used by BMC and other people. Although older, it is still a tool that should be in every TSO developers toolkit as it allows you to find unused context items, check cross module dependencies, etc - therefore it is invaluable for larger workflows and validation that you have done things correctly.
The only other ways have been mentioned in here:
- Viewing the whole workflow as the PDL and tracing from there (manual work and could be harder on larger workflows)
Thank you A. Li,
I will use that.
Although, It would be useful to implement a utility that does the trace.