DSXchange

Nah, Exception Manager for Information Analyzer installed with Foundation Tools (8.1.2) - one of the fix packs if I recall correctly.

Look for each code ending with "E", for example "SECJ0384E", "JSAS1501E", "SECJ0369E", "SECJ0270E" and "WSVR0009E". These tell you where the problem is occurring, in this case (apparently) in the security service, which means that WebSphere...

When you do your range lookup, zero or more rows will be returned. Count them (for example in an Aggregator stage, if you don't use COUNT in the retrieval SQL).

Kunal - Can you pls clarify what you said? I did not understand u. Please strive for a professional standard of written English on DSXchange. English is difficult enough for people whose first language is something else. SMS-style abbreviations are completely unnecessary - DSXchange is not a mobile...

Copy is always within the one server. To move the structures to another server the pathnames of every segment file, and the name of the descriptor file (which is part of the segment file name), would need to be identical to those used on the source server.

Change the space to something else upstream of the Link Collector and change it back downstream?

Exploded. DTM is a multi-valued field. The equivalent SQL query is

0x0 as a default stems from the fact that this is the C language string termination character. C code will read the string only as far as the first \0 character. It's not anything to do with DB2.

Does the Monitor report a specific instance?

Not easy. Much easier to use DataStage jobs to dump the Data Set contents into a file on one server and load the Data Set from this file on the other server.

Set the environment variable that reports the startup and determine, from the logged entries, where the problem starting up is happening. Also report the rsh commands being executed (this is another environment variable in the Reporting group).

This problem is being detected by the ODBC driver - it does not send that row through to SQL Server. Use a reject link from your ODBC stage to capture that row.

The reference data set for a Lookup stage must be able to reside in physical memory (other than for a sparse lookup). Any other stage that uses memory, such as Sort, Aggregator, Join stage types, will use the amount of memory allocated. Only if they need more memory than that will they spill to scra...

Open the Web Console for Information Server logging in as a Suite Administrator. On the Domain Management menu choose Licensing and you will be presented with a list of the items you have licensed (unless you have used the default licensing).

The analysis looks good. Simply use the number of rows returned from a lookup against the business days table. If you can use a sparse lookup, you might even return COUNT(*) from the table.