DSXchange

Kumar - UNLOCK ALL as administrator is very powerful and should not be used! It has a potential to really mess up a DS environment since all concurrency control in DataStage is based on locks. In this case if no jobs are running and no users are logged in the appropriate lock(s) should be easy to sp...

Unless you can define your source string type to be the same length or shorter than the output the PX system will always give you the informational warning and your only option is to use the message handler to demote or remove the warning.

Have you tried using embedded functions? I got a runtime fatal error with string_trim(string_trim(In.Col)) in a modify stage and couldn't see anything in the docs or on this site about using multiple functions.

You can try to clear the log file from the director; this might get rid of the data error, otherwise exporting the job, deleting it from the repository and re-importing should work.

You can set up message handlers and deprecate this warning message to an informational one or even remove it from the log completely (not a good idea, in my opinion).

Vincent - thanks for helping to confirm that it can't directly be done in a modify stage. I like your approach, even my positive numbers have a space in that first position - I tried using decimal_from_string(string_trim(In.Col)) yesterday but it would seem that the modify stage only likes single fu...

Let's see: (a) your routine stop running with an "abort". (b) You have 2 abort statements in your routine. Try putting in ON ERROR and getting the STATUS() and printing it out with a call to DSLogWarn() to see why you are getting a failed open or read. This is also logically the place in the program...

The product ships with a tutorial as well which can help learn the basics.

The message comes because there is a lock on a table record fro that job. If another user is editing the job, if it is running or if a monitor is open this is the message you will see. One other cause is if the job has somehow aborted or been killed so that the locks remain. If this is the case then...

Are you referring to the category of a job? If so, the category is not part of the job name, it is a display attribute used for grouping in the client tools. If this isn't what you meant, please explain what you mean by "moving" a job.

I have a string in the format "- 123.45" which I would like to change to decimal[15,2] without using a transform stage. Since there are spaces between the sign and the number the normal conversion to decimal_from_string will fail. The TRIM({string},' ','A') function in the transform stage to remove ...

From this thread you will have seen 2 places in the engine which might prevent an account from being re-used. The first is an entry in the UV.ACCOUNT file and the other is an entry in the UV_SCHEMA. Does your bad project exist in the UV_SCHEMA file (LIST UV_SCHEMA {projectname})?

If a job was created with a userid that had an incorrect umask setting, the it might be possible for one user to open and work with a job while others cannot.

1. Write a temporary DS job copy of your original to write just the 3 key columns to a sequential file call myfile.txt. 2. wc -l myfile.txt to get the number of lines. 3. sort -u myfile.txt > otherfile.txt 4. wc -l otherfile.txt are the counts in 2 & 4 the same? if you look at otherfile.tx t do ...

Ahh - I missed that; thanks. I thought it might be a connectivity issue.

Latha - are you logging into the Designer with the same userid on your machine (which isn't working) and on the other (which is)? If not, does your userid/login work on the other client PC?