Guru Of Geeks

Osh is interactive admin utility in datastage 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: APT_ORCHHOME  should point to Parallel Engine location APT_CONFIG_FILE  should point to a configuration file 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. Here is an example on how to set these variables for Unix or Linux environments:      APT_ORCHHOME=/IBM/InformationServer/Server/PXEng...

IBM Information Server is a client-server architecture made up of client-based design, administration, and operation tools that access a set of server-based data integration capabilities through a common services layer as shown here in  below Figure 1-2.  In this section, we briefly discuss the following topics: 1. Component overview 2. Topologies supported 1.2.1 Component overview The main components shown in Figure 1-2 are briefly described here. 1.2.1.1 Client tier : IBM Information Server provides a number of client interfaces, optimized to different user roles within an organization. The clients tier includes IBM InfoSphere DataStage and QualityStage clients (Administrator, Designer, and Director), IBM Information Server console, and IBM Information Server Web console. There are two broad categories of clients —  Administrative clients and User clients . Both these types of clients have desktop and Web based interfaces. 1.   Administrative clients These clients allow you to manage...

 " ACCESS DENIED: Project currently locked. The project is currently locked by the Administrator. Try again later or see your administrator " But there are some steps that might help you for solving this problems, there are: cd to $DSHOME (/opt/IBM/InformationServer/Server/DSEngine in Linux or equivalent) Edit the uvconfig file and change the following settings: MFILES=64, T30FILE=512, GLTABSZ=100 and RLTABSZ=100 Source dsenv if necessary (execute ". dsenv") Stop the DSEngine by executing "bin/uv -admin -stop" Apply the configuration changes by executing "bin/uvregen" Start the DSEngine by executing "bin/uv -admin -start"

If you got this error: main_program: Fatal Error: Service table transmission failed for <Node Machine> (<Node Machine>:Broken pipe.  This may indicate a network problem. Setting APT_PM_CONDUCTOR_TIMEOUT to a larger value (when unset, it defaults to 60) may alleviate this problem. You can resolve the problem with increasing the value of APT_PM_CONDUCTOR_TIMEOUT with add it into User Defined Variable at Project Environment Variable. The steps are: Open DataStage Administrator Client Choose your Project Name Click Properties Button Click Environment Button Add APT_PM_CONDUCTOR_TIMEOUT into User Defined Variable Set the value

​To Generate DataStage Log File from UNIX, you can use dsjob syntax. dsjob syntax: dsjob -logdetail               {Server_Name}               {Job_Name}                `dsjob -logsum -type {Type} -max 2 {Server_Name} {Job_Name}|cut -f1` > {Destination File}.txt Notes: {Type} = [ <INFO | WARNING | FATAL | REJECT | STARTED | RESET | BATCH>] ​

This syntax is used to generating job info status from a job: dsjob -jobinfo                   ${SERVER_NAME}                   ${JOB_NAME} > ${OUTPUT_DIRECTORY}.txt

DataStage Designer appear to hang when it tries to display a stage using invalid screen coordinates. This will happen every time you try to open a particular kind of stage. The solution is to remove the saved screen coordinates from the Windows Registry. Close the Designer. Use regedit to delete this key (and its subkeys): HKEY_CURRENT_USER                    > Software                            >  Ascential Software                                    >  DataStage Client                                             >  Designer Then open a new Designer and test.