DSXchange

... which is why I included "four digit year" in my specification.

What's different about the new environment that might be causing slowness? (Clearly "nothing" is not the correct answer.)

OK, you have two questions to answer. One can be a constraint expression.
(1) Is the incoming string valid as a timestamp with a four digit year (IsValid() function)?
(2) Convert the string to a timestamp then extract the time portion, or extract the time portion and convert it to a time data type.

Was the 7.5 version created with the 64BIT option (not available through the Hashed File stage)?

What is the data type of the source field? Where are you reading it from?

Are the hashed files identically sized in each environment?

Assuming there is a VOC pointer for the hashed file, you can use the command ANALYZE.FILE hashedfilename STATS to determine the current sizing.

Hashed File Calculator (hfc.exe) is provided on your installation media in a directory called Utilities, in a sub-directory called Unsupported.

Whenever you see "library could not be loaded" error messages check that the library's parent directory is included in the shared library search list (typically the LD_LIBRARY_PATH or LIBPATH environment variable) and that the executing user has execute permission for that library. If you'...

TimestampToTime() function requires no format string. It requires that the input is a timestamp (not a string).

If your input is a string, use the Field() function to isolate the time component and StringToTime() to convert the format.

oacvb wrote:We are currently using DataStage Version 8.5 with Fix Pack 1.

As far as I can recall version 8.5 is up to Fix Pack 4.

There is an environment variable that allows the otherwise illegal situation of all zero bits in a decimal data type.

Are you SURE you've created a server job? The term "schema" is not normally used in the context of a server job.

You would use a totally different approach in a parallel job - namely a Row Generator stage.

What is this fetish everyone seems to have with generic jobs for every circumstance?!! :roll: If you need to transform a column you need to name that column. Therefore you will need at least some of the metadata for that job. Using a Modify stage this can be fully parameterised, but it must still be...

I don't believe U (one of our posters from Singapore) would care. The second person personal pronoun is spelled "you" and, in its possessive form, "your". DSXchange is not a mobile phone; there is no need to use SMS abbreviations, as there is no practical limit to the number of c...

Nor will the schedule show up in Director unless the job was actually scheduled from there. For example, if you are using a third party scheduler, such as AutoSys, then the Director client has no knowledge of this; you must use the third party tool to view the schedule.