DSXchange

you can do a "rm -r \&PH\&" and so on for the other folders. These 3 contain the job run (phantom) stdout, saved select lists and other commands, and saved stdout redirects - none of which are crucial to runs. I wonder why they were not deleted in the first place, perhaps due to permissions.

Ranga, good approach, but in this case any write would cause the failure, and it seems that only a specific record is failing. My gut feeling is that there is a @FM or @VM in the key field which is causing the failure, but that doesn't explain the sporadicity (yes, that word does not exist in the di...

The "phantom" is an archaic term (coming from the UniVerse implementation on PRIMOS) which just means a background process, i.e. one not associated with a terminal/keyboard.

The PHantom processes and not the launching process are the ones actually doing the work, so they hold the locks.

I forgot to add you should look for "WinEMACS download" in Google or your favorite search engine to get a number of sites where you can get this package.

Venkat, I think EMACS might be overkill, it is a very powerful (but old) editor. You really should not write a shell script for this if you have DataStage. A simple job to read the .dsx file, do an EREPLACE() of your {search} and {replace} texts in a simple transform and write it to an output file. ...

Venkat, as Sreenivasulu has stated, the .DSX files are text (even the binary object code is UUencoded to displayable characters. Thus you can do all of your changes in the editor of your choice. I like EMACS (free dowloads available) which allows you to write quite nifty macros. You can also use VI ...

ml,

the CCSID doesn't ring a bell, but the 1252 and 937 are codesets (1252 is Windows Latin codepages, and 937 is traditional Chinese).

Do you have NLS enabled in DataStage or in the database?

Benny,

the DEADLOCK.MENU item lets you do some things with the deadlock daemon, but you need to be an Admin to access it and it should be automatically started at boot time. Usually the default 15 minutes are sufficient.

Kollurianu, the best and 100% guaranteed method is to do a String1=String2 comparison. But if the string is 500 characters long it sometimes makes sense to store a short CRC32'd string instead of the original and then do a comparison on the smaller value. The upside is drastically less storage space...

Yes, you can use stage variables in the transformer constraints.

Use an unsigned and declare it as PIC 9(6) COMP-3; then ensure you put the leading zeroes into the string.

Make the acutal key to your Hash file an uppercase name, create a temporary column in your job with the uppercase lookup name and use that as the lookup key to your hash file.

If you don't want the sign then declare as an unsigned COMP-3, but yes, the basic idea is to use the overlay mechanism.

Jack_dcy, doing a UNIX kill is not a good idea in DataStage, especially if you let slip a kill -9 . Killing processes from the command line can leave locks hanging around that are not cleared (even with the uvdlockd running) and at worst might require a DataStage server restart to get going again.

Benny, my point is that your method takes whatever bit representation the COMP-3 field is using an breaks that up into PIC(X) without any conversion at all. So, if you were to "fake" your input or output metadata to state that this is a CHAR field (and turning off EBCDIC/ASCII conversion) you will g...