The repository is built by extracting parameters for all the jobs within a project. Parameters are grouped into sets. There needs to exist a Master parameter set. This becomes the single version of a parameter. All parameters with the same name can be synced up with this master version. Within the Master parameter you can quickly see the jobs and what server and project they are in which have this parameter. You can also see the details of these parameters within the Jobs subject area of the tree. This will be explained later in more detail. You can quickly build your own parameter sets. This allows you to copy a set of parameters to a job instead of one at a time.
A Data Set is a similar concept of Parameter Set. The difference is a Data Set only deals with parameter values and not the prompts or any other property of a parameter within a job. Data Sets can be applied to one job, a group of jobs based on a filter or a whole project. Data Sets when applied only change default values of parameters. If the parameter does not exist within the job then it does nothing. This will help a user from updating the wrong database. This is important because you do not want to update production in a test run. Most DataStage developers create at least 3 projects one for development, one for test or unit test and one for production. Applying a test Data Set to a test project will make all job parameters point to a test database and not a development database. The same can be done for production.
The repository can also has a sanpshot of job parameters from many projects including development, test and production. This allows you to quickly compare parameter properties across servers and projects. If you are not using Version Control then this is important. You can also quickly jump into Designer from Parameter Navigator to make sure the job is exactly like you want it to be.
This is the splash screen for Parameter Navigator then the main form below will appear.
This is a classic explorer interface which most users should be used to.
You will need to register a server in order to extract parameters from it. Registering requires an authorization code for each DataStage Serial number. Almost every task has 3 ways to activate it. You can run it through the pull down menus, the toolbar and last the popup menu within the tree control. The tree control is the part with Parameter Sets, Data Sets and Jobs displayed on the left. Each of these subject area can be expanded or drilled down into by double clicking on the subject area name in the tree. If you right click on the subject area name then a menu pops up with more options. Most of these will display more information in the grid on the right. Some of the critical elements of Parameter Navigator are activated by a popup menu. This should be common to most users. The fastest way to build parameter sets is to copy and paste. You also can update jobs this way by copying and pasting parameters.
NOTE: It is recommended that a project be completely exported before using Parameter Navigator. It is also recommended that Parameter Navigator be the only connection to DataStage when updating jobs. Otherwise use at your own risk. This means you need to know what jobs are being updated in DataStage Designer and other IBM products.