DSXchange

As noted, the first step here is identification as in determining the actual ASCII value of the character. And then the next step is dealing with it properly, which isn't necessarily removal.

Yes. You will need to tell it where each column starts and ends and the name to use as they don't come with column headings.

It's BASIC.

Did you SEARCH? Check the link I posted? Or are we just waiting for Ray to come back and save the day?

We (and you too) need to see the octal or hex values, not their 'display' values. Do an "od -h" (octal dump in hexidecimal) against the file and post it here.

:!: EXAMPLES. Please. All it seems you've confirmed right now is the fact that if the metadata doesn't match the data, the record gets rejected - which as noted is standard expected behavior. Help us help you. Be precise. Show us the FD you are using and what kind of values in what fields are causin...

So... we're still having fun with high/low values? When you say here you are having trouble with a "non-decimal number" in a COMP-3 field you specifically mean HIGH or LOW VALUES? Rather than going a couple of pages like before, can you post examples of these problem values? I for one woul...

Couple of points... are you sure the population of the table hasn't increased between the time you ran the query and you ran the job? Meaning perhaps the source isn't static. I'd also be curious how many nodes your job runs with and if so what partitioning you are using. Lastly, if your source is st...

Search is your friend, found around 30 other posts on this topic or a variation thereof. For example, this should help:

viewtopic.php?t=106690

I'd look at the StringToDate() followed by DateToString() with %ddd for the day on the way back to a string. Then if you need to, convert the final string to a number. Not aware of a way off the top of my head to do this with a single function.

Moved you to the appropriate forum, no clue why this ended up in the 'Enhancement Wish List' forum. Unless you were just making a wish.

If those access methods are supported they can be 'called' from DataStage. The JDBC side would take extra shenanigans because, well... Java. You could always ask your official support provider as well.

The 'HDFS stage' is the Big Data File stage.

Gotcha - the Client is always on Windows but we have to ask what your Server platform is in case it matters to the problem at hand. I'll edit your original post but you could do so as well if you needed to.

Guessing this.

Okay... while you should be able to parse the XML using DataStage and perhaps even retrieve the pdf document in some fashion, we'd need more details to provide cogent help. How is it stored in the XML? And what specifically do you mean by "read the PDF content" in an ETL context?