Hi All,
I wanted to now how the status column of datastage director is defined or how it is derived.
Regards,
Lebu
Status column in DataStage Director
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There is a separate RT_STATUSnnn table for each job. The information is not summarised anywhere. The nnn is the unique job number allocated by DataStage when the job is created and which is recorded as JOBNO in the DS_JOBS table (whose key is NAME, the job name).
The status of each active or hybrid stage is also stored in the RT_STATUSnnn table for the job. This information is viewable in the Monitor view of Director.
Status is stored as a TinyInt; it can be decoded using mnemonics that can be found in the JOBCONROL.H header file. For example 0 is "running", 1 is "finished OK", 2 is "finished (see log)", 3 is "aborted", 21 is "has been reset", etc. From memory there are about 12 possible status values.
The status of each active or hybrid stage is also stored in the RT_STATUSnnn table for the job. This information is viewable in the Monitor view of Director.
Status is stored as a TinyInt; it can be decoded using mnemonics that can be found in the JOBCONROL.H header file. For example 0 is "running", 1 is "finished OK", 2 is "finished (see log)", 3 is "aborted", 21 is "has been reset", etc. From memory there are about 12 possible status values.
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.
