DSXchange

Hello roopaknair, The message probably reads "Variable previously undefined..."; it means that the first use of the variable was to see it's value instead of assigning one to it. You should check your TRANSformer stages in the job and look at stage variables or usage of parameters to perhaps spot an...

Hello Hemant,

I am not sure what you are looking for, in the post http://www.dsxchange.com/viewtopic.php? ... =dsjob+log it was mentioned that you can use the command line utility dsjob to get the information you are looking for.

Do none of the 3 dsjob options give you what you are looking for?

Nanda, the basic issue you are getting is not difficult to solve, your input date is of a variant of Julian. The solution you are looking for depends upon your job type, the forum & the title refer to a parallel job but your note talks about BASIC and transforms. If the day "71112" breaks down i...

Kumar, yes, the PX total temporary file size is [usually] going to be greater than for a server job. That is the nature of PX - and a reason why each node has it's own temporary file path. Not every job will actually 'land' data in temporary files. If you change your PX job partitioning you are goin...

akrzy, DataStage (both flavors) will use memory and temporary files. Sometimes memory buffers also get temporarily written to disk. It is wise to reserve quite a bit of temporary space for DataStage implementations. DataStage PX uses more temporary files than does Server, but allows you as a designe...

Anka,

no, it is not possible. If you use SEARCH and Informatica you will see that there is an active thread which discusses this.

Heck, I did the search for you: http://www.dsxchange.com/viewtopic.php? ... nformatica

The partitioning algorithm in the sense we are talking about here is how the single records are distributed across the PX node processes. So if you have 4 nodes and choose round-robin, each process will get a row in order; if you choose hash on a field then a number if generated from that field usin...

Kumar_s,

Your SQL code is getting it wrong, it is converting all Non-Read-Only to Read-Only.

Try

Roy, yes I did play with that setting. Oddly, when you removed the ticked "use project default" checkbox the displayed default value causes a runtime error - it somehow doesn't like the embedded space in the default "%yyyy-%mm-%dd %hh:%nn:%ss"! I was too busy trying to get the job working to bother ...

If you can sort your data on the column(s) that you are going to use for the aggregator these warnings will go away. In your case the store number. In the aggregator each row has to be kept in memory (in this case the hash table) until the last row comes in before any aggregations can be done. Altho...

King999,

sorry I wasn't more precise - there are no software tools, just people-power. I was referring to consultants that often post in here in my previous post.

There are quite a few tools who can help in converting from Informatica to DataStage, but they usually need to be paid by the day and need care & feeding as well. Some of them lurk in here, too. Unfortunately there is little in the way of commonality between the two products; at least nothing th...

If you write this column as a non-text type (numeric, integer, decimal) then there will be no quotes around the column's value.

Hello 120267, to expand on what Kim has already stated, the communication between a sequence (or controlling job) and a child is via job parameters. These parameters cannot be changed by the child, so the exchange of data only works in one direction - from parent to child. Your controlling process m...

Is this error coming after the job has processed many rows - if more space on the heap can't be allocated I would look at your available disk space in the scratch directories.