DSXchange

I'm also bothered that the telnet to the server doesn't work, that listener should be working. How much effort would a complete delete and re-install be?

karry450 - The format for that would be "D4/DMY[2,2,4]"

You won't know that you are processing the last row until you hit the end-of-file, when it is too late. You can pass the number of rows into the job as a parameter and compare against that number in the transform stage.

Karry450 - it is in the documentation for the OCONV function. Date, 4 digits for the year with a "/" as separator and European format.

I will assume that "cud" meand "could" - OBJ files are not a known ending of any files used in DataStage.

No, you need to concatentate the system variables @DATE and @TIME, i.e.

veera24 - The SQL that ag_ram gave you is (a) incorrect and (b) uses undocumented tables in the product as well as the TCL command line.
It is simpler and better to get the job number by running the job, then looking at your first director log file entry and getting the name from there.

This is not a Version 8 issue, it is a Server vs. Parallel issue. In Parallel jobs, the rejects are initiated in the stage that causes them - so you need to enable rejects in the DB2 stage and make a reject link from there.

No & No. "2008-03-19" is not a valid timestamp, and "2008-03-19 04:22:59" is not a valid date.

Adding to Craig's post to make it bulletproof:

if that string could show up elsewhere in the file

ag_ram - you have managed to post 5 paragraphs without actually adding anything to the thread or even coming close to touching upon the thread topic. I do find it amusing to see that you recommend that I delve into the internals of DataStage and even funnier to see how you lecture me on the use of u...

No more food for thought from me. I asked for the SQL twice without success so I am giving up.

Just to confirm that we are talking about the same thing: both your main data stream input to the lookup stage as well as your reference link to the lookup fileset both have a column called "SOURCE_SYSTEM_COUNTRY"; and this column was also defined with the same name when you created your lookup file...

The reason that you cannot see all of Ray's post is that he is one of the very few posters where you need a premium membership to view all of the contents. You can see the information about the advantages of becoming a member at Member Benefits.

The simplest way would be to check for the footer from a Job Sequence and then decide whether or not to call up the processing job.