DSXchange

Determine if it's server or client related. If other PC's have the same problem - it's server. If it's your PC only, determine if it's project related or global. Let us know which.

Now go and release all the job locks left on the jobs you had open.

whooaa dude, that is far out

But absolutely true.

Krazykoolrohit wrote:use the iconv and oconv functions to convert. check datastage help for usage

No. ICONV and OCONV work on integer days, not seconds. The time conversions don't include date components. You must write a custom function.

I suppose you could take your EPOCH value, divide it by 86400 (the number of seconds in a day) to get the whole number of days in the date. The DS BASIC internal date starts at 1 on January 1, 1968. So, you can work out the equation necessary to compute the date value you need. Then, take the number...

No, your date is EPOCH, the number of seconds since Jan 1, 1970. I don't know if we've got one of those.

Look at the final message on this post from DSGuru2B:

http://www.dsxchange.com/viewtopic.php? ... t=add+date

You mean Greenwich Mean Time? Are you asking how to add X hours to a date time to make it local to your standard? Write a DS function, search the forum, there's lots of examples.

Hey, around version 5 if you spooled the same value, say 123.456, to two identical columns in a Sequential file, one with scale of 3 and the other scale of 0, you would get the same value (123.456). However, if you added 0 to the scale 0 column, you'd get 123. Only performing a math operation caused...

Folks, the issue is that a text block contains trailing CR/LF that the poster wishs "trimmed". It has nothing to do with anything other than prettying up a column. As a piece of etiquette, it probably behooves anyone responding to a poster to read every reply, not just the last one. Then, replies wi...

Phantom errors occur when DS BASIC errors send messges to stdout, and since Server jobs don't have a screen component those messages are caught and return as "phantom" errors. Phantom is just the name of the background program used in DS Server to manage a task. The most common messages are variable...

Welcome aboard. What data types are in your target table that aren't CHAR, VARCHAR, INTEGER, DATE, TIMESTAMP?

Not a single job can run? Try creating just a Batch job from Director to do nothing. How about "CALL DSLogInfo("Hello World", "Msg"). If that job can't run from Director you have something seriously wrong. Try each project to see if it's a project or server-wide issue. If that job works, we're shoot...

1. Job scheduling to avoid conflicts 2. Locking mechanisms (such as lock a row in a table for update during the duration of the Routine call, if another job calls the routine it will stall until it can get the lock) Why are there issues with the same file? Are you writing to a file in a Routine? Hop...

Since you're Server, you don't have PX datasets. You will want to purge job logs and remove errant/retire hashed files and sequential files created within your project.