DSXchange

Ray - normally that happens in DS when you have a composite key, the @TM inserted by DS tends to display as separate lines.

No builtin PX equivalent to the "MCP" code of Iconv/Oconv.

The first error with a failed write to a Hashed file is most likely caused by the file exceeding the approximate 2Gb limitations. Can you check the size of this file (if it is a default dynamic file, then the file will actually be a directory with 2 visible and one hidden file, the DATA.30 file is m...

Welcome to DSXChange. You will find you get quicker answers when you post in the correct forum. You can use the TRIM function to do this, with TRIM(In.ColumnName,'"','A') or CONVERT('"','',In.ColumnName)

You can either re-import the copybook (recommended) or manually make the changes in the manager to the definitions when your metadata changes.

Unfortunately there is no automated import mechanism for metadata along the lines you are talking about.

Columns 72-80 are considered comments in Cobol (historically you had line numbers there). If column 7 has a * then the line is also considered a comment and is ignored.

In the manager you can do Import -> Table Definitions -> Cobol File Definitions.

The less data is read/written or touched the faster a job will perform. Declaring a char(120) column when the data length is only char(11) means that over 10x as many bytes are processed as necessary. This increase in data may or may not affect performance, but the overall load on a system will be r...

I looked at the formula on Wikipedia and it wasn't too bad, so I wrote: ************************************************************************* ** accept a delimited string of values to and a standard deviation. ** ** is started. ** ** ** ** Ver. Date Author Comments ** ** ===== ========== =======...

I would very much like to calculate standard deviation inside a DataStage job and/or a DataStage function. Has anyone here either written such a function or have any recommendations on how to achieve this?

I know I can do this in Excel but I would like to keep this contained inside a DataStage job.

Ok, then either use a stage variable ShortString = TRIM(IN.String) or do as before:

FIELD(Trim(In.String),' ',1) = fname, FIELD(Trim(In.String),' ',2) = middlei, FIELD(Trim(In.String),' ',3) = lname, FIELD(Trim(In.String),' ',4) = Suffix

...ds_ipcflush() - Error in mutex_unlock() - Not owner... This message is unfortunately not particularly help. When one side of the pipe terminates and the other side can no longer communicate you get this error by the surviving process. So this is just reporting that your job has terminated and is...

Umm.. no need to check /tmp for space - I only pointed out the last part of the error message for brevity's sake. The whole line reads

/app/dsadm/Ascential/DataStage/Projects/ReDSTest/RT_BP3440.O/V55S3_rds_iex_agent_loginout_data_string_to_decimal.tmp.o : No space left on device

Are there always the same number of fields? If so, then FIELD(In.String,' ',1) = fname, FIELD(In.String,' ',2) = middlei, FIELD(In.String,' ',3) = lname, FIELD(In.String,' ',4) = Suffix.

Are you sure this column is actually present in the DataSet's schema? Look at the schema using the "Dataset management" tab to make sure. Perhaps you could post that schema on this thread.