DSXchange

If thats the case then use EREPLACE() or convert() to replace all alphabets for so called numeric fields and replace all numbers for strings that dont require numbers.

Is this the only stage thats causing you problem or other stages as well, drop another stage on the same job and see if you can open the properties of any other stage.

Reset the job and see if any message "From previous run.." pops up. See what it says. Also search on key words "Access violation".

Uninstall the client and then re-install it. Dont just re-install on your existing client. See if that helps.

http://www.anotheritco.com/
Go through his white papers.

What is TRGT_FIELD defined as? Is it set as in integer? Change the metadata to match the incoming data from your db2 table.

Yes. If your changing a nullable column to non-nullable, use modify operator.

Look at the flow of columns from your first stage(s) to your last stage. All columns that are defined as null should remain the same and vice versa. Check your meta data again.

chulett wrote:ps. He's no Brian.

pravin1581 wrote: The C program will be doing everything . The C program will be doing everything including the generation of output.

That means its a stand alone program. Any stand alone program can be fired off. Any on your datastage box, using one of the many options listed by Craig.

kcbland wrote: :D It's good to see others remembering!

Always remeber your posts, almost word for word

Start coming up with real time problems and start solving them, once you have read about different stages. chucksmith has a list of job designs on his website (found on his footer), check for it.

Just a shot in the dark, try multiplying with 60.00
Also just for debugging purposes, try increasing the target size and see if the warning vanishes. Also what is your target stage?

Check the day part with if then else and if its not '01' then convert to ordinal date using JulianDateFrom() function (I think thats what its called) to convert it and do as Craig advised.

I don't know what was fixed in 7.5, but I'm on 7.5.2 and View Data using $PROJDEF still does not get the value from the project. I should not have said fixed. Its more like an enhancement. Check gateley's reply in this post for confirmation. View data does work in 7.5 and higher versions with $PROJ...