DSXchange

Hmm. George last posted in 2007. He may have nodded off by now.

Take a look at the source code for DS.CONNECT.

In that routine ($DSHOME/BP/CONNECT) there is the declaration
equ MAX.DS.DEFS to 99

This is the cause of the issue in using the test utility. I guess you could change it maybe to 200.

My doctor told me to stay away from cigarettes, so I bought a cigarette holder. In general avoid BASIC Transformer because of their overhead, but if there's no other way... (Like avoiding sorting unless it's necessary.) The Variables you found in the stage properties are actually the stage variables...

Does your batch job destroy or preserve the control records such as \\PURGE.SETTINGS ?

Add a unique key, such as the line number from the source file. (The Sequential File stage can generate the line number for you, via its Row Number Column property.)

The user status value is stored in one of the RT_... hashed files in the local DataStage repositories. I have not been able to find anything in the DataStage C API for accessing it. Would a BASIC Transformer be really that bad?

Read the file using a single VarChar column. Use a downstream Transformer stage to split the rows according to record type and to parse the different record types differently on those outputs. This has the added advantage that your read is not delayed by parsing, and that your parsing is occurring i...

There is actually a cost, that of evaluating the function every row. So a comparison against the literal string will be slightly more efficient. Many instances of "slightly" add to a useful amount. For a slightly more complex example, initialize a stage variable to the result of the functi...

1. No.

2. Not safely, except by recycling the Engine.

Welcome aboard.

IBM has some (free?) tools to help with this exercise. Get in touch with your IBM business partner or account rep. They get an "incentive" to steal customers from Oracle, so should be keen to help.

Maybe you're looking in the wrong field. They are numbered from zero.

You can, but I'm surprised you didn't find the session when managing sessions through the Web Console for Information Server. The session ID is the long hex number reported on the "job locked" message in Designer or Director. The locks in XMETA are stored in a table called XMETALOCKINFO - ...

81002 might be as simple as your inactivity timeout triggering.

I've actually moved on from that shop; hopefully one of its denizens will answer your questions. They know who they are, and they do visit DSXchange. Deepak? My current client is still migrating from 8.1 to 8.5 and therefore not yet in a position to implement source code control through ISM, though ...

NLS settings can not be parameterized.