DSXchange

It's the only way to fix this problem. Provided uvregen doesn't report a figure too close to the maximum shared memory segment size for your system, you could try increasing T30FILE to, say, 1500 or 2000. Each additional slot requires, as far as I can recall, just over 100 bytes of memory. The only ...

It would be a good idea, but even better if accompanied by (automatic redirection to?) separate forums for server, parallel and mainframe jobs. Any possibility of filtering the posts already on the DataStage forum into these three categories, based on the header information? (Yes, I know some of it'...

In Designer, when you choose File > New, do you have the choice of creating a "parallel job"? If not, you do not have the Parallel Extender (now known as Enterprise Edition) installed/licensed. If you do have the Parallel Extender (Enterprise Edition) installed and licensed, you still need to instal...

Welcome aboard! :D

As far as I know there is nothing in DataStage to support clustering in a Windows environment.

DataStage does not have its own users and passwords. You need someone with suitable authority to create a user ID - or reset your user password. DataStage security hinges on operating system groups, so you will need to be a member of an appropriate group, as was configured in the Administrator. You ...

Arun, "File descriptor table is full" refers to the in-memory table of concurrently open dynamic hashed files. The size of this tables is set by the T30FILE configuration parameter in the uvconfig file. Once you have increased this, you need to run the uvregen utility, then stop and re-start DataSta...

The whole point of DataStage is to have a graphical design metaphor. You draw a picture of what you expect to happen. There is no facility for taking existing COBOL and magically transforming it into DataStage's graphical format. Did you read the Chapter on the External Routine stage? It tells you t...

The quick, but not optimal solution, is to loop backwards until the required day is found. FUNCTION PreviousWeekdayFromDate(TheDate, WeekDay) aTheDate = TheDate aWeekDay = Upcase(WeekDay) Loop aTheDate -= 1 While Oconv(aTheDate, "DWA":@VM:"MCU") <> aWeekDa...

With or without a primary key, a query on a reference input must have a WHERE clause. For example WHERE postalcd_wid = ? However, a reference input is expected by DataStage to have at least one column marked as the key column (note, too, that this does not necessarily mean "primary key", but usually...

The following assumes the argument is an internal format date. FUNCTION PreviousWeekdayFromDate(TheDate) RoutineName = "PreviousWeekdayFromDate" * Oconv with "DWA" as the second argument returns the full weekday name, * "DWB" the abbreviated weekday name, * &quo...

Some time back I published (here, I think) a routine for dumping a table definition from the Repository. See if you can find it. Otherwise I'm sure I can dig it out. However, you'd have to have the table definition in the Repository; the routine does not read it from a stage (actually link) definiti...

I really don't know UniData well enough to be cogent on this. In UniVerse it should be OK. Try the same command at the ECL prompt (assuming you can get at it) and see the rows that are generated using BY.EXP.DSND to determine whether that's what you'd expect DataStage to be receiving.

There is no import capability. You can re-design the logic using DataStage, which will generate COBOL from scratch. If your existing COBOL functionality can be packaged as a callable routine, then DataStage has the capacity, through External Routine stages, to invoke these. Both static and dynamic i...

If you WANT multi-row lookup capability, use either ODBC or UV stage. How any other stage type works depends on what the database server delivers, but typically it's the first match found that DataStage uses. A hashed file, necessarily, has UNIQUE primary key values. If you want a secondary key look...

If that doesn't work, try

or possibly