Guru Of Geeks

Following are unix process list for a healthy DS system (Engine + Services + Metadata repository)

Problem When trying to open a job in Designer client in DataStage (DS), message indicates the job is locked by another user.

There are Three methods to unlock the DataStage jobs: –  Using DataStage Administrator Tool.   –  Using UV Utility   –  Using DataStage Director

The Only difference is : Scratch Disk is for Temporary storage (Like RAM in our PC) Ex : Files created during the process between the source and targtet such as Sort,Remove duplicate,Aggregator etc.. Resource Scratch Disk is for Permanent storage (like a Hard Drice in our PC)

DataStage Error:   Job xxx is being accessed by another user    Take below steps to get rid of locks in datastage -- In web console check active sessions and if job is listed disconnect session. To view all active sessions: In the Web console, click the Administration tab. In the Navigation pane, select Session Management > Active Sessions The Active Sessions pane shows the users that are currently connected to the server.

Following are unix process list for a healthy DS system (Engine + Services + Metadata repository)

Location of command: UNIX: /opt/IBM/InformationServer/Clients/istools/cli Windows: IBM\InformationServer\Clients\istools\cli

When attempting to open a job log in Director, user gets the following error message: Error selecting from log file RT_LOG### Error was: Unable to open DICT 'RT_LOG###'. This is because the D_RT_LOG file is missing from the projects directory.

Orchadmin is a command line utility provided by datastage to research on data sets. The general callable format is :  $orchadmin <command> [options] [descriptor file] 1. Before using orchadmin, you should make sure that either the working directory or the $APT_ORCHHOME/etc  contains the file “config.apt” OR The environment variable $APT_CONFIG_FILE  should be defined for your session.

What can you delete to free up disk space in IBM InfoSphere Information Server when disks are becoming full? What to do ???? Here are some things you can do to clean up space: Clear the &PH& file in the Project directory. There is a &PH& directory in each DataStage project directory, which contains information about active stages that is used for diagnostic purposes. The &PH& directory is added to every time a job is run, and needs periodic cleaning out. To clear the file from within DataStage: Ensure there are no DataStage jobs running anywhere on the system by running "ps -ef | grep dsrpc" From the DataStage Administrator, go to the Projects page, select the project whose file you want to clear and click the Command button. The Command Interface dialog box opens. Type the following into the command field: CLEAR.FILE &PH& (all uppercase) Click Execute to run the command and clear the file. For additional information, go to  Command ...

How should we manage cleaning up the &PH& directories for my DataStage projects? Can the process be automated? Files in the  &PH&  directories under DataStage project directories store runtime information when jobs are run and need to be cleared out periodically.  

When a DataStage job with a lookup stage aborts, there may be lookuptable files left in the resource directories and they will consume space. The filenames are similar to "lookuptable.20091210.513biba" When a job aborts it leaves the temporary files for postmortem review in the resource directories. Usually that is done in scratch, however, for lookup files, they are created in resource. Lookup filesets will not go away, just like regular datasets.

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

General Job Administration APT_CHECKPOINT_DIR APT_CLOBBER_OUTPUT APT_CONFIG_FILE APT_DISABLE_COMBINATION APT_EXECUTION_MODE APT_ORCHHOME APT_STARTUP_SCRIPT APT_NO_STARTUP_SCRIPT APT_STARTUP_STATUS APT_THIN_SCORE

    While attempting to compile job,  “failed to invoke GenRunTime using Phantom process helper” RC:      /tmp space might be full            Job status is incorrect            Format problems with projects uvodbc.config file

     While running ./NodeAgents.sh start command... getting the following error: “LoggingAgent.sh process stopped unexpectedly”

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.

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)) 

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.

API error codes in numerical order Code Error Token Description 0 DSJE_NOERROR No  InfoSphere DataStage  API error has occurred . -1 DSJE_BADHANDLE Invalid  JobHandle . -2 DSJE_BADSTATE Job is not in the right state (compiled, not running). -3 DSJE_BADPARAM ParamName  is not a parameter name in the job. -4 DSJE_BADVALUE Invalid  MaxNumber  value. -5 DSJE_BADTYPE Information or event type was unrecognized. -6 DSJE_WRONGJOB Job for this  JobHandle  was not started from a call to  DSRunJob  by the current process. -7 DSJE_BADSTAGE StageName  does not refer to a known stage in the job. -8 DSJE_NOTINSTAGE Internal engine error. -9 DSJE_BADLINK LinkName  does not refer to a known link for the stage in question. -10 DSJE_JOBLOCKED The job is locked by another process. -11 DSJE_JOBDELETED The job has been deleted. -12 DSJE_BADNAME Invalid project name. -13 DSJE_BADTIME Invalid  StartTime  or  EndTime ...