DSXchange

That said, if your maintenance agreement (and payments) are up to date, you are ENTITLED to a free upgrade. Be aware, though, that the hardware requirements are significantly higher in version 8 than in version 7 - QualityStage is no longer a separate product but one of a suite of products called In...

That the JobMonApp is running tells you nothing about the Node Agent.

Try netstat -a | grep 31531

Umm... I think your terminology lacks a little something. Do you mean "check for non-numeric characters" or "check for alphabetic characters" or some such? The Num() function will check whether it's purely numeric, or you could use IsValid() to check whether it's an integer. Anot...

It WILL run on multiple nodes. The main reason for its relative slowness is the need to convert to and from the typeless DataStage BASIC environment to the strongly-typed C++ environment of parallel jobs for every row processed.

You can find it here.

Because text files don't have data types (other than "text") VarChar(255) is used as a default. DataStage has a really high limit on length of a VarChar (64K ?); however some databases limit it (for example to 1024) making you use Long VarChar for anything larger.

No, that's just a generic error. Were there any other warnings in the log?

No. DataStage has some Java components, has some ActiveX components, has some VB components, has some C++ components, and that's just in the client! The server engine is pretty much all written in C and DataStage BASIC. The parallel engine is primarily written in C++.

You need YEAR, JAN_NAME, FEB_NAME, MAR_NAME, JANUARY, FEBRUARY, MARCH

Populate JAN_NAME, FEB_NAME and MAR_NAME with constants and pivot them.

You should be OK with that combination.

Try this trick if you're permitted to do so. Set up a Lotus Notes user with an empty password, then use that for access.

Where did you "check" the Web Console? DataStage credentials are in the Domain Management menu. They won't be enabled if you're not: (a) an Information Server Administrator (b) a DataStage and QualityStage Administrator (c) a DataStage and QualityStage User They may also not be enabled if ...

So why did you post the question in the Information Analyzer forum?

When the job is compiled, the generated OSH script should be visible in the Job Properties workspace. It also gets written into the job log. However this is never the script that gets executed. When the job is run, a new script, called the "score", is written. The score takes into account ...

Look in your job log. An early event in a job run (typically the second entry) lists the environment variable values that were used.

Error code 11 is an access violation. Parallel jobs load the entire reference data set into memory (if it's a Lookup stage reference input). If you don't have enough memory - if the executing user can not allocate enough memory - it will throw an access violation.