DSXchange

Is the Char(1) field really nullable in the target table? Are you trying to specify an out of band null (in which case you should be using MakeNull() rather than SetNull())? Can you try NullToValue(field," ") to replace null with a space character, to see whether it's the null handling or something ...

Try an External Routine stage or maybe an External Target stage (which can also invoke a routine). Or just get the DBA to create the table for you.

Based, much more importantly, on the volume of data you propose to load into the reference Data Sets, and whether you propose to use virtual Data Set or Lookup File Set for your reference source. The optimal size is one with the capacity to store that total volume. You can not succeed without all th...

If you don't have a COBOL FD from where did you get the metadata (the "table definition") so that you can be certain of the record structure?

One possible reason for this is that the actual data type is NChar or NVarChar, so the ODBC driver is allocating two bytes per character.

Unfortunately, it's a shortcoming (or feature?) of the ODBC driver itself.

You will need to adjust the imported metadata manually.

Go to the Table Definitions branch of your Repository view (in Manager or Designer client). Find the table definition into which you performed the import (this was under your control, and reported to you as part of the import process). In Manager perform a Usage Analysis to make sure that this table...

Is this needed on a per-row basis or just once? If just once, I'd prefer an Execute Command activity in a job sequence invoking the command line interface for running the COBOL program.

By my understanding the ...INTERM... environment variables are for intermediate values, for example results within expressions that are not the final result. I believe that in the case that prompted this post we are looking at a final result, and that therefore the ...INTERM... environment variables...

View Data does not work with $PROJDEF as the default value; you must replace it with an actual password when prompted. Just for View Data; it works fine when processing data.

Reporting row count and/or interval may be specified by environment variables for parallel jobs.

In stage seq1 make sure that (a) the field in question is declared as nullable and (b) that you have specified either a null field value or a null field length property for it. It's the lack of one of these properties about which the error message is complaining.

I do not use RCP, as it interferes with proper metadata management. Someone else will have to confirm this for you. It seems to accord with the description of RCP in the manual.

Yes.

Don't forget that you will need to OpenSeq the file, and CloseSeq when done.

Formal procedures at that site may prevent you from creating temporary tables; you may need to request the DBA to create a table for your use. And with that, the request, justification, walkthrough, budget, and so on. I don't believe you can issue a CREATE TABLE statement from a Relational stage, bu...

Probably the easiest is to check (ps -ef | grep qsrtmngr | grep -v grep) whether qsrtmngr process is running.