Setting up "CRON" Jobs in Nix

If you want to use the emacs editor for editing cron jobs, then, set the following in your "/home/user/.bash_profile"

EDITOR=emacs

Then, to edit cron jobs

$ crontab -e

You may want to put in the following header

How to setup environment variables in DataStage

In DataStage you can set environment variables using three different methods. The right method depends on how often you need to change the value of an environment variable and how specific this value is for a particular project or job. Here is a description of these methods:

How can I run the osh command of the InfoSphere Parallel Engine?

The osh command is the main program of the InfoSphere Parallel Engine. This command is used by DataStage to perform several different tasks including parallel job execution and dataset management. Normally, there is no need to run this command directly but sometimes it is useful to use it for troubleshooting purposes.

To run this command there are 3 environment variables that must be set. These are:

1. APT_ORCHHOME should point to Parallel Engine location
2. APT_CONFIG_FILE should point to a configuration file
3. LD_LIBRARY_PATH should include the path to the parallel engine libraries. Please note that the name of this environment variable may take a different name (such as LIBPATH in AIX or SLIB_PATH in HP-UX) depending on your Operating System. Note: This variable does not need to be set in Windows environments.

Setting Up and Using PuTTY

•  
• Run the installer package and extract the PuTTY components. PuTTY may be downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/
• Start the PuTTYGen application. This application is used to create your authentication keys. Select either "SSH2 RSA" or "SSH2 DSA" for the "Type of key to generate", with 1024 bit key size or greater. Press the "Generate" button and follow the instructions on the screen.
  

Magic Command to BackUp Putty Sessions

1) Open Run in Windows ( Window + R )
2) Put below command in Run

First time IIS User Setup - DataStage 8.7

Typical users list:

• wasadmin
• isadmin
• db2inst1,db2iadm1
• db2fenc1,db2fadm1
• dasusr1,dasadm1
• xmeta,xmeta (db owner)
• xmetasr (staging area)
• iauser,iadb (db user)
• dsadm,dstage

Specifying C++ compiler settings for DataStage in Windows

Today I am sharing how to specify the C++ compiler settings for DataStage in Windows Environment. From last few days I also face a lot of issue with this :P so thought it need to share with you all.

For :  DataStage 8.x

Environment Variable for Data Stage Best Practices and Performance Tuning

DataStage provides a number of environment variables to control how jobs operate on a UNIX system.  In addition to providing required information, environment variables can be used to enable or disable various DataStage features, and to tune performance settings. 

Data Stage Environment Variable Settings for All Jobs

SSH Login without Password in Nix

You want to use Linux/AIX/Unix and OpenSSH to atomize your tasks. Therefore you need an automatic login from hostA as user a to hostB as the same user. You don’t want to enter any passwords, because (for example) you want to call ssh from a within a shell script.

First log in on hostA as user a and generate a pair of authentication keys. Do not enter a passphrase:

Saving InfoSphere DataStage settings files

In Linux and UNIX, for Version 7.5.3 and earlier, the engine directory is /user_home/Ascential/DataStage/DSEngine, where user_home is the home directory of the InfoSphere DataStage administrator who originally installed InfoSphere DataStage.

For Version 8.0.1 and later, the engine directory is /opt/IBM/InformationServer/Server/DSEngine. By default, this user is named dsadm. For Version 7.5.3 and earlier, each project is in its own directory in the /user_home/Ascential/DataStage/Projects directory.

Tips for debugging a datastage job

Some tips for the beginners of datastage. Hope this will help you to debug the job in datastage.

Enable the following environment variables in DataStage Administrator:

• APT_PM_PLAYER_TIMING – shows how much CPU time each stage uses
• APT_PM_SHOW_PIDS – show process ID of each stage
• APT_RECORD_COUNTS – shows record counts in log