link report not found
Moderators: chulett, rschirm, roy
link report not found
I get this error
DSD_GenerateEvents.B:LinkReport for jobname.stagename.linkname
not found.
I copied the stage and the link since I have to do an update to an old job design.
I tried changing the link name but I still get the error. Any help why.
DSD_GenerateEvents.B:LinkReport for jobname.stagename.linkname
not found.
I copied the stage and the link since I have to do an update to an old job design.
I tried changing the link name but I still get the error. Any help why.
-
- Charter Member
- Posts: 299
- Joined: Wed Nov 13, 2002 5:38 pm
- Location: USA
Do you have MetaStage installed but not running? In other words, is the checkbox, in Administrator for this project under Properties, Operate in MetaStage Proxy mode checked but the Process MetaBroker daemon for it not running? You will then get this error when your job tries to report Process Metabroker events to MetaStage but MetaStage is not at home. This is a common annoying problem. It's a horse not a zebra.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I just encountered the same problem that Bryan had regarding the warning message:
"DSD_GenerateEvents.B:LinkReport for jobname.stagename.linkname not found"
I was running a Job that was copied from another and changed slightly (source file information, etc.). There are 4 Jobs total that are very similar in structure. 3 Jobs run w/out the Warning message appearing and 1 produces the Warning message.
I suspect that you are correct regarding MetaStage being installed but not turned on because I unchecked the "Operate in MetaStage Proxy mode" checkbox and reran the Job that usually produced the Warning message. This time there was no Warning message....
So....finally to my question. What is the impact to the Project of having this box unchecked? We plan to implement MetaStage processing at a later date and another team is testing MetaStage on various Projects. Another question we have is what is the risk of having this box checked in our Development Project and having it unchecked in our Acceptance Testing Project?
Any information that can be provided is most appreciated. Thank you for your time.
"DSD_GenerateEvents.B:LinkReport for jobname.stagename.linkname not found"
I was running a Job that was copied from another and changed slightly (source file information, etc.). There are 4 Jobs total that are very similar in structure. 3 Jobs run w/out the Warning message appearing and 1 produces the Warning message.
I suspect that you are correct regarding MetaStage being installed but not turned on because I unchecked the "Operate in MetaStage Proxy mode" checkbox and reran the Job that usually produced the Warning message. This time there was no Warning message....
So....finally to my question. What is the impact to the Project of having this box unchecked? We plan to implement MetaStage processing at a later date and another team is testing MetaStage on various Projects. Another question we have is what is the risk of having this box checked in our Development Project and having it unchecked in our Acceptance Testing Project?
Any information that can be provided is most appreciated. Thank you for your time.
Hi All,
I have had this problem as well. Our problem occured when custom SQL was used in an OCI stage (in our cases a lookup) - when using the process metabroker.
In our case, it turns out it was the lack of a table name in the OCI stage that caused this problem. Go into the offending link, change the type from Custom SQL to column-driven and put a table name in the box. Before pressing the ok button on the dialog, change the type back to custom sql (and your sql should still be there). Re-compile, and re-run without the warnings.
Chris.
I have had this problem as well. Our problem occured when custom SQL was used in an OCI stage (in our cases a lookup) - when using the process metabroker.
In our case, it turns out it was the lack of a table name in the OCI stage that caused this problem. Go into the offending link, change the type from Custom SQL to column-driven and put a table name in the box. Before pressing the ok button on the dialog, change the type back to custom sql (and your sql should still be there). Re-compile, and re-run without the warnings.
Chris.
-
- Charter Member
- Posts: 1
- Joined: Tue Sep 20, 2005 8:43 am
MetaStage Proxy mode, v.6
For the v.6, is it the same Checkbox "Proxy mode", or what is it called in v.6 ?throbinson wrote:Do you have MetaStage installed but not running? In other words, is the checkbox, in Administrator for this project under Properties, Operate in MetaStage Proxy mode checked but the Process MetaBroker daemon for it not running? You will then get this error when your job tries to report Process Metabroker events to MetaStage but MetaStage is not at home. This is a common annoying problem. It's a horse not a zebra.
Txs
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard! :D
Alas I don't have version 6 any more, so can't provide a direct answer. You could try searching your on-line help or Server Job Developer's Guide for "proxy mode".
Alas I don't have version 6 any more, so can't provide a direct answer. You could try searching your on-line help or Server Job Developer's Guide for "proxy mode".
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.
-
- Participant
- Posts: 94
- Joined: Wed May 08, 2002 8:44 am
- Location: Germany
- Contact:
-
- Participant
- Posts: 44
- Joined: Wed Sep 02, 2015 7:19 am
- Location: Brasilia, Brazil