DSXchange

Welcome aboard. :D Curiously, you're not the first to have encountered this, which is usually symptomatic of an overloaded system. At the top of the screen is a menu, on which there is a Search option. Use this to see what others have found when investigating this particular message. Search can save...

Take a look at the hashed file's file variable (HashedFile.fvar). It's declared to be in COMMON, and is accessible at all recursion levels. Any variable in COMMON contains the value that was most recently assigned to it. Therefore, if you assign a value at the innermost level, it will be available a...

Why don't you just use the sequence when inserting the rows with user-defined SQL? For example

Depending on exactly what you want to do, you also have row filtering (start row number and end row number) on the stage properties page, the ability automatically to generate FILLER columns on the column selection page the ability to specify pre-sorting of data during read (useful in some downstrea...

Assuming you have version 7.5 or later: Field(RoutineActivity.$ReturnValue, ";", 1, 1) and Field(RoutineActivity.$ReturnValue, ";", 2, 1) However, your code isn't doing what you want it to do. The final assignment statement always prevents Ans from being "File not...

DataStage/390 is designed to stream data from a sequential file. As you note, the generated COBOL includes an INITIALIZE. I'm assuming here that you're using a Fixed Width Flat File stage or a Delimited Flat File stage. While there's nothing you can do in DataStage, there's nothing to stop you from ...

Col1 is Arg at the innermost call. Lodge it in a COMMON or system variable such as @USER.RETURN.CODE.

Yes, but there are other options. For example, a Lookup stage can perform a "sparse" lookup directly to a DB2 or Oracle table. Almost no impact on memory whatsoever. Ask yourself whether a lookup to a Lookup File Set loads a virtual Data Set first? If not, again little impact on memory. That's anoth...

That's true as far as it goes, but remember that the libraries produced by compiling the Transformer stage have to be dynamically linked at run time. So there is also the call overhead. I prefer to use stage types that use operators directly, because the Orchestrate engine is geared to the explicit ...

No. Only if those are the tasks you need to perform. But they're as good a starting point as any, provided you don't overlook the technicalities of getting the passive stages to work right. Otherwise you won't be able to do the "E" and "L" parts of "ETL"! And you really will need one or both of Modi...

Welcome aboard. :D You did not state whether you are coming from a server edition background or are entirely new to DataStage EE. I doubt that you will get much consensus. DataStage EE has many more stage types than server, because it follows a philosophy of one stage, one task (unlike the Transform...

My guess is that there was an inadvertent & in the SQL statement.

That's not quite true. The File Set control file gives the location of the data files, and these are quite readable by humans and outside processes. The point is, however, that the File Set is partitioned, so that some of the data (rows) are on each processing node. That may inconvenience outside ap...

Here's a sketch of the algorithm. Open the hashed file into a variable in COMMON if it's not already open. You will, as noted above, need a DEFFUN declaration. FUNCTION ReadRec(Arg) DEFFUN ReadRec(X) Calling "DSU.ReadRec" COMMON /ReadRec/Initialized, HashedFile.fvar If Not&...

For one week only, all is revealed!