DSXchange

How about that:
1. Create flat file of 96 rows with time slot values.
2. Load your file (the file with missing time slots) to hash file.
3. Lookup row in hash file.
Match found: move values from hash.
Match not found: move defaults (zeroes).

If you run it manually you will set Invocation ID. If you run it using dsjob then you can use PID ($$) for it.

That how I did it: We have a script that: 1. Checks if hash file is in VOC. 2. If not then creates the VOC entry on a fly. 3. The gouv and runs SELECT COUNT(*) FROM filename. 4. Then if the VOC entry was added then it is deleted 5. Exit UV and script. I copied this script and replaced SELECT in step...

kduke wrote:Are you in the project directory?

No. I am in my directry on UNIX.
But I woud like to be able to execute it in the DS director usin job control as it was suggested before, not at prompt.

Some how it is doing something that it cannot recover from so you are not getting good error messages. Do the same command at the UNIX prompt but be in the project directory. See what happens. In my previous posting I've shown the result of the UNIX execution at prompt. $ whence clear.file /dsadm/A...

If the last 2 lines are not in the log then you are failing hard meaning you are probably core dumping. Your hash file may be corrupt or your filepath is bad or you need to quote it properly. If there is a space in this filepath then you could be clearing a directory or something other than what yo...

So, you have no idea what the error message is? :? Have you tried Resetting the job via the Director? Sometimes that will get you some additional information labelled as "From previous run". No I have not. :oops: I did it now. Still not getting much: From previous run DataStage Job 2741 P...

sys="UNIX" Command="/dsadm/Ascential/DataStage/DSEngine/bin/clear.file ":fullHashFilepathname *Command = "ls -l ":fullHashFilepathname Call DSLogInfo("System: ":sys, "") Call DSLogInfo("Command: ":Command, "") Call DSExecute(sys,...

Hi Ray, --------------------------- CLEAR.FILE will work via ExecTCL only if the hashed file was created in an account. If the hashed file was created in a directory you need the operating system variant (clear.file) with the pathname of the hashed file. Code: $DSHOME/bin/clear.file pathname execut...

CLEAR.FILE will work via ExecTCL only if the hashed file was created in an account. If the hashed file was created in a directory you need the operating system variant (clear.file) with the pathname of the hashed file. $DSHOME/bin/clear.file pathname executed via ExecSH (for UNIX) or ExecDOS (for W...

After doing the straight value, the output came in this format: 7385-10-08 Do not code any conversion in derivation, just bring the value over to new field unchanged.[/img] That is what I did. DATE1 --> DATE1 I brought the value over with no derivations at all. It is because the char to date data t...

phillip.small wrote: After doing the straight value, the output came in this format: 7385-10-08

Do not code any conversion in derivation, just bring the value over to new field unchanged.[/img]

The input data type is a character and I am converting it to a date column in this format (YYYYMMDD). However, the OCONV function still put the dashes in the output. I do not want the dashes in the table. That is what I am trying to do. Also the DIGITS function output looks like this: 9811-06-11) s...

Trim (string,character [ ,option] ) option specifies the type of trim operation and can be one of the following: L Removes leading occurrences of character. T Removes trailing occurrences of character. B Removes leading and trailing occurrences of character. R Removes leading and trailing occurrence...

phillip.small wrote: The input is coming from character field like this:

20041030

So what are you converting into what?
20041030 to 20041030?