DSXchange

hi, I'm using rogenerator and db2_udb_api stage.Rowgenerator generates dummy colmn and api stage for updation.Query used is UPDATE schema.ITEM_PUBL_EVNT SET STAT_C='2' WHERE STAT_C='U'; But the job is getting aborted.the log is DB2_UDB_API_ITEM_PUBL_EVNT: When processing argument -inlinkpropsWhen p...

What is the next error you got exactly- after you ran the job with a managable size of data.

Check the format for Date and Timestamp in Access.

The Sequencers will operate as they do in 7.5.1, as long as you donot make the change to the code of the Sequencers. Adding new logic like looping activity may need re-design, depending how it is used.

No need to say sorry. I understand that your topic is related. But depending upon the OS the answers might be different and hence creating a confusion.
This also helps later on when people use the search utility. Thats why, no biggie

You really need to start a new post. Post hijacking is frowned upon. By starting your own thread, you will give us info about your os type, server edition, which may have a different solution.
Try looking at the post i referenced in my earlier post.

You have a carrige return (^M) in your data in that particular column. This topic has been covered a lot here. Use the search engine.
Click herefor a start.

So the DSJobReport.dsx doesnt work on job sequences? Or you are not able to get information about the jobs executed in the job sequences? I dont use DSJobReport.dsx so i can say for sure but i bet it works for sequence jobs. To get the individual reports of jobs inside a sequence you need to go to t...

bhaskarjha wrote:here if i wann that all jobs should run in any condition

UNCONDITIONAL will run the next job no matter what happens, the job finishes, crashes and burns , it doesnt matter.

you can search for date functions in px. Check out this post. It also has where exactly you can find date functions in a px manual. Thanks to ArndW.

Is your source a database, and if it is , what database is it?
You can use the database functions to get this done at the database level as PX doesnt have very many data manipulation functions like server does.

Then you need to give the trigger expression fo the first job as UNCONDITIONAL.

Try to reference this site. Search for the SQL0443N on the page.
It seems like the user defined method or routine at the database level is creating a problem. Go through the explanation on that site.
The problem is database related and not DS specific.
Good Luck.

I want to know the length number of the source and target. Obviously your target length is smaller than your source. You need to either handle that or ask your dba to increase the length of that particular column.

What routine are you referring to. If its mine then its all there in the description.