DSXchange

Looks to me that you need to add the directory where the gzip executable resides to the PATH environment variable in $DSHOME/dsenv.

The dsenv file is used by every DataStage process to initialize its environment.

Provided that there are no "quoted quote characters", you can simply use Convert() function. Convert('"', '', TheQuotedString) Another technique is to remove the first and final characters using a substring technique. TheQuotedString[2,Len(TheQuotedString)-2] You may need to tri...

The Multiple Job Compile tool allows you to be selective about which jobs to compile. For example, you can select only uncompiled jobs.

While it's not clear directly how to select aborted jobs in this tool, I think it's worth investigating.

Just regular maintenance to make sure it never fills (we broadcast any "disk 75% full" alarm to all DataStage developers every 15 minutes!) and ensure that any likely user has write permission. The UVTEMP directory can be used for lots of things, but should in general have any temporary files delete...

Perhaps a before-job subroutine to write the header, then your Sequential File stage appends to the existing file.

Unfortunately the DataStage documentation tool does not pick up job sequences, and this tool is being phased out in the expectation that you'll use MetaStage. Even more unfortunately, MetaStage does not produce the kind of report you require. I'd suggest exporting in XML format, then selectively par...

You can change (set) the values of job parameters when requesting a job run. Once the job has started you can not legally change the value of a job parameter. At least one hack has been posted here that allows it to be done; there's a strong chance that that hack will not work in the next major rele...

You can also export via MetaBrokers, especially to a MetaStage hub, from where other MetaBrokers can import into other tools, such as CASE tools and BI tools.

No.

There are too many variables, such as row size, that you haven't revealed.

You won't do it in seconds, but it won't take days either.

The fundamental requirement is to get the table name correct!

SELECT TIMESTAMP, SEVERITY, FULL.TEXT FROM RT_LOG26 ;

All DataStage processes run as "phantoms" (which is DataStage-speak for background processes), with stdout and stderr redirected to a file in the &PH& subdirectory in your project (on the server). It is in there that you will find the output from any PRINT statement. In general use of these statemen...

You need to differentiate between the number of rows that were sent to the database by DataStage and the number of rows that were actually inserted, updated, rejected by the database server. To achieve this your inserts and updates should be on separate links, driven by a lookup against (a copy of) ...

No, unless /apps/dsadm/Vinod is the pathname of a project directory, and even then you can not without SETFILE. Because the hashed file was not created in an account (project), there is no entry for it in the vocabulary of DataStage (a special hashed file called VOC). You can create an entry in the ...

That message indicates that the help file (STPgui.hlp) can not be found in any expected location. The usual expected location is the DataStage client directory (C:\Program Files\Ascential\DataStage). It (the help file) may not have been installed. There have been instances of help files being left o...

Was "balmy" a misprint?