DSXchange

Roy, I am changing some test jobs right now to see about the lookup file sets; I gather I do need to make sure that the column names in the lookup file set and in the main data stream are the same so that the lookup will function, but I haven't seen any other modifications that I need to make. p.s. ...

I am trying to figure out the salient differences and inherent advantages/disadvantages between choosing to use a data set or a lookup file set in my job. I currently create a rather large DataSet.ds and later use a Lookup stage to do a lookup on this .ds file; this file is not used for anything els...

J - that means that the command works if you remove the Oracle Open 'DELETE FROM #GDSSSchemaOrcl#.T1_NDS_OFF_LINKS'?

What if you replaced the parameter in the open command with the Oracle schema name directly ? (perhaps that part of the command doesn't parse parameters correctly)

HSBC, the information about the separate instances of a job run are stored in the master job log file; so when you do a reset of the master job you are going to affect all of the instances (specifically in your case because the files are still noted as "running"). Normally, you can reset individual ...

snassimr, in your derivation delete the DSLink11.Key and then use the insert-column function to put it back in. Also, I am assuming that your stage variable is called "Last" and your derivation simply reads "DSLink11.Key" without the "Last =" part. Sometime when you change the name of link the subse...

snassimr,

if you could not cleanly and elegantly get rid of the jobs I would (once again) recommend restarting the DataStage engine instead of trying to master the complexities of DataStage lock and process management.

snassimr, the format for a column name is LinkName.ColumnName ; and it looks like all you specified is the LinkName portion. You can re-do your derivation and use the drop-down list to get a valid column name if you wish. Also, your derivation should be in red, showing you have a syntax error in the...

Madhav, this is a very practicable and intelligent approach, it makes sense to use a parameter for any value that can or will change in the future, and by using the path to a source file as a parameter you ensure this. Also, if you make a multi-instance job and your target is a database you can run ...

dsquestion,

the most common and likely cause for this problem is that your datastage engine is not running. If you telnet to your server and do a "ps -ef | grep ds" you should see a couple of processes such as "dsapi_slave", and a root process onto ...dsrpcd

kww, editing the VOC is not difficult to do, but you can easily corrupt your account if you are not careful. The IBM pages also have a PDF document on the UniVerse EDitor; but you have the general command syntax already - ED <filename> <recordname>. Once in the EDitor you can type HELP to get a list...

Hello madhukar,

with Px you can either use the filter command to run it through the shell script or command of your choice, or you can read the empty row and then remove it from the output stream with a filter stage, or a transform stage, or a modify stage.

dsxdev, in this case the UNIX/Windoze process is most likely already gone; what is stopping snassmir from continuing is an internal DataStage lock that has survived (either the job aborting or someone doing an OS level kill). Either let the daemon clear it in time or restart the services unless you ...

blewip - thanks for the concise post at the end of this thread - I think that not only I but others will learn from the results! (I hate it when a problem posting just ends with a "I solved it" and no solution description. The floating point problems are truly universal - I've seen them in various a...

snassimr, if you go into your Director and look at the drop-down-menu Job -> Cleanup Resources. It might be greyed-out, in which case your administrator would have to activate that option from within the DataStage administrator. I would think that there is a lock daemon running, which should remove ...

Roy, Oracle tells Px that data was rejected or at least not written and it's up to the Px/DataStage engine to transmit that to the log file or wherever. I did ask the DBA and was told that there was nothing that could be done from that side. I added a transform with a warning message when links go d...