DSXchange

U is not asking the question. Vishal1982 is. The second person personal pronoun in English is spelled "you", not "u", and it its possessive case is spelled "your", not "ur". Please strive for a professional standard of written English on DSXchange. Not only do...

Stop. Step back. Analyze thoroughly what you want to occur, with examples, on day one and on subsequent days. Document the rule under which the cycle resets to day one. From this analysis produce a detailed specification. Get someone else to review your work (peer review). This process ought to make...

Then the OP may as well use a server job and avoid the startup overhead of a parallel job.

None.

The way you do some things, particularly administration, may be different, but almost all functionality is available on both operating systems. (OLEDB is not available on UNIX is one of the few small exceptions.)

Did you Search for your answer? There are different methods, depending on factors such as the likely maximum size of your XML file and the complexity of its structure.

Moderator: please move to parallel forum

Did you bother to Search (this question has been asked and answered before) or to read the relevant chapters (one for each stage type) in the Parallel Job Developer's Guide?

Report the metadata import bug to your support provider, then change the setting within IA to UTF-8 manually.

sweta rai wrote:for field SUPNM. When moving data from source field type STRING(min=0,max=135,charset=windows-1252)

This tells me that either the source table has not been loaded properly or that your metadata are inconsistent.

A very simple counter-example is where there is a slow connection to the source database, or where the source database is comparatively very busy compared to the DataStage server.

... because the first row is only processed on one node.

SQL State is the generic ODBC error mechanism. A search on Google for "S1000 ODBC" will return lots of useful information.

It's a manual process. You can't automate it. The new columns on the Pivot stage input link contains just the actual column names, as literal strings. For example "July", "August" and "September". Perhaps you can call these columns Jul_MonthName, Aug_MonthName and Sep_M...

These lines will be near the end of the DSUBINARY object. The differences are because the date/time compiled (and various other things) are included in the object code itself.

You may need to be careful of data types in parallel jobs. Otherwise Index() is the best tool for the job specified in the original request.

The stored procedure must exist in the database. You can not create stored procedure code in the CLOSE command. You invoke the stored procedure from the CLOSE command (or from a Stored Procedure stage or wherever).