Something about DataStage, DataStage Administration, Job Designing,Developing, DataStage troubleshooting, DataStage Installation & Configuration, ETL, DataWareHousing, DB2, Teradata, Oracle and Scripting.
Showing posts with label orchadmin. Show all posts
Showing posts with label orchadmin. Show all posts
Friday, November 14, 2014
Linux Shell session setup for DataStage Command Line
To setup Linux Shell for Datastage command line is very important if you are a DataStage Developer and want to work hassle free on DataStage Command Line.
Follow below steps to setup your profile ---
a) First, we will create .dshome file which is containing the path of DS Engine. If you know what it is, good, create a file in root dir with DS Engine path
otherwise execute below scripts to do it by itself
Labels:
Administration
,
commands
,
DataSet
,
DataStage
,
environment
,
Linux
,
orchadmin
,
profile
,
set
Friday, September 06, 2013
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.
Data sets can be managed using the Data Set
Management tool, invoked from the Tools > Data Set Management menu
option within DataStage Designer (DataStage Manager in the 7.5
releases.) Alternatively, the 'orchadmin' command line program can be
used to perform the same tasks.
The files which store the actual data persist in
the locations identified as resource disks in the configuration files.
These files are named according to the pattern below:
descriptor.user.host.ssss.pppp.nnnn.pid.time.index.random
descriptor.user.host.ssss.pppp.nnnn.pid.time.index.random
Monday, August 05, 2013
Orchadmin Command : DataStage
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.
Subscribe to:
Posts
(
Atom
)