This is automatically created as you build the sequence or batch but can be out of sync or missing entries. The batch or sequence usually has a tab in job properties to show all jobs and routines dependent or "ran" by this sequence or batch.
#Infoserver datastage dos batch script example how to#
There are lots of posts on how to read these log records. This hashed file is called RT_LOGnnn where nnn is the job number. The job name that executes another job is put in I think the second record of the log. Your specific question was "the job name calling a qualified job". Even more complicated if everything is user defined SQL or using views. Automating this relationship is very difficult especially if you did not create the original job. Most of us want and need some of this information like the relationship between the tables used in a link. You have to create it manually or import it indirectly using q-pointers or some other Universe concept which requires a lot more knowledge of Universe. You cannot import metadata directly from DS_JOBS, DS_JOBOBJECTS or any repository table. The hardest part of using these repository SQL statements is creating the metadata. Doing any of this in BASIC either in a routine or job control code takes a lot more knowledge of Universe. All the SQL I post that runs at TCL against repository tables can be used in a UV stage as a source and written to any table or file. There are no documents about the repository tables.
0 kommentar(er)
