For a given build or function, is there any easy way to find out in which jobs they are used?
I think this is available in the "Document Catalog" feature.
Regards,
MF.
Ooo, that sounds promising.
What is the "Document Catalog" feature? I can't seem to find anything in the documentation we have about it, although the term "catalog" is used often. Which version of DS has this feature?
Hi,
All of the versions have this feature - right back to DecisionStream 6.0. Go to the File menu and select the "Document Catalog" option. Choose Full Documentation and provide a name. This will then create an HTML document of your work saved in the catalog. For each build you will find a Usage Summary, which details the jobstreams it is used in (look for "Build Node nn in JobStream Component xxxxx" - you will get one entry like this for each jobstream node the build is referenced from)
Cheers!
MF.
Thanks again for the help. :D
That's exactly the info I need. Although it isn't exactly easy to get at. Creating the catalog takes about 10 minutes on my machine and the resulting HTML file is 15 MB. Do you if it is possible to trigger the Document Catalog creation from the command line?
Quote from: eknight on 21 Jun 2012 02:29:45 AM
Thanks again for the help. :D
That's exactly the info I need. Although it isn't exactly easy to get at. Creating the catalog takes about 10 minutes on my machine and the resulting HTML file is 15 MB. Do you if it is possible to trigger the Document Catalog creation from the command line?
Yes - there is a 'catdoc' command to do exactly this. The syntax is covered in the Data Manager User Guide:
http://publib.boulder.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ug_ds.10.1.0.doc%2Fug_ds_id27284catdoc.html
Cheers!
MF.
Oh, perfect. It's a sub optimal solution (I'd prefer being able to have this built in the application) but I can autogenerate new docs overnight and auto publish them to a webserver.
Thanks again,
In theory, you could extract this information from the catalog database - it will be held somewhere in the table schema. It's probably not an easy task to find the relevant tables and columns to interrogate, but if the Document Catalog option proves too clunky, it might be something you could look at. It's not a supported technique, though - IBM don't want you messing around in the catalog tables, and of course they reserve the right to change the schema between versions without telling you :)
Cheers!
MF.
I've taken a look at the database :o . There are much better things I could do then go messing around in there. It seems like it wouldn't be too hard to add a context menu option on builds called "jobs..." which uses a similar query to the "Document Catalog" option and displays a clickable list of jobs that use this build.
Another option is to select the Build you are interested in, and use the View/Navigate menu (or click the "Open the Navigator window" icon. In the Navigator you'll see the Build nodes in the JobStreams where that build is used; click on one to take you there in the main tree.
This links from a jobstream node to a build, but not the other way around - it doesn't allow you to select a build and see which jobstreams it is used in, sadly. The only way I know of to get that info is in the Document Catalog feature.
Cheers
MF.
With the Navigator open, when I select a fact build in the tree, the navigator DOES show details of all the builds nodes in the catalog that use that fact build. The details include the name of the JobStream.
Isn't that what was wanted?
Quote from: ROBER82167 on 11 Jul 2012 02:15:56 AM
Another option is to select the Build you are interested in, and use the View/Navigate menu (or click the "Open the Navigator window" icon. In the Navigator you'll see the Build nodes in the JobStreams where that build is used; click on one to take you there in the main tree.
Yes! That is exactly what I was looking for! Thank you ;D
Quote from: ROBER82167 on 11 Jul 2012 07:50:57 AM
With the Navigator open, when I select a fact build in the tree, the navigator DOES show details of all the builds nodes in the catalog that use that fact build. The details include the name of the JobStream.
Isn't that what was wanted?
Hmmmmm. Not doing it on mine! It works for you and eknight though, so that's great news!! I wonder why mine doesn't?
Oh... Wait a minute. I think I know.
Cheers!
MF.
Quote from: MFGF on 11 Jul 2012 09:04:48 AM
Oh... Wait a minute. I think I know.
Cheers!
MF.
You can't just leave us hanging dude! Why doesn't it work for you? Or did you get it working? FYI I'm using DecisionStream 7.1 :-\