DSXchange

In our company, we will not include the job design to production system, that 's for security, someone can not change the job design in production and compile them. This choice severely hampers your ability to support the production jobs and leads to situations like you have found yourself in. Prom...

I have a flat file (csv) with 40 columns, i want to FTP the flatfile to other place. Here my question is can i ftp flatfile with 40 columns using Datastage FTP Stage. Yes, you can! Even one with 40 columns. but i m unable to ftp the file. Why not? I m not using any transfomer stage in between seque...

I was under the impression from the phrase "load views", that the OP was asking about targeting (i.e. writing to) views in PX jobs.

I think that the problem may, indeed, be a bug. OCONV could be being called by DSD.BCIOpenR (which opens the connection for reading). With the ODBC stage, if a data element is set to Date or Time, then an "implicit" conversion is performed - it's most likely that this uses Oconv (or Iconv, dependin...

Another option would be to establish a VOC record to the hash so that CLEAR.FILE would work for your pathed hash file. Search the forum for the syntax as it's been posted many times here. Yet another option would be to simply leverage your O/S - since pathed hashes are created by the mkdbfile comman...

What makes you think you can use OCONV in your SQL statements? Sure sounds from the error that that is what you are trying to do, and I would guess via custom sql. You'll have to wait until the data gets into your job and then, in a transformer, apply the OCONV (and any other DataStage specific) log...

Actually, not impossible at all. For whatever reason, I see people do stuff like this all the time - and most of the time they are convinced it is working. At least at first. I think it depends on the O/S - some allow it and some try to protect you from yourself. But 'allowing it' and it working any...

It's not even an issue, just The Way It Works.

It's sort -u not sort - u

(no space between the dash and the 'u')

Make sure it runs from the command line before you try it in a job.

In other words, a shell script 'wrapper' that does all this before actually running the job for real. All kinds of checking can go on. As Ray noted, first thing is to use -jobinfo to check the current status of the job - including if it even exists. If the job needs to be reset, another call to dsjo...

Or specifically trap your errors in the Routine and return something easily recognizable. I usually pass back negative numbers as long as normal returns can never be negative and them check for that in a custom trigger. Or as Ray noted, check the size of what you return.

No, not INCORRECT. It doesn't show you the delete statement in the stage any more than it shows you the truncate command if you go with that Update Action. However, it does log it when the job runs so you should see it there. Are you sure the job is running "successfully"? Just because it didn't abo...

FYI - Selecting 'sysdate from dual' does not get you the correct "oracle date format" to use in a DataStage job. What is your target stage - OCI? If yes, set your datatype in the stage to Timestamp and put what you've already got right in there, truncating off the milliseconds first. Assuming you ar...

No, it's not. The exact way would depend on your flavor of UNIX and can be found by reading the 'man' pages for the sort command on your system. If you wanted to sort based on all fields (the entire record) you could just use sort -u and be fine. However, if you only want to sort on certain field(s)...

sanjay wrote:not server jobs.

Then it would be prudent to ask the question in the appropriate forum.