DSXchange

Attu, this is a very common error message and has been discussed several times in this forum, try using an exact search for the string "Exporting nullable field without null handling properties" and you will get 25 hits. This happens when DS has a nullable field going to an output which either isn't...

Write the field to a sequential file using a space as the line terminator, then read this sequential file again using one column and space as the line terminator and you will read in each word as a distinct row, which you can then use to populate your table. For performance you can specify that this...

You shouldn't be using SUBSTRINGS function, that is specifically for dynamic array strings. Use the format Link_SecuentialFile.Date[1,4] instead. If you still have a problem, try replacing the hashed file with a sequential file, and also add in a column containing the original varchar column to see ...

I had the same issue a while ago and couldn't get PX to parse a variable length date format. So what I ended up doing was writing a server job to parse the date and output that to named pipe, which was used as input by the PX job.

Operating system are usually backwards compatible, so there should be no reason that I can think of why this won't work. But IBM/Ascential won't support it if anything does go wrong since 5.2 is no longer in the support matrix.

I cannot recall the exact conditions, I'd have to look at the documentation to get those values.

Are you loading other files to memory in the same job? If yes, and you don't preload them, does the original file load without having to resort to the heap?

tutul - I'm sorry about my post earlier, I was off dreaming and thought that the maximum memory for file buffering was set in the uvconfig file; while it is actually a setting that is done in the Administrator and tunables tab. I'm not at a system with DS right now, but I seem to remember you also n...

There is no single function that does this, but with PX you won't need to check, since you can use the reject link on the database stage to ensure that no records are dropped.

Srimitta, do you now understand why all the other posters are asking you for your definition of "years"? I posted my snippet knowing that it would be incorrect, but at least it did require you to define in more detail what you need. If you use ICONV() on both dates the difference between them will b...

The error messages look odd.

What options are you using when calling the job from the sequence? Have you thought about using the "reset then run@ option so you don't need to explicitly reset the job?

Srimitta,

it looks like you haven't experimented yet, but what would be wrong with:

It would seem that either your hashed file is larger than the 999Mb you specified, or that this value isn't being used at runtime. Are you sure that you ran uvregen after changing your configuration file? Use "smat -t" to see what your current values are.

The Designer (as well as the manager, director and administrator) are all PC-client based tools and have no UNIX server versions. Some of the actions and commands can be run from the command line, but none of the designer functionality is available outside of the graphical interface.

Does that mean you can login using the Designer/Director/Manager/Administrator using your admin account, but get the error message when trying to login as a DataStage user?

The ICONV function has several options that can convert the data appropriately, depending upon your definition of "year" as noted in Craig's post. You can convert the date into the internal format (using the 10 character substring and format of "D4/MDY" and then use the difference in days or just us...