We have a server job which has been running for some time without any problems
The jobs has a ODBC stage a hash file stage and after lookup the data is written to sequential file. Today the job failed with the following error
Abnormal termination of stage Hash File Stage.IDENT1 detected
I reset the job and it gave the following info
From previous run
Could not load program phantom:
Dependent module libgciudt6.so could not be loaded.
Could not load module libgciudt6.so.
System error: No such file or directory
On more analysis I found that the environment variable was not loaded at all. It appeared strange to me. In any job the first step is Loading environment variable
I recompiled and ran the job. This time it ran successfully.
I am still wondering the reason for this.
Environment variable
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What has changed on your system between when it ran OK and now when it doesn't run?
What is the environment variable that isn't loaded?
Search the forum for "libgciudt6.so".
What is the environment variable that isn't loaded?
Search the forum for "libgciudt6.so".
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: 284
- Joined: Fri Oct 13, 2006 4:31 am
Nothing has changed in the system per se.
In the previous successful run of the job there was a info log entry in the Director with the heading
"Environment variable settings:"
The body contained many paths and all other information.
In the failed run also the entry was there but when I expanded the log entry it was empty..not even a single path information was there. The heading "Environment Variable Settings" was intact
This is the reason why it could not find the library.
On recompile everything was back to normal...So this suggests that the environment variable was not being accessed in the failed run. I am not getting the reason for the same
In the previous successful run of the job there was a info log entry in the Director with the heading
"Environment variable settings:"
The body contained many paths and all other information.
In the failed run also the entry was there but when I expanded the log entry it was empty..not even a single path information was there. The heading "Environment Variable Settings" was intact
This is the reason why it could not find the library.
On recompile everything was back to normal...So this suggests that the environment variable was not being accessed in the failed run. I am not getting the reason for the same
-
- Participant
- Posts: 284
- Joined: Fri Oct 13, 2006 4:31 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 284
- Joined: Fri Oct 13, 2006 4:31 am
I had no other option, I had to get the job up and running.
Recompiling was the only option.
But in my query in above post, I have mentioned the error when the job was reset? Does that help?
Recompiling was the only option.
But in my query in above post, I have mentioned the error when the job was reset? Does that help?
ray.wurlod wrote:That you are wrong when you assert that nothing had changed.
By recompiling you've destroyed all the evidence. ...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: