Hi,
When ever I run a job I get a first entry in the log of type reset "Log cleared by user". Second entry is of type info "From previous run
DataStage Job 6647 Phantom 27873 Program "*DataStage*DSR_LOADSTRING": Line 138, Read operation failure. Program "*DataStage*DSR_LOADSTRING": Line 142, Read operation failure"...
The job runs fine. The row count of the source and rows loaded in database are same.
I even tried to clear the log specifying immediate purge-> clear all entries. but still the above 2 entries are comming. The job completes successfully withput any warning.
Please let me the reason of me getting the above 2 entries and how to get rid of it.
Regards
VJ
From previous run info
Moderators: chulett, rschirm, roy
Odd. The first entry in the log should always be the 'Starting' message, then the 'Environment variable settings one and Auto Purge messages are always posted last in the log. For example:
How are you starting your jobs? Do you have job control that issues a Reset and a Clear Log somehow when the job starts? I don't see how else you'd get both of those kind of entries straight away in your logs.
As for the read option failure, can you post the complete message? Double-click on it in the Director to see what comes after the ellipsis. I've had this same error myself, I do believe, but heck if I can remember the why for or the resolution at the moment.
Code: Select all
Log prior to last 14 runs cleared by user
Auto-purged 105 log entries.
![Confused :?](./images/smilies/icon_confused.gif)
As for the read option failure, can you post the complete message? Double-click on it in the Director to see what comes after the ellipsis. I've had this same error myself, I do believe, but heck if I can remember the why for or the resolution at the moment.
-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:
NEVER use -9 (SIGKILL) to remove DataStage processes. Use -15 at worst. Be aware, also, of the hierarchy of processes involved in executing a DataStage job - if you kill the parent, the child turns into a zombie, and these are much more difficult to get rid of.
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.