Almost every Data warehousing project requires that your job runs in batches at specified time slots.

In many cases they batches may be consisting of jobs from different systems in addition to the ones in Datastage. In such cases the Datast age jobs are usually scheduled by using an external scheduling tool like ESP Sch eduler, Control M, Autosys, etc This is made possible by writing scripts that wil l run your jobs through the command line. I would consider the command line a v ery powerful interface to Datastage which lets us do more than just run the norm al job. There guides present in the Datastage documentation will be very helpful in exploring the various things that can be done through the command line. Howe ver I plan on giving you the basics you will need to need to carry out your exec ution IN UNIX, the Datastage home directory location will always be specified in the .d shome file which will be present in the root directory. Before you can run your Datastage commands you will have to run the following commands cd `cat /.dshome` This will change the location to the home directory. By default this will be /op t/IBM/InformationServer/Server/DSEngine . ./dsenv > /dev/null 2>&1 This will run the dsenv file which contains all the environment variables. Witho ut doing this, your UNIX commands won t run on the command prompt. After you have done this then you can use any Datastage command for interacting with the server. The main command you can use is the dsjob command which is not us ed only to run jobs but for a wide variety of reasons. Let s look at the various w ays you can use the dsjob command To run a job Using the dsjob command you can start,stop,reset or run the job in validation m ode. dsjob run mode VALIDATE project_name job_name

This command will actually run the job in validation mode. Similarly you can use RESET or RESTART instead of VALIDATE depending on what type of run you want. If you want a normal run then you will not need to specify the mode keyword as show n below dsjob run project_name job_name job_name.invocationid

Running with the invocationid would mean that the job would be run with that spe cific invocation id Now if you have parameters to set or paratemeterset values to set then this can also be as set as shown below dsjob run ame param variable_name= VALUE param psParameterSet= vsValueSet

project_name jo

To stop a job Stopping a job is fairly simple. You might not actually require it but still its worth to take a look. It acts the same way as you would stop a running job the Datastage director.

dsjob stop project_name job_name job_name.invocationid To list projects, jobs, stages in jobs, links in jobs, parameters in jobs and in vocations of jobs dsjob can very easily give you all the above based on the different keywords. It will be useful for you if you want to get a report of what s being used in what p roject and things like that The various commands are shown below dsjob dsjob lprojects will give you a list of all the projects on the server will give you a list of jobs in a particular project

ljobs project_name

dsjobs lstages project_name job_name will give you a list of all the stages used in your job. Replacing lstage with links will give you a list of all the links in your job. Using lparams will give you a list of all the parameters used in your j ob. Using linvocations will give you a list of all the invocations of your multip le instance job. To generate reports of a job You can get the basic information of a job buy using the below dsjob -jobinfo project_name job_name Running this command will give you a short report of your job which includes The current status of the job, the name of any controlling job for the job, the dat e and time when the job started , the wave number of the last or current run (in ternal InfoSphere Datastage reference number) and the user status You can get a more detailed report using the below command dsjob -report project job_name BASIC DETAIL XML BASIC means that your report will contain very basic information like start/end time of the job , time elapsed and the current status of the job. DETAIL as the name indicates will give you a very detailed report on the job down to the stage s and link level. XML would give you an XML report which is also a detailed repo rt in an XML format. To access logs You can use the below command to get the list of latest 5 fatal errors from the log of the job that was just run dsjob -logsum type FATAL max 5 project_name job_name jobinfo option as shown

You can get different types of information based on the keyword you specify for t ype. Full list of allowable types are available in the help guide for reference. There are a number of other options also available to get different log informat ion. You can explore this in more detail in the developer guide. With the Datast age commands you can administer jobs, run jobs, maintain jobs, handle errors, pr epare meaningful job logs and even prepare reports. The possibilities are endle ss. If you like to code then you won t mind spending your time exploring the comma nd line options available.