DSXchange

DataStage will always issue a commit when a stage is completed.

1000% is a very high number, and certainly more than the free buffer size can use.

Any memory used by DataStage jobs is always returned to the OS when the jobs finish. This has nothing to do with DataStage, but with how UNIX works - once a process completes and logs out, any and all memory is released. It is unlikely that such a serious memory leak exists, particularly on AIX. The...

There are many possibilities here. A lot depends upon your definition of "encrypt". Does it need to be secure against active penetration or just against casual observation. You could either put in a simple transcription which could obfuscate the data or add in a call to do actual encryptio...

Does the file exist and, if so, does the user executing the job have sufficient access rights to delete the file?

Try identifying one process and doing a "truss" on it to see which (if any) system calls are being generated.

The thing is that "$temp$" is not a valid jobname, and this error is detected within the DSR_LOADSTRING routine.

Nobody answered since the post was marked as "resolved". This is not easy, since hashed files can be utilized by name or by path. If all references are by name or all uses of the hashed file are done by using the same metadata columns then one can search from within the tool. Otherwise a p...

It is greyed out in the admin program if you aren't the administrator. You can look into the "uvconfig" file to get the system NLS settings. Look for "NLSMODE" to see if NLS is activated.

It looks like your script has a "$temp$" string that is not being resolved. I don't think that jobs names can contain a "$" sign but can't check that right now.

Normally through the NLS tab in the Administrator. What specifically are you looking to find out?

Yes, there are other ways. All involve sorting the data. The Sort can remove duplicate rows and you can use stage variables in a transform stage to detect duplicate column values and drop those rows.

In addition to what Ray has said, how are you determining that the characters read in a "junk" (hint: don't use "View Data" to determine this)?

You would need to answer Srini's question in order to get a good answer. Basically, stage variables are used to store values from the previous row and compare them to the current row. You would compare those columns you wish to detect duplicates on and, using constraints, skip rows with duplicates. ...

Stage variables will work but you would also need to sort the data.