PX_Debug variable - Help required
Moderators: chulett, rschirm, roy
PX_Debug variable - Help required
Hi All,
Previously I had raised some questions regarding the swap memory usage in son solaris, as our jobs were failing. We had logged a ticket with IBM regading this, The engineer asked us to run the job using PX_Debug(=1) environment variabe. Hence this variable was setup on our project.
Now that the case has been resolved We have removed the variable from the project. But if I go through the job logs I cans still see the information a lot of information being displayed into it.
How do I get rid the effects that PX_Debug has done to the project environment.
Will a Server reboot work for this or is there anything else need to be done?
Previously I had raised some questions regarding the swap memory usage in son solaris, as our jobs were failing. We had logged a ticket with IBM regading this, The engineer asked us to run the job using PX_Debug(=1) environment variabe. Hence this variable was setup on our project.
Now that the case has been resolved We have removed the variable from the project. But if I go through the job logs I cans still see the information a lot of information being displayed into it.
How do I get rid the effects that PX_Debug has done to the project environment.
Will a Server reboot work for this or is there anything else need to be done?
Thanks
DSDexter
DSDexter
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 10
- Joined: Thu Aug 28, 2008 12:40 am
-
- Participant
- Posts: 10
- Joined: Thu Aug 28, 2008 12:40 am
That is interesting.
Would like to see others' opinions and experiences.
[quote="DSDexter"]dsdeveloper13: I had this same issue with out test environment. I removed the job from there and I am not facing this issue any more in test.
So as of now I can think of this as solution to my query. Although I will still wait for experts comment from Ray :lol: for the comment you raised.[/quote]
Would like to see others' opinions and experiences.
[quote="DSDexter"]dsdeveloper13: I had this same issue with out test environment. I removed the job from there and I am not facing this issue any more in test.
So as of now I can think of this as solution to my query. Although I will still wait for experts comment from Ray :lol: for the comment you raised.[/quote]
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Clearly and definitely "maybe". Is $PX_DEBUG in any other job as a job parameter? How can you be sure? Is PX_DEBUG set in Administrator? Is PX_DEBUG set in dsenv or some other setup script?DSDexter wrote:Nice Catch Ray, I had created a dummy job for the IBM guys, So that they'll get the necessay info. And that job still exist in the project. This job has PX_Debug variable as a job parameter.
If I delete this job from the project, Will this issue be resolved?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 125
- Joined: Mon Sep 11, 2006 4:22 am
- Location: India