Whenever I run a job in DataStage server, it creates a cli_NNNN.trc file in the projects home directory, where NNNN is number. How can I disable this setting.
I do not have server side or job tracing on. These files get created in project home directory not in &PH& directory.
I am using DataStage Server 7.5 version.
Dinesh
.trc files in project home directory?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This is something new in 7.5, I suspect (I haven't played with 7.5 yet).
Server side trace files are in the &COMO& subdirectory, while active stage trace files are in the &PH& subdirectory. Neither has the name form given in the original post.
Server side trace files are in the &COMO& subdirectory, while active stage trace files are in the &PH& subdirectory. Neither has the name form given in the original post.
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.
Hi Ketfos,ketfos wrote:Hi Dinesh,
Can you see this files in DataStage Adm --- Projects --- Properties --- Tracing ---- option.
Ketfos
I checked this. It is not enabled. Strange part is, it started happening two days back only. we did not change anything on the server. We are doing developemnt on 7.5 since it was released and never saw this problem.
The file start with following text: (for a small job, it create very big file)
(1) [19-NOV-2004 22:02:34:166]
--- TRACE CONFIGURATION INFORMATION FOLLOWS ---
(1) [19-NOV-2004 22:02:34:166] New trace stream is /dstage/projects/loadqa/cli_1
2017.trc
(1) [19-NOV-2004 22:02:34:167] New trace level is 16
(1) [19-NOV-2004 22:02:34:167] --- TRACE CONFIGURATION INFORMATION ENDS ---
(1) [19-NOV-2004 22:02:34:167]
--- PARAMETER SOURCE INFORMATION FOLLOWS ---
(1) [19-NOV-2004 22:02:34:167] Attempted load of system pfile source /u01/app/or
acle/product/9.2.0/network/admin/sqlnet.ora
(1) [19-NOV-2004 22:02:34:167] Parameter source loaded successfully
(1) [19-NOV-2004 22:02:34:167]
(1) [19-NOV-2004 22:02:34:168] Attempted load of local pfile source /.sqlnet.ora
(1) [19-NOV-2004 22:02:34:168] Parameter source was not loaded
(1) [19-NOV-2004 22:02:34:168]
(1) [19-NOV-2004 22:02:34:168] -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
(1) [19-NOV-2004 22:02:34:168] Successful parameter table load
(1) [19-NOV-2004 22:02:34:168] -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
Dinesh
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That's perfectly explicable. The project directory is the "home" directory for the process that runs your DataStage job. It's this process that is the Oracle client.
The mechanism for running a server job is (slightly simplified):
The mechanism for running a server job is (slightly simplified):
- cd to project directory
invoke uv (or uvsh) as a PHANTOM (backround process) to execute the (DataStage BASIC) program DSD.RUN
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.