DSXchange

dpending upon which session type he has open and how the locks are released the developer might just see a timout message or get no message at all, at least until they try some screen action when a whole cascade of spurious messages will show up.

If you plan on taking this test, why don't you also plan on trying the search functionality and "PX certification" to get a number of threads and a very useful set of links to Vincent McBurney's information on this certification examination.

If you are in PX then: See DataStage Parallel Job Developer's Guide Appendix B-1, the function is called DaysSinceFromDate If you are in Server then: The internal date format in server is a number. So if you ICONV() your 2 dates and take the difference between these two numbers you will have your re...

The answers you get depend upon whether you are working in Server or in Parallel jobs. Even better answer will come when you explain what type of source data you have (sequential files don't have keys, and sometimes DB level filtering is more efficient than doing it in DataStage)

Hopefully you are not issuing "kill" commands to stop the job. After you stop the job and do a "reset" you might have an entry in the log file labelled "from previous run", if so what does that log entry say? Have you turned on any PX logging (i.e. APT_DUMP_SCORE)? Have you any jobs at your site tha...

kumar_s wrote:Shouldnt be the CLEAR.FILE for RT_LOG** working?

This is usually not a good idea, since by doing so you remove the purge settings and that log file will no longer have any autopurge (and will then most likely grow to huge size again).

OK, I was afraid of that. In this case DS (both server and PX) have no way of knowing where to split the columns. The file is not machine-readable (unless you can guarantee that the string of `","` does not show up in the text and all columns are double-quote delimited. Have your program that genera...

In my case I just used a sequential file stage to read the file (DS Server interprets the ",," nullable input correctly) and then outputted a fixed width sequential that PX Server then reads. With an appropriate null pad character and fixed lengths the PX read is very easy to do. I'm not sure that I...

When you call DSAttachJob() you need to specify the instance you want, i.e. doing DSAttachJob("MyJob.ThisInstance",DSJ.ERRNONE) will open up that instance.

PX has problems when the source csv file is of the format 1,2,"He,llo","",,"World" The 3rd column is interpreted correctly, but if the 5th is a string column then it isn't imported as a "null" but causes and error. If this is your problem then I understand your frustrat...

And if you do a command line "db2 connect..." "db2 set schema..." and then "db2 {yoursqlquery}" does it work and return results?

Meena, he could try but would get a PX compiler error

I used JobHandle = DSJ.ME and you changed that, so that part won't work. After you get a job name you need to issue a call to DSAttachJob() to open up a new handle and then use that handle for the next call to DSGetJobInfo() . Any more code would only be visible to you if you were a premium member, ...

300 jobs in one project is not too many, especially if you distribute them across different categories.

The pros are that one project is less overhead and easier to maintain, backup and monitor.

I can't think of another way to do it, unless you pass in the date as a parameter from a sequence and generate it there.