DSXchange

It's all stored in the local project repository.

However some of it is also stored in XMETA.

You should be able to recover the XMETA side using the SyncProject utility within ISA Lite, once you've imported from the export file.

The best reference is the chapter for each stage type in the Parallel Job Developer's Guide. Put them "side by side" mentally. You'll also find the statement that one has been deprecated in favour of the other; take that statement with the proverbial grain of salt. The big difference (for ...

If you restore the system backups of the projects on a system with DataStage installed, you are most of the way there. You will need to adjust the pointers to system tables (using VERIFY.SQL) and that may be enough to allow you to export from those projects using DataStage Designer. Those exports ca...

No, it's been there since at least version 7.5.

devsonali wrote:Any suggestions/inputs from the members ?

Learn patience. Don't push. You waited barely over an hour, at a time when many members are sleeping.

DSXchange is an all-volunteer site whose members post if, when and as they can. "Pushing" is considered offensive.

For each "other" column which value from all the records in the group do you want associated with the grouped value? Maybe you could look at a "fork join" job design. But think, how would you achieve the results in SQL? You can't. For exactly the same reasons you can not achieve ...

You should find ISALite under /opt/IBM/InformationServer (or wherever you installed the product).

Most easily done with a pair of jobs, the file name being passed as a parameter to the second job. Use a Data Set for the staging area between the two jobs.

The issue is probably a difference between the two repositories. Use SyncProject (part of ISA Lite) to reconcile the differences.

Actionable analytics from Big Data in the Cloud?

COMMON declares that variables will be placed in memory accessible to more than one routine, or even to multiple calls to the same routine. EQUATE is a compiler directive to load a variable effectively at compile time. Assignment statements have their effect at run time. You include any header file ...

You can do it, but you need two Lookup stages. A Lookup stage with a range lookup actually compiles to a transform operator.

Or you could change APT_STRING_PADCHAR to 0x20.

You could also use the "UniVerse" numbered public semaphores for this.

I have already given my (complete) answer. Get yourself a premium membership so that you can read it. Premium membership is inexpensive (less than Rs12 per day) and helps to defray the hosting and bandwidth costs of DSXchange.