DSXchange

"2" is a number and not an English word. The "dsjob" command is meant to be executed from your shell, not from the TCL command line.

Try using "CART:string[7]=substring[0,7] (Mat)"

The status of a job's last run is not available in the DS_JOBS or DS_JOBOBJECTS. Here is some code that you can run in a DataStage routine to get the results you wish. Note that this is a quickie program with no error handling and it also will not show any instances, if you have multi-instance jobs ...

No reason to post the same question twice, the answer remains the same

It will have been delivered with the product and if you cannot locate it then you need to contact whomever you purchased DataStage from to get it.

Yes. Use the search function to find out how.

uppalapati2003 - you've now gotten the answer you need - just type in the 150 or so non-displayable CHAR codes (which you can look up on any ASCII chart) for your CONVERT() statement.

<sigh> this why I requested this thread "die" and even posted a link to the other thread so that people could follow it. The CONVERT() function is good, but you would need to explicitly enter a very long function for all the non-displayable characters than need to be transposed to space, i.e. CONVER...

Please do not double-post the same question several times, it won't help you get an answer any faster. In fact it usually has the opposite effect.

the duplicate post can be found here


Moderator - Please delete this duplicate post

MAnoy - in your first post you stated that you delete the HHH and D_HHH from unix using rm. You obviously did not do that. The normal removal of a hashed file from a DataStage job or by using the "DELETE.FILE {filename}" performs 3 actions that you need to do manually if something has gone awry (i.e...

Manoy1 wrote:...Actually, the (delete from VOC where NAME = 'HHH' ) worked.

No, it didn't work, otherwise you wouldn't be getting that error message. Try using 'DELETE VOC HHH' command and make sure the 1 record was deleted.

Craig - I don't know what could be happening on your system; and I guess you don't have the luxury of removing the CPUs and resetting the configuration parameters to see if they really were the cause of your woes. I think that the base shared segment is not removed with a ipcrm -m {segment} call, bu...

This means your

delete from VOC where NAME = 'HHH'

did not work. Try it again or try to remove the VOC entry. After that just use the approved methods in DataStage.

C'mon Craig - that would be far too easy.

Parallel routines are c++ based, Server routines are DS/BASIC based. You can, with a lot of work, make external routines callable directly from DS/BASIC (that includes calling them directly in server jobs) but it involves reloading the DS core and is not undertaken lightly. So even though techinical...

Use an external command stage calling "wc -l /my/file/path/testfile.txt" and check the return value for your size.