Hi All,
What is the use of this $Apt_disable_combination Variable. Why we are Enabling this.
Thanks,
$Apt_disable_combination
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 1
- Joined: Sun Mar 31, 2013 6:26 am
- Location: Chennai
$Apt_disable_combination
Karthikeyan.M
-
- Premium Member
- Posts: 24
- Joined: Fri Oct 28, 2011 10:55 am
Re: $Apt_disable_combination
Why not just post the link to the IBM documentation, which also does not answer the question as to "WHY".
The "why" of it has been discussed here in the past but not recently from what I recall. There are several core APT variables that people have identified as ones you should include in every job. Sorry that I don't remember the full set but this is definitely one of them. As noted, it allows you to simply set it to TRUE if you ever need to debug a job with a generic "CombinedOperator" error without having to go back to the design (and promotion process) to add it.
Perhaps we can morph this conversation around to that topic. General question to the home audience: what APT variables are you setting up in every job as a best practice?
Perhaps we can morph this conversation around to that topic. General question to the home audience: what APT variables are you setting up in every job as a best practice?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
We do not include any APT environment variables on every job. If we hit some sort of unusual problem, then we will create a copy of the job for debugging purposes and start narrowing down the problem as needed. That process may or may not require special APT environment variables to be added.
We do, as a standard practice, set APT_DUMP_SCORE=True at the project level on every project, via Administrator.
We do, as a standard practice, set APT_DUMP_SCORE=True at the project level on every project, via Administrator.
Choose a job you love, and you will never have to work a day in your life. - Confucius