DSXchange

Assuming you're using the Import utility within Manager, there are three steps. Step 1 is to identify the file. Step 2 is to specify its format. Step 3 is to name the columns, add descriptions, data elements and correct the "best guess" data types that the Import utility has applied. It's in Step 2 ...

Not working at any Red Brick site at the moment. If it's urgent, you might be able to get some from IBM (the new owners of Red Brick, but with no idea what a star is in their stable - after all, it's not DB2!) There are many variables that would have to be standardised in such a benchmark, so that a...

The problem was the telco has 10 different switch input formats You haven't encountered the problem when they change the CDR format without telling anyone, then? It will happen! DataStage BASIC can treat a directory as if it were a table, the operating system file names being treated as "keys". Ope...

Hashed files do NOT have a hard-coded limit of 999MB, and never have. This limit occurs only in the GUI, where "someone" neglected to allow more than three digits in the SpinButton control. By default, hashed files have a limit of 2GB, caused by internal pointers being four bytes (32 bits). By expli...

This behaviour is correct, because in C the \0 character represents "end of string". So what's being returned is a zero-length string ("") rather than NULL. The very lowest levels of the engine are written in C. Where are the data coming from? You ought not to be able to get a character string begin...

Can you check it on a machine that's not using Client Switcher? That is, one on which DataStage 5.x has never been installed.
Can you also report, from its Properties, the exact version of DSAdmin.exe on the system?

Here's three more. Name matches "'&'0X'&'" Index(VocRecord<2>, System(32), 1) > 0 And Left(VocRecord,1) = "F" Index(VocRecord<2>, UV.FSEP, 1) = 0 And Left(VocRecord,1) = "F" Don't forget to read for update (READU), to prevent lost updates. UV.FSEP is the pathname delimiter character, which y...

You're trying to us the DataStage function DSTransformError (congratulations - it's the right one to use).

Unfortunately, you added an extra, and incorrect, er to its name (DSTransformerError) so DataStage can't find it.

All the message relate to the different places it searches.

You can totally destroy DataStage with such a routine, by overwriting existing VOC items with pointers to nowhere. When I wrote one of these (as part of a job that returns the row count from a hashed file), there was a whole lot of "idiot proofing" in the code!

Try using an explicit name for the ODBC data source, rather than SQLServer (which may be a reserved word).

The best way is to configure it for auto-start in the dsdlockd.config file in the DataStage engine directory on the server. Log in as superuser, cd to the DataStage engine directory, invoke UniVerse, and bring up DEADLOCK.MENU; there is an option on this menu for starting the dsdlockd process. Check...

I seriously doubt that CExporterAPI is the whole story; in particular, even if it is an appropriate source of objects, what are these objects and what are the properties and methods associated with them? And what is the format of the generated export? You may (or may not) find it useful to switch on...

I found it extremely helpful to have two BAT files, one to invoke the client switcher to set up for 5.2, the other to set up for 7.0. These were placed in the Windows folder (or any folder in PATH) and executed from Start > Run.

In Windows environment variables can be set in Control Panel > System > Environment.
They can also be set using DataStage Administrator, in the "user defined environment variables" section (on both platforms).

Isn't that what MetaRecon and Quality Manager were about (and INTEGRITY to a lesser extent)? These all have new names since being acquired and integrated by Ascential: ProfileStage, AuditStage and QualityStage.