DSXchange

If you do a CLEAR.FILE and then a "RESIZE {fname} * * *" the OVER.30 will also get set back to it's original size. If you have a MINIMUM.MODULO set your files will not shrink to a couple of Kb, either.

I might have to, but with a requirement of 500 rows per second (very big rows) it might not have the oomph necessary and certainly won't scale. I might need to play around with string conversion and manual checking for this column; but I'm still hoping that the solution is getting a simple syntax fr...

I don't recall where I got that syntax from, since the Developer's Guide description of IsValid() only hints at a format string. It is nasty that neither the docs nor the Orchestrate manuals contain any description on how to do this. I would normally change the default date format for the job, but w...

Trammohan = "2007400" has a length of 7, so does "2x0x4x0".

Ray - I tried that as well yesterday, the runtime message states

Parsing parameters for schema type "date": Expected "[" or EOF; got: "%"

", so all of my further tests had the open square bracket.

What error does it "throw" at compile time?

Also, check for NULL before doing any computations on the field.

trammohan - of course that works. Now use "2008400" or "200805". The whole point is to avoid errors and warning in the StringToDate() function by using IsValid().

No, in my case the dates are formated as strings like "2008032" (for Feb 1, 2008) and therefore I need to use a non-default date format for the IsValid() function and it seems that the functionality is supported, but nobody seems to know what the correct syntax is for the first parameter.

In the DB2 stage you include job parameter values in the SQL query, so you could pass the appropriate query in at runtime.

Umm, that defeats the whole purpose of using IsValid() in the first place - if you can successfully convert the string to a date then IsValid() will always be true. And if the string is an invalid format, then you get the error message that you are using IsValid() to avoid in the first place.

I have a VarChar(7) column containing a date in YYYYddd format, i.e. "2008234" which can be parsed using StringToDate(In.Col,"%yyyy%ddd"). Unfortunately, there are rows that contain invalid values. According to the documentation, the derivation IsValid('date [%yyyy%ddd]',In.Col) should retur...

That means somewhere in your job you are converting from a fixed length CHAR field to a VarChar and are getting those ^Zs

What load method are you using and are these VarChar2 columns?

By default the read-only objects are not exported. When you specify your export you can include read-only objects and they will be exported. Your production project is probably protected, which is why you are getting this large amount of skipped objects.

APT_STRING_PAD_CHAR

That means that the DataStage engine is running, but the path that the projects are supposed to be in are invalid or missing key files.