DSXchange

You appear to be using "." as the delimiter whereas the web service you are calling is expecting ";".

You need to adjust only your understanding. NUMBER(10) cannot be the same as Integer, because not every 10 digit number can be an Integer.

As far as I can recall, the Hashed File Calculator is a stand-alone exe (that is, it has no dependent DLL files). However, since it is written in Visual Basic, I can not be 100% certain on that.

Another good source is Chapter 2 of Parallel Job Developer's Guide which explains how each data type is stored. Using this knowledge you can calculate row sizes and tune your jobs optimally.

In both your examples you are getting the data BEFORE the ampersand. What data types are involved?
Are the data being truncated in View Data, or in the job itself (that is, what is the output of the job)?
Are there any non-printing characters in the data?

The three possibilities are LDAP, operating system or IIS internal user registry - there's no such thing as WAS security. I'm assuming you now have the third of these. Have you properly set your DataStage Engine Credentials (in the Domain Management menu on the Administration tab of Web Console for ...

In 7.5 you can run the dsdlockd program with -p option. You need to be logged in with local Administrator privilege.

Column names that contain "#" or "$" need special handling. This is completely documented in the Information Center and in the manuals.

Rows/sec is meaningless in this context. The initial burst is misleading, as this is showing you writes into memory cache. The figure at the end is an average of that and of flushing the cache to disk, which will necessarily be quite slower. As Craig mentioned, well-tuned hashed files will perform b...

That would have been useful to know at the outset.

Use the equivalent Oracle commands to quiesce the database. If you don't know the commands, consult your Oracle DBA.

zaino22 wrote:Jobs that were compiling yesterday morning cannot compile.

What has changed?

Try using the -user and -password options for your stopServer and startServer commands, to name your actual WAS administrator.
Or login as root and use the MetadataServer.sh command to stop and start.

This is where it's vital to know the version. There are scripts to clean up defunct licences, but the names of the scripts are different in different versions.

Usually that means that some vital piece of information (maybe export format?) has not been provided.

Turns out it was a "harmless" ad server (not malware). Still don't know how it got onto my laptop - suspect it was one of the hotel "connection" web pages, but can't prove it. Anyway, their software showed up in Add/Remove Programs, so I did. All good since.