where are the log files for DS
Moderators: chulett, rschirm, roy
where are the log files for DS
I know how to use Director to view job logs. I would like to view/use the job logs outside of the director.
Where does DS store job logs? Are they in a text file that can be edited?
Where does DS store job logs? Are they in a text file that can be edited?
Re: where are the log files for DS
David seems to have thrown you straight into the Advanced Placement class when it doesn't even seem like you've taken the 101 version yet.hiltsmi wrote:Where does DS store job logs? Are they in a text file that can be edited?
In addition to all that, the simple answer is 'no' - they are not text files. You'll soon find that the vast majority of information stored in the repository is stored in hashed files just like you would use in a job, and the logs are no exception. Each job is assigned a number when it is created and a series of hashed files are created to hold its design, object code, logs, etc. Have a peek inside one of your Project directories and you'll see.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The newer model is the ak74. Played with one of those, the ak47 is better.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Oh, perfectly well aware of what a Kalashnikov AK47 is - just wasn't quite sure of the relevance to the topic being discussed.
And as we drift ever further from the dock... I guess the connection was short usernames. Not nice to poke fun at 'short' people. And you know Arnd has a soft spot for automatic weapons.
And as we drift ever further from the dock... I guess the connection was short usernames. Not nice to poke fun at 'short' people. And you know Arnd has a soft spot for automatic weapons.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Charter Member
- Posts: 36
- Joined: Thu Jun 10, 2004 11:22 pm
etlstat cannot be deleted
hi KDuke,
I downloaded etlstat & imported into DS but now I cannot delete them.. ?
This solution does not work for me, because we have very limited access to DB, therefore I'm still searching for solutions based on hash or files only (anything that's only limited to ds, w/o touching DB)'
Thanks - HT
I downloaded etlstat & imported into DS but now I cannot delete them.. ?
This solution does not work for me, because we have very limited access to DB, therefore I'm still searching for solutions based on hash or files only (anything that's only limited to ds, w/o touching DB)'
Thanks - HT
Use the dsjob API to dump log summaries. If you want full log dumps, youre going to have to write something using intenal knowledge of the job repository. The APIs are not complete enough to give you full dumps of the job log.
The simplest thing to do is cross-reference the job name to the job number out of DS_JOBS. Then, dump out the hash file RT_LOGnnn where nnn is the job number. You'll have to learn DS BASIC and figure out how to sort and normalize the data.
One thing to consider is writing a DS job to point at the RT_LOGnnn file using the hash file stage and stream the output to a sequential file. The hash file will have to be a job parameter that can change from one run to another. That will allow you to more easily parse that log file. At least poke around and see what you can come up with.
The simplest thing to do is cross-reference the job name to the job number out of DS_JOBS. Then, dump out the hash file RT_LOGnnn where nnn is the job number. You'll have to learn DS BASIC and figure out how to sort and normalize the data.
One thing to consider is writing a DS job to point at the RT_LOGnnn file using the hash file stage and stream the output to a sequential file. The hash file will have to be a job parameter that can change from one run to another. That will allow you to more easily parse that log file. At least poke around and see what you can come up with.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
You can run this against hash files. You can change all the stage types to hash files in job DSJobReportDb. Also why can't you delete these jobs? When you use hash files the DSN is localuv. Leave the user and password blank for localuv. The job GenHtmlJobLog uses SQL to extract the log. This could easily be changed into a UV stage and extract the RT_LOGnnn file directly. You would need to change the nnn into a job parameter like RT_LOG#JobNo#. Anyway here are the SQL statements from the job above.hi KDuke,
I downloaded etlstat & imported into DS but now I cannot delete them.. ?
This solution does not work for me, because we have very limited access to DB, therefore I'm still searching for solutions based on hash or files only (anything that's only limited to ds, w/o touching DB)'
Thanks - HT
Code: Select all
SqlStmt = ''
SqlStmt< 1> = 'select'
SqlStmt< 2> = ' TIMESTAMP,'
SqlStmt< 3> = ' SEVERITY,'
SqlStmt< 4> = ' FULL.TEXT'
SqlStmt< 5> = 'from'
SqlStmt< 6> = ' RT_LOG':JobNo
SqlStmt< 7> = 'where'
SqlStmt< 8> = ' EVAL "@ID" NOT LIKE ':"'//%'"
Mamu Kim