DSXchange

I found 88 matches using the exact term "vertical pivot" and the powerful, yet user-friendly "search" function that can be found in the menu bar above this post. I'll subtract 1 from that total since it also included your post, so you have 87 exact maches and there is a very good chance that your qu...

Approach it from another angle, can you start any UNIX job on a server from a COBOL program? If the answer to that question is 'yes' then you can start DataStage jobs. Your sysop can answer that.

Right.

A piece of string is ALWAYS exactly 42 long. Of course, the units used for measuring are always different.

The default location is a directory called "Configurations" located at $APT_ORCHHOME/../Configurations (or $DSHOME/../Configurations). Note that the configuration file(s) can be located anywhere, their location is specified in jobs using a parameter or the contents of the environment variable APT_CO...

You will need to use a routine to do this, as Craig has already suggested. The reason is that loops are not supported in transform stages, and you will need to loop the conversion statement for each column.

That is complex. If the algorithm would accept "close" values, you could convert the date to a julian one then subtract int(months*30.41666) days from it. Otherwise you will need to write some code.

What stage is generating the error? Could you be lacking write permission to the target directory? Does the error always happen or is it sporadic?

Ray - thanks for catching that; I had forgotten that DataSets will pad out VarChar strings and thus can use significantly more disk storage. We had a case here recently where a VarChar(800) column was used to store 15 characters of data - but for millions of rows. Just changing the data type signifi...

The issue is missing columns and how that affects your data. If a column in the middle is missing DataStage cannot know that, it can only assume that the last column is missing and all the values shift left one position. You probably have your input stage settings so that missing columns are accepte...

Use the FIELD function to parse out your 3 string elements, i.e. FIELD(In.Date,'/',3) to get the year portion. Then format those strings to the correct length since you are getting variable length columns and finally concatenate them to the resulting format.

login as the same user you are running in datastage, then "cd Data/CDH/Scratch" and see if you can do a "touch testme"

If by memory you mean disk space then both are going to use similar amounts of storage. If you mean memory usage while processing the dataset will most likely use more (but run faster) since it will have at least one reader process per node

Keep on reducing the columns until you have one that is causing the abort, then post that.

If the input column in a transforms stage is nullable and the output is not and you handle nulls appropriately you will not get this message. Can you make a copy of the job and remove portions until the error goes away - that way you can narrow down the possible cause.