DSXchange

File types are not actually defined in the VOC file. The VOC file records the name and locations of data and dictionary portions; the file type is an inherent quality of a file, accessible when the file is opened.

The only reliable tool is the brain, imho.

The export is done without any problem, But the dsx doesnt contain the job executables. I think we'll just have to agree that such is the current state of the technology. You might like to lodge an enhancement request. It's not a big problem - just means that you will need to re-compile jobs after ...

These are in a frame called "compilation options" which is a less-than-subtle hint that you need to re-compile the job sequence after changing these settings.

If you need to be able to report specific differences, the best approach is to use 74 stage variables. Plus a few more stage variables to assemble the diagnostic message(s).

"Heap" always refers to memory, but it's virtual memory so can be exhausted by running out of spill space (scratch disk resource) or of swap space, depending on what's actually occurring. So I think you are on the right track suspecting memory, but probably need to do some more detective work. There...

Override the default for a particular job by choosing Clear Log from the Job menu in Director and selecting Auto-Purge. This enables the frame at the bottom of the window so that you can override the defaults.

Welcome aboard. :D

I suspect that this question has nothing to do with DataStage TX (the former Mercator product). Correct me if I'm wrong. Otherwise can you please post this kind of question on the server forum?

Welcome aboard! :D (Kapiti as in Kapiti coast?) DSR_LICENSE is a "helper subroutine" that retrieves license information for a connected client. GETPROTECT is one of the tasks that it can be given. DSD.UVOpen is a lower-level function that opens a hashed file - in this case probably the hashed file D...

Right now I am in an airport lounge and cannot check, but I believe you can read about this in the Orchestrate Operators manual.

Only if the data are stored in fixed-width format. In that case, you must import or create a table definition in which those widths are recorded. Handling the missing c5 and c6 in the first row will differ depending on whether the job is a server job or a parallel job. The good news is that it can b...

Are you doing this function in a Modify stage or in a Transformer stage?

The leading space is for the sign.

The job log is a table, not a file, and the row has a column that identifies the instance number, so to display just the entries for one instance is a simple WHERE clause. You will find, in Director, separate entries in Status view for each instance. Select one of those and switch to log view from t...

Welcome aboard! :D

You stand a better chance of an answer if you post in the correct forum. This one is for DataStage TX, which is not really about sequences.

The answer to your question is Yes.

The RT_CONFIGnnn table contains the runtime version of the job design. I suggest you solve that first, as per the other thread. The error that is the subject of this thread may then magically vanish.