Posts

Showing posts with the label Configuration

Managing and Deleting Persistent Data Sets within IBM InfoSphere Datastage

Data Sets sometimes take up too much disk space. This technote describes how to obtain information about datasets and how to delete them.  

APT_CONFIG_FILE : Configuration File

APT_CONFIG_FILE  is the file using which DataStage determines the configuration file (one can have many configuration files for a project) to be used. In fact, this is what is generally used in production. However, if this environment variable is not defined then how DataStage determines which file to use? 1)If the APT_CONFIG_FILE environment variable is not defined then DataStage look for default configuration file (config.apt) in following path: 1)Current working directory. 2)INSTALL_DIR/etc, where INSTALL_DIR ($APT_ORCHHOME) is the top level directory of DataStage installation.

Something about CRON in Linux

cron is a Nix utility that allows tasks to be automatically run in the background at regular intervals by the cron daemon. These tasks are often termed as cron jobs in Nix.  Crontab (CRON TABle) is a file which contains the schedule of cron entries to be run and at specified times. This document covers following aspects of Unix cron jobs  Crontab Restrictions  Crontab Commands  Crontab file – syntax  Crontab Example  Crontab Environment  Disable Email  Generate log file for crontab activity

Error 81015 when logging into DataStage

Unable to connect to host error 81015 when logging into IBM InfoSphere DataStage (DS): Failed to connect to host: <hostname>, project: UV  (The connection has timed out (81015)) 

dsenv file in DataStage

The WebSphere DataStage server has a centralized file for storing environment variables called  dsenv  in $DSHOME. $DSHOME identifies the WebSphere DataStage installation directory. The default directory is /opt/IBM/InformationServer/Server/DSEngine. You might need to add new environment variables as you configure WebSphere DataStage to connect to different databases using plug-ins or ODBC drivers. Any environment variables you need for interactive use of ODBC drivers to make a connection to an ODBC data source must be added to the  dsenv  file. This lets the WebSphere DataStage server inherit the proper environment for ODBC connections. For a connection using a wire protocol driver, there are no changes required to dsenv.

Cleaning the DataStage Server

Below are the list of the things you will have to do to safely clean and restart your server. The first task (in UNIX and WINDOWS) that you will have to perform is to stop the Datastage services.  The services that have to be stopped are the dsrpc service,  dstelnet service, DSEngine service,  ASBAgent service and Logging Agent service.  

Setting environment variables for the parallel engine in DataStage

Setting environment variables for the parallel engine in DataStage You set environment variables to ensure smooth operation of the parallel engine. Environment variables are set on a per-project basis from the Administrator client. Procedure 1. Click Start > All Programs > IBM Information Server > IBM InfoSphere DataStage and QualityStage Administrator, and log in to the Administrator client. 2. Click the Project tab, and select a project. 3. Click Properties. 4. On the General tab, click Environment. 5. Set the values for the environment variables as necessary.   Environment variables for the parallel engine Set the listed environment variables depending on whether your environment meets the conditions stated in each variable.